Exclude others namespace from harvesting "oai_dc" metadata prefix #10837
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.
What this PR does / why we need it:
This PR allows the harvesting of certain repository who expose metadata with specific namespace.
Some repository extend the "oai_dc" with specific namespace. For example, SEANOE expose specific metadata with
dct
namespace. Below, the result of https://www.seanoe.org/oai/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:seanoe.org:41307Actually, this record can't be harvested because the following exception occurs :
We propose to ignore everything that is not the
dc
namespace which means skip theWstxParsingException
.Which issue(s) this PR closes:
No related issue funded
Special notes for your reviewer:
Not really but I've a suggestion to improve the scope of this pull request with another one (or issue) : the
ForeignMetadataFormatMapping
can be more flexible and can be used for more namespaces thandcterms
. With this, we can add a mapping fordct
namespaceSuggestions on how to test this:
Add a new harvesting client with
https://www.seanoe.org/oai/OAIHandler
server andGROUP:EMSO
set.Before the PR, all datasets are in error, with this PR, all datasets are imported.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No
Is there a release notes update needed for this change?:
A release note snippet has beed added