...
More information about these alerts is available in ExLibris' Alerts on the Metadata Editor documentation.
...
Recommendations
...
NOTE: The following recommendations are a DRAFT ONLY (5/3/21). Members of the "Wranglers" group are invited to review the recommendations and send suggestions or feedback to hamerman@princeton.edu .
Recommendations
Most validation alerts are “warnings” allowing the cataloging user to save the record. Original cataloging will take place in OCLC, which has its own validation settings, some of which are more comprehensive than those in Alma. The task group felt that only issues that significantly affect discovery/indexing should trigger an "error" that requires correction before saving.
...
(Approved by Jennifer Baxmeyer, 5/17/21)
Retain the following errors in Alma’s default settings, requiring correction before releasing the record:
- Field * must be empty [Do not configure any fields that must be empty.]
- Mandatory field 245 is empty
- Mandatory field 245 is missing
- Mandatory field LDR is missing
- Multiple occurrences were found for non repeatable field 100
- Multiple occurrences were found for non repeatable field 110
- Multiple occurrences were found for non repeatable field 111
- Multiple occurrences were found for non repeatable field 245
The task group recommends upgrading Upgrade the following from warnings to errors:
- Invalid indicators in fields 100, 110, 111Multiple occurrences are found for field 130
- Fields 100, 110, 111, 130 are missing $a
- Field 245 is missing $a; or 245 $a, $b, $c are repeated
- 600, 610, 611, 630, 650, 651 fields are missing $aInvalid indicators in fields 700, 710, 711
- $a is missing in fields 700, 710
- Field 800 has invalid indicators
Other notes/ recommendationsThe task group also recommends adding :
The group discussed the potential that Normalization Rules can be used to correct errors involving correspondence between fields. No warning/error will appear for these, as Alma only validates elements within a single field :
- 245 1st indicator is 1 or 0 depending on presence of 1xx
- If 040 $e is rda, add 33x fields (and possibly convert 260 → 264 _1?)
- 490 1st indicator is 1 or 0 depending on presence of 8xx
- Add a warning
...
- if 043 has invalid code. Will need to add 043 geographic codes to controlled vocabulary registry.
Solution: Editing Validation Processes and Validation Exception Profiles
...
- Validation tasks for MARC Bibliographic Records can be added or removed using the Validation Processes tab.
- Validation Exception Profiles determine the severity of a validation error. Admins can add/edit a Validation Severity Profile to determine whether something is a ‘warning’ (yellow) or an ‘error’ (red).
- Systems staff (Peter Green and Regine Heberlein) will configure the validation settings to reflect the recommendations of the task group (as approved by the Wranglers group and Jennifer Baxmeyer, above)