Bionomia icon

Bionomia

Link natural history specimens to the world's collectors
Join our community

Actions6

  • Occurrence Actions
  • Occurrence Search Actions
  • Parse Actions
  • Person Actions
  • People Search Actions
  • Speciman Actions

Overview

This node integrates with the Bionomia API to parse human names into structured components. Specifically, the "Parse" resource with the "Get" operation takes a full human name as input and returns parsed details about that name. This is useful in scenarios where you need to extract or standardize parts of a person's name for further processing, such as linking natural history specimens to collectors or cleaning datasets containing personal names.

Practical examples:

  • Parsing a collector's full name from specimen metadata to separate given names and family names.
  • Standardizing author names in biodiversity databases.
  • Preparing names for matching against external authority files or identifiers.

Properties

Name Meaning
Human Name The full human name string to be parsed. Example: "Charles Darwin"

Output

The output is a JSON object representing the parsed components of the provided human name. The node returns the first element of the array response from the API, which typically includes structured fields such as given names, family names, initials, and possibly other metadata related to the name parsing.

The exact structure depends on the Bionomia API response but generally includes:

  • Parsed name parts (e.g., given name, family name)
  • Possibly normalized or canonical forms
  • Additional metadata if available

No binary data is returned by this node.

Dependencies

  • Requires internet access to call the Bionomia API endpoints.
  • No explicit credentials are required for the "Parse" resource "Get" operation.
  • The node uses HTTP GET requests with Accept: application/json headers to fetch data.

Troubleshooting

  • Common issues:

    • Network connectivity problems may cause request failures.
    • Providing an empty or invalid human name string will likely result in an error or empty response.
    • Rate limiting by the Bionomia API could cause temporary failures.

  • Error messages:

    • HTTP errors (e.g., 4xx or 5xx) indicate issues with the request or server.
    • JSON parsing errors might occur if the API response format changes unexpectedly.

  • Resolutions:

    • Ensure the "Human Name" property is correctly filled and URL-encoded.
    • Check network connectivity and API availability.
    • Handle API rate limits by adding retries or delays if necessary.

Links and References

Discussion