Bug #9395
Invalid OAI Identify response
| Status: | Verified | Start date: | 02/02/2016 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Dan Gillean | % Done: | 0% | |
| Category: | Import/Export | |||
| Target version: | Release 2.3.0 | |||
| Google Code Legacy ID: | Tested version: | 2.2, 2.3 | ||
| Sponsored: | No | Requires documentation: |
History
#1 Updated by Jesús García Crespo over 6 years ago
- Status changed from In progress to QA/Review
- Assignee changed from Jesús García Crespo to Dan Gillean
Merged and squashed @ 712ce7b
#2 Updated by Dan Gillean over 6 years ago
- Status changed from QA/Review to Verified
- Requires documentation set to Yes
Looks good! Thank you so much to Damian Bauder for submitting this pull request to the AtoM project! From his original notes on the PR:
This will require an update to our sample response in the documentation, here:I noticed that the XML returned by the OAI Identify response does not validate. Validation would fail because of the format of the repositoryIdentifer and sampleIdentifier elements. This patch fixes the output of those elements and ensures validation succeeds.
...
Refer to the following:
- http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Identify, for information on the Identify response
- http://www.openarchives.org/OAI/2.0/guidelines.htm, section 3.1, for information on the description container
- http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm, for specifics on the oai-identifier format
#3 Updated by Dan Gillean about 6 years ago
- Requires documentation deleted (
Yes)
Updated Identify sample response added to 2.3 docs in https://github.com/artefactual/atom-docs/commit/2edd365ea8e0d216dce49a034879c01eb5f640d7