Minimum Requirements for Preparing Digital Collections for UChicagoNode

For each new collection, we designate a

Project Coordinator (PC) or Project Manager (PM)

We have sometimes hired project managers as part of grant-funded initiatives, but in the absence of a PM we still need a designated PC. Collections may also have one or more Principal Investigators (PI), and/or one or more principal stakeholders (PS), who might or might not be the same as the PI.

For example, in its first phase, the Mesoamerican Languages Collection had a PI (John Lucy), a co-PI (David Woken), a PS (also John Lucy), and a PM (Maria Victoria Fernandez, paid from the grant which funded the first phase of building the collection).

The PC/PM is responsible for coordinating assembly of the following deliverables. These serve as a checklist of what is needed before UChicagoNode development can begin. The PC/PM can use these in discussions with the PI/PS to develop what is needed for the collection.

Determines rights and permissions (PI/PS or PC/PM)
Writes static content describing the collection, rights and permissions, credits/acknowledgments, contact information, etc. (PI/PS)
Provides metadata (PI/PS or PC/PM)
May provide born-digital files for the collection if these exist (PI/PS or PC/PM)

Digitization Unit (DU)

Creates inventory of files created
Creates files in preservation-worthy digital formats (e.g., TIFF) unless these have been provided by the PI/PS or PC/PM
Prepares metadata for files
Delivers files and metadata to the Digital Library Development Center

Digital Library Development Center (DLDC)

Receives metadata and files from the DU
Arranges them in the Library Digital Repository (LDR) using the Oxford Common File Layout (OCFL)
Generates ARK identifiers and RDF triples for the files (edm:WebResource)
Creates IIIF manifests for image data
Delivers metadata with ARK identifier and RDF triples for each file to the UChicagoNode Migration Specialist

UChicagoNode Migration Specialist [1]

Ensures representation of constraints (rights, permissions, etc.) on materials in OCHRE
Remediates metadata (e.g., supply TGN values for dcterms:spatial, ISO 8601 or EDTF values for dcterms:date, Glottolog codes for dcterms:language, NAF, ISNI, VIAF for dcterms:creator, dcterms:contributor) and deposits it into OCHRE
Deposits static content into OCHRE
Adds ARK identifiers for materials as the value of dcterms:identifier in the RDF triples being generated for the RDF triplestore
Creates RDF triples from metadata and adds them with the edm:WebResource triples received from the DLDC into the RDF triplestore
Publishes metadata as XML in MarkLogic
Publishes metadata as RDF in MarkLogic

Web Designer / User Researcher

Creates Wireframes/Mockups (UChicagoNode Web Designer/User Researcher) (PI/PS sign off if custom interface) [2]
Define Actions for UChicagoNode Web Developer (UChicagoNode Web Designer/User researcher) [2]

UChicagoNode Web Developer

Creates the interface for digital collections with unique front ends [3]

PI/PS

For digital collections with custom front ends:

Establish URL for the collection
Sign off on launch

[1] For more detail, see Migration Specialist.

[2] Not needed for collections using the core interface for discovery.

[3] Other collections will use the core interface for discovery, using IIIF, Luna, etc. for delivery.