MIT Libraries

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

borderColor	#31849b
bgColor	White
borderWidth	3
borderStyle	solid

Table of Contents

minLevel	3

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.

Description of what makes an element a core element

Ur-Core Element Set

DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT

Element Name	Question?	Examples we thought of	Element Description
Identifier	How do I know I have the right item? How do I get the item?	Handles, infoURIs, homegrown URIs	A globally unique, persistent string.
Rights	Who can use it? What is it's copyright status?	Copyright, Usage rights
Name	What is it?	Title, Caption	Title proper, parallel title, alternative title, or other title information. Descriptive title, a statement of identification (item is known as...) can include a combination of values from other elements; Also known as a "caption;" short explanantion, or description accompanying a digital object.
Agent	Who did it?	Corporate, Personal, Creator, Contributor, Role	A person, organization, or service responsible for the content creation of the resource. Catch-all for unspecified contributors.
Location	Where do the libraries keep store it? Where was it made?	Repository Location, Location Created, Location Depicted	when was it made who can use it what is the copyright, what is the location being depicted, where do the libraries keep it, how was it made
Date	When was it made?	Date material was created, Date depicted, Date Event,
Type	How was it made?	Genre, Medium, Format, (Image, Text, Audio, Video, Data)
Repository	Who can use it? Where to find it	Repository holding material	Entity responsible for providing intellectual access to materials
Notes		Description, Abstract
Not Quite Ur-Core
Relation Is a core element for object in hierarchy	What is it a part of?	Collection, Components, Items in Other Collections	If object is part of a larger collection to show its place in the collection; or if a digital object itself is a complex digital object, relation of each file to the whole object.
Language	What language is it written it?
Subject	What is the location depicted/described? Who is depicted/described? What is the date depicted/described?

DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT

------------

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

Wiki Markup
Preservation \[Technical, Provenance, Rights\]

Domain Metadata Mapping

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
(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

Metadata Element

Qualifier

DC Terms

MARC

VRA Core 4.0

EAD (used for Finding Aids)

Archivists' Toolkit (Digital Object Module)

METS

contributor

(null)

dcterms: contributor

111,711

contributor

advisor

—

contributor

author

100,110,700

—

contributor

department

710

contributor

editor

—

contributor

other

—

contributor

illustrator

—

contributor

creator

100, 110, 111

Agents (agent name, agent culture, agent dates)

creator

100, 110, 111

origination (if more than one, pick one for MARC)

sortName (role:creator)

identifier

(null)

identifier

digitalObjectId

fileVersionId

sequence

identifier

oclc

035

identifier

govdoc

086

identifier

isbn

020

identifier

issn

022

identifier

sici

identifier

ismn

identifier

other

strn(027,088)

Record number

identifier

uri

856

unitid

metsidentifier,
fileVersions uri,

identifier

citation

bibliographicCitation

524

prefercite

preferred citation note (maps to dc.description)

identifier

fileVersions use statement

language

iso

Language

041

langmaterial

languageCode

description

(null)

description

500,513

View title, Work Description

description

abstract

520

abstract

abstract note

description

provenance

541

acqinfo

Immediate Source of Acquisition note (maps to dc.source)

description

sponsorship

536(funding)

sponsor

description

statementofresponsibility

description

545

bioghist

Biog/Hist note

description

520

scopecontent

scope & content note

description

500

odd, note

general note note

description

tableofcontents

tableOfContents

505

description

uri

852, 856

repository, archref

RepositoryName, (?)repository uri (maps to description?)

description

degree

date

(null)

date

Date

date

accessioned

date

available

date

copyright

dateCopyrighted

260

date

created

245

Start/End Year

unitdate

dateExpression or dateBegin, dateEnd

date

issued

date

submitted

dateSubmitted

subject

(null)

subject

600, 610

Subject

controlaccess, persname, famname role=subject

sortName
(role: subject)

655

controlaccess,
genreform

subjectTerm
type=genre/form
(maps to dc.type)

657

controlaccess,
function

subjectTerm
type=function

651

656

controlaccess,
occupation

subjectTerm
type=occupation

650

controlaccess,
subject

subjectTerm
type=topical

630

controlaccess,
uniform title

subjectTerm
type=uniform title

subject

classification

subject

ddc

subject

lcc

subject

lcsh

600,610,650,651

Subject

subject

mesh

subject

other

Culture

subject

cip

title

(null)

title

245

Title (primary)

unittitle

title

245

label

title

alternative

130,210,240,242,246,730,740

Title (variant)

format

(null)

format

Technique

254, 255, 256

materialspec

material specifics details note

300

physfacet

physical facet note

format

extent

300

dimensions

dimensions note

format

medium

Material

phystech

physical characteristics & technical requirements

format?

support

Material

format

mimetype

publisher

(null)

publisher

relation

(null)

relation

Relation_Type

544

relatedmaterial

related archival material note

relation

isformatof

isFormatOf

"Model for"

Relation?

hasformat

hasFormat

"Model is"

Relation?

isplanof

"Plan for"

Relation?

hasplan

"Plan is"

Relation?

isstudyof

"Study for"

Relation?

hasstudy

"Study is"

relation

ispartof

isPartOf

856

"Component of"

(Collection number)
ResourceIdentifier 1
ResourceIdentifier 2

relation

ispartofseries

relation

haspart

hasPart

"Component is"

relation

isversionof

isVersionOf

"Copy after"

fileVersions digital object title

relation

hasversion

hasVersion

"Copy is"

relation

isbasedon

relation

isreferencedby

isReferencedBy

relation

requires

relation

replaces

relation

isreplacedby

isReplacedBy

relation

uri

Related_Work_No

archref

parent resource title, eadFaLocation

535

originalsloc

Existence and location of originals (maps to dc.source)

rights

(null)

rights

uri

rights

access

accessRights

506

Image_Rights Statement

accessrestrict

conditions governing access note

rights

copyright

540

Image_Copyright

userestrict

conditions governing use note

*type

(null)

type

008

WorkType

objectType

coverage

temporal

'Period

coverage

spatial

Location

controlaccess, geoname

...

)	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 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)

Child pages

Versions Compared

Old Version 48

New Version Current

Key

MIT Libraries

Dome Collections

DomeCore Metadata Element Set

Domain and Genre Metadata Core Element Sets

Ur-Core Statement of Principles

DomeCore Defined

Objectives for an DOMEcore

Element Set

Description of what makes an element a core element

Ur-Core Element Set

Search Indexes

Kinds of Metadata

Domain Metadata Mapping

DomeCore Element Set

DomeCore Crosswalks

Other Elements Considered for DomeCore

Format and Genre DomeCore Elements

Digital Collections Metadata Application Profile (DRAFT)

Child pages

Page History

Versions Compared

Old Version 48

New Version Current

Key

MIT Libraries

Dome Collections

DomeCore Metadata Element Set

Domain and Genre Metadata Core Element Sets

Ur-Core Statement of Principles

DomeCore Defined

Objectives for an DOMEcore

Element Set

Description of what makes an element a core element

Ur-Core Element Set

Search Indexes

Kinds of Metadata

Domain Metadata Mapping

DomeCore Element Set

DomeCore Crosswalks

Other Elements Considered for DomeCore

Format and Genre DomeCore Elements

Digital Collections Metadata Application Profile (DRAFT)