This is an overview of metadata application profiles and related documentation used within the Cornell University Libraries, generated originally from a MWG Working Session in 2016/2017. The goal is to get a high-level overview of metadata profiles and needs at CUL, which we hope will lead us to see collaboration opportunities. We hope to have another session in the fall of 2017 to see where this overview stands and update/expand it.
What are Metadata Application Profiles (MAPs)?
Wikipedia gives a decent stub on Metadata Application Profiles: https://en.wikipedia.org/wiki/Application_profile Metadata Application Profiles are metadata specifications attached (sometimes loosely, sometimes tightly) to a particular application or metadata service - whether it is a datastore, repository, management system, discovery indexing layer, or other. It helps communicate expectations of the metadata being ingested, processed, managed and exposed by that particular application or service. MAPs are the documentation that connect metadata implementations to shared community models and standards, as well as document where implementers need to diverge from community standards. This makes it easier for outsiders to understand and work with metadata from or headed to your application or system.
Metadata Application Profiles can touch on descriptive, technical, administrative, structural or other (or a mix of all of the above) metadata. They can rely heavily on community standards, but good MAPs don't just copy a community standard over. This is due to the fact that, in implementation, there are points your data needs to diverge or to further specify a datapoint's usage. These MAPs can also be made machine-actionable, with the enabled action being validation of your data against a profile, guiding the creation of data that follows your profile, transforming your data to/from another profile or standard. A popular metadata application profile example is the Digital Public Library of America Profile: https://dp.la/info/wp-content/uploads/2015/03/MAPv4.pdf which has a machine-actionable representation here: https://github.com/dpla/dpla_map.
What you'll most often see in cultural heritage institutions' metadata management are MAPs represented via spreadsheets or some kind of text documentation with tables. Depending on the data representation (RDF, XML, CSV, JSON, Arvo, (X)HTML, MARC, ...) you are ultimately working with, you might have some technology available for specifying machine-actionable MAPs. A common example is a XSD file which clarifies or validates that metadata is following the MAP specified for your namespace or XML dataset. Another example is the emergence of RDF shapes technologies (ShACL, ShEx, RML) or application-focused RDF-based object management libraries (ActiveTriples / ActiveFedora) for both checking the state of metadata against a specified MAP or converting to/from that MAP.
CUL-Used or Important Community-Used MAPS
CUL MAPs
FYI: These are provided not to guide policy or implementation decisions, but rather to share metadata efforts across CUL for the purpose of increasing the level of common understanding of metadata work and helping highlight collaboration, metadata infrastructure, or cross-pollination opportunities.
Repository or Unit | Data Representation | Resource Type(s) | Human-Readable MAP | Machine-Actionable MAP |
---|---|---|---|---|
Digital Portal Hydra PCDM | RDF | |||
eCommons | ||||
Kheel (Bepress & SharedShelf) | ||||
CULAR (F3) | ||||
Embedded Digitization Lab Binaries Metadata | ||||
MARC Hip Hop LPs | ||||
... | ||||
Community MAPs
Institution | Data Representation | Resource Type(s) | Human-Readable MAP | Machine-Actionable MAP |
---|---|---|---|---|
Digital Public Library of America | RDF | Cultural Heritage Objects, Digital Representations, Aggregations | https://dp.la/info/wp-content/uploads/2015/03/MAPv4.pdf | https://github.com/dpla/dpla_map (ActiveTriples representation of the MAP, which can guide Ruby applications in creating resources that follow the DPLA MAP. |
Europeana | RDF | |||
Sufia / Scholarsphere | RDF, Ruby Objects | |||
NYPL Digital Collections | RDF | |||
Creating a MAP - Guidelines and a Generic Template
First Steps
Generic Template
Need Help with your MAP?