that for systems with a lot of records (more than 100,000) this will be
a significant performance hit. Also note that if you don't have your
syspref for sortbynonfiling chars set the code will not execute.
* for builded authorities / subject, the subject is correctly rebuilded (for example, if you have a subject history -- europe -- world war II -- France, it is correctly rebuilded). This will be interesting only for libraries with complex MARC authorities/thesaurus.
* the link to find related subject is correctly written (using the $9 subfield)
Should change nothing if the subject is not builded through authority ($9)
Some cleaning :
- removing dirty hack getMARCurl in SearchMarc.pm & replacing it by some Perl in Search.pm : if repeated, urls are stored in biblioitems.url, separated by a |. Now, the urls are splitted in an array. WARNING : the template has been modified & NPL MUST modify their templates as well, should be really trivial (open http://bureau.paulpoulain.com:9010/cgi-bin/koha/opac-detail.pl?bib=1 to see the result)
- using getMARCsubjcts and getMARCnotes in css templates as well. WARNING (specially for NPL) : the MARC notes & subjects were outside from BIBLIO_RESULTS array. As notes & subjects were in this <!-- TMPL_LOOP --> i had to add them IN the loop. I think it's better, so I commented (line 73 and 74 of opac-detail) 2 lines that are useless for me but useful for you. My opinion is that it would be better to modify your template to put notes & subjects in the <TMPL_LOOP> (should be trivial) than uncommenting those lines (= create duplicate code)
However, my real opinion is that we have no good reason to use <!-- TMPL_LOOP name="BIBLIO_RESULTS" --> as we always have only 1 biblio here. But that's something we should fix in HEAD, not in 2.2
* removing "not reservable" for not for loan items (the info is in the previous column)
* setting "request" button to css=button as all other buttons !
- on order (= item has been ordered, but not yet arrived at the library)
- not for loan : if the "notforloan" field is mapped to an authorised value list, the right value is shown. Thus, an item can be "lost" or "being repaired", or whatever you put in the authorised values list. (reminder : the "notforloan" field, when 0 means 'ok, book can be issued', and all other values means 'nok, book can't be issued' (whatever the reason, that can be in the authorised value table)
* partial support of the "linkage" MARC feature : if you enter a "link" on a MARC subfield, the magnifying glass won't search on the field, but on the linked field. I agree it's a partial support. Will be improved, but I need to investigate MARC21 & UNIMARC diffs on this topic.
In 2.4, a new DB structure will highly speed things and this limit will be removed.
FindDuplicate is activated again, the perf problems were due to this problem.
* adding "suggestion", that popup a windows. The popup windows shows, for each word entered in the search form, the 10 words that sounds like the word entered, and that are used most often.
* fixes some minor bugs
Still to do :
* good support of ' and ,
* search on non marc fields : the marc field is found by a sub in Biblio.pm
* ordering a search
This commit shows the sql in log. Pls test it's correctly indexed (using : explain <sql_in_log>)
kados
thd
tipaul
hdl
joshferraro
shedges