Hi Kevin João,
I finally got around to creating a JIRA ticket for this bug.
It's at:
https://jira.duraspace.org/browse/DS-1479
- Tim
On 2/5/2013 1:45 PM, João Melo wrote:
Hi Tim and Kevin,
as the initial purpose of this new OAI module was (also) to guarantee
100% backward compatibility,
Hi Kevin,
To add or change the OAI-PMH elements in the new DSpace 3.x OAI
interface (aka XOAI), you can just modify the proper crosswalk.
XOAI uses a variety of metadataFormat crosswalks which all exist in:
[dspace]/config/crosswalks/oai/metadataFormats/
In this case, it sounds like you just
Hi Tim,
Thanks for the reply. I don't think this is what I'm looking for though -
as per the requirements of Theses Canada, the description element must be
included in the OAI-PMH Identify response. Currently, the default value
of the description element that I get when making an Identify request
Hi Kevin,
Yes, I misunderstood. I now see what you mean..
It looks like, unfortunately, in both DSpace 3.0 and 3.1 this Identify
response description value is hardcoded. It's actually not the DSpace
source code itself, but rather in the com.lyncode.xoai library that
DSpace uses. This
Hi Tim and Kevin,
as the initial purpose of this new OAI module was (also) to guarantee 100%
backward compatibility, in the following weeks i'll pull for this change
(configurable description).
PS - It would be better to create a jira issue.
On 5 February 2013 18:40, Tim Donohue
5 matches
Mail list logo
