Page History

...

1. Digitization Project Kick-off Meeting Review

Participant: Jasmine Burns

Input: n/a

Output: Expectations for upcoming, project-based work

Steps Involved:

During the kick-off meeting, a Metadata Services representative (with invited member from Batch or Cataloging, as needed) discusses the:

...

2. Digitization Lab Inventory & Digital Assets Identifiers Request

Participants: Jasmine Burns, user-9f226 (as needed), Gary Branch (as needed), Pamela Stansbury (as needed),

Input: Inventory of Items to be digitized - CSV with Call Number, Title, BIBID for physical/analog resource (if analog resource is already cataloged)

Output: Inventory of Items Needing a Catalog Record & Existing Records/Metadata to leverage

Steps Involved:

• The Digitization Lab work hands final inventory of items to be digitized (generally, Call Number, Title, BIBID of the physical/analog) to Metadata for review & routing. Review Metadata review includes:
  • Checking list for completeness.
  • Logging workflow steps into project tracking systems (probably just Zoho).
  • Capturing the hand-off in some version-controlled documentation source like https://github.com/cmh2166/AV2eCommons.
• According to discussions decisions made at Digital Project Kick-off Meeting (Step 1. above), the Metadata Contact routes this inventory list and additional context to the appropriate Batch contact for digital (and possibly analog) record creation.
  • If the records or metadata of record is not loaded into MARCdestined for the Catalog, then step Step 3 is not followed skipped and Batch / Cataloging is not involved in the workflow until past a Collection-level record is discussed.

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

...

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

• 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
• flag in record for ignore this:
basically load bibs, no holdings, keep
• • suppressed until reloaded with links
• come up with a flag, 995 -ignore 
• generate bibs based on existing workflows in Gary
• based on format
• cataloger review
• pam looks at sample
• decides on 
• create collection-level records 
• collection-level bib record stub 
• collection-level descriptive information can stand in
• holdings, bibs unsuppressed with links
• have format + generating this
• • (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

• 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.
• load bibs:
• generate MARC
• items being generated
• create items
without piece 

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

• 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.
• load bibs:
• generate MARC
• items being generated
• create items
without piece 

4. Generate Updated Inventory with "eBibs", Hand back to Digitization

...

• 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.
• Handoff: Christina will give Pam's group a list of BIBIDs to review and manually update as needed. Physical-digital links should be displayed in Blacklight after next Solr update.
• need to indicate clearly suppress / unsuppressed
• copyright 

PostScript: eBib to analog Bib linking

...

• • 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

When deriving digital asset Catalog records from physical or analog asset Catalog records, we want to indicate the derivative relationship between the two resources.

Currently:

• a special 035 field is generated by Batch that links the derived, digital asset bibliographic record to the physical/analog bibliographic record (documentation for this?)

Proposed:

• In generating future records as part of this workflow, we'd like to clearly indicate the derivate relationship so it can be better exploited in Metadata batch processes/updates as well as in Discovery interfaces.
• Use...
  • 899 field to relate the two records?
  • or further exploit and add a backwards pointer to the 035 field?
  • or fall more closely in-line with the MARC bibliographic specification by using a 776 field?
• This needs to be decided.

Metadata Examples & Profiles for the Above Workflow

Example: Pre-Digitization Inventory

to be added

Example: Post-Digitization Inventory / Metadata

https://github.com/cmh2166/AV2eCommons/blob/master/data/CUlecturetapes_20160211/post-Kaltura_files/CUlecturetapes_metadata_kalturaIDs.csv

Example: Digital Asset MARC Bibliographic Record

to be added

Example: Digital Collection-level MARC Bibliographic Record

LEADER 01852cam a22003255a 4500
0016790930
00520160128091848.0
006m        d        
007cr cn ---|||||
008091211s2010    nyua    s     000 0 eng d
035 __ ‡a (OCoLC)667617581
035 __ ‡a 6790930
245 04 ‡a The Huntington Free Library Native American Collection ‡h [electronic resource].
260 __ ‡a [Ithaca, N.Y.] : ‡b Cornell University Library, ‡c c2010.
520 __ ‡a One of the largest collections of books and manuscripts of its kind, the Huntington collection contains extensive materials documenting the history, culture, languages, and arts of the native tribes of both North and South America. Contemporary politics and human rights issues are also important components of the collection.
520 8_ ‡a Full text of a selection of 91 books from the Huntington Free Library Native American Collection representing the various genres in the collection.
500 __ ‡a Title from home page, viewed Sept. 30, 2010.
538 __ ‡a Mode of access: World Wide Web.
650 _0 ‡a Indians of North America.
650 _0 ‡a Indians of South America.
650 _0 ‡a Indians of North America ‡x History ‡v Sources.
650 _0 ‡a Indians of South America ‡x History ‡v Sources.
710 2_ ‡a Huntington Free Library.
710 2_ ‡a Cornell University. ‡b Library. ‡b Division of Rare and Manuscript Collections. ‡0http://vivo.cornell.edu/individual/individual32117 ‡0 http://id.loc.gov/authorities/names/nr97000951 ‡2http://id.loc.gov/authorities/names ‡4 http://id.loc.gov/vocabulary/relators/cur ‡e Curator
856 40 ‡u http://resolver.library.cornell.edu/misc/6790930 ‡x http://dlxs.library.cornell.edu/h/hunt/
899 __ ‡a CULDigReg
906 __ ‡a gs
948 2_ ‡a 20140618 ‡b m ‡d batch ‡e lts ‡x add899CULDigReg
948 1_ ‡a 20100930 ‡b o ‡d mnr1 ‡e lts
948 2_ ‡a 20160128 ‡b m ‡d str1 ‡e lts ‡x RDC Experiment