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

The node integrates with the Bionomia service to link natural history specimens to their collectors and related data. Specifically, for the Person - Get operation, it retrieves detailed information about a person identified by an ORCID or Wikidata ID. This is useful in biodiversity informatics workflows where you want to enrich specimen or occurrence data with authoritative collector or researcher details.

Practical examples include:

  • Fetching biographical or identifier data for a collector referenced in specimen records.
  • Enriching datasets with linked person metadata from ORCID or Wikidata.
  • Automating data curation pipelines that require validation or augmentation of collector identities.

Properties

Name Meaning
ID The unique identifier for a person, which can be either an ORCID or a Wikidata ID. This is required to fetch the person's data from Bionomia.

Output

The output is a JSON array containing one or more objects representing the person’s data retrieved from Bionomia. The structure corresponds to the JSON-LD format returned by the Bionomia API, typically including fields such as identifiers, names, affiliations, and linked specimens.

No binary data is output by this operation.

Example output snippet (simplified):

[
  {
    "@context": "...",
    "@id": "https://bionomia.net/{personID}",
    "name": "Full Person Name",
    "identifiers": [...],
    "affiliations": [...],
    "specimens": [...]
  }
]

Dependencies

  • Requires internet access to call the Bionomia REST API endpoints.
  • No explicit API key or authentication is needed as per the code; it uses public endpoints.
  • The node depends on n8n's HTTP request helper to perform GET requests.

Troubleshooting

  • Common issues:

    • Providing an invalid or malformed ID will result in no data or an error response.
    • Network connectivity problems will cause request failures.
    • If the Bionomia API changes or is temporarily unavailable, the node may fail.

  • Error messages:

    • HTTP errors (e.g., 404 Not Found) indicate the person ID does not exist in Bionomia.
    • Timeout or network errors suggest connectivity issues.

  • Resolutions:

    • Verify the correctness of the ORCID or Wikidata ID.
    • Ensure stable internet connection.
    • Retry later if the API is down.

Links and References

Discussion