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?

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

On Jul 19, 2012, at 11:59 AM, DSpace @ Lyncode wrote:

At the test phase i would recommend to use some tools specially designed for validating OAI-PMH interfaces. I've tested OAI 2.0 against those validators, but, of course, confidence grows with more results:

http://validator.oaipmh.com/
http://validator.driver.research-infrastructures.eu/ (Driver!)
http://www.openaire.eu:8380/dnet-validator-openaire (OpenAIRE)


On 19 July 2012 16:48, Tim Donohue <tdonohue@duraspace.org> wrote:
All,

Copying in dspace-devel. This thread likely should be over on -devel if
we want broader feedback.

On 7/19/2012 9:17 AM, Mark Diggory wrote:
>
>
> On Thursday, July 19, 2012, Robin Taylor wrote:
>
>     Hi Sands et al,
>
>     I inadvertently started a discussion on how to cater for addons to
>     DSpace yesterday but that wasn't my intention.
>
>
> I think I was as much to blame for this ;)
>
>       think we need to
>     consider what to do with the XOAI module but within the existing
>     framework. The Lyncode guys have gone to the trouble of contributing so
>     they deserve an answer of some sort. For the sake of discussion lets
>     assume its a good piece of work, the options would appear to be...
>
>     1. Replace the existing OAI module with the new one.
>
> The original OAI app hasn't changed in 10 years... No one really is here
> to support the original code... I think it's time is ripe to throw it out.
>
>     2. Distribute it alongside the old one.
>     3. Put the new module in Github somewhere but as a separate repo, as is
>     the case with dspace-rest. This gives it sort of semi-official status.
>     4. Do nothing.
>     5. Other options I can't think of.
>
>
> All these paths lead to greater complexity with the only benefit being,
> for some hypothetical status quo who fear change, not having to.
>
>
>     Any ideas ?
>
>
> Here's my position, the contribution of a solution to DSpace does not
> require a concensus vote, that would significantly slow the progress of
> contributing.  What is needed are one or two commiter "eyes" looking at
> the code to assure its sane and works, then agreeing to the pull
> request, accepting or rejecting it with comment.  We already made
> comments and recommendations, we need someone to quickly test the code
> and confirm it works, then accept the pull request.  The testing period
> will rat out any bugs...

+1 to what MarkD has said above.

I'd be of the frame of mind to *replace* the existing OAI with OAI-2.0,
ASSUMING that we get more eyes on OAI-2.0 and those
committers/developers are comfortable with the new implementation &
think it works well. Further testing can happen during Testathon.  I
also agree with MarkD's point that the existing OAI work is essentially
"unmaintained" for many years...

So, to anyone listening...if you have some time to try out OAI-2.0 (aka
XOAI) work, please provide us with your feedback! Relevant links:

Docs: https://wiki.duraspace.org/display/DSPACE/OAI+2.0
Download & Install from: http://www.lyncode.com/dspace/addons/xoai/
Add feedback/comments to: https://jira.duraspace.org/browse/DS-1202

It should be noted, that there is also the option of doing the following:

* Replace "OAI-1.0" with OAI 2.0, and *MOVE* the old OAI-1.0 code to a
place where people can download & install it if they are unsatisfied
with OAI 2.0.

Personally, I think we should try to get out of the habit of keeping old
modules (in this case OAI-1.0) around in the DSpace release as a "just
in case" measure. We can always make that old OAI-1.0 module available
for download separately, if people really need/want it.

Just my personal opinions here... If I'm in the minority though, that's
fine! :)

- Tim

------------------------------------------------------------------------------
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-release mailing list
Dspace-release@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-release



--
 
Thanks, DSpace @ Lyncode
DSpace Department
LyncodeOfficial website

------------------------------------------------------------------------------
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-release mailing list
Dspace-release@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-release




--
 
Thanks, DSpace @ Lyncode
DSpace Department
LyncodeOfficial website