https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38336

--- Comment #16 from Mathieu Saby <[email protected]> ---
Created attachment 178126
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=178126&action=edit
Bug 38336: Fix confusion between 099 and 942 UNIMARC fields

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
- test in TestBuilder.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 "Local dates (Koha)" and should be
used in default configuration only for this storing creation
and modification dates of record.
- The 942 field is mandatory (because its $c subfield is)
and should be used for all other Koha local information,
like its MARC21 counterpart.
- 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.
- A test on record-level itemtype in TestBuilder.pm is fixed
in order to replace 099 with 942 field.

Test plan:

Note that sample data in ktd and sandbox will need to be fixed once
this patch is pushed (there is no data in 942$c for example).
It may cause warnings if you edit existing record but it is not a bug.

A. Check framework changes
1/ In a UNIMARC k-t-d or sandbox, with Zebra search engine
2/ Apply the patch
3/ Check default and FA framework
- 099 should be labelled "Local dates (Koha)" and
contain 2 subfields:c and d
- 942 should be mandatory, labelled "ADDED ENTRY ELEMENTS (Koha)"
and contain 5 subfields : 0,2,6,c (mandatory),s
4/ Create a new record with default framework
-- add a 200$a field, a 100$a field (with the cataloging plugin)
-- in 942$c 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"
5 / Do the same operation for a new record with FA framework

B. Check Zebra indexing changes
6 / Search "livre" in the catalog. 419 results should be shown
7 / Check that an "Item type" facet is visible and functional
8 / Edit the first record of the result list, change its 942$c
value and save
9 / Edit an item of that record and change the 995$r value
(with a value different from the 942$c) and the 995$h value
(3 possible values: Non-fiction, Fiction, Reference)
10 / Refresh the search for "livre"
11 / 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
12 / I believe you cannot currently test Elasticsearch in a sandbox,
so, open a new k-t-d with Elasticsearch search engine (ktd --es7 up)
13 / Repeat operations 6 to 11 in that new instance
(277 results should be shown after the search in step 6,
instead of 419 for Zebra, this is normal)

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to