Solved. It now exposes confidence and authority data. Example:
Hi,As you know, all "metadatavalue" records have their own "authority" and"confidence" fields. We are using these fields. The intermediate XML of XOAIdoes not include data of these fields. So we can not translate it with any xslt.For example, please check the following url,http://dspace.lib.kanazawa-u.ac.jp/dspace-oai/request?verb=GetRecord&metadataPrefix=junii2&identifier=oai:dspace.lib.kanazawa-u.ac.jp:2297/30366There is a following "creator" element which has "id" attribute.<creator id="http://rns.nii.ac.jp/nr/1000090253335">Hasegawa, Hiroshi</creator>In this element, "Hasegawa, Hiroshi" is from "text_value" field and "1000090253335" isfrom "authority" field of the one metadatavalue record (dc.contributor.author).And we also use the "confidence" field of the record in order to judge whetherwe should include this attribute.I hope that you understand our situation by this explanation.Thank you,Keiji SuzukiEbetsu Japan2012/7/25 DSpace @ Lyncode <email@example.com>
Hi SUZUKI,OAI 2.0 exposed metadata could be easily changed. In fact one just need to change a specific XSL file (for example, using oai_dc schema: https://github.com/lyncode/DSpace/blob/dspace-with-xoai/dspace/config/modules/oai/metadataFormats/oai_dc.xsl). OAI 2.0 backward-compatiblity is of the most importance.As so i've opened an issue (https://github.com/lyncode/DSpace/issues/40). But could you be more specific? Which metadata fields aren't exposed? In which metadata schema?The referred 100% backward-compatiblity was tested against some validators and also some service providers.On 25 July 2012 06:23, SUZUKI Keiji <firstname.lastname@example.org> wrote:
Hi,It seems there are two problems in the current XOAI about itsbackward-compatiblity.1) It seems XOAI ignores authority and confidence data of metadata.Many Japanese repositories use these data to identify the authorin the crosswalk for the domestic metadata format.2) The form of bitstreams' url are for XMLUI although we set JSPUI as a"bitstreams.baseUrl" property in the xoai.cfg.The latter is a trivial and seems to be easy to fix, but if the formeris true, we will be able to change to XOAI.Keiji SuzukiEbetsu, Japan
2012/7/20 DSpace @ Lyncode <email@example.com>Yes, the default context (/request) is 100% backward-compatible.On 19 July 2012 17:01, Sands Alden Fish <firstname.lastname@example.org> wrote:
Forgive my ignorance here, but just wanted to be clear. Is the new OAI 100% backward-compatible, so that it includes all of the feature-set and identical interfaces/URL spaces that the original implementation has?
--Thanks, DSpace @ Lyncode
DSpace DepartmentLyncode: Official website