You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The results have a matchedNameID as a UUID. We do have our own 10 digit name identifiers and it would be better if they were used. They are described on this page:
These URIs handle semantic web content negotiation correctly.
I would recommend always using the IDs and links to names (ten digits without the name on the end) as they will always redirect to the current placement of that name and only use the classification specific 16 digit versions if the taxon concept used is particularly important.
This is a little confusing because the GNA is matching names but takes into account whether they are accepted names or not so loading new classifications will change that. But linking to names is best.
We will have a new data release on the December solstice so January might be a good time to make any changes.
Happy to help.
The text was updated successfully, but these errors were encountered:
I'm not sure how the ingest is done but it would good if we could have some changes made to the WFO data in the public instance of GNA.
Currently if I do a search like this:
https://verifier.globalnames.org/?all_matches=on&capitalize=on&ds=196&format=json&names=Rhododendron+ponticum
The results have a matchedNameID as a UUID. We do have our own 10 digit name identifiers and it would be better if they were used. They are described on this page:
https://list.worldfloraonline.org/
The outlink in the returned data is also broken
outlink": "http://www.worldfloraonline.org/taxon/wfo-0000400178-2023-12",
We describe how the stable URIs for names and taxa work on this page
https://list.worldfloraonline.org/sw_index.php
For example that one should be https://list.worldfloraonline.org/wfo-0000400178
These URIs handle semantic web content negotiation correctly.
I would recommend always using the IDs and links to names (ten digits without the name on the end) as they will always redirect to the current placement of that name and only use the classification specific 16 digit versions if the taxon concept used is particularly important.
This is a little confusing because the GNA is matching names but takes into account whether they are accepted names or not so loading new classifications will change that. But linking to names is best.
We will have a new data release on the December solstice so January might be a good time to make any changes.
Happy to help.
The text was updated successfully, but these errors were encountered: