Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Incoming recordExisting recordNotes
MARC Bib 001Instance HRID
MARC Bib 001MARC Bib 001

Usually this is the Instance HRID

MARC Bib 035$aInstance OCLC number
MARC Bib 035$aInstance System control number
MARC Bib 024$aInstance Other standard identifier
MARC Bib 9xx$yPurchase Order Line number (POL) associated with the InstanceCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399
MARC Bib 9xx$yVendor reference number (from POL) associated with the InstanceCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399

MARC Bib 999 ff $i

MARC Bib 999 ff $iInstance UUID
MARC Bib 999 ff $sMARC Bib 999 ff $sMARC Bib SRS UUID
Static matchInstance status = Used as a submatch, to determine whether an instance has been cataloged or is yet to be cataloged
Static matchStatistical code?Is this currently being used? If so, please provide an example or use case. (NOTE: I have tried this several times and I've not had any of my tests work. For the 5C one use story case is to work with HathiTrust records, using . Using the statistical code could would provide a convenient way to mark HT records in FOLIO Inventory to work with them such as updating status (like for emergency status). Another use case for the 5C is that we want to use stat codes for our batch loaded collections. This way we have a mechanism to grab all records in that set and even determine which records belong to different sets such as JSTOR purchased and open access. Having a controlled stat code vocabulary for this is preferred.)
MARC Bib 01x, 02x, 03x 9xxMARC Bib 01x, 02x, 03x, 9xxNeed MARC-to-MARC matches for various control numbers (beyond 001 and 999 ff). Not yet available. See UXPROD-2742
MARC Bib 039 9\MARC Bib 035 9\In time it would be great to match to such this field. In the 5C, this is where we keep our unique identifier for batch loading which is constructed using the vendor number or OCLC number and a local code for the collection such as umsaf9394949.

...

Incoming recordExisting recordNotes
MARC Bib 9xx$yHoldings HRIDCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$yHoldings UUIDCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$yFormer Holdings IDCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case..
Static matchHoldings Permanent locationSubmatch after the correct Instance is identified
Static matchHoldings Temporary locationSubmatch after the correct Instance is identified
MARC Bib 856$uHoldings Electronic access URI
MARC Bib 856$yHoldings Electronic access link textSubmatch after the correct instance is identified or a direct match. For 5C, a good use case is our NAXOS where we have 5 urls that are pretty much the same but our link text is all different and unique for each school. Having this match point would be powerful to work with our eResources
MARC Bib 9xx$yPurchase Order Line number (POL) associated with the HoldingsCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399
MARC Bib 9xx$yVendor reference number (from POL) associated with the HoldingsCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399
Static matchStatistical code?Is this currently being used? If so, please provide an example or use case. (Note: Please see use cases above for stat code. For 5C with merged records, matching on stat code could be very powerful for updates and batch processes.)
Static matchHoldings Type?Is this currently being used? If so, please provide an example or use case.
Static matchHoldings Call number type?Is this currently being used? If so, please provide an example or use case.






...

Incoming recordExisting recordNotes
MARC Bib 9xx$yItem HRIDCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$yItem UUIDCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$yItem BarcodeCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
Static matchItem status?

Is this currently being used? If so, please provide an example or use case.

Cornell: Static match on "on order" status to move an item from "on order" to "in process" (+1 for 5C)

MARC Bib 9xx$yItem Accession numberCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case.
MARC Bib 9xx$yItem Former identifierCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case.
MARC Bib 856$uItem Electronic access URI
Static matchStatistical code?Is this currently being used? If so, please provide an example or use case. (Note: See use cases for instances and holdings for 5C.)
MARC Bib 9xx$yPurchase Order Line number (POL) associated with the ItemCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399
MARC Bib 9xx$yVendor reference number (from POL) associated with the ItemCan be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Not yet available; will be an important match; hopefully can implemented in Kiwi; see MODDATAIMP-399












...