Page History

...

3. Digital & Analog (as needed) Asset MARC Record Creation & Loading

Participants: Gary Branch (hands off to Batch staff member), Pamela Stansbury (as needed), Jasmine Burns (as needed)

...

3a. MARC exists for the Analog/Physical Item, Need to Derive MARC for the Digital Asset

Input: List of Analog Bibliographic Record IDs

Output: Derived, suppressed Digital Asset Bibliographic Record IDs, and a List of those IDs matched to the Analog Bib IDs

• List of Analog/Physical Bibliographic Records are handed to Batch Processing (Gary as point person).
• Batch Processing:
  • Derives Bibliographic Records for the Digital Surrogate from the Analog/Physical Bibliographic Record.
  • The Digital Asset, Derived Bibliographic Records have no holdings and are kept suppressed until reloaded with links (Step 6)
• The Digital Asset, Derived Bibliographic Records have need a unique a flag, like a 995 ignore, so Batch Processing's validation jobs don't flag these as errors
• Bib record derivation specification and data profile:
• based on format, to be documented.
• upon generation of the Digital Asset, Derived Bibliographic Records, Cataloging (Point Person, Pam) is requested to review a sample to check for adequate data.
• The resulting decisions/updates/edits should be added back to the format-specific derivation profile, to inform future derivations.

3b. MARC does not exist for the Analog/Physical Item, Need to Derive MARC for the Analog and the Digital Asset from a provided CSV

Input: CSV including Title (of Work), Date, Barcode (on Item), Part Number, Notes

Output: Generated, minimum-level Physical/Analog Bibliographic, MFHD, & Item Records; and Derived suppressed Digital Asset Bibliographic Record IDs, and a List of those IDs matched to the Analog Bib IDs

• The Requesting Party for the Digital Project creates and provides a CSV with the following information:
  • Title (of Work), Date, Barcode (on Item), Part Number, Notes, Other Metadata Fields as encountered / able to be pulled
• The CSV is handed to Batch Processing (Gary as point person).
  • That CSV is used by Batch (can Metadata help with this at all?) to generate minimum-level MARC Bibliographic, Holdings & Items records for the Physical/Analog Resource
  • the Physical/Analog Bibliographic Records are unsuppressed unless explicitly requested by the originating party (and approved in the kick-off meeting)
• Batch Processing:
  • Derives Bibliographic Records for the Digital Surrogate from the Analog/Physical Bibliographic Records generated above.
  • The Digital Asset, Derived Bibliographic Records have no holdings and are kept suppressed until reloaded with links (Step 6)
• The Digital Asset, Derived Bibliographic Records have need a unique a flag, like a 995 ignore, so Batch Processing's validation jobs don't flag these as errors
• Bib record derivation specification and data profile:
• based on format, to be documented.
• upon generation of the Digital Asset, Derived Bibliographic Records, Cataloging (Point Person, Pam) is requested to review a sample (of the physical and the digital records) to check for adequate data.
• The resulting decisions/updates/edits should be added back to the format-specific derivation profile, to inform future derivations.

3c. MARC exists (but not in Voyager) for the Analog/Physical Asset, Need to Load MARC for Analog/Physical Asset and Derive MARC for the Digital Asset

Input: Minimum level MARC records (Bib with holdings and items information as relevant)

Output: Voyager-loaded Physical/Analog Bibliographic, MFHD, & Item Records; and Derived suppressed Digital Asset Bibliographic Record IDs, and a List of those IDs matched to the Analog Bib IDs

• The Requesting Party for the Digital Project creates and provides a set of MARC Bibliographic records stored somewhere open to them, Metadata and Batch Processing
  • The Physical/Analog Bibliographic Records are loaded into Voyager.
  • These records are unsuppressed unless explicitly requested by the originating party (and approved in the kick-off meeting)
• Batch Processing:
  • Derives Bibliographic Records for the Digital Surrogate from the Analog/Physical Bibliographic Records generated above.
  • The Digital Asset, Derived Bibliographic Records have no holdings and are kept suppressed until reloaded with links (Step 6)
• The Digital Asset, Derived Bibliographic Records have need a unique a flag, like a 995 ignore, so Batch Processing's validation jobs don't flag these as errors
• Bib record derivation specification and data profile:
• based on format, to be documented.
• upon generation of the Digital Asset, Derived Bibliographic Records, Cataloging (Point Person, Pam) is requested to review a sample (of the physical and the digital records) to check for adequate data.
• The resulting decisions/updates/edits should be added back to the format-specific derivation profile, to inform future derivations.

...