...

• MARC BIB : Tenant cannot change the validation rules for Leader (LDR),  001, 005, 245, 999 ff, and control fields 006/007/008 008
  • EXCEPTION:  Can change Help URL 
  • EXCEPTION: 245/999 indicator - will follow standard indicator rules
  • EXCEPTION: 245/999 subfield - will follow standard subfield rules. 
• MARC AUTHORITY: Tenant cannot change the validation rules for Leader (LDR), 001, 005, 1XX, 999 ff, and control field 006/007/008. 
  • EXCEPTION:  Can change Help URL 
  • EXCEPTION: 999 indicator - will follow standard indicator rules
  • EXCEPTION: 999 subfield - will follow standard subfield rules. 
• MARC Field
  • Required means the field is required to save the record. 
  • Non-repeatable (NR)/Repeatable (R) = Cannot save a record if the MARC field is set to NR and the MARC tag has been entered multiple times 
• Indicator 1 
  • If user enters an invalid value then system will log it as a Warn but proceed with saving the record 
• Indicator 2 
  • If user enters an invalid value then system will log it as a Warn but proceed with saving the record 
• Subfield 
  • If user enters an invalid value then system will log it as a Warn but proceed with saving the record 
  • Non-repeatable (NR)/Repeatable (R) = Cannot save a record if the subfield is set to NR and the subfield has been entered multiple times 
  • If subfield is required then cannot save the record
• If the library enters a MARC field that is not on the validation list then system will log it as a Warn but proceed with saving the record 
• ECS 
  • Local record will validate against the member library's validation list 
  • Shared record will validate against the central tenant's validation list 

...

Types of MARC fields rules

• System-level: Tenant cannot change validation rules for the following fields

  • MARC BIB : LDR, 001, 005, 245, 999 ff, and control fields 006/007/008. 

  • MARC AUTHORITY:  LDR, 001, 005, 1XX, 999 ff, and control field 008.

• Non-local:  Standard:  Some validation rules can be configured at the tenant level. Non-local Standard fields are documented by LOC as not local. (ex. 130) 

• Local: all validation rules can be configured by the tenant. Local fields are: 

  • Not documented by LOC as a valid tag (ex. 192) 

  • Documented as a MARC local tag by LOC > 9xx, x9x, or xx9 (except 999 and 490)

System field rules

Tenant configuration

...

Tenant configuration

Standard field: Tenant level configuration options

• Status
  colour Green title yes

  - can be changed

• Status
  colour Red title no

  - cannot be changed

• Status
  colour Blue title Append

  -cannot change MARC specified values. Can add more codes with descriptionsnames. 

Standard (fna Non-local) fields > Tenant can modify

• Tag
  • Required/Optional
  • MARC Tag field name (Tenant cannot override) 
  • MARC Tag - help URL (Tenant can override) 
• Indicator 
  • Indicator 1 and Indicator 2
    • Tenant cannot change Indicator name specified by MARC 
    • Tenant cannot change Indicator codes and Indicator code names specified by MARC 
    • BUT Tenant can add/append more valid Indicator codes and Indicator code names NOT specified by MARC MARC (IOW can define local indicator codes and indicator code names) 
• Subfield  
  • Tenant cannot change subfield name specified by MARC 
  • Tenant cannot change subfield code and subfield code names specified by MARC 
  • But Tenant can add/append more valid subfield codes and subfield code names NOT specified by MARC (if invalid value) (IOW tenant can define local subfield codes and subfield code names) 
  • Non-repeatable (NR) / Repeatable (R) - (Tenant can set/modify for additional valid subfield codes but not MARC specified)  
  • Subfield is required/optional (Tenant can set required/optional for any subfield code but not MARC specified) Exceptions might be $9 and $0 for a field that can be controlled by an authority heading 
  • Cannot specify $9 for linkable bib fields since it is reserved for authority linking
• See more details MARC Validation Rules - Definition and Acceptable values

...