End-user workflows for name matching - Revision history

WalterBerendsohn at 15:35, 22 September 2025

2025-09-22T15:35:59Z

← Older revision		Revision as of 17:35, 22 September 2025
Line 2:		Line 2:
	#'''Direct Use of the Name Matching Service:''' Utilizing the on-line tools provided directly by the service.		#'''Direct Use of the Name Matching Service:''' Utilizing the on-line tools provided directly by the service.
	#'''Using Third-Party Tools:''' Leveraging tools such as [[https://openrefine.org/ OpenRefine]] that access the name matching services.		#'''Using Third-Party Tools:''' Leveraging tools such as [[https://openrefine.org/ OpenRefine]] that access the name matching services.
	#'''Using a web-accessible API''' to access the name matching services.		#'''Using a web-accessible API''' or a programming package to access the name matching services.
	#'''Using Local Tools:''' Downloading the dataset provided and using local tools to perform the matching.		#'''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 [[Taxonomic datasets\|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 ~~are~~ pointed out in a [[Name matching services\|list of general capabilities of aggregators]].		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 [[Taxonomic datasets\|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 is pointed out in a [[Name matching services\|list of general capabilities of aggregators]].

	The process itself can be divided into four phases:		The process itself can be divided into four phases:
Line 18:		Line 18:
	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, and for many users, OpenRefine (in spite of its quite straight-forward procedures) seems to be an overly technical tool. 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.		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, and for many users, OpenRefine (in spite of its quite straight-forward procedures) seems to be an overly technical tool. 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 [[Aggregator_services_wish_list\|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.		The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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, yielded 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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/a/a9/2025-09-22-CheckMyName-Description.pdf this document].		To help users to make a choice of services and datasets available, TETTRIs has developed 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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/a/a9/2025-09-22-CheckMyName-Description.pdf this document]. The choice of criteria to define the user's needs as well as the corresponding metadata needed to make a choice will be detailed in a forthcoming article.

WalterBerendsohn at 15:27, 22 September 2025

2025-09-22T15:27:42Z

← Older revision		Revision as of 17:27, 22 September 2025
Line 20:		Line 20:
	The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.		The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in ~~[[:File:2025-09-22-CheckMyName-Description.pdf\|this document]].~~ [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/a/a9/2025-09-22-CheckMyName-Description.pdf this document]		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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/a/a9/2025-09-22-CheckMyName-Description.pdf this document].

WalterBerendsohn at 15:27, 22 September 2025

2025-09-22T15:27:07Z

← Older revision		Revision as of 17:27, 22 September 2025
Line 20:		Line 20:
	The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.		The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [[:File:2025-09-22-CheckMyName-Description.pdf\|this document]].		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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [[:File:2025-09-22-CheckMyName-Description.pdf\|this document]]. [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/a/a9/2025-09-22-CheckMyName-Description.pdf this document]

WalterBerendsohn at 15:25, 22 September 2025

2025-09-22T15:25:32Z

← Older revision		Revision as of 17:25, 22 September 2025
Line 20:		Line 20:
	The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.		The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in this document.		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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in [[:File:2025-09-22-CheckMyName-Description.pdf\|this document]].

WalterBerendsohn at 15:00, 22 September 2025

2025-09-22T15:00:39Z

← Older revision		Revision as of 17:00, 22 September 2025
Line 4:		Line 4:
	#'''Using a web-accessible API''' to access the name matching services.		#'''Using a web-accessible API''' to access the name matching services.
	#'''Using Local Tools:''' Downloading the dataset provided and using local tools to perform the matching.		#'''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 [[Taxonomic datasets\|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~~ [[Name matching services\|list of general capabilities of aggregators]].		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 [[Taxonomic datasets\|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 are pointed out in a [[Name matching services\|list of general capabilities of aggregators]].

	The process itself can be divided into four phases:		The process itself can be divided into four phases:

WalterBerendsohn at 14:59, 22 September 2025

2025-09-22T14:59:07Z

← Older revision		Revision as of 16:59, 22 September 2025
Line 4:		Line 4:
	#'''Using a web-accessible API''' to access the name matching services.		#'''Using a web-accessible API''' to access the name matching services.
	#'''Using Local Tools:''' Downloading the dataset provided and using local tools to perform the matching.		#'''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 [[~~Downloads_from_aggregators~~\|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 [[~~Existing_name_checking_mechanisms~~\|list of general capabilities of aggregators]].		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 [[Taxonomic datasets\|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 [[Name matching services\|list of general capabilities of aggregators]].

	The process itself can be divided into four phases:		The process itself can be divided into four phases:
