[
https://jira.duraspace.org/browse/DS-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27655#comment-27655
]
Mark H. Wood commented on DS-1479:
----------------------------------
Considering the way that <description> is supposed to work, the hardcoded
XOAIDescription element is reasonable -- it should be ignored by anything that
doesn't care about it. I think the correct approach would be to provide for
multiple additional <description>s. It might be appropriate to define a
contained <dspace> element of our own to help clients understand the service.
To address this issue, it might be good to be able to configure XOAI with a
list of paths or Files, at each of which is an XML document which could be
merged into the <Identify> as it is built. The data are to be XML anyway, and
making them complete documents would facilitate the use of validation tools and
such. Just load each file, pick out the document element, and enclose it in a
<description> element. Then we can configure something like "pmh.description =
dspace-pmh-description.xml theses-description.xml /foo/bar/more-if-we-wish.xml"
and be assured of either a well-formed response or an error logged (if one of
the files won't parse).
> In OAI-PMH "Identify" response, the <description> is no longer configurable
> ---------------------------------------------------------------------------
>
> Key: DS-1479
> URL: https://jira.duraspace.org/browse/DS-1479
> Project: DSpace
> Issue Type: Bug
> Components: OAI-PMH
> Affects Versions: 3.0, 3.1
> Reporter: Tim Donohue
> Assignee: João Melo
> Fix For: 4.0
>
>
> The OAI-PMH "identify" response (e.g.
> http://demo.dspace.org/oai/request?verb=Identify ) returns a hardcoded
> <description> which says "XOAI: OAI-PMH Java Toolkit ". In the old
> OAI-PMH interface (DSpace 1.8 and previous), this description was
> configurable.
> There are some use cases where this description tag may need to either be
> configurable, or allow for additional <description> elements to be added
> (according to OAI-PMH, multiple <description> elements are allowed:
> http://www.openarchives.org/OAI/openarchivesprotocol.html#Identify ). An
> example use case is described in this thread on dspace-tech:
> http://dspace.2283337.n4.nabble.com/Modify-Add-additional-OAI-Identify-Description-elements-td4661833.html
> The hardcoded <description> value seems to be coming from Lyncode XOAI
> codebase, so I've assigned this to João Melo from Lyncode. Here's the place
> where the value is hardcoded:
> https://github.com/lyncode/xoai/blob/master/src/main/java/com/lyncode/xoai/dataprovider/OAIDataProvider.java#L105
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
