Difference between revisions of "Target aggregator's resolvable name ID"

From TETTRIs
Jump to: navigation, search
m
 
Line 10: Line 10:
 
[under construction]
 
[under construction]
 
===Algaebase===
 
===Algaebase===
Name-ID: <br />
+
Name-ID: Yes, taxa above species carry a number, species and below a species_id <br />
Resolvable:<br />
+
Resolvable: YES, examples: [[https://www.algaebase.org/browse/taxonomy/#198021 https://www.algaebase.org/browse/taxonomy/#198021]], [[https://www.algaebase.org/search/species/detail/?species_id=190498 https://www.algaebase.org/search/species/detail/?species_id=190498]<br />
Resolves to (taxon or name): <br/>
+
Resolves to (taxon or name): name page<br/>
 
===Australian Plant Name Index===
 
===Australian Plant Name Index===
 
Name-ID: <br />
 
Name-ID: <br />

Latest revision as of 14:36, 23 May 2024

Purpose

What can be achieved by matching and storing an aggregator name ID in the local database?
Having revised and matched the names and as a result incorporating a NAME ID establishes an unequivocal link between the local name and the name in the aggregator treatment. This enables direct linking to a name and its (potentially changing) treatment (but without the ambiguity introduced by a search on the canonical name string). The link could also be shown on the local website, enabling its users to do the same.
A further step, not yet realized by target aggregators, is to offer a "taxon concept subscription" that notifies users about changes in the circumscription of taxa on the aggregator's side.
Resolvable IDs also open possibilities for semantic linking and searching in various contexts.
The simple lookup could of course also be done by the "canonical name" string (i.e. name without authors and/or year), but this does not really deal with homonyms and orthographic variants, so a once done revision needs to be repeated on the user's side because the results may be ambiguous. Moreover, the link may simply not work if the aggregator corrects errors in the orthography.

Aggregator IDs

We have looked at the handling and resolution of IDs in the following target aggregators. [under construction]

Algaebase

Name-ID: Yes, taxa above species carry a number, species and below a species_id
Resolvable: YES, examples: [https://www.algaebase.org/browse/taxonomy/#198021], [https://www.algaebase.org/search/species/detail/?species_id=190498
Resolves to (taxon or name): name page

Australian Plant Name Index

Name-ID:
Resolvable:
Resolves to (taxon or name):

Catalogue of Life

Name-ID:
Resolvable:
Resolves to (taxon or name):

Checklist Bank (GBIF & Catalogue of Life)

Name-ID:
Resolvable:
Resolves to (taxon or name):

Euro+Med PlantBase

Name-ID:
Resolvable:
Resolves to (taxon or name):

GBIF Taxonomic Backbone

Name-ID:
Resolvable:
Resolves to (taxon or name):

Global Names Verifier

Name-ID:
Resolvable:
Resolves to (taxon or name):

Index Fungorum

Name-ID:
Resolvable:
Resolves to (taxon or name):

International Plant Name Index (IPNI)

Name-ID:
Resolvable:
Resolves to (taxon or name):

LifeWatch

Name-ID:
Resolvable:
Resolves to (taxon or name):

PESI

Name-ID:
Resolvable:
Resolves to (taxon or name):

TNRS Taxonomic Name Resolution Service

Name-ID:
Resolvable:
Resolves to (taxon or name):

Tropicos

Name-ID:
Resolvable:
Resolves to (taxon or name):

World Flora Online WFO Plant List

Name-ID:
Resolvable:
Resolves to (taxon or name):

WoRMS (World Register of Marine Species)

Name-ID:
Resolvable:
Resolves to (taxon or name):