OpenRefine / OpenRefine/OpenRefine

Make it possible to discard reconciliation errors

Open
#6,112 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

reconciliation Type: Feature Request
Dominant language
Java
Stars
12k
Forks
2.2k
Avg merge
1d 14h
Merged PRs (30d)
27

Description

In #6006, @ostephens wrote:

For me I think that if the error doesn't need any further follow up I'd want to be able to get rid of it. Is there going to be some mechanism by which the user can clear any reconciliation errors that have been stored? (except a later successful reconciliation)? Perhaps a menu option to clear errors in the same way we have one that clears reconciliation data?

Proposed solution

The operations which match a cell to a reconciliation candidate (or match it to a new item) should clear the error. This would mean that one could get rid of an error by either:

  • matching the cell to a manually-selected candidate
  • matching the cell to a new item
  • discarding reconciliation info in the cell (making the cell unreconciled)
Alternatives considered

Make it possible to clear the error without making a reconciliation judgment? I am not sure why one would want to do that, since the three options above seem sufficient to me.

Additional context

Follow-up to #6006.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the reconciliation operations described in the issue: matching a cell to a selected candidate, matching it to a new item, and discarding reconciliation information. Check the existing reconciliation-error behavior and tests, if present; done means each of those actions clears the stored error without requiring a separate menu action.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.