Scope: Procedure for handling batch creation or editing of MARC records of Digitization-related assets slated for delivery to support their management in the Catalog.
Contact: Jasmine Burns
Unit: Batch Processing, Cataloging, Metadata Services, DCAPS
Date created: 02/17/2017
Date of next review: February 2019
Please note that this procedure has been revised extensively as of May 2018, therefore previous references to the procedure may no longer apply
These are the three cases in which DCAPS initiates a Batch process
1. BIBs need eBIBs
Participants: user-0b855, Batch staff
Scenario: Creation of eBIBs for digitized items in delivery systems. eBIBs will only be created if the following criteria is met:
- Items are individually cataloged (not items where the only representation in the catalog is at the collection-level)
- Access with a URL will be provided (only create eBIBs at the time of provisioning for access)
Input: spreadsheet of BIBs with Delivery URLs
Output: eBIBs are created
- DCAPS hands user-0b855 a spreadsheet of BIBs and URLs
- user-0b855 passes along to appropriate Batch Processing representative
- Batch processing creates eBIBs and notifies user-0b855 when they are complete
2. Digitized items need 899 code
Participants: DCAPS Project Manager, user-0b855, Batch representative
Scenarios:
- DCAPS has digitized items and would like the catalog record to note that these items have been digitized (single items)
- DCAPS has a group of records that belong to a single digital collection and would like the catalog records to note that they belong to that collection
- if the representation of these items exists somewhere as a collection (i.e. finding aid, catalog record, etc.), option 2 will be the likely scenario
Input: spreadsheet of BIBs and the date that the items were digitized
Output: BIBs get 899 code
- DCAPS hands spreadsheet of BIBs to user-0b855 to hand over to Batch representative
- Batch places an 899 code on the records with a subfield $d for date
- In the case of Scenario 1, code xxxx will be used
- In the case of Scenario 2, see LTS Procedure xxx for the creation of 899 codes (does not yet exist)
- Batch notifies user-0b855 which 899 code was used
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.
- 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?)
- 776 0 8 $i Print version | Online version $w (Voyager) bibidnum
- 899 ind1 = 0 $a 899code