GDCC fork with version 5 - polished codebase, new features, Java 11+ only

[poikilotherm]

Just a note: for Dataverse also relying on this library, we have been hacking on it to create a new version 5.0 and are near to a first release on Maven Central.

You may find it here https://github.com/gdcc/xoai

Would be nice to get in touch!

[tdonohue]

@poikilotherm : Somehow, I never saw your note from last year. Glad to hear that Dataverse is finding ways to improve/support this XOAI library!

Would you mind if I added a note to the README of DSpace/xoai to redirect others to gdcc/xoai if they are looking for a later copy of this XOAI library?

At this time, while DSpace still uses XOAI, we don't have a "product owner" or ongoing funding to support this XOAI library. So, it's only updated/maintained when DSpace needs to make a major change. Additionally, DSpace still only uses XOAI v3, and has never used v4.

I'd love for others to find a way to support this library together & we don't want to stand in the way of it. The DSpace team only took XOAI over when the original creator had to abandon it & was looking for a home for the code. DSpace claimed the code just to "keep it alive". But, at this time, we simply don't have any way to actively maintain it on behalf of others.

[poikilotherm]

Hi there @tdonohue good to hear from you!

Sure, if someone else find the updates useful, anyone shall be free to reuse. No promises though...

"We" did not have any kind of formal funding. I simply carved out time to do this, as we did not want to be stuck with old libraries and such. Feel free to give it a whirl!

That said, I dunno how much you actually tweaked the v3 library for DSpace. I'd be happy to give you a guided tour if you want to.

[tdonohue]

Thanks @poikilotherm ! I just updated the README to add a note about the lack of maintenance around here & linked folks to your fork if they need something newer: https://github.com/DSpace/xoai/#readme

At this time, DSpace is still back on v3 and somewhat "hardcoded" that way. We've been (slowly) maintaining v3 (just to get off older libraries), but at some point likely need to move on to v4 (or your v5). We will get in touch whenever we can find a way to prioritize that effort (or simply find a volunteer to help drive it forward).