authorized_vocabularies.md

The collection registry manages provenance and non⁃provenance based collections

• provenance based collection registry
  • needs to sync/link to OAC/ArchviesSpace/MARC when already described
  • use for digitized and potentially digitizable collections
  • control harvest/crawling
  • embargo information

Vocabulary Management

Vocabularies maintained in collection registry to support non⁃provenance based collections

• institution name values (for UCs)
• locations/units at institutions (for Library and sub-unit)
• format types
• rights browse values
• contributor/creator name values
• other systemwide access points (subjects etc.)

The collection registry also needs to support the integration of external vocabularies.

Integrated use of authoratative vocabulary terms/headings from Library of Congress, Getty, Visual Resource Association, Thesaurus of Geographic Names, or locally created headings within metadata records

That does not make 100% sense; the Thesaurus of Geographic Names is one of several Getty Vocabulary Program products. VRA is a professional organization with a schema but no vocabulary that I know of.

• Library of Congress (via http://id.loc.gov/ integration?)
  • and/or FAST?
• Getty (will need to license?)
  • The Art & Architecture Thesaurus (AAT)®
  • The Cultural Objects Name Authority (CONA)®
  • The Getty Thesaurus of Geographic Names (TGN)®
  • The Union List of Artist Names (ULAN)®

---

10. Facets: Facets should serve to refine or expand search results and should be made available for the following primary metadata: title, subject, description, contributor, date, format, rights

not sure if it makes sense to facet on description because there will be so many unique values.

selected_requirements.md

The Golden Summer would be part of the DAMS with D&D from pot1_lt1a_finalreport_july2012.pdf

3. Metadata and Object Modeling

...

Integrated use of authoratative vocabulary terms/headings from Library of Congress, Getty, Visual Resource Association, Thesaurus of Geographic Names, or locally created headings within metadata records

...

Ability to link campus digital objects back to an external finding aid or collection description, through the metadata

m. Ability to associate one or more digital objects with a collection (defined by provenance, topic, etc.), through the metadata

g. Published digital objects to display full metadata records, so users have complete descriptive, rights, etc. information for an informed use of the resource.

h. Published digital objects to indicate what collection(s) they are associated with.

i. Published digital objects clearly branded with the institution name, so it's clear to end users who/where to contact for more information, which institution manages the content, etc.; URL branding is less important.

j. (2) Ability to associate campus digital objects with thematic or topically-­‐clustered curated collections in the UC Libraries Digital Collection access layer.

k. (2) A mechanism that monitors embargoed digital objects; when embargo ends, the curator is notified for further action (e.g. publish, extend embargo

Aggregation

A persistent reference for each UC campus.

...

6. The repository should appear in digital object metadata records (e.g., URI or identifier) so campuses can consistently manage and track information for the repository for the purpose of generating reports, statistics, etc.

7. Harvest digital objects using an OAI interface in order to gather all of the metadata.

8. Clearly identify that content held in federated repositories is from the contributing institution.

9. Relate objects to non-­‐provenance based collections.

discovery and display

9. Item level information: Each item in a result set should be accompanied by the following primary metadata: title, subject, description, contributor, date, format, rights.

10. Facets: Facets should serve to refine or expand search results and should be made available for the following primary metadata: title, subject, description, contributor, date, format, rights .

11. Sorting: Default sorting of search results should be by relevance; users should have option to sort by additional sorting criteria: collection, author, title, date.

Contributor / Collection Information

31. Contributing institutions: A full alphabetical list of contributing institutions should be made available, with each entry linked to a customized landing page including full contact information. The right to perform administrative activities relative to the landing page (e.g., institution contact information) should be granted to the contributing institution.

32. Collection description: A document describing the collections included in the UCL Digital Collection should be available on the site.