Documentation is apparently wrong

[amouat]

The documentation of the API at https://github.com/CatchPlus/EPIC-API-v2/wiki/Core-API seems to be completely wrong.

URLs do not take the form «root»/NAs/«NAsegment»/handles/«LNsegment»/ as suggested, and attempting to use * for LNsegment in a POST does not work.

[pieterb]

Indeed, the Core-API definition you refer to is completely outdated. The real, up-to-date, API documentation is in the web-service itself, when you approach it with a web-browser.

I hope that helps for now...

[amouat]

Well, not really when you're trying to do PUTs and POSTs via the REST API.

Please mark the documentation as out of date.

I did eventually find some incomplete but usable documentation on the EUDAT wiki.

[pieterb]

Ah, I see. If you GET a URL that you're planning to PUT or POST to, it will tell you which verbs it supports, and what kind of data it expects. Does that make sense?

[amouat]

I have to say I never noticed the small "Help" button in the upper right corner. It does rather seem to be hiding.

However, it's still nowhere near complete or sufficient.

For example, if I go to https://epic.sara.nl/v2_test/handles/842/ I get no inkling that I need to do a POST command (without a *) with correctly formatted JSON in order to get EPIC to generate a handle with a randomised PID.

(In fact, I wonder if we are talking about the same thing, as there is no mention of the supported verbs)

[pieterb]

Can't disagree with you there.

I'm not sure about the current status of this software. I used to be its main developer while I worked at SURFsara in Amsterdam. I no longer work there, and development has abruptly stopped since. I offered SURFsara to further develop this software (I sent them a quote), but the offer was declined.

I've been told that EUDAT has interest in a (Handle System based) PID web service. If you're looking at this software as a member of the EUDAT project, maybe we should discuss this issue offline. I'll contact you through LinkedIn.