Line 16:		Line 16:
	#*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.		#*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.		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, and for many users, OpenRefine (in spite of its quite straight-forward procedures) seems to be an overly technical tool. 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 [[Aggregator_services_wish_list\|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.		The ongoing effort to document these processes faces a moving target, as the main services and datasets are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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 ([https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"]~~) is nearing completion [August 2025]~~.		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 is provided as [https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"] and described in more detail in this document.

WalterBerendsohn at 10:34, 21 August 2025

2025-08-21T10:34:25Z

← Older revision		Revision as of 12:34, 21 August 2025
Line 1:		Line 1:
	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 ~~three~~ main types of name-~~checking~~ processes:		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:
	#'''Direct Use of the ~~Aggregator's~~ Name Matching ~~Mechanisms~~:''' Utilizing the tools provided directly by the ~~aggregator~~.		#'''Direct Use of the Name Matching Service:''' Utilizing the on-line tools provided directly by the service.
	#'''Using Third-Party Tools:''' Leveraging tools such as [[https://openrefine.org/ OpenRefine]] that access the ~~aggregator~~'s name matching services.		#'''Using Third-Party Tools:''' Leveraging tools such as [[https://openrefine.org/ OpenRefine]] that access the name matching services.
	#'''Using Local Tools:''' Downloading the ~~aggregator's data~~ and using local tools to perform the matching.		#'''Using a web-accessible API''' to access the name matching services.
	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 process usually requires some expertise in biodiversity data management. TETTRIs provides links to [[Downloads_from_aggregators\|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 [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].		#'''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 [[Downloads_from_aggregators\|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 [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].
	The choice of method depends on the expected outcome, the volume of records to be matched, and the technical expertise available to the user. Type 3 processes generally require expertise in biodiversity data management. TETTRIs offers links to [[Downloads_from_aggregators\|download sites]] for the aggregator's data. For type 2 processes, TETTRIs provides example use cases that have been successfully tested. For type 1 processes, relevant documentation will be documented paralleling the listed [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].

	The process itself can be divided into four phases:		The process itself can be divided into four phases:
Line 15:		Line 14:
	#*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.		#*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.
	#'''Incorporating the Results Locally:'''		#'''Incorporating the Results Locally:'''
	#*This involves making local corrections based on the matching results. It also ~~includes~~ integrating the aggregator’s name ID into the local dataset to enable linkage and potential interaction with the aggregator.		#*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 [[Aggregator_services_wish_list\|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.

	~~We currently focus on OpenRefine for medium~~ to ~~large~~ datasets~~. The current effort~~ to ~~document these processes faces~~ a ~~moving target, as the main aggregators are continuously evolving, hopefully influenced by~~ the [~~[Aggregator_services_wish_list\|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 ([https://wiki.bgbm.org/tettriswiki/uploads/tettriswiki/demo/ "CheckMyName - Taxonomic Name Matching Service Explorer"]) is nearing completion [August 2025].

WalterBerendsohn at 12:08, 23 May 2024

2024-05-23T12:08:26Z

← Older revision		Revision as of 14:08, 23 May 2024
Line 17:		Line 17:
	#*This involves making local corrections based on the matching results. It also includes integrating the aggregator’s name ID into the local dataset to enable linkage and potential interaction with the aggregator.		#*This involves making local corrections based on the matching results. It also includes integrating the aggregator’s name ID into the local dataset to enable linkage and potential interaction with the aggregator.

	The current effort to document these processes faces a moving ~~targets~~, as the main aggregators are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.		We currently focus on OpenRefine for medium to large datasets. The current effort to document these processes faces a moving target, as the main aggregators are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.

WalterBerendsohn at 12:02, 23 May 2024

2024-05-23T12:02:23Z

← Older revision		Revision as of 14:02, 23 May 2024
Line 7:		Line 7:
	The choice of method depends on the expected outcome, the volume of records to be matched, and the technical expertise available to the user. Type 3 processes generally require expertise in biodiversity data management. TETTRIs offers links to [[Downloads_from_aggregators\|download sites]] for the aggregator's data. For type 2 processes, TETTRIs provides example use cases that have been successfully tested. For type 1 processes, relevant documentation will be documented paralleling the listed [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].		The choice of method depends on the expected outcome, the volume of records to be matched, and the technical expertise available to the user. Type 3 processes generally require expertise in biodiversity data management. TETTRIs offers links to [[Downloads_from_aggregators\|download sites]] for the aggregator's data. For type 2 processes, TETTRIs provides example use cases that have been successfully tested. For type 1 processes, relevant documentation will be documented paralleling the listed [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].

	~~For the~~ process itself~~, we~~ can ~~in principle distinguish 4~~ phases:		The process itself can be divided into four phases:
	*Preparing the ~~data~~		#'''Preparing the Data:'''
	~~In all cases, a~~ list of names is ~~needed in text-only format~~, which can be created from a spreadsheet column or ~~be part of~~ a table ~~containing these names~~. ~~One~~ name ~~only in one~~ line ~~is always required~~.		#*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.
	*Submitting the ~~data~~		#'''Submitting the Data:'''
	~~Depends~~ on the type of checking process.		#*This phase depends on the chosen type of checking process.
	*Getting and ~~interpreting~~ the ~~results~~		#'''Getting and Interpreting the Results:'''
	~~Essentially, for~~ process ~~type~~ 1 and 2 ~~the~~ results are provided ~~by listing~~ exact matches and possible candidates~~, i.e. names that match the input to a certain extent~~. Interpretation ~~refers to~~ assessing ~~the~~ candidates and~~, if appropriate,~~ selecting ~~one of them as~~ the correct match.		#*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.
	*Incorporating the ~~results locally~~		#'''Incorporating the Results Locally:'''
	On the ~~one hand, this refers to corrections of names made locally as a result of candidate~~ matching. On the ~~other hand, once matches were made unambiguously, this may result in incorporating the aggregator's~~ name ID into the local dataset, to ~~allow~~ linkage to the ~~aggregator and~~ (~~if such functionality is made available~~) ~~interaction~~ with the ~~aggregator~~.		#*This involves making local corrections based on the matching results. It also includes integrating the aggregator’s name ID into the local dataset to enable linkage and potential interaction with the aggregator.

			The current effort to document these processes faces a moving targets, as the main aggregators are continuously evolving, hopefully influenced by the [[Aggregator_services_wish_list\|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.

WalterBerendsohn at 11:45, 23 May 2024

2024-05-23T11:45:11Z

← Older revision		Revision as of 13:45, 23 May 2024
Line 1:		Line 1:
	The ~~details of~~ workflows that end-users follow ~~very strongly depends~~ on the ~~individual~~ use case, ~~which may range~~ from checking a single name to uploading a regional or monographic checklist with thousands of names.		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 three main types of name-checking processes:
	~~Three~~ types of ~~the~~ checking ~~process itself can be distinguished~~:		#'''Direct Use of the Aggregator's Name Matching Mechanisms:''' Utilizing the tools provided directly by the aggregator.
	#~~Directly using~~ the ~~name matching mechanisms~~ the aggregator ~~provides~~		#'''Using Third-Party Tools:''' Leveraging tools such as [[https://openrefine.org/ OpenRefine]] that access the aggregator's name matching services.
	#Using ~~a tool that accesses the aggregator~~'~~s name matching services (~~such as [[https://openrefine.org/ OpenRefine]])		#'''Using Local Tools:''' Downloading the aggregator's data and using local tools to perform the matching.
	#Using ~~local tools (following a download of~~ the aggregator's data)
	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 process usually requires some expertise in biodiversity data management. TETTRIs provides links to [[Downloads_from_aggregators\|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 [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].		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 process usually requires some expertise in biodiversity data management. TETTRIs provides links to [[Downloads_from_aggregators\|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 [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].

			The choice of method depends on the expected outcome, the volume of records to be matched, and the technical expertise available to the user. Type 3 processes generally require expertise in biodiversity data management. TETTRIs offers links to [[Downloads_from_aggregators\|download sites]] for the aggregator's data. For type 2 processes, TETTRIs provides example use cases that have been successfully tested. For type 1 processes, relevant documentation will be documented paralleling the listed [[Existing_name_checking_mechanisms\|list of general capabilities of aggregators]].

	For the process itself, we can in principle distinguish 4 phases:		For the process itself, we can in principle distinguish 4 phases: