*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
- The Delivery System contact (identified at the kick off meeting) will hand off a spreadsheet with BIBID, eBIBID, and persistent URL for delivery system to Metadata Services contact. The Metadata Services contact will:
- Check list for completeness.
- Log workflow steps into project tracking systems (probably just Zoho).
- Capture updated metadata inventory in some version-controlled documentation source like https://github.com/cmh2166/AV2eCommons.
- If the system of record is the Catalog:
- Metadata will hand to Batch Processing a CSV of digital asset bib ids and persistent URLs
- Batch Processing will un-suppress the digital asset bibliographic record and add the persistent URL.
- Batch Processing will attach an appropriate Holdings for the Digital Asset, Derived Bibliographic Record (no Item record is attached to Digital Asset Bibliographic/Holdings records)
7. Create Collection-Level Bib Record for the Digital Collection
Participants: Jasmine Burns, Pamela Stansbury
Input: Digital Collection Link in Delivery System & Any Related Description
Output: Catalog BIB Record for the Digital Collection - Exemplar: https://newcatalog.library.cornell.edu/catalog/6790930
Steps Involved:
- Upon receipt of a URL for the digital assets in the delivery system, the Metadata Contact passes that URL and any other relevant, collection-level information on to Cataloging (Pam).
- Cataloging (Pam) creates a collection-level Bib record for the Collection.
PostScript: Linking the Digital Asset Bib Record to the Physical/Analog Asset Bib Record
...