(post go-live) Publishing profile for Google Books/HathiTrust

Legend: not started IN PROGRESS STALLED decided

Status	decided
Scope	post go-live
Description	Create a standard record output for items being sent for Google books/HathiTrust digitization
Decision	see below
Owning group	RMFG
Approver	PPC
Stakeholders	R = RMFG A = RMFG C = Campus contacts, CDL (Paul Fogel, Kathryn Stine) I = Campuses, CDL
Decision-making process
Priority
Due date	Aug 25, 2021

Recommendation

RMFG recommends the following publishing profile/CDL data elements:

Common Data Elements	Proposed field
Bibliographic System ID	001
OCLC Number	035 $a (OCoLC)
Bibliographic System Item ID	991$a
Item barcode	991$b
Call number	991$c
Item Enumeration/Chronology	description: 991$d enum A: 991$e enum B: 991$f Chron I: 991$g Chron J: 991$h
Other item identifiers	991$q
Item Print Holding Status	991$s
Item Condition	991$z
Former Bibliographic System ID(s)	996$a AND 035 $z Standard prefixes to be added prior to sending to CDL: (UCBmil) (UCDalma) (UCIalma) (UCLAvoy) (UCMwms) (UCRalma) (UCSBalma) (UCSCalma) (UCSDmil) (UCSFmil)

Updated 9/7/2021 to include 035 $z

Reasoning

Standard exports will make it easier for CDL to process metadata from all of the UC campuses and also allow us to share workflows with one another. The data elements listed above were the ones needed by CDL to process Google Book/HathiTrust items. Any other needed elements can be added by campuses as needed.

Background

CDL submitted a request to RMFG asking for a single export format to support digization workflows:

“The efficiency and efficacy of the SILS workflows described in this document would be substantially improved by the following two recommendations:

Establishing a single, common standardized export format: this would dramatically reduce the resources required to reconfigure digitization support systems and would simplify long-term management, maintenance, corrections, and updates.
Providing CDL with the ability to view and extract metadata directly: this would allow CDL to correct, update, remediate, etc. systems that it coordinates when campuses are unable, ex. HathiTrust. This would also help with triage activities, long-term preservation and management, etc.”

RMFG is unable to address the second request for the time being since it would involve a long discussion of access/permissions and roles but did feel that we could address the first request.

Questions to consider

Can we repurpose existing publishing profiles at already-Alma campuses
Can we build something that is reusable for other digitization efforts
How MARC21 compliant does the profile need to be (Alma and MARCEdit may not throw errors but other system/data processing tools will)

Action Log

Action/Point Person	Expected Completion Date	Notes	Status

Action/Point Person	Expected Completion Date	Notes	Status
Proposal draft complete	8/25/2021		done
PPC approval	8/27/2021		done
Update	9/7/2021	Added 035 $z for Former system ID after consultation with CDL	done