DS-2915 oai database fixes #1189
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As of DSpace 6, the OAI-PMH database backend has been retired. OAI-PMH now only supports the Solr backend. This was a result of https://jira.duraspace.org/browse/DS-2701 Therefore, I'm closing this ticket as "won't fix". The code is still available for anyone using 5.x, if they want it. But, at this point there are no additional 5.x releases planned. |
tdonohue
added
the
won't fix
|
Hi Tim. May I argue that there have been new releases of 5.x since and that merging to the 5.x branch would allow existing 5.x users to benefit from the fix above? I just rebased the idmgroup/Dspace/DS-2915-oai-database-fixes branch in case you change your mind. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://jira.duraspace.org/browse/DS-2915
Hi, I've just fixed the SQL query and slightly modified the order of OAI sets so that it is the same as when storage=solr.
Could you double check there is no mistake in the query and pull this change please?