Bug 34191 - Record overlay rule to protect 942 with asterisk being ignored with z39.50 overlay
Summary: Record overlay rule to protect 942 with asterisk being ignored with z39.50 ov...
Status: RESOLVED DUPLICATE of bug 33268
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 22.11
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-03 17:28 UTC by Esther Melander
Modified: 2025-05-12 13:15 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esther Melander 2023-07-03 17:28:28 UTC
To recreate:

1. Create multiple Record overlay rules with Source, z39.50, TAG, protect, skip, skip, skip, skip. 
2. Create Record overlay rule Source, *, 942, Protect, skip, skip, skip, skip.
3. Find a bib record and make sure it contains a 942 with selected item type.
4. Replace record via z39.50 (using the basic editor)
5. Edit the bib and change the protected tags in the overlay rules for z39.50.
5. Attempt to save the record. If 942 is a required field, you must select the item type. If that happens, select an alternate item type.

The record will save and restore the tags protected through the z39.50 overlay rules. But the record will also save the alternate item type and not protect/restore the 942 tag to the previous item type. The asterisk should protect the 942 tag regardless of the cataloging process.
Comment 1 Katrin Fischer 2025-05-12 13:15:44 UTC
I believe this is a duplicate to 

Bug 33268 - Overlay rules don't work correctly when source is set to *

It was pushed only pretty recently, so not available in 22.11, but if you avoid * for now you can make it work at least until properly fixed.

*** This bug has been marked as a duplicate of bug 33268 ***