Version 3.1 of the DPLA Metadata Application Profile (MAP) now available!

By DPLA, August 12, 2014.
Published under:

The DPLA is pleased to announce an update to the Metadata Application Profile (MAP). The DPLA MAP is the basis for how data is structured and validated in DPLA, and guides how data is stored, serialized, and made available through our API in JSON-LD. The MAP is based on the Europeana Data Model (EDM), and integrates the experience and specific needs for aggregating the data of America’s cultural heritage institutions.

The newest version, 3.1, is now available at

Changes to the MAP include the addition of three new properties (Genre, Standardized Rights Statement, and Intermediate Provider), requirement adjustments to existing properties, and better descriptions and indications of property relationships to the DPLA API structure. To help guide new users of the MAP v3.1, the document also indicates which properties are required and which display in the DPLA front-end portal.

We’re providing a summarized list of changes here; the full list of changes is available on page 10 of the MAP document.

  • Added JSON-LD expressions for data as represented in DPLA repository and API.
  • Revised usage notes for Provider and Data Provider, and added an Intermediate Provider property.
  • Clarified range and superproperty declarations and revised obligations for several properties.
  • Updated value origination field throughout document to provide guidance about value formats and entity responsible for providing the value.
  • Added “Genre” property to Source Resource.
  • Added “Standardized Rights Statement” property to Web Resource and Aggregation
  • Added indicators for required fields and fields that display in the DPLA portal.

Finally, we would like to acknowledge and offer our deep appreciation to the many people who provided input to and review of this document.

cc-by-iconAll written content on this blog is made available under a Creative Commons Attribution 4.0 International License. All images found on this blog are available under the specific license(s) attributed to them, unless otherwise noted.