After reviewing a
<http://myexampledspace.org/xmlui/metadata/handle/1/1/ore.xml>
http://myexampledspace.org/xmlui/metadata/handle/1/1/ore.xml, I realize that
the atom:id probably doesn’t actually matter much besides being a persistent
unique identifier… and that the “ore.xml” is what one gets from
“oai/request?verb=ListRecords&metadataPrefix=ore”. Silly me!!!
So this should work. It looks like either the jspui or xmlui will work with
“bitstream.baseURL”, although users of the jspui will potentially run into that
problem with the URL encoding of spaces… (all the more reason to avoid spaces
when naming files I suppose).
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St, Ultimo, NSW 2007
From: David Cook [mailto:[email protected]]
Sent: Monday, 27 April 2015 3:07 PM
To: '[email protected]'; 'Hilton Gibson'
Cc: 'dspace-tech'
Subject: 3RE: [Dspace-tech] OAI-PMH/OAI-ORE Harvesting configuration
documentation
Hi Helix:
Thanks for the suggestion to use
“oai/request?verb=ListRecords&metadataPrefix=ore”.
However, that doesn’t seem to work either:
1) It uses “ <http://hdl.handle.net/%3cnumber%3e/%3cnumber%3e/ore.xml>
http://hdl.handle.net/<number>/<number>/ore.xml” as the atom:id to point to
the ore.xml, but it never resolves, even though
<http://hdl.handle.net/%3cnumber%3e/%3cnumber%3e>
http://hdl.handle.net/<number>/<number> will resolve to the item record.
2) I got stumped by the “bitstream.baseURL” for a bit, but then I
remembered that I was using OAI-PMH response caching. I found some problems*
when using the JSPUI for the bitstream.baseURL, so I’ve just switched to the
XMLUI, and that seems good for providing access to the bitstreams.
*There seems to be a problem with URL encoding? For instance,
jspui/bitstream/1/1/1/annual+report.pdf doesn’t work, but but
jspui/bitstream/1/1/1/annual%20report.pdf. Unfortunately, the former is what is
being displayed in the OAI-PMH ORE response, when using a “bitstream.baseURL”
with “JSPUI” in it. However, xmlui/bitstream/1/1/1/annual+report.pdf will work…
it’ll turn it into /xmlui/bitstream/handle/1/1/annual+report.pdf?sequence=1.
It really does seem that the OAI-PMH/OAI-ORE is set mostly set up to work with
the XMLUI rather than the JSPUI. Which is fine… we’ll just use the XMLUI
instead for harvesting purposes.
It also appears that neither the pre-3.x or 3.x+ methods for using OAI-ORE
actually work though :S. Surely someone must be using these successfully?
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St, Ultimo, NSW 2007
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of helix84
Sent: Wednesday, 22 April 2015 6:57 PM
To: Hilton Gibson
Cc: David Cook; dspace-tech
Subject: Re: [Dspace-tech] OAI-PMH/OAI-ORE Harvesting configuration
documentation
If DSpace is the harvester, you can harvest from any OAI-ORE-compliant provider.
If DSpace is the provider, it's only OAI-ORE-compliant if you point
bitstream.baseUrl in oai.cfg to the UI you want to serve bitstreams. It's
trivial but necessary because DSpace cannot know which UI you consider primary
if you have both deployed, so it doesn't try to guess.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
