DC Metadata Application Profile (MAP)

DC Metadata Application Profile (MAP)



General Notes

This document provides best practices for creating and editing metadata for a wide variety of digital objects in Ohio State University Libraries’ Digital Collections (DC) platform. The metadata reflects both born-digital objects and analog objects that have been reformatted to digital surrogates. While the document provides guidance and examples for the entire platform, the Metadata Initiatives Department can provide specialized documentation to specific units and projects.

Subsequent sections of the documentation clarify the application of national and international standards that are relevant to DC metadata and list each metadata element in detail. Each metadata element is presented in a table with the following structure.

Explanation of the Metadata Elements Table

Label

The human-readable name for the metadata element.

Property

The computer-readable name of the metadata element.

Visible

An indication of whether the metadata field is visible to the public (Yes/No) or requires login access to view.

Obligation

An indication of whether a value for the metadata element is required, required-when-available, recommended, or optional.

Repeatable

An indication of whether a single value or multiple values are acceptable for the metadata element.

Description

A description of the purpose or usage of the metadata element.

CV/Syntax

Recommendations for controlled vocabularies to employ or preferred method of entering a value or values for the metadata element.

Notes

Explanations and recommendations for use of the metadata element.

Examples

Example values for the metadata element.

Metadata Standards

The DC Metadata Application Profile utilizes and is inspired by existing metadata standards.

Content Standards

Data Types

Controlled Vocabularies and Thesauri

When noted in the metadata element tables, it is recommended to utilize controlled vocabularies (CV) and thesauri for metadata values. Commonly used CVs and thesauri are listed below with acronyms in parentheses.

Related cataloging resources

Core Metadata

This section is for the most commonly used metadata fields.

Resource Type

Label

Resource Type   (Type in submission form)

Property

dcterms:type

Visible

Yes

Facet

Yes

Obligation

Required

Repeatable

Yes, but discouraged

Description

The primary nature or genre of the described resource.

CV/Syntax

DCMI Type Terms (Collection; Dataset; Event; Image; Interactive Resource; Moving Image; Physical Object; Service; Software; Sound; Still Image; Text)

Notes

  • Type is intended as a broad categorization, not a more granular term like format or genre.

  • Select the appropriate value(s) that best corresponds to the digital object.

  • Select "Text" for scanned images of textual materials.

  • Select "Image" for musical notation.

  • Note: OSU has traditionally used "Image" instead of "Still Image". However, motion pictures, including videos should be entered as "Moving Image".

Examples

  • "Text"

  • "Image"

Title

Label

Title

Property

dc:title

Visible

Yes

Facet

No

Obligation

Required

Repeatable

No

Description

The primary name given to the described resource.

CV/Syntax

n/a

Notes

  • When possible, refer to content standards, e.g. RDA, CCO, for the formulation of titles.

  • When supplying a title for an untitled work, the title should be concise. The Abstract and Descriptions fields should be used for more detail.

  • Descriptive and informative titles are preferred whenever possible (as opposed to values like “unknown” or an id number).

  • Omit leading articles, e.g. The, A, and An.

  • Capitalize proper nouns.

  • The use of square brackets for devised titles is discouraged.

  • Enter parallel, variant, and translated titles in Alternative Title.

  • If the work is part of a Series, enter the Series title followed by a period a space and, then, the individual work's title ("Series title. Individual title"). If there is no individual title for the work, use a caption on the work as the individual title ("Series title. Caption title"). In the case of comic strips with a caption in a speech balloon, enter individual title with quotation marks (e.g. Sacramentans. “There goes the richest man in Sacramento – He’s really got it made!”).

Examples

  • "Noyon (Oise) La rue de Paris au fond la cathédrale" (example record)

  • "McKinley’s Own : march" (example record)

  • "Development of the yuppie social conscious"

  • "House Resolution 1277 summary"

Alternative Title

Label

Alternate Title

Property

dcterms:alternative

Visible

Yes

Facet

No

Obligation

Optional

Repeatable

Yes

Description

Any alternative title for the described resource, including abbreviations and translations.

CV/Syntax

n/a

Notes

  • When possible, refer to content standards, e.g. CCO, RDA, for the formulation of titles.

  • Each alternative title should be a separate entry.

  • Omit leading articles, e.g. The, A, and An.

  • Capitalize proper nouns.

  • The use of square brackets for devised titles is discouraged.

Examples

  •  "Noyon (Oise), The Rue de Paris, the cathedral in the background" (example record, translated title)

Creator

Label

Creator

Property

dc:creator

Visible

 Yes

Facet

 Yes

Obligation

 Required, if available

Repeatable

 Yes

Description

 The person or group primarily responsible for the creation of the work.

CV/Syntax

 LCNAF; ULAN; VIAF; HAF Persons, Families, and Organizations

Notes

  • If a personal name is not in a CV, enter the name in inverted order with life/death dates if known, e.g. "Smith, John, 1900-1990".

  • If creator is unknown, do not enter anything.

  • In interview situations, the interviewee is the creator.

Examples

  • "King, Karl, 1891-1971" (example record, composer)

  • "Caniff, Milton Arthur, 1907-1988"

  • "Keystone View Company"

Contributor

Label

Contributor

Property

dc:contributor

Visible

Yes

Facet

No

Obligation

Optional

Repeatable

Yes

Description

A person or group responsible for making secondary contributions to the work.

CV/Syntax

LCNAF; ULAN; VIAF; HAF Persons, Families, and Organizations

Notes

  • If a personal name is not in a CV, enter the name in inverted order with life/death dates if known, e.g. "Smith, John, 1900-1990".

  • In interview situations, the interviewer is the contributor.

Examples

Genre

Label

Genre

Property

vra:worktype     (Note: corresponds to VRA 4.)

Visible

Yes

Facet

Yes

Obligation

Recommended

Repeatable

Yes

Description

A term or terms that designate a category characterizing a particular style, form, or content, such as artistic, musical, literary composition, etc.

CV/Syntax

LCGFT; RBMS Genre Terms; Getty AAT; TGM

Notes

Genre often refers to what the item is regardless of whether it is in a physical or digital format.

Examples

Language

Label

 Language

Property

 dc:language

Visible

 Yes

Facet

 Yes

Obligation

 Required, if available

Repeatable

 Yes

Description

 The language(s) of the work's content.

CV/Syntax

 ISO 639-2 language code

Notes

  • Enter language terms for any written text and/or languages spoken.

  • If there is no written text or language spoken, do not enter a language term.

  • If both a bibliographic and terminology code are available, the terminology term is preferred. 

Examples

Publisher

Label

 Publisher

Property

 dc:publisher

Visible

 Yes

Facet

 Yes

Obligation

Recommended

Repeatable

 Yes

Description

 The person or group making the work available in a formal publication process.

CV/Syntax

 LCNAF; VIAF

Notes

  • Contrary to prior practice, do not enter OSUL or any of its units in this field.

  • The publisher is different from the name of the publication, e.g. newspaper name.

  • For audiovisual resources that have been broadcasted, the broadcaster (e.g. radio station, TV station) is the publisher.

Examples

    Logo of The Ohio State University

    If you have a disability and experience difficulty accessing this content, please contact the Libraries Digital Accessibility Coordinators.