Actions10
Project Metadata → List
AI-generatedOverview
This node integrates with OpenRefine, an open-source desktop application for data wrangling, allowing users to interact programmatically with OpenRefine projects and metadata. Specifically, the Project Metadata - List operation retrieves metadata about all projects available on the specified OpenRefine server.
This operation is useful when you want to get an overview of existing projects in OpenRefine, such as their IDs and associated metadata, without manually opening the OpenRefine interface. For example, it can be used to automate workflows that need to process or analyze multiple OpenRefine projects by first listing them and then performing further actions based on the metadata.
Properties
| Name | Meaning |
|---|---|
| Server | The URL of the OpenRefine server instance. Defaults to http://127.0.0.1:3333. Change this if your OpenRefine server runs on a different address or port. |
Output
The output is an array of JSON objects, each representing metadata for a single OpenRefine project. Each object has the following structure:
{
"id": "projectId",
"data": {
// Project metadata fields as returned by OpenRefine API
}
}
id: The unique identifier of the project.data: An object containing various metadata details about the project (such as project name, creation date, etc.) as provided by the OpenRefine server.
This output allows downstream nodes or processes to access detailed information about each project managed by OpenRefine.
Dependencies
- Requires an accessible OpenRefine server endpoint.
- No explicit API keys or authentication tokens are required by default, but the node fetches a CSRF token from the server to authorize requests.
- The server URL must be correctly configured in the "Server" property.
- The node uses HTTP requests to communicate with the OpenRefine REST API.
Troubleshooting
- Connection errors: Ensure the OpenRefine server is running and reachable at the specified URL. Verify network connectivity and correct port usage.
- CSRF token fetch failure: If the node cannot retrieve the CSRF token, check that the OpenRefine server supports the
/command/core/get-csrf-tokenendpoint and that no firewall or proxy blocks the request. - Unexpected response format: If the server returns unexpected data or errors, verify the OpenRefine version compatibility and that the server API endpoints have not changed.
- Empty or missing project list: Confirm that there are projects created in OpenRefine; otherwise, the list will be empty.