-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harvest: Investigate OAI-PMH protocol test for registration as a data provider. #3307
Comments
Any informations/help needed about my pull request, or anything else about OAI-PMH (as much as I can help about it) ? |
- adds working implementation of ListRecords mechanism; - cleaner organization of the classes implementing and/or extending XOAI interfaces and classes; - more improvements and fixes.
This issue was just mentioned at https://groups.google.com/d/msg/dataverse-community/OlOsF5tJrrE/_FFRocaPAAAJ |
Passed on test env with small test data, failed on one test with full prod data: Checking for correct use of resumptionToken (if used) Request: GET http://dvn-vm5.hmdc.harvard.edu:8080/oai?verb=ListRecords&metadataPrefix=oai_dc [FAIL] A cursor value was supplied with the resumptionToken but it did not have the correct value zero for the first response. The value was '1'. |
Pushed a fix into the branch. |
OK, merged. Tests pass, submitted production url for registration though their process for https is currently manual on their end. Closing ticket! |
This came up in https://groups.google.com/d/msg/dataverse-community/_gLUaA47aOY/RVGfwOhqAgAJ . I accidentally, reconfirmed that this issue is fixed in 4.6, perhaps. 😄 |
The OAI-PMH website has information on registering as a data provider, including running a protocol test. We had done this for our first version of harvesting and would be good to do this for validation, improved interoperability, and increased data discovery (being on the list of data providers).
http://www.openarchives.org/pmh/register_data_provider
http://www.openarchives.org/pmh/register_data_provider#Protocol_Conformance_Testing
We currently pass the basic functionality test but have some issues on the in-depth test needed to register as a provider.
The text was updated successfully, but these errors were encountered: