Global MARC Validation Rules Updates

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 field level errors for fields that have no field rules defined.

   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 invalid or a local field tag (ex. enter 299 or 920) that has no rule defined.

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

   2. Body should only include

      {   "enabled": false }

3. Ignore subfield code level error because code is not specified in rules.

   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 }

4. Ignore indicator code level error because code is not specified in rules.

   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 }