Child pages
  • OAI Metadata for Steel collection
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

OAI Metadata for Steel collection

Source data: EAD file, attached to infrastructure project page
Mapping notes:

  • Please keep track of all changes in the output MODS you make, and share this information with Mike Durbin so that he can ensure the in-development new Steel site can accommodate them.

(tick) oai_dc

metadataPrefix: oai_dc
target namespace: http://www.openarchives.org/OAI/2.0/oai_dc/
schema location: http://www.openarchives.org/OAI/2.0/oai_dc.xsd
method of generating: generic mods2dc.xsl

Previously used the legacy stylesheet generating DC from EAD attached to infrastructure project page. Do not use this method in the future.

(tick) QDC

metadataPrefix: qdc
target namespace: http://epubs.cclrc.ac.uk/xmlns/qdc/
schema location: http://epubs.cclrc.ac.uk/xsd/qdc.xsd
method of generating: generic MODS2QDC stylesheet
sample QDC record: steel_qdc.xml

(tick) MODS 3.4

metadataPrefix: mods_3.4
target namespace: http://www.loc.gov/mods/v3
schema location: http://www.loc.gov/mods/v3/mods-3-4.xsd
method of generating: ead2mods_steelNEW.xsl

  • Parameters expected
    • outputDir (directory location to write output MODS files to)
  • Support files needed
    • digitizeditems.txt (lists all items digitized from this collection)
    • exceptions.txt (list of IDs of items that require a different mapping; should be empty for this collection)
    • blockeditems.txt (lists IDs of digitized items for which we can expose metadata, but not the digitized object itself; should be empty for this collection)

Previously used the legacy stylesheet generating MODS from EAD attached to infrastructure project page. do not use this method in the future.

  • No labels