{"id":74,"date":"2017-11-27T13:23:32","date_gmt":"2017-11-27T18:23:32","guid":{"rendered":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/?post_type=chapter&p=74"},"modified":"2018-06-23T16:31:10","modified_gmt":"2018-06-23T20:31:10","slug":"metadata-standards-schemas-and-profiles","status":"publish","type":"chapter","link":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/chapter\/metadata-standards-schemas-and-profiles\/","title":{"raw":"Metadata: standards, schemas, and profiles","rendered":"Metadata: standards, schemas, and profiles"},"content":{"raw":"

Metadata: standards, schemata, and profiles<\/h3>\r\n\r\n<\/a>There are many metadata standards, each providing ways to structure data. When data is structured we can discover, trace, and visualize relationships between data. Keep in mind that metadata standards, like any knowledge structures, reflect the particular biases and mentalities of the institutional organizations, individuals or communities of practice that develop and use them.\r\n\r\nDublin Core is a type of metadata standard. Dublin Core<\/a> (DC) is a\u00a0small set of vocabulary terms developed for describing digital objects. DC is the minimum standard for describing digital objects. Dublin Core comes in a simple (15 elements) and a larger set. The Simple Dublin Core Metadata Element Set (DCMES) includes 15 metadata elements (terms). Each element describes a property of a resource.\r\n\r\nSimple Dublin Core set:\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
1. Title<\/td>\r\n6. Contributor<\/td>\r\n11. Source<\/td>\r\n<\/tr>\r\n
2. Creator<\/td>\r\n7. Date<\/td>\r\n12. Language<\/td>\r\n<\/tr>\r\n
3. Subject<\/td>\r\n8. Type<\/td>\r\n13. Relation<\/td>\r\n<\/tr>\r\n
4. Description<\/td>\r\n9. Format<\/td>\r\n14. Coverage<\/td>\r\n<\/tr>\r\n
5. Publisher<\/td>\r\n10. Identifier<\/td>\r\n15. Rights<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nAll elements are optional and repeatable.\r\n
Uploading Digital Objects<\/h5>\r\nAt York University Libraries, born digital or digitized objects are deposited in YorkSpace,<\/a> our institutional repository, or\u00a0 York University Digital Library (YUDL),\u00a0<\/a>our preservation repository, depending on their audience, format, and their copyright\/rights status.\r\n\r\nIn YorkSpace, metadata is stored in a Dublin-Core (DC) form. In YUDL, metadata is stored in a MODS form. For both platforms, librarians, archivists,\u00a0 and research team members can hand-enter descriptive metadata through an online form.[footnote]For step-by-step instructions for YorkSpace see: https:\/\/docs.google.com\/presentation\/d\/14OdnFq9gU2NiJNu6o7xmIfpUAaZCoStIjwazqvKpAgs\/edit?usp=sharing .[\/footnote][footnote]For step-by-step instructions for YUDL, contact York University Libraries' Digital Scholarship Centre .[\/footnote] For research projects, we recommend teams work in shared spreadsheets and then uploading digital objects and their accompany metadata in bulk.\r\n
Adding Descriptive Metadata<\/h5>\r\nYUL uses the MODS<\/a> metadata schema since it supports the system we are moving towards. This systems supports a linked data environment. Linked data is a process by which data is shared and connected on the Semantic Web. Linked data is made possible through the use of Uniform Resource Identifiers <\/a>(URIs). URIs are characters that identify resources.[footnote]https:\/\/en.wikipedia.org\/wiki\/Uniform_Resource_Identifier[\/footnote] Linked data is also made possible by the Resource Description Framework (RDF), \"a general method for conceptual description or modeling of information that is implemented in web resources, using a variety of syntax notations and data serialization formats.\"[footnote]https:\/\/en.wikipedia.org\/wiki\/Resource_Description_Framework[\/footnote]\r\n\r\nMODS is a subset of MARCXML elements. MODS is embedded in METS (Metadata Exchange) records for item level description. \"The METS schema is a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.\"[footnote]http:\/\/www.loc.gov\/standards\/mets\/[\/footnote]\r\n

Taxonomies, Ontologies, Controlled Vocabularies<\/h3>\r\nWhat information you decide to capture about your content in a first step. How<\/em> you decide to describe, categorize and tag up your content is also important. Generally within the GLAM (Galleries, Libraries, Archives & Museums) we embrace collaborative solutions to information challenges. Why recreate the wheel when there is a community of practice that will allow the creation of a shared vocabulary.\r\n\r\nControlled vocabularies can be used to ensure consistency and can be structured in such a way that related or similar terms can be linked to each other.[footnote]See for example the definition by the American Society for Indexing here: http:\/\/www.taxonomies-sig.org\/about.htm#cv <\/a>.[\/footnote]\r\n\r\nTaxonomies are controlled vocabularies that are structured into simple parent>child hierarchies. If you look at the Library of Congress Thesaurus for Graphic Materials, you can see how the term Photographs<\/a> is part of the broader category of Pictures<\/a> and includes a number of narrower terms related to format (i.e. Daguerreotypes<\/a>) or genre (Fashion photographs<\/a>, Marine photographs<\/a>).\r\n\r\nOntologies are a taxonomy with more complex structures and specific relationship between terms, so that relationships between terms are more complex (and are qualified beyond a simple hierarchy).\r\n

Schema and Data Profiles<\/h3>\r\nApplication Profiles\u00a0 are policy documents that instruct how particular project teams, institutions, or communities of practice use, describe and preserve metadata.[footnote]See for example, the Digital Public Library of America's Metadata Profile<\/a>, available at http:\/\/dp.la\/info\/wp-content\/uploads\/2015\/03\/MAPv4.pdf .[\/footnote] At York University Libraries, librarians and archivists have developed application profiles for digitized projects over many years, both formally, and informally. Currently, we are in the process of implementing a metadata profile using MODS with the intention to normalize as much metadata in anticipation of migrating to an RDF<\/a> standard.\r\n\r\nHere is our current documentation<\/a> on how York University Libraries goes about it's preservation of digital and digitized objects. The section on metadata<\/a> is brief, with more detailed policy and documentation currently in development.\r\n\r\nHere is a sample spreadsheet of how one might track and structure the metadata for the objects being generated as part of the digitization project: Metadata_YUL_Template_for_AIFProjects .<\/a>\r\n

Linked Data<\/h3>\r\n\"Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods.\"[footnote]See: http:\/\/linkeddata.org\/[\/footnote] In practical application, linked data uses URIs and RDF to create machine-readable information that will follow best practices to surface, share and connect information.\r\n\r\nLinked data requires collaboration among different creators of metadata, and is based on open vocabularies.\r\n\r\nPublishing structured data so that it can be interlinked and become more useful through semantic queries\u2026 in other words, breaking up your information into discrete \u201cbits\u201d to create strings of interrelations. So individuals are assigned a unique identifier (see VIAF<\/a>, ORCid<\/a>), a published work is assigned a unique identifier (DOI<\/a>, ISBN<\/a>), places get a unique identifier (GeoNames<\/a>), discrete objects get unique identifiers (like file formats<\/a>).\r\n\r\nLinked data shifts value from discrete scholarly online projects to more open projects that share their own data, mobilize the work of others, and connect data sets with others.\r\n\r\n \r\n\r\n[caption id=\"\" align=\"alignnone\" width=\"1000\"]\"Image Linking Open Data cloud diagram 2017, by Andrejs Abele, John P. McCrae, Paul Buitelaar, Anja Jentzsch and Richard Cyganiak. http:\/\/lod-cloud.net\/[\/caption]\r\n\r\n[footnote]Linking Open Data cloud diagram 2017, by Andrejs Abele, John P. McCrae, Paul Buitelaar, Anja Jentzsch and Richard Cyganiak. http:\/\/lod-cloud.net\/.\u00a0 For interactive version, see:\u00a0http:\/\/lod-cloud.net\/versions\/2017-08-22\/lod.svg . [\/footnote]","rendered":"

Metadata: standards, schemata, and profiles<\/h3>\n


\n<\/a>There are many metadata standards, each providing ways to structure data. When data is structured we can discover, trace, and visualize relationships between data. Keep in mind that metadata standards, like any knowledge structures, reflect the particular biases and mentalities of the institutional organizations, individuals or communities of practice that develop and use them.<\/p>\n

Dublin Core is a type of metadata standard. Dublin Core<\/a> (DC) is a\u00a0small set of vocabulary terms developed for describing digital objects. DC is the minimum standard for describing digital objects. Dublin Core comes in a simple (15 elements) and a larger set. The Simple Dublin Core Metadata Element Set (DCMES) includes 15 metadata elements (terms). Each element describes a property of a resource.<\/p>\n

Simple Dublin Core set:<\/p>\n\n\n\n\n\n\n\n
1. Title<\/td>\n6. Contributor<\/td>\n11. Source<\/td>\n<\/tr>\n
2. Creator<\/td>\n7. Date<\/td>\n12. Language<\/td>\n<\/tr>\n
3. Subject<\/td>\n8. Type<\/td>\n13. Relation<\/td>\n<\/tr>\n
4. Description<\/td>\n9. Format<\/td>\n14. Coverage<\/td>\n<\/tr>\n
5. Publisher<\/td>\n10. Identifier<\/td>\n15. Rights<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

All elements are optional and repeatable.<\/p>\n

Uploading Digital Objects<\/h5>\n

At York University Libraries, born digital or digitized objects are deposited in YorkSpace,<\/a> our institutional repository, or\u00a0 York University Digital Library (YUDL),\u00a0<\/a>our preservation repository, depending on their audience, format, and their copyright\/rights status.<\/p>\n

In YorkSpace, metadata is stored in a Dublin-Core (DC) form. In YUDL, metadata is stored in a MODS form. For both platforms, librarians, archivists,\u00a0 and research team members can hand-enter descriptive metadata through an online form.[1]<\/sup><\/a>[2]<\/sup><\/a> For research projects, we recommend teams work in shared spreadsheets and then uploading digital objects and their accompany metadata in bulk.<\/p>\n

Adding Descriptive Metadata<\/h5>\n

YUL uses the MODS<\/a> metadata schema since it supports the system we are moving towards. This systems supports a linked data environment. Linked data is a process by which data is shared and connected on the Semantic Web. Linked data is made possible through the use of Uniform Resource Identifiers <\/a>(URIs). URIs are characters that identify resources.[3]<\/sup><\/a> Linked data is also made possible by the Resource Description Framework (RDF), “a general method for conceptual description or modeling of information that is implemented in web resources, using a variety of syntax notations and data serialization formats.”[4]<\/sup><\/a><\/p>\n

MODS is a subset of MARCXML elements. MODS is embedded in METS (Metadata Exchange) records for item level description. “The METS schema is a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.”[5]<\/sup><\/a><\/p>\n

Taxonomies, Ontologies, Controlled Vocabularies<\/h3>\n

What information you decide to capture about your content in a first step. How<\/em> you decide to describe, categorize and tag up your content is also important. Generally within the GLAM (Galleries, Libraries, Archives & Museums) we embrace collaborative solutions to information challenges. Why recreate the wheel when there is a community of practice that will allow the creation of a shared vocabulary.<\/p>\n

Controlled vocabularies can be used to ensure consistency and can be structured in such a way that related or similar terms can be linked to each other.[6]<\/sup><\/a><\/p>\n

Taxonomies are controlled vocabularies that are structured into simple parent>child hierarchies. If you look at the Library of Congress Thesaurus for Graphic Materials, you can see how the term Photographs<\/a> is part of the broader category of Pictures<\/a> and includes a number of narrower terms related to format (i.e. Daguerreotypes<\/a>) or genre (Fashion photographs<\/a>, Marine photographs<\/a>).<\/p>\n

Ontologies are a taxonomy with more complex structures and specific relationship between terms, so that relationships between terms are more complex (and are qualified beyond a simple hierarchy).<\/p>\n

Schema and Data Profiles<\/h3>\n

Application Profiles\u00a0 are policy documents that instruct how particular project teams, institutions, or communities of practice use, describe and preserve metadata.[7]<\/sup><\/a> At York University Libraries, librarians and archivists have developed application profiles for digitized projects over many years, both formally, and informally. Currently, we are in the process of implementing a metadata profile using MODS with the intention to normalize as much metadata in anticipation of migrating to an RDF<\/a> standard.<\/p>\n

Here is our current documentation<\/a> on how York University Libraries goes about it’s preservation of digital and digitized objects. The section on metadata<\/a> is brief, with more detailed policy and documentation currently in development.<\/p>\n

Here is a sample spreadsheet of how one might track and structure the metadata for the objects being generated as part of the digitization project: Metadata_YUL_Template_for_AIFProjects .<\/a><\/p>\n

Linked Data<\/h3>\n

“Linked Data is about using the Web to connect related data that wasn’t previously linked, or using the Web to lower the barriers to linking data currently linked using other methods.”[8]<\/sup><\/a> In practical application, linked data uses URIs and RDF to create machine-readable information that will follow best practices to surface, share and connect information.<\/p>\n

Linked data requires collaboration among different creators of metadata, and is based on open vocabularies.<\/p>\n

Publishing structured data so that it can be interlinked and become more useful through semantic queries\u2026 in other words, breaking up your information into discrete \u201cbits\u201d to create strings of interrelations. So individuals are assigned a unique identifier (see VIAF<\/a>, ORCid<\/a>), a published work is assigned a unique identifier (DOI<\/a>, ISBN<\/a>), places get a unique identifier (GeoNames<\/a>), discrete objects get unique identifiers (like file formats<\/a>).<\/p>\n

Linked data shifts value from discrete scholarly online projects to more open projects that share their own data, mobilize the work of others, and connect data sets with others.<\/p>\n

 <\/p>\n

\"Image
Linking Open Data cloud diagram 2017, by Andrejs Abele, John P. McCrae, Paul Buitelaar, Anja Jentzsch and Richard Cyganiak. http:\/\/lod-cloud.net\/<\/figcaption><\/figure>\n

[9]<\/sup><\/a><\/p>\n

  1. For step-by-step instructions for YorkSpace see: https:\/\/docs.google.com\/presentation\/d\/14OdnFq9gU2NiJNu6o7xmIfpUAaZCoStIjwazqvKpAgs\/edit?usp=sharing . ↵<\/a><\/li>
  2. For step-by-step instructions for YUDL, contact York University Libraries' Digital Scholarship Centre . ↵<\/a><\/li>
  3. https:\/\/en.wikipedia.org\/wiki\/Uniform_Resource_Identifier ↵<\/a><\/li>
  4. https:\/\/en.wikipedia.org\/wiki\/Resource_Description_Framework ↵<\/a><\/li>
  5. http:\/\/www.loc.gov\/standards\/mets\/ ↵<\/a><\/li>
  6. See for example the definition by the American Society for Indexing here: http:\/\/www.taxonomies-sig.org\/about.htm#cv <\/a>. ↵<\/a><\/li>
  7. See for example, the Digital Public Library of America's Metadata Profile<\/a>, available at http:\/\/dp.la\/info\/wp-content\/uploads\/2015\/03\/MAPv4.pdf . ↵<\/a><\/li>
  8. See: http:\/\/linkeddata.org\/ ↵<\/a><\/li>
  9. Linking Open Data cloud diagram 2017, by Andrejs Abele, John P. McCrae, Paul Buitelaar, Anja Jentzsch and Richard Cyganiak. http:\/\/lod-cloud.net\/.\u00a0 For interactive version, see:\u00a0http:\/\/lod-cloud.net\/versions\/2017-08-22\/lod.svg . ↵<\/a><\/li><\/ol><\/div>","protected":false},"author":8,"menu_order":3,"template":"","meta":{"pb_show_title":"","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-74","chapter","type-chapter","status-publish","hentry"],"part":3,"_links":{"self":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapters\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/wp\/v2\/users\/8"}],"version-history":[{"count":41,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapters\/74\/revisions"}],"predecessor-version":[{"id":132,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapters\/74\/revisions\/132"}],"part":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/parts\/3"}],"metadata":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapters\/74\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/pressbooks\/v2\/chapter-type?post=74"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/wp\/v2\/contributor?post=74"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks-dev.library.yorku.ca\/metadata\/wp-json\/wp\/v2\/license?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}