Under construction
Per updates in MODDICORE-200 and UIDATIMP-1043, as of Kiwi the following adjustments have been made:
The following fields are system-protected
- 001 (Non-rep)
- 999 ff (Non-rep)
The following fields are disallowed from Field protection:
- Leader (Non-rep)
- 002
- 003 (Non-rep)
- 004
- 005 (Non-rep)
- 009
The following control fields are allowed for Field protection:
- 006 (Rep)
- 007 (Rep)
- 008 (Non-rep)
- But with the following restrictions:
- If one of these control fields is entered, then no Indicators or Subfields are permitted
- No wildcard Data is permitted
The following variable fields are allowed for Field protection:
- 010-899
- 900-998
- 999, except for 999 ff
The non-repeatable variable fields are: (if not listed, consider it a repeatable field)
- (look at bib, holdings, authority - see if any clashes)
Wildcards (asterisk) are currently allowed for
- Fields
- Indicator 1
- Indicator 2
- Subfield
- Data
- But with the following restrictions:
- Control fields (006, 007, 008) are not governed by any wildcard logic
- For field 999, wildcards in Ind 1 and/or Ind 2 are not honored (since 999 ff is protected)
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.