You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »

MIT Libraries DOME Collections Ur-Core Metadata Element Set

Team members:

Ann Whiteside          Jolene Deverges          Tom Rosko         Patsy Baudoin

Liz Andrews             Selina Wang                Robert Wolfe      Nina Davis-Mills

Beverly Turner              Carl Jones

Ur-Core Statement of Principles (DRAFT)

The members of the DOME metadata strike force were charged to review and document the current metadata conventions for digital libraries, and to develop a set of recommend standards and guidelines to govern future metadata creation within DOME. The outcome of this research will be a core set of elements for each type of object (audio, video, etc.) that may one day be deposited into DOME. In addition, the strike force developed Ur-Core, a common set of elements that all objects require, regardless of type, collection, or project. We recommend that it be mandatory for all digital objects being deposited into DOME to have the proper metadata to fulfill the needs of this common element set.

Objectives for an Ur-Core Element Set

  1. To mediate translation from one metadata standard to another and from one system to another
  2. To govern the aggregation of different kinds of metadata in the same systems.
  3. To enable the archiving and preservation of digital objects through their lifecycle.
  4. To ensure a consistent, high level of quality metadata across collections

We recognize that these elements could describe either:

  1. The intellectual content of the information resource
  2. A physical object containing the intellectual content
  3. A digital object containing the intellectual content

The Ur-Core 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 Ur-Core elements we attempt to describe the object. Only the “Name” and “Notes” fields describe the subject.

Ur-Core Element Set

   The previous version of this element set and crosswalks can be found here

Ur-Core 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

Ur-Core Crosswalks

Ur-Core

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
(Image Record: Image_No)

mets: mets@OBJID=“IDENTIFIER”
(DO Resource Record: Digital Object  ID)

035
086
020
022
027
088
010
024
856

Rights

 

dcterms:rights (dc.rights.none)

vra: rights/text
(Image Record: Image_Copyright)

mods:accessCondition type=”useAndReproduction”
(DO Resource Record:  Intellectual Property Rights note)

506
540

Name

 

dcterms:title
(dc.title.none)

vra: work/title
( Work Record: cPreferred_title)

mods:titleInfo/title
(DO Resource Record:  Title)

245

Agent

 

dcterms:creator (dc.contributor.author)

vra: agent/name
(Work Record: Free_Text_Agents_Display (agent name, agent culture, agent dates))

mods:name/role/@roleTerm = Creator
mods:name/displayForm
(DO Resource Record:  Name, function= “Creator”, role=blank)

100
110
111
700
710

Type

 

dcterms:type
(dc.type.none)

vra: work/worktype
(Work Record: WorkType)

mods: genre
(DO Resource Record:  Subject)
mods:typeOfResource
(DO Resource Record:  Object Type)

655
Leader/06

Date

 

dcterms:date (dc.date.issued)

vra: date@type="creation"
Start/End Year
(Work Record: CCO_Date_Display)

mods:origInfo/datecreated
(DO Resource Record:  Date Expression)

260c

Notes

 

dcterms:description (dc.description.none)

vra: description
(Image Record: View_Title (concatenate Label_View_Type, View_Title, and View_Date))

mods:abstract@displayLabel=”Abstract”
(DO Resource Record:  Abstract note)

520

* based on DSpace behavior, not DOME

Other Elements Considered for Ur-Core

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

Domain and Genre Metadata Core Element Sets

Genre Metadata

Video Metadata

Audio Metadata

Datasets Metadata

Reference sites:

http://guides.lib.virginia.edu/content.php?pid=40437&sid=316002

http://guides.lib.virginia.edu/content.php?pid=40437&sid=316020#title

http://www.cdlib.org/inside/diglib/guidelines/dmdreqs.html#dmddescription

Search Indexes

Dome search indexes:

search.index.1 = author:dc.contributor.*
search.index.2 = author:dc.creator.*
search.index.3 = title:dc.title.*
search.index.4 = keyword:dc.subject.*
search.index.5 = abstract:dc.description.abstract
search.index.6 = author:dc.description.statementofresponsibility
search.index.7 = series:dc.relation.ispartofseries
search.index.8 = abstract:dc.description.tableofcontents
search.index.9 = mime:dc.format.mimetype search.index.10 = sponsor:dc.description.sponsorship
search.index.11 = identifier:dc.identifier.*
search.index.12 = coverage:dc.coverage.*
search.index.13 = type:dc.type
search.index.14 = format:dc.format.*
search.index.15 = description:dc.description

DSpace search indexes:

search.index.1 = author:dc.contributor.author
search.index.2 = author:dc.creator.*
search.index.3 = title:dc.title.*
search.index.4 = keyword:dc.subject.*
search.index.5 = abstract:dc.description.abstract
search.index.6 = author:dc.description.statementofresponsibility
search.index.7 = series:dc.relation.ispartofseries
search.index.8 = abstract:dc.description.tableofcontents
search.index.9 = mime:dc.format.mimetype search.index.10 = sponsor:dc.description.sponsorship
search.index.11 = identifier:dc.identifier.*
search.index.12 = advisor:dc.contributor.advisor
search.index.13 = department:dc.contributor.department
search.index.14 = author:dc.contributor.editor
search.index.15 = author:dc.contributor.illustrator
search.index.16 = other:dc.contributor.other

Kinds of Metadata

  • Descriptive
    • Description
    • Subject Analysis
  • Administrative
  • Structural Metadata
  • Technical
  • Provenance
  • (Metametadata)
  • Rights

  • Preservation [Technical, Provenance, Rights]

  • No labels