Bionomia icon

Bionomia

Link natural history specimens to the world's collectors

Actions6

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

Speciman → Get

AI-generated

Overview

This node integrates with the Bionomia service to link natural history specimens and related data to collectors worldwide. It supports multiple resources such as occurrences, people, and specimens, allowing users to retrieve detailed information about these entities.

For the Speciman - Get operation specifically, the node fetches detailed specimen data linked to a given identifier (such as an ORCID or Wikidata ID). This is useful for researchers or institutions wanting to access specimen metadata associated with particular collectors or identifiers.

Practical examples:

  • Retrieve all specimens linked to a specific collector's ORCID.
  • Access specimen metadata in JSON-LD format for integration into biodiversity databases.
  • Use specimen data to enrich research datasets or validate collector contributions.

Properties

Name Meaning
ID The ORCID or Wikidata ID for a person whose specimens you want to retrieve.

Output

The output is a JSON array where each element contains specimen data in JSON-LD format linked to the specified person ID. This structured data includes metadata about the specimens collected or associated with that individual.

No binary data output is produced by this operation.

Dependencies

  • Requires internet access to call the Bionomia API endpoints.
  • No explicit API key or authentication is required based on the code; it uses public endpoints.
  • The node relies on n8n's HTTP request helper to perform GET requests to Bionomia URLs.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent ID may result in empty or error responses.
    • Network connectivity problems can cause request failures.
    • Rate limiting by the Bionomia API if too many requests are made in a short time.

  • Error messages:

    • HTTP errors (e.g., 404 Not Found) indicate the requested resource does not exist.
    • Timeout or network errors suggest connectivity issues; verify internet access.

  • Resolutions:

    • Double-check the correctness of the ID input.
    • Ensure stable internet connection.
    • Implement retry logic or reduce request frequency if rate limits are encountered.

Links and References

Discussion