LAC OAI-ORE sample

<?xml version="1.0"?>
<atom:entry xmlns:atom="http://www.w3.org/2005/Atom" xmlns:doc="http://www.lyncode.com/xoai" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:oreatom="http://www.openarchives.org/ore/atom/" xmlns:ore="http://www.openarchives.org/ore/terms/" schemaLocation="http://www.w3.org/2005/Atom http://www.kbcafe.com/rss/atom.xsd.xml">
  <atom:id>http://hdl.handle.net/10294/3386/ore.xml</atom:id>
  <atom:link rel="alternate" href="http://hdl.handle.net/10294/3386"/>
  <atom:link rel="http://www.openarchives.org/ore/terms/describes" href="http://hdl.handle.net/10294/3386/ore.xml"/>
  <atom:link type="application/atom+xml" rel="self" href="http://hdl.handle.net/10294/3386/ore.xml#atom"/>
  <atom:published>2011-07-11T02:23:04Z</atom:published>
  <atom:updated>2011-07-11T02:23:04Z</atom:updated>
  <atom:source>
    <atom:generator>oURspace</atom:generator>
  </atom:source>
  <atom:title>Another Radio is Possible: Community Radio, Media Reform and Social Change in Thailand</atom:title>
  <atom:author>
    <atom:name>Elliott, Patricia W.</atom:name>
  </atom:author>
  <atom:category label="Aggregation" term="http://www.openarchives.org/ore/terms/Aggregation" scheme="http://www.openarchives.org/ore/terms/"/>
  <atom:category scheme="http://www.openarchives.org/ore/atom/modified" term="2011-07-11T02:23:04Z"/>
  <atom:category label="DSpace Item" term="DSpaceItem" scheme="http://www.dspace.org/objectModel/"/>
  <atom:link rel="http://www.openarchives.org/ore/terms/aggregates" href="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/1/Another%20Radio%20Is%20Possible.pdf" title="Another Radio Is Possible.pdf" type="application/pdf" length="462315"/>
  <oreatom:triples>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://hdl.handle.net/10294/3386/ore.xml#atom">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceItem"/>
      <dcterms:modified>2011-07-11T02:23:04Z</dcterms:modified>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/1/Another%20Radio%20Is%20Possible.pdf">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>ORIGINAL</dcterms:description>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/2/license_url">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>CC-LICENSE</dcterms:description>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/3/license_text">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>CC-LICENSE</dcterms:description>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/4/license_rdf">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>CC-LICENSE</dcterms:description>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/5/license.txt">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>LICENSE</dcterms:description>
    </rdf:Description>
    <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="http://ourspace.uregina.ca:8080/xmlui/bitstream/10294/3386/6/Another%20Radio%20Is%20Possible.pdf.txt">
      <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream"/>
      <dcterms:description>TEXT</dcterms:description>
    </rdf:Description>
  </oreatom:triples>
</atom:entry>

LAC staff have confirmed the following:

• Their new harvester requires OAI data providers to support both ETDMS and ORE metadata (i.e., to support both metadataPrefix=etdms and metadataPrefix=ore)
• They will harvest each in a separate request, e.g., their harvester first requests http://an.oa.org/OAI-gateway?verb=ListRecords&set=theses&metadataPrefix=etdms to harvest the descriptive metadata and then, separately, requests http://an.oa.org/OAI-gateway?verb=ListRecords&set=theses&metadataPrefix=ore.

If this is the case, I believe that all we need to do is enhance the Islandora OAI module to respond to requests for an additional metadata prefix, metadataPrefix=ore, with XML as illustrated above.

It's unclear whether the hard-coded references to DSpace are required for LAC's ingest (they are using DSpace as their access platform) or whether we should localize those to Islandora.

Currently we specify oai_etdms as the format ... not sure if that needs to be changed to etdms?
Is there a more fulsome example of a thesis in the ore format?
Donald

@mjordan @dmoses we would need to investigate the schema/vocab correctly to make sure we get the Dspace usage correctly replaced with our own repository / local domain specificities. Wonder if anyone has some experience with the recommended tools? Like the validation ones?
http://www.openarchives.org/ore/1.0/tools#validation

@DiegoPino agreed, we need to pin LAC down on this.

@dmoses, the site LAC has been testing with, University of Regina, uses DSpace. Their ListMetadataFormats response indicates 'etdms' with the namespace 'http://www.ndltd.org/standards/metadata/etdms/1.0/'. I'd have to check with the OAI-PMH spec, but I assume an OAI provider can use any metadata prefix they want as long as it references the 'http://www.ndltd.org/standards/metadata/etdms/1.0/' namespace.

Checking the specs now. My interpretation of the OAI-PMH spec supports my understanding that the string used as the metadata prefix is not as important as its mapping to the default namespace of the expected XML documents. But maybe my understanding of the spec doesn't matter 😄 . The spec says:

Communities should adopt guidelines for sharing of metadataPrefixes, metadata schema and XML namespace URI's of metadata formats. Such guidelines are outside of the scope of the OAI-PMH. The accompanying Implementation Guidelines document provides some sample XML Schema and instance documents for common metadata formats such as MARC and RFC 1807.

As far as I can tell, none of the OAI-PMH implementation guidelines offer any advice on choice of metadata prefixes. The ETD-MS spec is also silent on a preferred OAI-PMH metadata prefix.

However, I don't see any indication anywhere that multiple metadata prefixes can't refer to the same namespace. In other words, the Islandora OAI module could continue to use 'oai_etdms' and start using 'etdms'. Both would return the same responses.

I emailed LAC to ask the following questions:

1. Are there any items in oreatom:triples that are mandatory other than ORIGINAL? In other words, do you require LICENCE or TEXT entries? Related, what if the thesis has supplemental data files like Excel, image, etc. Do you want triples for each of those as well?

2. Each of these triples has a <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream" /> child element. For repositories like Islandora and Hydra, what <rdf:type rdf:resource> values do you expect here? Can each repository platform make up its own or should we just use <rdf:type rdf:resource="http://www.dspace.org/objectModel/DSpaceBitstream" />?

Here's UAlberta's prototype ORE record (in Hydra context): https://github.com/ualbertalib/metadata/blob/master/metadata-wrangling/era_ore_example.xml