Preparing Collections for UChicagoNode
Table of Contents
Before starting, see Digital Collections Working Group: Project Proposal Form.
1. Overview
| Who | What | Where |
| Project Manager | Make sure the following steps are done | Digital Library Development Center |
| Rights Assessment Librarian | Rights Assessment | |
| Project Manager & Stakeholder | Interface Assessment: core/generic, custom, IIIF, Luna | |
| Project Manager & Stakeholder | Create collection description | |
| Project Manager & Stakeholder | Create entry for the Digital Collections and Exhibits page on the Library's main website | Web Administration |
| Digitization Manager, Digitization Specialists, and Digitization Assistants | Digitize materials | Digitization Unit |
| Metadata Specialist and metadata assistants (student staff) | Create metadata | Digitization Unit |
| Digital Preservation Specialist | Generate information for WebResource RDF triples | Digitization Unit |
| Digital Preservation Specialist | Generate ARK identifiers for digitized materials (data) | Digitization Unit |
| Digital Preservation Specialist | Create IIIF manifests if applicable | Digitization Unit |
| Digital Preservation Specialist | Create Submission Information Packages (SIPs) using BagIt from data and metadata for the OCHRE Data Service and the Digital Library Development Center | Digitization Unit |
| Migration Specialist | Create table of ARK identifiers and URLs they point to | OCHRE Data Service |
| Migration Specialist | Update ARK identifier table | OCHRE Data Service |
| Migration Specialist | Remediate metadata if necessary | OCHRE Data Service |
| Migration Specialist | Add metadata to OCHRE | OCHRE Data Service |
| Migration Specialist | Add collection description to OCHRE | OCHRE Data Service |
| Migration Specialist | Publish metadata as XML and RDF triples | OCHRE Data Service |
| Library Digital Repository Manager | Use SIPs to add data and metadata to Library Digital Repository OCFL file structure (AIPs) | Digital Library Development Center |
| Web Designer / User Researcher | Create wireframes/mockups for collection if not using Node core/generic interface | Digital Library Development Center |
| Web Developer | Code web front end if not using Node core/generic interface | Digital Library Development Center |
| Project Manager & Stakeholder | Sign off on launch |
2. Notes
2.1. Project Manager
Designate a project manager or project coordinator, who will be responsible for making sure the following tasks are done.
Who: Director of Digital Collections
2.2. Rights Assessment
Perform a rights assessment on the proposed collection. Rights and permissions include copyright, performance rights, deposit agreements with donors, ethical considerations (e.g., the rights of contributors in linguistic or ethnographic surveys, photographic collections, etc.). Record the results of the assessment for future reference.
Who: Rights Assessment Librarian
2.3. Digitize Materials
This will either be done in house or vended out. The Digitization Unit may act as a consultant on how to do the work.
Who: Digitization Manager (Digitization Specialists, Digitization Assistants)
2.4. Create Metadata
All collections require minimal metadata for preservation and discovery, and may benefit from very rich metadata for discovery and display.
For preservation, minimal metadata include title OR description OR BOTH title and description, date, and identifier. Metadata may include other fields as well. Here is an example:
title: University of Chicago Magazine
date: 1922-01-31
identifier: mvol-0002-v014-i09
relation: 14:9
description: The alumni magazine of the University of Chicago.
description: Missing p. 5.
For discovery, the following are the required elements:
title or description or both.
date. Values are expressed according to ISO 8601-2019[https://www.iso.org/standard/70907.html], falling back to EDTF[https://www.loc.gov/standards/datetime/] as needed.
identifier. String-literal values for locally-created ARK identifiers are used, e.g., “https://n2t.net/ark:61001/z9m865s34c01”. Note: uchicago:identifier may be used for any original identifiers occurring in provided metadata.
language for TEXT objects and for other object types if there is a language aspect. Language codes conforming to ISO 639-3:2007[https://www.iso.org/standard/39534.html] are used as values.
spatial. Values from Getty’s Thesaurus of Geographical Names (TGN) are used.
type. Values should be drawn from the “DCMI Type Vocabulary”.[https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7] These are Collection, Dataset, Event, Image, InteractiveResource, MovingImage, PhysicalObject, Service, Software, Sound, StillImage, Text. “Note that digital representations of, or surrogates for, [PhysicalObject] should use Image, Text or one of the other types.”
Who: Metadata Librarian and metadata assistants (student staff)