https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38336 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #186392|0 |1 is obsolete| | --- Comment #32 from David Nind <david@davidnind.com> --- Created attachment 188438 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=188438&action=edit Bug 38336: Fix confusion between 099 and 942 UNIMARC fields (updated) This patch fixes 099 and 942 fields (and incidentally 200$b) in the default and the FA UNIMARC frameworks and provides the changes that follow logically : - Zebra and Elasticsearch indexing - removal of the unused TYPEDOC authorized values category - UNIMARC facets in Koha.pm These changes are minimal and are intended to correct only the most serious problems. Subsequent work may bring improvements. Detail of changes : - The 099 field is renamed "ADDED ENTRY ELEMENTS (KOHA)" like 942 in MARC21, and should be used in the same way. It is mandatory, because the 099$t (item type) is mandatory - The 942 field is renamed "OTHER ADDED ENTRY ELEMENTS (KOHA)". It is not mandatory, and may removed by subsequent Bugzilla bugs. - Subfields $c and $s are removed from 942 because they are already defined in 099 - The 200$b field is no more indexed (it is now obsolete in cataloguing standards, and its MARC21 counterpart is not indexed). - Like in MARC21, ccode is now defined only at item level and itemtype/itype is now defined at item and biblio level. - The default values for itemtype at biblio and item level are the same, controlled by itype values (document type). - The TYPEDOC authorized values category, which was used for controlling the value if itemtype at record level, is removed. - In Koha.pm UNIMARC facets are fixed to be a mirror of MARC21 facets: a facet for itemtypes is created, and the facet for ccode is now based only on items. Test plan: Note that sample data in ktd and sandbox may need to be fixed once this patch is pushed. It may cause warnings if you edit existing record but it is not a bug. A. Check AV and framework changes 1/ In a UNIMARC k-t-d or sandbox, with Zebra search engine 2/ Apply the patch 3/ Check that there is no "TYPEDOC" authorized value category 4/ Check default and FA framework - 099 should be labelled "ADDED ENTRY ELEMENTS (KOHA)" and contain subfields c, d, t (item type), s (serial flag), x (totalissues) - 942 should be labelled "OTHER ADDED ENTRY ELEMENTS (KOHA)" and contain subfields 2 and 6 5/ Create a new record with default framework -- add a 200$a field, a 100$a field (with the cataloging plugin) -- in 099$t field, check that the values in dropdown list are the one defines for 'item types' in administration (Books, Computer Files, Continuing Resource, etc). -- Choose the value "Computer field" and Save the record -- Koha displays the item creation form. Check that the preselected value in 995$r (item type) is "Computer field" 6/ Do the same operation for a new record with FA framework B. Check Zebra indexing changes 7 / Search "livre" in the catalog. 419 results should be shown 8 / Check that an "Item type" facet is visible and functional 9 / Edit the first record of the result list, change its 099t value and save 10 / Edit an item of that record and change the 995$r value (with a value different from the 099$t) and the 995$h value (3 possible values: Non-fiction, Fiction, Reference) 11 / Refresh the search for "livre" 12 / Check that the facet "Item types" has been updated and that a facet "Collections" is shown (from the 995$h) and functional C. Check Elasticsearch indexing changes 13 / You cannot currently test Elasticsearch in a sandbox, so, open a new k-t-d with Elasticsearch search engine (ktd --es7 up) 14 / Repeat operations 7 to 12 in that new instance (277 results should be shown after the search in step 7, instead of 419 for Zebra, this is normal) Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.