MARC Authority - System updates and quickMARC validation rules
This page is no longer being updated.
Please see the complete and updated list of quickMARC - MARC21 Validation rules here:
https://folio-org.atlassian.net/wiki/display/MM/quickMARC+-+MARC21+Validation
Changes to MARC fields that done by the system
MARC field | MARC type | Change logic | Related feature | Source of change |
|---|---|---|---|---|
LDR | Authority | Update 00-04 position with a new record length | Update MARC | mod-quick-marc |
001 | Authority | No HRID Generation/Assignment - Library will enter control number | Import MARCs | mod-source-record-manager |
003 | Authority | No logic to apply | Import MARCs | mod-source-record-manager |
005 | Authority | Set current date-time | Update MARC | mod-quick-marc |
010 | Authority | Add additional spaces to match valid LC control number | Update MARC | mod-quick-marc |
035 | Authority | No logic to apply | Import MARCs | mod-source-record-manager |
999ff | Authority | Update $s with SRS UUID and Update $i with mod-inventory-storage | Import MARCs | mod-source-record-storage / mod-source-record-manager / mod-inventory-storage |
XXX | Authority | Remove field if its content is empty | Update MARC | mod-quick-marc |
MARC Authority Validation rules in quickMARC
MARC field | MARC type | Validation rule |
|---|---|---|
LDR | Authority |
|
006 | Authority |
|
007 | Authority |
|
008 | Authority |
|
010 | Authority |
|
1XX | Authority |
|
01X - 999 | Authority | Only 2 indicators with one-character values can exist |
245 | Authority | No validation |
aaa-zzz | Authority | Alphabetical fields are restricted |
Comments
Hello @Lisa Robinson, I made the following updates
Leader and 008 rules
006, 007, 245 are noted to ensure the dev team does not apply the same MARC bib validation rules to MARC authority.
Regarding 008 subfield statement are you referring to 010?
aaa-zzz, we do not allow a user to enter alpha characters as a MARC tag.
@Lisa Robinson : Leader 17-18 - I don't think validation is needed on Leader 17-18. Leader 17 is always 'n' (complete) for folks outside Library of Congress. (The other possible value for Leader 17 is 'o' (incomplete) & no one wants an incomplete authority record!). For Leader 18, I'm not aware of the need to specify a punctuation policy as one does in a bib record. I'm also not aware of the need for a match between Leader 17-18 & values in the 008.
Leader, Only positions 5, 8, 17, 18 and/or 19 can be edited in the Leader - I don't think anyone would manually edit the Leader. But, does "edit" include overlaying one authority record with another? If it does, then all positions of the Leader (and 008) need to be editable (i.e. replaceable during overlay).
The 006 & 007 fields don't exist in MARC Authorities.
008 subfield length more than 3 characters - All subfields in MARC Authority 008 fields are just one character long.
01X-999, Only 2 indicators with one-character values can exist - The 2nd indicator is now undefined (& unused) for most MARC Authority fields. The main exception are the 130, 430, & 530 fields, which instead have the first indicator undefined/unused. (It's a MARC thing.) The other exception are the 7XX fields, which uses the same indicators are MARC Bibliographic format. I've never see a 7XX field in a Library of Congress authority record. I believe these fields were used by Library & Archives Canada in their French-language authority file to provide English equivalents for French names/subjects. This authority file is now part of OCLC & can be searched through WorldShare Record Manager (which my library doesn't use). See https://help.oclc.org/Metadata_Services/WorldShare_Record_Manager/Authority_records/Work_with_authority_records/Canadiana_Authorities?sl=en
245 - this field does not exist in MARC Authorities.
aaa-zzz - What are alphabetical fields?
The one thing I think should be required in validating MARC Authority records is that Leader 6 be 'z' (which means that the record is an authority record).