Global MARC Validation Rules Updates

Overview

Some institutions may prefer to not setup these rules and use MARC validation as it exist pre-Ramsons release. Some institutions may want to configure rules for just fields and not subfields (vice versa). If that is your preference, then the following details will allow you to configure MARC validation rules to ignore rules that are undefined and only follow system MARC validation rules (IOW pre-Ramsons validation support).

Use endpoint, GET /specification-storage/specifications/{MARC bib or authority specificationId}/rules to view global MARC validation rules and retrieve id(s).

1. Ignore undefined field warnings

   1. Use endpoint PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Field"}

   2. Body should only include

      {   "enabled": false }

2. Ignore undefined subfield code warnings

   1. Use endpoint PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Subfield"}

   2. Body should only include

      {   "enabled": false }

3. Ignore undefined indicator warnings

   1. Use endpoint PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Indicator Code"}

   2. Body should only include

      {   "enabled": false }

Global MARC Validation Rules we recommend you DO NOT change to false

1. endpoint PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "nonRepeatable1XXField"}

• This rule prevents a cataloger from having multiple 1XX on a MARC bib and MARC authority record.

2. endpoint PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Invalid Field Tag"}

• This rule prevents catalogers from creating a MARC field tag like these examples

  • 22

  • 2

  • 2ax

  • 2a

  • YYY

Questions

1. If I disable any/all global MARC validation rules settings, what will happen with a release upgrade? Your settings will be honored. A release upgrade will not reset MARC validation rules settings to default values.

2. If I disable any/all global MARC validation rules settings, what will happen to any rules I have created/edited? Any rules you have created/edited are saved and will be honored based on your global MARC validation rules setting selections. They will never be overridden unless you use the endpoint to reset to default MARC validation rules.

3. My institution has disabled any/all global MARC validation rules settings and we are preparing to upgrade to a new release, what should I expected? No change from current UX.

4. My institution has disabled any/all global MARC validation rules settings and we now want to enable any/all global MARC validation rules settings, what should I do? Anytime, you can enable MARC validation rules; it not dependent on a release. Ditto for disabling global MARC validation rules

5. Will a UI be provided to manage MARC validation rules? In the next 1-2 releases, we will make setting global MARC validation rules available via the UI. TBD when a UI will be available to manage MARC field/indicator/subfield rules.

6. Can you just change the global undefined rules API endpoints default to false? Yes, we changed the default to false with the Trillium release MRSPECS-102: MARC authority and bib validation rules - Change API defaults for undefined field rules to falseClosedPreview