...
- First iteration created in MODDATAIMP-137, but did not take into account repeatable and non-repeatable fields
- Thus, bugfixes were required and were delivered in Morning Glory. This page is based on the developer page MARC field protections, to document the behavior for 1) Protecting MARC field and then 2) Overriding MARC field protections
- Related bugs
See MODDICORE-146 SPIKE: Instance & SRS record updates need to honor MARC field protections for additional technical information
...
- As with applying MARC field protections, overriding those protections are somewhat limited in releases prior to Morning Glory, in that they cannot be used without an Update MARC action in the job profile, and do not distinguish the handling for repeatable and non-repeatable fields properly.
- As of the Morning Glory release, all of the details in the above MARC field protections scope section also apply to overriding MARC field protections.
- Field protection override behavior:
- Field is non-repeatable, and the field protection for the existing field is overridden in the job profile
- Existing field's will be replaced by the incoming field's data in the updated record, regardless of whether that data is the same or different from the existing data
- Field is repeatable, and the field protection for the existing field is overridden in the job profile
- Existing field also is in the incoming record:
- The field will be retained in the updated record (actually replaced by the incoming version of the field, which is an exact duplicate to the existing field)
- Existing field is not in the incoming record:
- The field will not be retained in the updated record (since its protection was overridden)
- Existing field also is in the incoming record:
- Field is non-repeatable, and the field protection for the existing field is overridden in the job profile
Under construction
Per updates in MODDICORE-200 and UIDATIMP-1043, as of Kiwi the following adjustments have been made:
Additional adjustments will be made to ensure that the field protection settings meet these additional requirements, hopefully during the Lotus development cycle
- Different handling logic for repeatable and non-repeatable fields
- Ensure that field protections are followed for Updates triggered by Inventory Single Record Updates or by regular Data Import, without an Update MARC action profile (similar to how SRS MARC updates are often implicit actions when the data import profile updates Instances)
- Review MARC Holdings records and MARC Authority records to determine if any additional adjustments are needed to accommodate them with the same field protection settings
- Information from MARC field protections will be reviewed and consolidated with this page.