Conform fully to the OAI2 standard
| Project: | OAI-PMH Module |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I recently tried registering our drupal site with http://www.openarchives.org/ but their validation on registration wouldn't let me continue because the OAI feed failed most of their tests. I've included some blurb from the email I received below:
Complete log available at
http://www.openarchives.org/Register/ValidateSite?log=2018...............................................................................
Unfortunately your repository did not validate at version 2.0 of the OAI-PMH according to our OAI protocol conformance tester. The errors received during testing are listed below.
[1] Datestamp in GetRecord response (2008-06-17T15:34:32ZZ) is not valid. See [http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Dates].
[2] ListRecords gave an unexpected error response to a request using from and until datestamps taken from the previous GetRecord response: badArgument (The value '2008-06-17T15:34:32ZZ' of the argument 'from' is not valid.)
[3] Error code noRecordsMatch should be given to the request:
verb=ListRecords&metadataPrefix=oai_dc&until=2007-02-19T12:12:50Z The request specified a date one year before the earliestDatestamp given in the Identify response. There should therefore not be any records with datestamps on or before this date and a noRecordsMatch error code should be returned.[4] POST test 1 was unsuccessful. Response to Identify was:
<?xml version="1.0" encoding="UTF-8"?>2008-06-23T12:19:21Z
http://www.ies.aber.ac.uk/oai
The request does not provide any verb.[5] POST test 2 was unsuccessful. Response to Identify was:
<?xml version="1.0" encoding="UTF-8"?>2008-06-23T12:19:22Z
http://www.ies.aber.ac.uk/oai
The request does not provide any verb.SUMMARY:
Total exceptions improperly handled: 3 out of 15 Total error count: 5
#1
I've just made available a new version (1.2) which should fix this problems. You must run update,php after installation because I had to make a small change to one of the database tables.
Ron.
#2
Hi Ron,
Thats brilliant! Thanks so much for your work on the biblio project, I am making heavy use of it on a university deparment website: http://www.ies.aber.ac.uk/ All the staff were impressed with the available functionality, so I'd like to pass on their thanks too!
Have fun,
Matt.
#3
Hi Ron,
There are still issues with what the OpenArchive standard expects, here is the latest log:
http://www.openarchives.org/Register/ValidateSite?log=30477
Looks like one of the main chunks of error is that post requests instead of get requests are not supported currently. It's not that important for me to register this, but I figure if there is going to be an OAI-PMH module it's probably best to make it conform to the standard. There isn't much else you can do with OAI other than register it :D I can take a look at the code at some point if you think this is low priority, compared with your other commitments to Drupal.
Thanks for your efforts,
Matt.
#4
Hmmm, I had used this repository explorer for validation (http://re.cs.uct.ac.za/), but it seems to differ from the one used for data providers. I'll look into it.
Ron.
#5
OK, version 1.3 now validates my site at http://www.openarchives.org/Register, so give it a try...
Ron.
#6
Hi Ron,
Great work on this, thank you! It's all working and our repository has been registered as conforming.
Total error count: 0Your repository is robust as well as compliant
Conplete log:
http://www.openarchives.org/Register/ValidateSite?log=3047
#7
Good to hear I finally squashed all those bugs. It was actually an interesting exercise which revealed some flaws in the code logic which I hadn't seen before.
Ron.
#8
Automatically closed -- issue fixed for two weeks with no activity.