MIT Libraries
...
Dome Collections
...
Team members:
Ann Whiteside
Jolene Deverges
Tom Rosko
Liz Andrews
Ur-Core Element Set
...
DomeCore Metadata Element Set
Approved by the Metadata Coordinating Group: 17 August 2010
approved document
| Excerpt |
|---|
The purpose of this document is to help support the common digitization needs of the MIT Libraries. Metadata needs vary from collection to collection, and sometimes project to project. Decisions about metadata are often made by the individuals who create it, with consideration for the requirements of the project and/or the cataloging system used to capture the metadata. These objects and the associated metadata are typically deposited into Dome, where the metadata decisions have lasting impact on the usefulness of the repository. Combining these various collections/projects often adds additional metadata requirements needed for interoperability within the shared system. |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
DomeCore Defined
DomeCore establishes a minimum standard for descriptive metadata used for resources in Dome. DomeCore is a set of seven metadata elements that are common across the various digital resources/collections of the MIT Libraries. It is recommended that it be mandatory for all digital objects being deposited into Dome have the proper metadata to fulfill the needs of this common element set. DomeCore is a starting point for the application of metadata standards in Dome digital collections. A digital resource/collection may require additional metadata elements based on format, genre, provenance or management needs.
The DomeCore element set was defined by the members of the Dome metadata strike force as the initial phase of their charge to develop a set of recommended standards and guidelines to govern future metadata creation within Dome. Future phases will include a core set of elements for each type of object (audio, video, datasets, ect.) that may one day be deposited into Dome.
Objectives for an DOMEcore Element Set
- To mediate translation from one metadata standard to another and from one system to another
- To govern the aggregation of different kinds of metadata in the same systems.
- To enable the archiving and preservation of digital objects through their lifecycle.
- To ensure a consistent, high level of quality metadata across collections
We recognize that these elements could describe either:
- The intellectual content of the information resource
- A physical object containing the intellectual content
- A digital object containing the intellectual content
The DomeCore elements describe the intellectual content of the information resource. In describing the intellectual content we will sometimes describe the content as an object (when was the content created, where, by whom), and other times analyze the subject of the content (date of a performance advertised in a broadsheet, a place described by a travel book, or a person that is the subject of a portrait). In selecting DomeCore elements we attempt to describe the object. Only the “Name” and “Notes” fields describe the subject.
DomeCore Element Set
The previous version of this element set and crosswalks can be found here
DomeCore Element | Definition |
Identifier | A globally unique, persistent name/code/uri for the resource. |
Rights | Information about the copyright status and the rights holder for the resource. |
Name | The title or identifying phrase given to the resource. May be title proper, statement of identification, or a brief description. |
Agent | Name of the primary agent (person, corporate body, group, institution, organization) responsible for the creation of the content of the resource. |
Date | Date or date range associated with the creation of the content of the resource. |
Type | The genre or format/medium of the content of the resource. |
Notes | A brief free-text note or descriptive statement that characterizes more fully than the title the scope or content of the resource. |
*Type in DSpace - Archival material, Article, Conference Proceeding, Book, Book chapter, Dataset, Image, Learning Object, Other, Plan or blueprint, Preprint, Presentation, Recording, acoustical, Software, Technical Report, Thesis, Video, Working Paper
DomeCore Crosswalks
DomeCore | DCterms:element (What we would like to use in DOME) | DCterms:element*(DSpace Name) | VRA Core 4.0 path(IRIS Field Name) | MODS path(AT Field Name) | MARC |
Identifier |
| dcterms:identifier (dc.identifier.none; dc.identifier. uri) | vra:image/id | mets: mets@OBJID=“IDENTIFIER” | 035 |
Rights |
| dcterms:rights (dc.rights.none) | vra: rights/text | mods:accessCondition type=”useAndReproduction” | 506 |
Name |
| dcterms:title | vra: work/title | mods:titleInfo/title | 245 |
Agent |
| dcterms:creator (dc.contributor.author) | vra: agent/name | mods:name/role/@roleTerm = Creator | 100 |
Type |
| dcterms:type | vra: work/worktype | mods: genre | 655 |
Date |
| dcterms:date (dc.date.issued) | vra: date@type="creation" | mods:origInfo/datecreated | 260c |
Notes |
| dcterms:description (dc.description.none) | vra: description | mods:abstract@displayLabel=”Abstract” | 520 |
* based on DSpace behavior, not Dome
Other Elements Considered for DomeCore
Many elements discussed by the task force did not qualify as core elements. Each of the elements below may be very important to a specific collection, project, or item, and should be included in the metadata of an object, when needed.
- Access restrictions: Information about restrictions imposed on access and use of a resource
- Relationships: Aggregation; Peer-to-peer
- Subject Analysis: Dates associated with what is depicted in the content of the resource; People and locations associated with the resource (depicted/described/created); Additional Agents; Topics
- Language
- Descriptions of the physical and digital versions of the resource: The location depicted in the physical resource
- Dimensions
- Format
- Provenance: Source
- Custodianship: Name of the owning institution and/or the institution responsible for providing access to the resource
Format and Genre DomeCore Elements
Digital Collections Metadata Application Profile (DRAFT)
Element Name | Element Description |
|
|---|---|---|
Title |
|
|
Name |
|
|
Location |
|
|
Date |
|
|
Language |
|
|
Relation |
|
|
Copyright |
|
|
Usage rights |
|
|
Notes |
|
|
DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT
------------
Disc notes 2009-04-29
What labels to use for these elements? Tom mentioned using DC
What kinds of metadata? Descriptive, Administrative. Not Preservation
Selina -- Can we focus on one or the other first?
What are the kinds?
Description
Description
Subject Analysis
Administration
Technical
| Wiki Markup |
|---|
Preservation \[Technical, Provenance, Rights\] |
(Administrative)
Rights
Tom -- Can we point to a purpose for each element? Rob -- Use cases for each element would be good.
Isn't DC the Ur-core?
Nina -- What is the stripped down set of elements that belong in each record.
Rob -- DC is put forth as a common language for sharing metadata. We may decide the DC is how we will express and share metadata, but we need to choose our own elements.
------------
This page has been created to capture the discussion and recommendations of the DOME Advisory Committee Metadata Strikeforce as they attempt to reach consensus regarding the design of metadata structures in DOME.
Topics of discussion include:
Data Models (Both Content Models and Information Models)
Property Semantics
Value Syntax
Application of Metadata Standards (Element Sets, Serializations, Cataloging Standards)
...