The pre-set (default) value for the itemcallnumber syspref is “082ab”, and the relevant example text is “Examples: Dewey: 082ab or 092ab; LOC: 050ab or 090ab; from the item record: 852hi”, even in UNIMARC installations. While this may be correct for MARC21/USMARC installations, I understand that the correct entry for a UNIMARC installation would be “676a” for Dewey, or something similar. Both the default value and the example text could be amended to reflect this in UNIMARC installations. As it regards the example text, I wonder however if MARC flavor selection during set-up can go beyond framework selection and default values; The text may have to be expanded to cover more flavours or warn the user that the example only stands for USMARC/MARC21.
The pref description currently reads: Map the MARC subfield to an item's callnumber. [ .... ] (This can contain multiple subfields to look in; for instance 082ab would look in 082 subfields a and b.) Examples (for MARC21 records): Dewey: 082ab or 092ab; LOC: 050ab or 090ab; from the item record: 852hi I think the easiest solution for now would be to add a UNIMARC example in the text and remove the default setting for new installations. Presetting it with a matching value depending on the MARC selection would not be so easy. For every language installer, a syspref.sql file can be added later to set individual values (check it-IT or de-DE for examples) that are good for the given language.
Created attachment 112542 [details] [review] Bug 11460: Remove MARC21 default mapping from itemcallnumber system preference The mapping in the itemcallnumber system preference is only valid for MARC21 libraries using DDC classification, but not for libraries using UNIMARC or other classification. This patch suggests to remove the default mapping and start new installations with an empty value. To test: - On an emtpy database - Apply patch - Run the web installer, selecting either MARC21 or UNIMARC - Verify that the itemcallnumber system preference is empty - Verify the description now also include examples for UNIMARC https://bugs.koha-community.org/show_bug.cgi?id=26723
We get asked often to deactivate the itemcallnumber preference as most libraries in Germany don't use DDC, but the records from the union catalogs contain all kinds of classifications including DDC - so they end up as suggestions in the items.
Created attachment 112762 [details] [review] Bug 11460: Remove MARC21 default mapping from itemcallnumber system preference The mapping in the itemcallnumber system preference is only valid for MARC21 libraries using DDC classification, but not for libraries using UNIMARC or other classification. This patch suggests to remove the default mapping and start new installations with an empty value. To test: - On an emtpy database - Apply patch - Run the web installer, selecting either MARC21 or UNIMARC - Verify that the itemcallnumber system preference is empty - Verify the description now also include examples for UNIMARC https://bugs.koha-community.org/show_bug.cgi?id=26723 Signed-off-by: David Nind <david@davidnind.com>
Created attachment 112896 [details] [review] Bug 11460: Remove MARC21 default mapping from itemcallnumber system preference The mapping in the itemcallnumber system preference is only valid for MARC21 libraries using DDC classification, but not for libraries using UNIMARC or other classification. This patch suggests to remove the default mapping and start new installations with an empty value. To test: - On an emtpy database - Apply patch - Run the web installer, selecting either MARC21 or UNIMARC - Verify that the itemcallnumber system preference is empty - Verify the description now also include examples for UNIMARC Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Change makes sense, passing QA
Pushed to master for 20.11, thanks to everybody involved!
backported to 20.05.x for 20.05.06
enhancement, not backported to 19.11.x