Parse → Get
AI-generatedOverview
This node integrates with the GlobalNames services to parse, find, and verify biological scientific names. Specifically, for the Parse - Get operation, it takes a scientific name string as input and returns parsed information about that name. This is useful in scenarios where you have raw scientific names and want to extract structured data such as canonical forms, authorship, rank, or other taxonomic details.
Practical examples include:
- Cleaning and structuring scientific names from biodiversity datasets.
- Preparing scientific names for further taxonomic verification or matching.
- Extracting detailed components of a scientific name for research or database entry.
Properties
| Name | Meaning |
|---|---|
| Scientific Name | The biological scientific name string to be parsed. |
| With Details | Boolean flag indicating whether to return detailed parsing information (true/false). |
| Cultivars | Boolean flag specifying whether to include cultivar information in the parsing results. |
Output
The output is a JSON array containing parsed scientific name objects. For the Parse - Get operation, the node returns the first element of the response array, which includes structured data about the scientific name. This typically contains fields such as canonical name, authorship, rank, and possibly cultivar information if requested.
No binary data is output by this node.
Dependencies
- Requires internet access to call the GlobalNames parsing API endpoint at
https://parser.globalnames.org/api/v1/. - No explicit API key or authentication is required based on the code.
- The node uses HTTP GET requests with query parameters to fetch parsed data.
Troubleshooting
Common issues:
- Network connectivity problems may prevent reaching the GlobalNames API.
- Providing an invalid or malformed scientific name string may result in empty or error responses.
- If the API changes or is temporarily unavailable, the node will fail to retrieve data.
Error messages:
- HTTP request failures will throw errors related to network or server issues.
- If the response is not as expected, the node might return empty arrays or incomplete data.
Resolutions:
- Ensure stable internet connection.
- Validate scientific name inputs before using the node.
- Retry later if the API service is down.