OpenRefine icon

OpenRefine

OpenRefine is an open-source desktop application for data wrangling

Actions10

Project Tags → Update

AI-generated

Overview

This node integrates with an OpenRefine server to manage project tags by updating them. Specifically, the "Update" operation under the "Project Tags" resource allows users to add new tags and/or remove existing tags from a specified OpenRefine project. This is useful for organizing and categorizing projects within OpenRefine, enabling better project management and filtering.

Common scenarios:

  • Automatically tagging projects based on data processing results.
  • Cleaning up or standardizing tags across multiple projects.
  • Removing outdated or incorrect tags from projects in bulk.

Practical example:
You have an OpenRefine project with ID 12345 and want to add tags "cleaned, verified" while removing the tag "raw". Using this node, you specify the project ID, provide the tags to add and remove as comma-separated strings, and the node updates the project's tags accordingly.

Properties

Name Meaning
Server The URL of the OpenRefine server. Usually defaults to http://127.0.0.1:3333 unless your server differs.
Project ID The unique identifier of the OpenRefine project whose tags you want to update.
Add Tags Comma-separated list of new tags to add to the project. Example: "tag1, tag2, tag3".
Remove Tags Comma-separated list of tags to remove from the project. Example: "tag1, tag2, tag3".

Output

The output is a JSON object representing the response from the OpenRefine server after attempting to update the project tags. It typically includes status information about the success or failure of the update request.

Example output structure:

{
  "statusCode": 200,
  "message": "Tags updated successfully"
}

If the update fails, the output may contain error details.

Dependencies

  • Requires access to a running OpenRefine server reachable at the specified Server URL.
  • The node fetches a CSRF token from the OpenRefine server before making requests, so the server must support this security mechanism.
  • No external API keys or credentials are required beyond access to the OpenRefine server.

Troubleshooting

  • Common issues:

    • Incorrect Server URL or port: Ensure the OpenRefine server address is correct and accessible.
    • Invalid Project ID: Verify that the project ID exists on the OpenRefine server.
    • Network connectivity problems between n8n and the OpenRefine server.
    • Improperly formatted tag strings (e.g., missing commas or extra spaces).

  • Error messages:

    • Errors related to CSRF token fetching indicate server communication or configuration issues.
    • HTTP errors such as 400 or 404 suggest invalid parameters or non-existent projects.

  • Resolutions:

    • Double-check the Server URL and Project ID.
    • Confirm the OpenRefine server is running and accessible.
    • Format tag lists correctly as comma-separated strings.
    • Review server logs for more detailed error information if available.

Links and References

Discussion