Metadata crosswalks
From Library of Congress Subject Headings
Metadata crosswalks
URI(s)
- http://id.loc.gov/authorities/subjects/sh2010013649
- info:lc/authorities/sh2010013649
- http://id.loc.gov/authorities/sh2010013649#concept
Instance Of
Scheme Membership(s)
Collection Membership(s)
Variants
- Conversions, Metadata
- Crosswalks, Metadata
- Mappings, Metadata
- Metadata--Conversion tables
- Metadata conversions
- Metadata mappings
Broader Terms
Sources
- found: Work cat.: Godby, C.J. Mapping ONIX to MARC, c2010: p. 11 (mapping between ONIX and MARC) p. 13 (a crosswalk, or a set of semantic correspondences, from ONIX to MARC21; ONIX-to-MARC crosswalk)
- found: MARC standards website, Sept. 13, 2010 (MARC mappings; Dublin Core to MARC crosswalk; Dublin Core/MARC/GILS crosswalk)
- found: MODS official web site, Sept. 13, 2010 (conversions; MODS mappings)
- found: Wikipedia, Sept. 13, 2010 Crosswalk (metadata) (A crosswalk is a table that shows equivalent elements (or "fields") in more than one database; crosswalks show people where to put the data from one scheme into a different scheme)
- found: St. Pierre, M. Issues in crosswalking content metadata standards, 1998, via WWW, Sept. 13, 2010 (Semantic mappings: many metadata standards already provide a semantic mapping to related metadata standards; Crosswalks: a crosswalk is a set of transformations applied to the content of elements in a source metadata standard that result in the storage of appropriately modified content in the analogous elements of a target metadata standard; a complete or fully specified crosswalk consists of both a semantic mapping and a metadata conversion specification)
- found: Xu, A. Metadata conversion and the library OPAC, 1997, via WWW, Sept. 13, 2010.
Change Notes
- 2010-09-14: new
Alternate Formats
Suggest terminology
The LC Linked Data Service welcomes any suggestions you might have about terminology used for a given heading or concept.
Would you like to suggest a change to this heading?
Please provide your name, email, and your suggestion so that we can begin assessing any terminology changes.
Fields denoted with an asterisk (*) are required.
