Metadata: Difference between revisions
From Santa Fe Institute Events Wiki
| Line 1: | Line 1: | ||
=== Native SFI Metadata === Here | === Native SFI Metadata === Here are the basic '''definitions'''. | ||
From Jewel (AISTI consultant who assisted SFI in Feb. 2004) | From Jewel (AISTI consultant who assisted SFI in Feb. 2004) | ||
Revision as of 19:02, 22 March 2006
=== Native SFI Metadata === Here are the basic definitions.
From Jewel (AISTI consultant who assisted SFI in Feb. 2004) 1) Definition of "native metadata":
I found this paper on the National Science Digital Library (NSDL), which provides standards for metadata.
comm.nsdl.org/download.php/196/PC3Draft1b.pdf
(If you have problems accessing the paper, let me know.)
I'll see if I can get a hold of the final version, but in the meantime, you may wish to look at section 1.2.13.1, which provides a definition of native metadata, and other types of metadata for a collection.
This document may be useful as you redesign your systems/db in the next phase. ;-) I will also read through the entire document; at this point, I've skimmed through it. At that point, if you don't mind I may make some further recommendations for SFI, based on what we have discussed.
2) MARC 21 to DC Crosswalk from the Library of Congress
This covers both qualified and unqualified DC.
MARC to DC: http://www.loc.gov/marc/marc2dc.html This one provides the mapping in the form of an easy-to-read table.
DC to MARC: http://www.loc.gov/marc/dccross.html
As for whether or not "report number" maps to dc:relation...MARC #088 is "rept.#"; therefore, your report numbers would map to dc:identifier rather than relation. See the back page of the copy of the TRI mappings that I gave you.
I have not been able to find a better explanation of each element, other than what is in the DCMI web site. I did find a page full of links to crosswalks, though: http://www.ukoln.ac.uk/metadata/interoperability/
Regards,
Jewel