Failed With Unprocessable Entity about metha HOT 8 OPEN

using -no-intervals works

from metha.

Yes, it is strange. It used to work some months back which is why I wrote an email to zenodo to find out whether the changed any settings. It is weird that the indicate an Earliest Datestamp 2014-02-03T14:41:33Z and then nothing is returned from that interval.

Thanks for the fix. I'll try it out and get back to you.

from metha.

I can confirm that with 0.3.2 I am able to harvest without the -no-intervals flag. Thanks for fixing that so quickly!
In case a get answer from zenodo explaining the behaviour, I'll let you know.

from metha.

Interesting. It seems that your example query does not match any record, and the server chooses to return an HTTP/1.1 422 UNPROCESSABLE ENTITY for that. I added a workaround for the 422 error (although I haven't seen this failure that much in other endpoints, yet).

from metha.

I have just heard from Zenodo. They logged the issue and will report back with an update once the fixed it.

from metha.

Thanks for the update. Somehow, HTTP 422 does not seem so wrong, after all:

The HyperText Transfer Protocol (HTTP) 422 Unprocessable Content response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. -- https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/422

The OAI spec is not against using additional HTTP status codes: http://www.openarchives.org/OAI/openarchivesprotocol.html#StatusCodes

OAI-PMH repositories MAY employ HTTP Status-Codes in addition to "200 OK".

If I find other endpoints using HTTP 422, I'll make a note.

from metha.

Still I don't understand why the earliest timestamp would not return any data.

from metha.

The missing earliest timestamp issue I saw in other endpoints as well and that should be fixable.

from metha.