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.

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".

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.

Examples

  •  News Syndicate Co., Inc. (New York, N.Y.)

Date Metadata

This section is for providing date(s) associated with the work. If you are not sure which date field to use, consult the MI_Record_Date_Decision_Flowchart_Simple.pdf.

Date Created

Label

 Date Created

Property

 dcterms:created

Visible

 Yes

Facet

 No

Obligation

 Required, if available

Repeatable

 Yes

Description

 The date on which the work was created.

CV/Syntax

W3C Date Time Format (DTF); Extended Date Time Format (EDTF)

Notes

  • For exact dates, follow W3C DTF, i.e. YYYY, YYYY-MM, or YYYY-MM-DD.

  • For approximate and uncertain dates, use EDTF.

  • For date ranges, use EDTF.

  • Do not enter dates as text, e.g. “Undated”.

  • If work is published, the date of publication should be entered in Date Issued instead.

Examples

  • "1969"

  • "1972-12-17"

  • "1915/1918" (for date range of 1915-1918, example record)

Date Issued

Label

Date Issued

Property

dcterms:issued

Visible

Yes

Facet

No

Obligation

Required, if available

Repeatable

Yes

Description

The date(s) on which the work was issued, e.g. published.

CV/Syntax

W3C Date Time Format (DTF); ; Extended Date Time Format (EDTF)

Notes

  • Do not enter dates as text, e.g. “Undated”.

  • Do not enter approximate or uncertain dates.

  • Do not enter date ranges.

  • If the work was not formally published or distributed, use Date Created instead.

  • If the work has a copyright date associated with it, enter that information in Date Copyrighted.

Examples

  • "1972-12-17" (when year, month, and day are known)

  • "1972-12" (when only year and month are known)

  • "1972" (when only year is known)

Date Copyrighted

Label

Date Copyrighted

Property

dcterms:dateCopyrighted

Visible

Yes

Facet

No

Obligation

Required, if available

Repeatable

Yes

Description

The date(s) on which the work was copyrighted.

CV/Syntax

W3C Date Time Format (DTF)

Notes

  • Date should be derived from a copyright statement indicated on the work.

  • Enter date as YYYY.

Examples

"1972"

Date

Label

 Date

Property

 dc:date

Visible

 Yes

Facet

 No

Obligation

Required, if available

Repeatable

 Yes

Description

A point or period of time associated with an event in the lifecycle of the resource.

CV/Syntax

W3C Date Time Format (DTF); Extended Date Time Format (EDTF)

Notes

Only use this field if there is a date associated with the work that does not conform to the criteria of creation, publication, or copyright of that work.

Examples

  • "1939/1941" (An example of mittens as an artifact of a scientific expedition where only the dates they were worn are known. The artifact's creation date is unknown. However, the dates of use are relevant to the collection.)

  • "1972-06-04" (An example of original comic strip art where the date of creation is unknown. However, the creator indicated the planned date of publication on the work.)

Description Metadata

This section is for providing more descriptive details about the work.

Summary

Label

Summary

Property

dcterms:abstract

Visible

 Yes

Facet

 No

Obligation

 Recommended

Repeatable

 Yes

Description

 An explanation of the work’s content.

CV/Syntax

 n/a

Notes

This could be a summary of the textual content of the work, a description of the picture's imagery, or an explanation of the content in audio and moving images (e.g. plot summary for fictional works or conversation points for interviews).

For publicly accessible DC records, populate the Summary field (decterms:abstract) to support the University’s Digital Accessibility Policy (https://das.osu.edu/sites/default/files/2020/11/policy-final-digital-accessibility-20210518.pdf).

Examples

  •  "Heavily damaged homes along a street in Noyon, France, with a view of the equally damaged cathedral in the background." (example record)

Description

Label

 Description

Property

dc:description

Visible

Yes

Facet

No

Obligation

Optional

Repeatable

Yes

Description

Describe or note other aspects of the work that are not appropriate to the Summary or other fields.

CV/Syntax

n/a

Notes

  • Use for any metadata that does not conform to an existing metadata field which can be displayed to the public.

  • May denote information that is lacking in this field, e.g. "Work is undated."

Examples

  • "Round white sticker affixed with identifier R 5045." (example record)

Version

Label

Version

Property

bibframe:version

Visible

Yes

Facet

No

Obligation

Optional

Repeatable

Yes

Description

Use for denoting different versions of a work.

CV/Syntax

local CV to be developed

Notes

BIBFRAME usage indicates "Term or terms that identify works such as arranged for music, vulgate for religious work, etc."

Examples

  • original art

Staff Notes

Label

Staff Notes

Property

local field

Visible

No

Facet

No

Obligation

Optional

Repeatable

Yes

Description

Internal notes that should only be accessible to logged in users.

CV/Syntax

n/a

Notes

Do not put any confidential information related to the work.

Examples

  • "Record created by Annamarie Klose."

Format Metadata

This metadata describes the work in terms of its physicality, digital aspects, dimensions, etc.

File Format - formerly Format

Label 

File Format

Property 

dc:format

Visible 

Yes

Facet

Yes

Obligation 

Required if available

Repeatable 

Yes

Description 

The file format(s) of the work whether born-digital or digitized from an analog source.

CV/Syntax 

IANA Media Types

Notes 

  • This field has traditionally been used by OSUL for the format of the physical objects and/or digital objects. However, the format of physical objects will be moved to Medium.

  • Files stored in the record only for administrative purposes, e.g. vendor-generated XML files, should not be indicated in the field.

Examples 

  • application/pdf

  • image/tiff

Medium

Label

Medium

Property

dcterms:medium

Visible

Yes

Facet

Yes

Obligation

Recommended

Repeatable

Yes

Description

The material or physical carrier of the resource.

CV/Syntax

 

Notes

  •  This field is about the physicality of analog objects.

  • For digitized images, is the work reformatted from a print, negative, or other format? In unusual cases, the work may be reformatted several times, e.g. digitized version of a microfilm of a print. In that case, each analog object represented by the work should be addressed in this field as separate terms. In addition, it is helpful to explain the relationship between these formats in Description.

Examples

Extent

Label 

 Extent

Property 

 dcterms:extent

Visible 

 Yes

Facet

 No

Obligation 

 Optional

Repeatable 

 Yes

Description 

 The size or duration of the resource.

CV/Syntax 

 n/a

Notes 

  • Follow RDA or CCO standards for consistency.

  • For still images, RDA 3.5.3.2. states, "Record dimensions of still image by using the measurements of the pictorial area. Record the height × width, diameter, or other dimensions, as appropriate, and give the dimensions with reference to the position in which the image is intended to be viewed. When recording dimensions other than height × width of a rectangle, indicate what is being measured."

  • May list with qualifiers, e.g. "Outer dimensions: # x # cm" and "Inner dimensions: # x # cm".

  • Three-dimensional carrier: height x width x depth

Examples 

  • "8 x 10 cm" (example record, dimensions of photograph)

  • "125 pages"

  • "3 photographs"

  • "29 min., 20 sec."

  • 4 x 4 x 5 cm

Relationship Metadata

This metadata relates the work to its collection, other works, and related information.

Repository

Label

Repository

Property 

foaf:basedNear

Visible

 Yes

Facet

 No

Obligation 

 Required, if available

Repeatable 

 No

Description 

The name of the repository where the original resource is located.

CV/Syntax 

 LCNAF

Notes 

  • For reformatted works, only indicate repository if the item is physically held by OSUL.

Examples 

  •  "Ohio State University. Billy Ireland Cartoon Library & Museum"

Source Collection - formerly Collection

Label

Collection

Property 

 vra:collection

Visible

 Yes

Facet

 Yes

Obligation 

 Required, if available

Repeatable 

 No

Description 

Name of the collection that the work is a part of.

CV/Syntax 

 n/a

Notes 

  • Collection name should be consistent with how it is listed in related records, e.g. finding aid and catalog record.

  • Artificial collections should not be created for grouping and/or display of records in DC.

Examples 

Sub collection

Note: This field will be deprecated after the collections as objects project is complete. As appropriate, related information will be populated in the Source field instead.

Label

Sub Collection

Property 

 vra:subcollection

Visible

 Yes

Facet

 Yes

Obligation 

 Optional

Repeatable 

 No

Description 

Name of the sub-collection that the work is a part of.

CV/Syntax 

 n/a

Notes 

  • DC is not capable of nesting sub-collections effectively within collections. 

  • The creation of sub collections is discouraged. One-level of sub collection is permitted, however, further levels of sub collections are not allowed. 

  • If collections represent collections with large finding aids, sub collections, when necessary, should correspond to finding aid arrangement, i.e. series name and series identifier.

Examples 



Source

Label

Source

Property 

dc:source

Visible

Yes

Facet

No

Obligation 

Optional

Repeatable 

No

Description 

Indicate source of the work as a digital object(s).

CV/Syntax 

 n/a

Notes 

  • For born digital works, enter "Born digital"

  • For reformatted works, note the reformatting process and the location of the original work. Works from from a finding aid can follow this format “Digitized from [Item #], [Box #], [Collection Name], [Unit], The Ohio State University Libraries." Works with only a catalog record follow this format “Digitized from [Item #], [Title in catalog record] (catalog number), [Unit], The Ohio State University Libraries."

Examples 

  • "Digitized from Item 24, Box 4, Jeffrey Family Collection of World War I Glass Slides, Rare Books and Manuscripts Library, The Ohio State University Libraries." (example record)

  • "Digitized from Pro-Suffrage campaign literature (JK1901 .P96), Rare Books and Manuscripts Library, The Ohio State University Libraries." (example record)

Provenance

Label

Provenance

Property 

dcterms:provenance

Visible

Yes

Facet

No

Obligation 

Optional

Repeatable 

Yes

Description 

A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.

CV/Syntax 

 n/a

Notes 



Examples 

 "Donor: Winston Ross"

Related Finding Aid

Label

Related Finding Aid

Property 

 bibframe:findingAid

Visible

 Yes

Facet

 No

Obligation 

 Optional

Repeatable 

 No

Description 

Hyperlink to access the finding aid that work is directly related to.

CV/Syntax 

 URL

Notes 

If applicable, enter the URL for the OSUL finding aid in the Special Collections Registry (https://library.osu.edu/collections) that the work is associated with. If Special Collections Registry entry is not available, XML finding aid link is acceptable. 

Examples 

Related URL

Label

Related URL

Property 

 rdfs:seeAlso

Visible

 Yes

Facet

 No

Obligation 

 Optional

Repeatable 

 Yes

Description 

A link to a website related to the work.

CV/Syntax 

 URL

Notes 

  • This field can also be used for permanent link(s) from a DC record that is related to the work.

  • Enter the entire URL, including "http://" or it will not link correctly.

Examples 

Identification Metadata

This metadata helps users identify the work.

Identifier

Label 

Identifier

Property 

dcterms:identifier

Visible

Yes

Facet

No

Obligation 

Required, if available

Repeatable 

Yes

Description 

The unique identifier(s) associated with the work.

CV/Syntax 

 n/a

Notes 

  • In the case of reformatted items, identifiers could be associated with the work in a physical or digital format. Examples including accession numbers and unique identifiers for digital files.

  • If the identifier is a call number, enter it in Call Number instead.

  • If the identifier is a collection number, enter it in Collection Identifier instead.

Examples 



Call Number

Label 

Call Number

Property 

bibframe:shelfMark

Visible

 Yes

Facet

 No

Obligation 

 Required, if available

Repeatable 

 Yes

Description 

 If applicable, the call number(s) of the physical work that the digital object is reformatted from.

CV/Syntax 

 n/a

Notes 

  • Enter call number exactly as it is listed on the physical item.

  • Call number should match how it is listed elsewhere in OSUL, e.g. catalog record.

Examples 



Collection Identifier

Label 

Collection Identifier

Property 

vra:collectionIdentifer

Visible

Yes

Facet

No

Obligation 

Required, if available

Repeatable 

No

Description 

Identifier for the collection that the work is a part of.

CV/Syntax 

n/a

Notes 

Examples 

Archival Context

Label 

Archival Context

Property 

n/a - local field

Visible

Yes

Facet

No

Obligation 

Optional

Repeatable 

No

Description 

Identifier for the work in the hierarchy of its related finding aid.

CV/Syntax 

For syntax, follow instructions link.

Notes 

If applicable, enter the Finding Aid Container ID that links the work to its series, box, or other section in its related finding aid.

Examples 



Published In

Label 

Published In

Property 

dcterms:bibliographicCitation

Visible

Yes

Facet

No

Obligation 

Optional

Repeatable 

Yes

Description 

Bibliographic information related to the work.

CV/Syntax 

n/a

Notes 

  • It is preferable to enter a full bibliographic citation(s) for previously published version(s) of the work.

  • Use only for works that were formally published.

Examples 



Subject Metadata

This metadata helps users understand what the work is about or depicts.

Subject

Label 

Subject

Property 

dc:subject

Visible

Yes

Facet

Yes

Obligation 

Recommended

Repeatable 

Yes

Description 

Terms which describe what the work is about.

CV/Syntax 

LCSH; LCNAF

Notes 

  • Use LCSH for topical subject headings.

  • Use LCNAF for preferred names of individuals and organizations.

  • If person or organization is not in LCNAF, follow its naming practice. Names of individuals are in inverted order - last name, first name, life dates. For example, John L. Smith who was born in 1975 but is still alive would be "Smith, John L., 1975- ". If John L. Smith was born in 1975 and died in 2018, the appropriate term would be "Smith, John L., 1975-2018".

Examples 

Keyword

Label 

Keyword

Property 

dc:relation

Visible

Yes

Facet

Yes

Obligation 

Optional

Repeatable 

Yes

Description 

Words or phrases to describe what the work is about. This field is for terms that do not conform to a controlled vocabulary.

CV/Syntax 

n/a

Notes 

  • If a term(s) can be located in LCSH, use Subject instead.

  • This field is useful for noting terms that are unusual.

Examples 

  • "muscular rabbit"

Place (Topic)

Label 

Place (Topic)

Property 

dcterms:spatial

Visible

Yes

Facet

Yes

Obligation 

Optional

Repeatable 

Yes

Description 

A place name, e.g. city, state, country, that the work is about.

CV/Syntax 

LCNAF (preferred); TGN

Notes 

Examples

Time Period (Topic)

Label 

Time Period (Topic)

Property 

dcterms:temporal

Visible

Yes

Facet

Yes

Obligation 

Optional

Repeatable 

Yes

Description 

A time span that the work is about or depicts.

CV/Syntax 

local - see Notes

Notes 

  • Indicate the time period in terms of decades, e.g. “1890s (1890-1899)”, and centuries, e.g. “19th Century”.

  • Follow existing standards in DC.

Examples 

Rights & Access Metadata

This metadata relates to the work’s rights.

Rights Statement

Label 

Rights Statement

Property 

edm:rights

Visible

Yes

Facet

No

Obligation 

Required

Repeatable 

No

Description 

Standardized rights statement related to the work.

CV/Syntax 

RightsStatements.org

Notes 

  • Consult OSUL’s Copyright Services Department for the appropriate value.

  • As the Rights Statement is generic, specific information about the work's copyright date and copyright holder can be entered, respectively, in Date Copyrighted and Rights Holder.

Examples 

Rights Note

Label 

Rights Note

Property 

dc:rights

Visible

Yes

Facet

No

Obligation 

Required

Repeatable 

No

Description 

OSUL's disclaimer regarding the use of the work.

CV/Syntax 

  • This item, made available for research and educational purposes, may be protected by copyright; the user is responsible for making a final determination of copyright status.

  • The Ohio State University Libraries believes this object is in the Public Domain in the United States; users are responsible for making a final determination of copyright status.

Notes 

Consult OSUL’s Copyright Services Department for the appropriate value.

Rights Holder

Label 

Rights Holder

Property 

dcterms:rightsHolder

Visible 

Yes

Facet

No

Obligation 

Optional

Repeatable 

Yes

Description 

Name of the individual(s) and/or organization(s) that retain rights to the work.

CV/Syntax 

n/a

Notes 

If rights holder is indicated on the work, e.g. copyright statement, transcribe it here.

Examples 



License

Label 

License

Property 

dcterms:license

Visible 

Yes

Facet

No

Obligation 

Required, if available

Repeatable 

No

Description 

If appropriate, select a Creative Commons license to be applied to the work.

CV/Syntax 

Creative Commons licenses

Notes 

  • Consult OSUL’s Copyright Services Department for appropriate term.

  • CC 3.0 licenses have been deprecated.

  • License field is only appropriate when the work's creator has selected to share their work via a Creative Commons license.

Examples 



Access Rights

Label 

Access Rights

Property 

dcterms:accessRights

Visible 

Yes

Facet

No

Obligation 

Required, if available

Repeatable 

Yes

Description 

Statement that lets patrons know how to access Digital Collections content that requires logins or on-site access due to copyright and other rights-related restrictions.

CV/Syntax 

  • OSU faculty, staff, students can login for access to the recordings. Other users may access the recordings on site in an Ohio State University Libraries’ location.

  • Users may access the recordings on site in an Ohio State University Libraries’ reading room.

Notes 

  • Institution access: OSU-affliated users with logins and passwords have streaming and/or view access only to the specific file(s) with Shibboleth. Download is not enabled in this setting.

  • When appropriate, curators can provide a single-use link to patrons to enable file download.

Examples 

  • OSU faculty, staff, students can login for access to the recordings. Other users may access the recordings on site in an Ohio State University Libraries’ location. (example record - Institution)

  • Users may access the recordings on site in an Ohio State University Libraries’ reading room. (example record - Private)

Preservation Metadata

This metadata relates to digital preservation of the work. This section is under review and will be revised.

Preservation Level

Label 

Preservation Level

Property 

premis:preservationLevel    (Note: PREMIS 2. Not in PREMIS ontology.)

Visible 

No - visible only to DC OSUL accounts 

Facet

No

Obligation 

Required, if available

Repeatable 

No

Description 

A value indicating the set of preservation functions expected to be applied to the object, e.g. “Full.”

CV/Syntax 

 

Notes 

  • Consult with Digital Preservation Librarian for the appropriate value.

  • This metadata element is under review.

Examples 

  • "Full"

Preservation Level Rationale

Label 

Preservation Level Rationale

Property 

premis:hasPreservationLevelRationale     (Note: PREMIS 2. Not in PREMIS ontology.)

Visible 

No - visible only to DC OSUL accounts

Facet

No

Obligation 

Required, if available

Repeatable 

No

Description 

The reason a particular Preservation Level value was applied to the object.

CV/Syntax 

  • Preservation Master

  • Provisional Master

  • Derived Master

  • Access Copy

Notes 

  • Consult Digital Preservation Librarian for the appropriate value.

  • This metadata element is under review.

Examples 



Preservation Level Date Assigned

Label 

 Preservation Level Date Assigned

Property 

premis:hasPreservationLevelDateAssigned     (Note: PREMIS 2. Not in PREMIS ontology.)

Visible 

 No - visible only to DC OSUL accounts

Facet

 No

Obligation 

 Required, if available

Repeatable 

 No

Description 

 Date the preservation level was assigned.

CV/Syntax 

 W3C Date Time Format (DTF)

Notes 

  • Enter date as YYYY, YYYY-MM, or YYYY-MM-DD.

  • Consult with Digital Preservation Librarian for the appropriate value.

  • This metadata element is under review.

Examples 





Custom Metadata

Metadata created for OSUL-specific needs.

Syndicate

Label 

Syndicate

Property 

n/a

Visible 

Yes 

Facet

?

Obligation 

Optional

Repeatable 

Yes

Description 

Agency that grants media publishers, particularly newspapers, the right to publish a creator's work.

CV/Syntax 

local CV

Notes 

  • This field is only for records from Billy Ireland Cartoon Library and Museum. It should not be used by other units in the library.

  • For a clearer understanding of the role of a media syndicate in distribution of comic strips, etc., see Wikipedia's article on "Print syndication". There is a relevant Wikidata item (https://www.wikidata.org/wiki/Q63968517).

  • The syndicate may or may not be the copyright holder of the work. In some cases, the creator retains the copyright to the work.

  • Wikidata calls it a "print syndicate" with additional names of press syndicate, newspaper syndicate, and feature syndicate. Print syndicate is not an exact match since there are web-based syndicates?

Examples 





The Ohio State University

If you have a disability and experience difficulty accessing this content, please contact LIB-a11y@osu.edu.