This repository has been archived by the owner on Jan 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Metadata
Nathan Tallman edited this page Oct 12, 2018
·
14 revisions
- Metadata schemas are at the work-type level.
- Core fields will be applied to all work-types and collection objects
- The data dictionary will contain all the possible fields and their properties. Work-type metadata schemas pull fields from the data dictionary and store customizations for that work-type. Fields can also be pulled from the data dictionary and added to individual works as needed.
- In MVP metadata is either editable (descriptive) or non-editable (administrative, technical, rights, etc.)
- Controlled vocabularies will pull from source on regular basis and cached in CHO for MVP. (1.0+ will use a triple store)
- Locally controlled vocabularies will be controlled outside of CHO and managed via input guidelines for data entry and metadata quality control. (Terms already used in the same field for the same work type can be auto-suggested based on SOLR, but that is not-MVP.)
- Batch loads of metadata are handled via CSV. These requirements are in-flux and best documented with the file specifications as part of import.
- Fileset titles are derived from filenames if there is no supplied title in CSV or if there is no CSV (GUI uploads). There should always be a title when loaded via CSV but needed to have a title for GUI uploads.
- Home
- About
- Resources
- Metadata
- Management
- Batch Management
- Development
- Accessibility