TETTRIs Name Matching API

The TNLS (Taxonomic Name Linking Services) was a sub project of TETTRIs (Transforming European Taxonomy through Training, Research and Innovations). Its purpose was to enable TETTRIs participants to link their services with those of the major, global taxonomic datasets thus aligning multiple datasets to a common, global taxonomic backbone system. The first work area in TNLS was to develop a common name matching design pattern applicable across multiple projects.

This is an demonstration of that initial common design pattern. Its aim is to explore the concept rather than be a finished tool.

Twenty different name matching services were surveyed. Forty input parameters were found across the services. There were six parameters that were considered common to all. Sixty different output fields were identified. Analysis narrowed these down to six common fields. These input parameters and output fields have been mapped to the WFO Plant List dataset and can be explored below.

Common Input Parameters

This form implements the six common input parameters identified. The shared documentation in highlighted in blue. The WFO implemenation is in grey.

# Parameter Type Definition Notes
1 name string The full scientific name of the organism as defined by an appropriate nomenclatural code. Required. This may include the rank part of a name, the authority string and the year of publication where appropriate.
WFO's default is to assume the author string is included in the name.
2 authorship string A string representation of the authors of the name. If the client is able to pass this as a separate field.
This is implemented as a filter to restrict results to names matching this authors string exactly.
3 year integer The year of publication of the name as an integer. The match must be published in this year if it is provided. More relevant in zoology than botany.
94% of names in the WFO Plant List have the year of publication specified as a separate field.
4 rank string The matching name must be at this rank or ranks if provided. It is recommended the service provides a controlled vocabulary for this field.
WFO has a controlled vocabulary of 29 ranks.
5 kingdom string The matching name must be within this kingdom (e.g. Animalia, Plantae, Fungi, Protista, Archaea and Bacteria) Useful for data aggregators covering all forms of life. Limits matching to a single nomenclatural code and prevents cross code homonyms.
Defaults to Plantae The WFO Plant List only contains names from the plant kingdom.
6 include_accepted boolean If the name matched is considered a synonym by the data source then also return the accepted name. Differentiates between pure nomenclators that are only providing name matching services and taxonomic services.
  WFO includes general taxonomic placement data in response to this parameter.
Clear  

Common Output Fields

The table below are suggestions of a minimum set of common fields. Services are likely to provide many more than these core fields depending on their user requirements.
Field Name Type Definition Notes
ID string A persistent, unique (within the scope of the database or globally) identifier for this name object and or taxon. Services may provide standard ways to convert local IDs to global (e.g. prepend URL). Should not change when name spelling changes.
name string The full scientific name of the organism as defined in by an appropriate nomenclatural code. The correct way to cite the name according to the service provider.
name_html (optional) string The same as name but with the code mandated italics parts of the name delimited with <i> tags. This is to allow client software to render the names correctly without needing to re-parse them.
authorship (optional) string A string representation of the authors of the name. The correct author string for the name ideally following any domain standards such as IPNI authors.
accepted (optional) boolean Whether the name is an accepted name of a taxon or not. Can be ignored by pure nomenclator services.
placement (optional) array Where the name is placed in the classification./td> How this is presented will depend on the service. It could be a single string path or a more complex structure.