AtoM returns "badVerb" response instead of "cannotDisseminateFormat" when OAI-PMH request made for unavailable metadata format
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
First reported via the user forum, 2016-09-06: https://groups.google.com/d/msg/ica-atom-users/EsoaZ9xWfvs/n_2s1P49BwAJ
- Ensure the OAI plugin is enabled, and that your OAI repository is configured in Admin > Settings
- Try something like the following request (requesting oai_ead, a format we do not support):
AtoM returns a "badVerb" response:
<OAI-PMH xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2016-09-07T19:43:34Z</responseDate><request verb="ListIdentifiers" metadataPrefix="oai_ead">http://www.example.com/;oai</request> <error code="badVerb">The metadata format identified by the value given for the metadataPrefix argument is not supported by the item or by the repository.</error> </OAI-PMH>
According to OAI-PMH, AtoM should return a "cannotDisseminateFormat response when the verb itself is valid but the format requested is not. This should be the case for the following verbs:
The user who reported the bug has also provided a patch. From the description in the user forum, it sounds like the patch might only deal with the ListRecords response - but it's still an improvement. Attaching the patch so it can be code reviewed and potentially merged.
#7 Updated by Dan Gillean almost 4 years ago
- Status changed from QA/Review to Verified
I found what appears to be a regression while testing for this, but after testing before the merge, I think this is unrelated to the patch. The fix itself does what it advertises; marking verified.
Thanks to Martin Malmsten for this bug report and community code contribution!