Keiji, I'm guessing you meant to say that "if the former is true, we will *not* be able to change to XOAI" ?

--
sands fish
Senior Software Engineer
MIT Libraries
Technology Research & Development
sands@MIT.EDU
E25-131

On Jul 25, 2012, at 1:23 AM, SUZUKI Keiji wrote:

Hi,

It seems there are two problems in the current XOAI about its
backward-compatiblity.

1) It seems XOAI ignores authority and confidence data of metadata.
   Many Japanese repositories use these data to identify the author
   in 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 former 
is true, we will be able to change to XOAI.

Keiji Suzuki
Ebetsu, Japan

2012/7/20 DSpace @ Lyncode <dspace@lyncode.com>
Yes, the default context (/request) is 100% backward-compatible.

On 19 July 2012 17:01, Sands Alden Fish <sands@mit.edu> 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?



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel