...
| Info |
|---|
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) Described | Human-Readable MAP | Machine-Actionable MAP |
|---|---|---|---|---|
| Digital Portal Hydra PCDM | RDF | Collections, Cultural Heritage Objects, Digital Surrogates, Filesets, Files | (static version from last September that's easier to share than the version currently being used): https://docs.google.com/spreadsheets/d/1z-dddDvijPIa84dml76YTenSJ_gMnZZ0zR3JnHSZVPc/edit?usp=sharing | being built |
| eCommons | XML, some CSV to XML | Scholarly Output Objects, Digital Surrogates, Collections | https:// |
| cornell. |
| box.com/ |
| s/7eweceb0dxhbgq3ja5yko69ednbeefb4 | being built | |||
| SharedShelf | JSON | Visual Resource Objects, Files, Collections, Agents, Events | https://github.com/cul-it/sharedshelf-metadata (being built, probably not public) | being built |
| ETDs Uber Records | MySQL Data, XML for one representation | ETDs, ETD Agents, ETD Subjects, ETD Binaries | MySQL: https://docs.google.com/spreadsheets/d/1L_06uqiDL5AeBSMm5aDC2BkA-GNABr2_E8iGCaiKyPY/edit#gid=0 Example 1 one MAP fork: eCommons XML: ETD Metadata Profile | being built |
| Kheel (Bepress & SharedShelf) | CSV to XML | Cultural Heritage Objects, Digital Surrogates, Collections | https://docs.google.com/spreadsheets/d/1X50d8-pnOZ35mU-52mMTVWfWGAgCxoWBW4M4Ih-dlho/edit?usp=sharing | n/a |
| CULAR (F3) | XML largely? | Preservation Collections, Binaries | Data Model (not really a profile): CULAR Data Model Some parts are here: https://github.com/cmh2166/CULAR | n/a |
| Embedded Digitization Lab Binaries Metadata | Embedded data in header of digital assets | Primarily technical metadata about the Digital Asset/Binary, as well as administrative metadata for the original analog resource or collection. | https://gist.github.com/cmh2166/84e30b81227e2e5b47f0f51d71e8d9db (in process) | n/a (would be profiles loaded into the various tools used for digitization and binary management) |
| Vitro Authorities Pilot | RDF | Agents, Topics, Places, Events, Authorities | https://github.com/cul-it/lts-vitro-pilot/wiki ( |
| on hold) | n/a | |||
| LD4* Ontology (BF2) | RDF | Bibliographic Resources (Work, Instance, Items), Agents, Subjects, Contributions, ... | https://docs.google.com/spreadsheets/d/14ccalbnpr8qhh0O7M43n6vv3xbyE1ydJdJjnQaVDht4/edit?usp=sharing (largely unstarted) http://bibframe.org/bibliomata/profile-edit/#/profile/list (LC's BF Profiles can be seen in their Profile Editor) TODO: add link to Sinopia Profile Editor when it is available | https://github.com/lcnetdev/verso/tree/5a444f7cdd203fbf25563098e18f84302bdd2e6a/data/profiles (LC's BF Editor profiles in json config files) https://github.com/LD4P/HipHop/tree/master/application-profiles (Cornell Hip Hop LPs application profile in SHACL) https://github.com/LD4P/arm/tree/master/application_profiles/raremat_monograph/shacl (ARM extension application profile in SHACL) |
| KMODDL | 1) three-dimensional models designed for demonstration and/or teaching purposes; 2) stereolithography files for creating 3-D replicas of the models; 3) still, moving, and interactive images of the models; 4) |
| tutorials aiding in the use of KMODDL materials; and 5) related textual resources including books and articles. | http://wayback.archive-it.org/2566/20180418122322/http://kmoddl.library.cornell.edu/aboutmeta2.php | no | ||
| ... (add yours here) |
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://pro.dp.la/ |
| hubs/ |
| metadata-application-profile | 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 | Cultural Heritage Objects, Digital Representations, Aggregations... and more (works based off of CIDOC-CRM | More generic metadata documentation: http://pro.europeana.eu/page/edm-documentation | ? |
| Sufia / Scholarsphere | RDF, Ruby Objects |
| See here for a static copy: https://docs.google.com/spreadsheets/d/1FL15HSy0d_Mb6I3r7vjH8yEMkkRCJJkiqOt42Khl8ss/edit?usp=sharing | ||
| NYPL Digital Collections | RDF |
| See here for a static copy: https://docs.google.com/spreadsheets/d/1FL15HSy0d_Mb6I3r7vjH8yEMkkRCJJkiqOt42Khl8ss/edit?usp=sharing | ||||
Creating a MAP - Guidelines and a Generic Template
...
This is a generic MAP template that may be helpful. All the columns aren't needed for all cases, but those with stars beside them are strongly recommended for your MAP. You can make a copy of this template from this Google Spreadsheet.
| Field* | Schema Mapping* | Domain | Expected Value or Range* | Definition | Obligation* | Usage Notes | Source | Remediation Notes | Exposure or Other Representation Element |
|---|---|---|---|---|---|---|---|---|---|
| This is the name of the field for ease of referring to it in documentation, communication, etc. | This field should represent where the field is mapped to in the metadata records in the application, system, or service. It should also be the field mapped to a shared standard, namespace, or specification. This helps clarify the understanding of what the field means, as well as facilitates mapping that field to other metadata and MAPs. | The expect resource or object type this metadata field is asserted against. Required if you're not going to split MAPs but need to specify fields that apply to only certain types of described resources. | This is the expected metadata value for this field. Here you can specify data types (string, integer, datetime, etc.), specify value sources (controlled vocabularies, authorities, free-text entry, other), and any other specifications around the expected metadata (is identifier for an Agent resource; is a date following EDTF; is a Cornell email address; etc.) | This is the definition for the field. This is helpful if it doesn't map (or doesn't map entirely) to a Namespaced Mapping or a Standard. | Indicates if the field is required and repeatable in the format: {number of times expected, number of times can be present}i.e. {0,1} == Not required (can appear 0 times), Not repeatable (can only appear at most 1 time) {1,1} == Required (must appear 1 time), Not repeatable (can only appear at most 1 time) {0,n} == Not required, repeatable (can appear at most n times) {1,n} == Required, repeatable. You can also break this out into "Required?" and "Repeatable" columns with TRUE/FALSE values if easier. | Any notes on using this field in the metadata generated. | The source of the field - transformed from existing data in XYZ store or format, user-entered in the application, pulled from a shared database, etc. | Any notes on cleanup, normalization, or enhancement of this field. | This is the element or place this field gets captured in alternate exposure points, i.e., here is the element this field is presented as in the application's OAI-PMH stream. Here is the element the field appears in a backup copy of the metadata. Here is the field as the it appears in Solr. Etc. |