Recommended Fields Formatting Requirements

If possible use the spelled out title of the language of the described resource (e.g. English, Spanish). If using language codes use the three digit codes found here. Note DPLA does not use the three-digit code ger for German, rather the code is deu for Deutsch.

DPLA can transform dates in a variety of formats, as listed below. Note if you are sending the full date/time pattern such as “2009-06-15T13:45:30,” we will use XSLT to remove the timestamp.

DPLA provides location enhancements for the API interfaces for the information in the dcterms:spatial field. Due to this location enhancement, the location information in the dcterms:spatial field must refer to a geographic place name. Names such as building names, neighborhoods, or landmarks cannot be accepted.

In order for DPLA to work correctly the hierarchical place names must be listed in ascending order. See the examples below for the correct ordered places.

  • <dcterms:spatial>Erie, Pennsylvania</dcterms:spatial>
  • <dcterms:spatial>Toledo—Ohio—United States </dcterms:spatial>
  • <dcterms:spatial>Erie, Pennsylvania</dcterms:spatial>

In these examples, the terms are listed in descending order. Currently the DPLA enhancement software is unable to properly transform the information in the API interfaces.

  • <dcterms:spatial>United States, Pennsylvania, Erie</dcterms:spatial>
  • <dcterms:spatial> United States—Ohio—Toledo</dcterms:spatial>

Place should also not be encoded in the own individual properties (in other words for Erie, Pennsylvania, and United States to be placed in separate <dc:coverage> fields). If records are formatted this way we would still be able to use the data to find matches for each individual place, but it is impossible to tell which place names are related to which:

  • <dc:coverage>United States</dc:coverage>
  • <dc:coverage>Pennsylvania</dc:coverage>
  • <dc:coverage>Erie</dc:coverage>

The example above could be for Erie, Pennsylvania, but there are also places named Erie in Colorado, Illinois, Michigan, Kansas, and North Dakota. Without hierarchy, DPLA will have trouble disambiguating terms. The resulting enriched record would contain entries for “United States”, “Pennsylvania” and whichever “Erie” is selected by DPLA’s software.

Lastly, the field cannot contain any additional information such as street names, neighborhood names, building names, etc. It should only contain place names such as city, state, and country.

For more information on DPLA’s requirements date and geospatial requirements visit these guidelines.

If you are using hyphens for subject, or geospatial order DPLA best practices include:

  • No spaces between terms.
  • Double hyphens (—) not single smart hyphens. Occasionally Microsoft programs will automatically edit the double hyphens to one single hyphen, so check the autocorrect settings if necessary.

See correct and incorrect examples below:

  • Probate Records—Ohio—Butler County
  • Probate Records — Ohio — Butler County
  • Probate—Ohio—Butler County

The type field must be filled with one of the DCMI Type Vocabulary Terms. If you would like a more detailed explanation of the values check out the Dublin Core Metadata Initiative DCMI Type Webpage (note: you will need to scroll to the middle of the page to find the DCMI type Vocabulary terms). Due DPLA’s collection development guidelines, they do not want the DCMI type “collection used. The
accepted DCMI Type vocabulary terms are:

  • Class
  • Event
  • Image
  • InteractiveResource
  • MovingImage
  • PhysicalObject
  • Service
  • Software
  • Sound
  • StillImage
  • Text