GlobalNames icon

GlobalNames

GlobalNames helps parse, find, and verify scientific names

Actions3

  • Finder Actions
  • Parse Actions
  • Verify Actions

Verify → Get

AI-generated

Overview

This node integrates with the GlobalNames services to parse, find, and verify biological scientific names. Specifically, the Verify - Get operation allows users to verify a given scientific name by querying the GlobalNames verification API.

Typical use cases include:

  • Validating scientific names in biological datasets to ensure correctness.
  • Enriching data quality by confirming that names conform to recognized taxonomies.
  • Automating workflows where scientific name validation is required before further processing or analysis.

For example, a researcher can input a scientific name like Homo sapiens and get back verification details confirming its validity and associated metadata.

Properties

Name Meaning
Scientific Name A biological scientific name string to be verified (e.g., "Homo sapiens").
With Details Boolean flag indicating whether to include detailed information in the verification response. Defaults to true.

Output

The node outputs a JSON array containing the verification result(s) for the provided scientific name(s). The structure corresponds to the response from the GlobalNames verification API and typically includes:

  • Verification status of the scientific name.
  • Metadata about the name such as matched canonical form, authorship, and taxonomic details.
  • Additional details if the "With Details" property is enabled.

No binary data output is produced by this node.

Dependencies

  • Requires internet access to call the GlobalNames verification API endpoint.
  • No explicit API key or credential is required based on the code, but network connectivity is essential.
  • The node uses standard HTTP GET requests to the URL: https://verifier.globalnames.org/api/v0/verifications/{encodedScientificName}.

Troubleshooting

  • Common issues:

    • Network connectivity problems may cause request failures.
    • Providing an invalid or empty scientific name will likely result in an error or empty verification results.
    • If the API service is down or unreachable, the node will fail to return verification data.

  • Error messages:

    • HTTP errors (e.g., 404, 500) indicate issues with the API endpoint or the requested resource.
    • JSON parsing errors could occur if the API response format changes unexpectedly.

  • Resolutions:

    • Ensure the scientific name is correctly spelled and properly encoded.
    • Verify internet connection and API availability.
    • Retry after some time if the service is temporarily unavailable.

Links and References

Discussion