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 service to retrieve detailed information about natural history specimens and their collectors. Specifically, for the Occurrence - Get operation, it fetches data about a particular occurrence record identified by an ID from the Global Biodiversity Information Facility (GBIF). This is useful in biodiversity research, museum collections management, or ecological studies where linking specimen occurrences to collector data is important.

Practical examples include:

  • Retrieving metadata about a specific specimen occurrence to verify collection details.
  • Enriching datasets with linked collector information for analysis.
  • Integrating occurrence data into workflows that track biodiversity records.

Properties

Name Meaning
ID The occurrence ID provided by the Global Biodiversity Information Facility (GBIF). This uniquely identifies the occurrence record you want to retrieve.

Output

The node outputs a JSON object representing the occurrence data retrieved from the Bionomia API. The structure corresponds to the linked data format (application/ld+json) returned by the endpoint https://bionomia.net/occurrence/{id}. This typically includes detailed metadata about the occurrence such as taxonomic information, collection details, geographic location, and links to associated collectors.

No binary data output is produced by this operation.

Dependencies

  • Requires internet access to call the Bionomia API at https://bionomia.net.
  • No explicit API key or authentication token is required based on the code; the requests are made with standard HTTP GET and accept headers.
  • The node uses n8n's built-in HTTP request helper to perform API calls.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent occurrence ID will likely result in an error or empty response.
    • Network connectivity problems can cause request failures.
    • Rate limiting or temporary unavailability of the Bionomia API may lead to errors.

  • Error messages:

    • HTTP 404 Not Found: The specified occurrence ID does not exist. Verify the ID is correct.
    • HTTP 429 Too Many Requests: You have exceeded the API rate limit. Wait and retry later.
    • Network errors/timeouts: Check your internet connection and proxy settings if applicable.

To resolve these issues, ensure the occurrence ID is valid, confirm network connectivity, and consider implementing retries or delays if hitting rate limits.

Links and References

Discussion