-
Notifications
You must be signed in to change notification settings - Fork 2
Glossary
Information used to manage a collection, such as how it was created, access rights, and policies.
Archival information package.
Archival collections are based on provenance, all the content is generated by or otherwise comes from a single person, family, or organization. The content is generally unique. Archival collections are generally described at aggregate levels which may be a series (a related subset of content), box, or folder level.
A collection is an intentional grouping of materials that have associated metadata and usually a workflow. Collections may be archival, library, or curated. All works must have a designated primary collection, child works will inherit properties and requirements, such as whether or not master files (within filesets) should be exposed to the public. Collections may be ordered, though it is not necessary.
Curated collections are intentionally gathered content around a topic or theme. Curated collections include discrete works from multiple archival or library collections. Curated collections may not serve as a primary collection. Curated collections have no workflow.
Contains all the pertinent information about every kind of metadata field in CHO. This includes descriptive, administrative, as well as technical metadata.
Information about an individual collection or work such as its title and creator.
Dissemination information package.
Governs the visual representation of a work and its files. This could contain concepts associated with a DIP.
Classification of a file's digital content, such as text, image, or audio. This will most often be the mime type.
Library collections are based on traditional, librarian-selected, published, non-archival content. Collections may include digitized or born-digital content that is described in the library catalog.
A single instance of a term found in the data dictionary. It contains all of the same properties as the dictionary term, but with additional modifications such as changes to its display properties, validation, or controlled vocabulary.
A grouping of one or more metadata fields, in a specific order, that are assigned to a given work type and used as properties for any number of works.
A set of operations and procedures applied to the files contained in a work. This could contain concepts associated with an AIP.
Submission information package.
Information about the aspects of an individual file, such as its size, composition, and digital structure.
The concrete, real-world data that represents an instantiation of a work type.
Set of actions applied to works when they are added to collections. Every work must have a workflow, but that workflow is determined by the collection to which the work is added.
A generic model of a kind of work. It encompasses the concept of a SIP, but it is defines the metadata, display, and processing schemas that apply to a given work.
- Home
- About
- Resources
- Metadata
- Management
- Batch Management
- Development
- Accessibility