correct urls for api requests + problem in local api url about gnverifier HOT 7 CLOSED

oups I meant https://github.com/gnames/gnparser#getting-the-simplest-possible-canonical-form

from gnverifier.

@abubelinha, if you want "stable until dead" API, it is better to use /api/v1

if you want to have "currently developed with new features, but less stable" then use /api/v0.

https://apidoc.globalnames.org/ (gnames API old, gnames API current) has both of them documented. I think /api/v0 is stabilizing now, so I do not expect huge changes there. When I feel it is doing all what it should do, I will release v1.0 for gnverifier, gnames, gnmatcher, and the api/v0 will become /api/v2.

I guess the point of confusion is the same domain name I use for production API (gnames) and its frontend (gnverifier). On a production site they both are verifier.globalnames.org, so it looks as if gnverifier local woud also have /api/v0 or /api/v1, but in reality it is just an nginx trickery.

I will add some warning in documentation about this, hopefully it will help to avoid confustion.

from gnverifier.

https://verifier.golobalnames.org got updated to v0.7.0, and I am going to actively develop all 3 verificaton components for the next few days, so website might be a bit ahead of binaries for the next few of days.

In your example

http://192.168.1.8:8052/api/v1/verifications/Tradescantia%20fluminensis

would not work, because gnverifier does not really have its own API, it only has a GET method for its form. So your example would not work. API so far exists only as a remote service. However:

I did update the database dump, so a local install is possible again (on Linux). But it
is much more work, and will become incompatible when database will evolve again.

So I would use remote api/v1 or api/v0 according to their documentations

from gnverifier.

When you call GET method on local recent gnverifier, it still goes to the remote /api/v0

It is just a convenience feature, so if someone has a question about a name, or want to submit a bug about a name verification, they can illustrate their question/problem with a URL like one you provided:

http://verifier.globalnames.org/?&format=json&names=Tradescantia+fluminensis

from gnverifier.

OK ... thanks a lot for clarifying multiple api versions.

I was assuming that gnverifier -p option was very much like gnparser (I thought the request would be redirected to a remote verifier api, so I could serve a "local api" for other machines which are restricted to LAN).
Understood now. It's not really that important.

Regarding my preferred_only=on failures, I still have not clear if this should work or not in any of the api versions. Any api url example? (where I set preferred data_sources and bestResult is not returned)

I also take the opportunity to ask ... where can I see an explanation of the different simple/full canonical names returned? Or an api url example where they show different values (i.e. matchedCanonicalSimple vs matchedCanonicalFull).
I'm sorry ... I think I have read about that somewhere before, but I don't recall where it was.

Thanks a lot for your patience

from gnverifier.

hm, preferred_only is actually currently a presentation modification feature of gnverifier. I guess I can add it to API

there is a secton about it in the gnparser docs. I added a table there, so it is a bit easier to find.

from gnverifier.

Thanks a lot again.
I just was wondering why preferred_only didn't work in API. Your clarification is enough.
Don't worry, I will just skip bestResult when I don't need it.

I think you posted a bad link?

from gnverifier.