MARC bib: logic and rules in FOLIO
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 | Bibliographic | Update 00-04 position with a new record length | Update MARC / Derive new MARC | mod-quick-marc |
001 | Bibliographic | Move field value with 003 to 035 and set HRID | Derive new MARC / Import MARCs | mod-source-record-manager |
003 | Bibliographic | Move field value with 001 to 035 and remove | Derive new MARC / Import MARCs | mod-source-record-manager |
005 | Bibliographic | Set current date-time | Update MARC / Derive new MARC | mod-quick-marc |
010 | Bibliographic | Add additional spaces to match valid LC control number | Update MARC / Derive new MARC | mod-quick-marc |
035 | Bibliographic | Set data from 001 and 003 field | Derive new MARC / Import MARCs | mod-source-record-manager |
999ff | Bibliographic | Update $s and $i with newly created SRS Record and Instance IDs | Derive new MARC / Import MARCs | mod-source-record-storage / mod-source-record-manager |
XXX | Bibliographic | Remove field if its content is empty | Update MARC / Derive new MARC | mod-quick-marc |
Validation rules in quickMARC
MARC field | MARC type | Validation rule |
|---|---|---|
LDR | Bibliographic |
|
006 | Bibliographic | Unexpected length of the field |
007 | Bibliographic | Unexpected length of the field |
008 | Bibliographic | Leader at 17-18 position doesn't match 008 field |
Bibliographic | Unexpected length of the field | |
01X - 999 | Bibliographic | Field length should be more than 3 characters. (relates only to API) |
01X - 999 | Bibliographic | Only 2 indicators with one-character values can exist |
245 | Bibliographic | Can only have one 245 field with not empty value |
aaa-zzz | Bibliographic | Alphabetical fields are restricted |
quickMARC data flows
quickMARC only stores quickMARC record status
quickMarc has direct interaction only with source-record-manager (SRM)
quickMARC
Through SRM, creates a record in SRS via the Derive a new MARC bib record action
Through SRM creates a record in mod-inventory-storage via the Derive a new MARC bib record action
Through SRM, updates a record in SRS via Edit in quickMARC action
Through SRM, updates a record in mod-inventory-storage via Edit in quickMARC action
Comments
Thanks @Ann-Marie Breaux (Deactivated), this analysis only covers quickMARC > MARC bib handling. I asked Pavlo to provide details on what existing logic quickMARC has that may result in data being changed by quickMARC and not by data import or a user.
@Pavlo Smahinseems like we need to do what Ann-Marie outlined for the 003 work for deriving a new MARC bib record?
Along with the 001, field 003 should be changed as well, since they should travel together. 003 represents the organization that assigned the 001. We pair it with the 001 and move to an 035 field. We do not replace the 003, so after the 001/003/035 manipulation, there is no longer an 003 on the MARC record, and the 001 is the FOLIO HRID. Here's the Jiras for the 003 work for MARC Bibs MODSOURMAN-345 and MODSOURMAN-249
Hi @Pavlo Smahinthis is only covering changes by QM, not changes by Data Import, right? And is this for MARC Holdings, MARC Authorities or both?
A couple things:
Along with the 001, field 003 should be changed as well, since they should travel together. 003 represents the organization that assigned the 001. We pair it with the 001 and move to an 035 field. We do not replace the 003, so after the 001/003/035 manipulation, there is no longer an 003 on the MARC record, and the 001 is the FOLIO HRID. Here's the Jiras for the 003 work for MARC Bibs MODSOURMAN-345 and MODSOURMAN-249 (we missed it and had to circle back to do it).
Regarding the 999 ff field, for Authorities, there is only $s (since there is no Inventory equivalent). For Instances and Holdings, there's $s (for SRS UUID) and $i (for Inventory UUID)
And for Holdings, you may want to include (from the MARC Holdings-Inventory Holdings mapping spreadsheet)
004 (no indicators or subfields): HRID of the related Instance
014 (ind 1 = 1, ind 2 = blank) $a: UUID of the related Instance