Difference between revisions of "End-user workflows for name matching"

Revision as of 11:34, 21 August 2025

The workflows that end-users follow vary significantly based on the specific use case, ranging from checking a single name to uploading a regional or monographic checklist with thousands of names. There are four main types of name-matching processes:

1. Direct Use of the Name Matching Service: Utilizing the on-line tools provided directly by the service.
2. Using Third-Party Tools: Leveraging tools such as [OpenRefine] that access the name matching services.
3. Using a web-accessible API to access the name matching services.
4. Using Local Tools: Downloading the dataset provided and using local tools to perform the matching.

The choice of method mainly depends on the expected result but also on the number of records to be matched and on the technical in-house expertise available to the user. A type 3 or 4 process usually requires some expertise in biodiversity data management. TETTRIs provides links to download sites to get the aggregator's data. For type 2, TETTRIs will provide some example use cases that have been successfully tested. For type 1 (direct use of the aggregator’s services, the respective documentation will be pointed out in a list paralleling the list of general capabilities of aggregators.

The process itself can be divided into four phases:

1. Preparing the Data:
   • A text-only list of names is required, which can be created from a spreadsheet column or a table. Each name should be on a separate line.
2. Submitting the Data:
   • This phase depends on the chosen type of checking process.
3. Getting and Interpreting the Results:
   • For process types 1 and 2, results are provided as lists of exact matches and possible candidates. Interpretation involves assessing these candidates and selecting the correct match if appropriate.
4. Incorporating the Results Locally:
   • This involves making local corrections based on the matching results. It may also include integrating the aggregator’s name ID into the local dataset to enable linkage and potential interaction with the aggregator.

In the course of the project, we have first focused on OpenRefine, especially for medium to large datasets. However, not all relevant services provide an API that allows to use OpenRefine. We have also employed downloads and direct matching, for example for the herbarium and Euro+Med PlantBase use cases with the WFO Plant List. Realizing that many users are thoroughly confused by the offers available, we later focused on online matching mechanisms that do not require a technical background on the users side, i.e. those that either have a direct drag-n-drop interface or that allow uploads of files, or both.

The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the requirements posted by TETTRIs WP2. Close collaboration with the TETTRIs 3PP project on Taxonomic Name Linking Services (TNLS), along with the involvement of the Catalogue of Life as a project member, is expected to yield productive complementarity in enhancing end-user workflows.

To help users to make a choice of services and datasets available, TETTRIs is developing an online tool that allows users to enter their preferences and retrieve a list of potentially useful and available service/dataset combinations. A prototype of the tool ("CheckMyName - Taxonomic Name Matching Service Explorer") is nearing completion [August 2025].