https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39667
Bug ID: 39667
Summary: Copy and replace of 952$y to 942$c MARC modification
template fails
Change sponsored?: ---
Product: Koha
Version: 24.05
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Cataloging
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
To replicate
1. Make sure there are no record overlay rules that protect the 942$c.
2. Find a bibliographic record. Edit the record in the advanced editor and
remove the 942$c if there is one.
3. Create a MARC modification template with these actions:
Copy and replace 1st 952$y to field 942$c if field 942$c doesn't exist.
4. Apply the MARC modification template to the example record.
Look at the MARC and notice the 942$c has not been replaced.
This scenario can be repeated with a bibliographic record that does have a
942$c, but have it be different from the 952$y. Update the template to:
Copy and replace 1st field 952$y to field 942$c if 942$c doesn't match
Apply the template to the record and see that the 942$c is untouched despite
the success message.
Multiple variations on the rules above result in no changes to the
bibliographic record. I think the rule is trying to apply the descriptive text
of the 952$y to the 942$c and it is being rejected because the descriptive text
is not the same as the item type code. The success message after the template
is applied is in error because no changes were made to the bibliographic
record.
The 942$c needs to have the item type code in order for the template to work.
As an alternative example the template actions of Update existing and add new
work, but only if the item type code is entered into the template.
Many libraries have bibliographic records with a missing 942$c but have item
records with a 952$y. It would be nice if the MARC template can be used to
update the bibliographic records by copying the item type code of the 952$y to
the 942$c, if it is at all possible. While a library could create a rule using
the Update existing or add new rule, they would have to run reports to sort the
records by item type first. Which is perhaps less efficient if there are
thousands of records. Otherwise the libraries have to manually edit each record
or have a script run from a terminal to accomplish the same thing.
--
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/
