Reprocessing a project
Reprocessing reads a project's earlier messages again and organizes them the way Provenience would organize them today. You see the old and new records side by side and decide whether to keep the new ones. Nothing changes until you confirm.
When to use it
Reprocess a project when its records no longer match how you would organize them now:
- you have added or changed categories since the project's messages arrived; or
- its older messages were organized before an improvement, and you want its records brought up to date.
Only an active project can be reprocessed. Closed projects and company-level records are not reprocessed. New categories apply to new messages on their own; reprocessing is how you apply them to a project's earlier ones. See Typology.
Start, watch, and cancel
Open the project from Projects and find its reprocessing section. Reprocess project opens Reprocess this project?, which says how many messages the run would cover. Choose Start to begin, or Not now to leave it.
The run covers every message that has a current record on the project, including messages that have open cards in the Review Queue. Only one reprocess can be open for a project at a time. If one is already open, or the project is not active, the section says so instead of offering the button.
While it runs, the section shows progress, such as Reprocessing: 40 of 120 messages, with a count of any that failed. Messages are handled one at a time, oldest first. New messages that arrive meanwhile are handled normally and are not part of the run, and they always go first, so a long run never holds up your day-to-day work. A run is paused while organizing is switched off and carries on where it left off when organizing is back on, and it picks up again after any interruption.
To stop a run, choose Cancel, then Stop the rerun in Cancel the rerun?. Nothing changes; anything written so far is kept as history.
What changes and what doesn't
Your current records stay in place and visible for the whole run, and until you confirm. If you discard or cancel, they are exactly as they were.
- Messages that can't be rerun keep their current records. A message may fail, for example because a person on it isn't registered yet or because it couldn't be filed to one project. These are listed in the review.
- The new records are filed and governed like new arrivals. The same rules for filing and access apply.
- Your own work carries over. Category corrections you made, access levels you set by hand, exclusions, and filings you made by hand are carried to the matching new records. Nothing else is copied from the old records.
Most carrying is automatic: when an old record maps to exactly one new record, your work simply moves across. A few cases cannot carry cleanly, such as a new record that contradicts your correction, or an old record the rerun split into several or merged into one. The review lists each one with a default:
- If the new run puts a record in a different category than you chose, your category wins.
- If a record was split or merged, the default is the new category.
- If merged records had different access levels, the strictest applies.
- If merged records were filed differently, the first filing is used.
No default ever widens access. A new record from a message you had restricted takes that restriction.
Read the review
When a run finishes, the project's section shows Finished with a link to Review the results, and a Reprocessing review card appears in the Review Queue. The review has these parts:
- Summary. How many messages were rerun and how many failed, how many records there were before and after, how many categories changed, and how many of your corrections carried over automatically. When you had made category corrections, it adds a line such as "The new run reached 8 of your 10 category fixes by itself." This tells you whether the change fixed what you had been correcting by hand: a high share means the new categories already do what you were doing manually.
- Needs your decision. The cases that could not carry cleanly. Each shows the records Before and After and offers the choices, with the default marked. If nothing needs you, it says "Nothing needs a decision. Confirm applies everything automatically."
- Messages that couldn't be rerun. Each failed message with its reason. These keep their current records.
- Message by message. The Before and After records for every rerun message, with a note on how each new record relates to the old one: carried, split, merged, dropped, or new.
Your choices are not saved until you confirm. If you leave the page, you will lose them.
Confirm or discard
Confirm opens Confirm the new records?, which says how many messages' records will be replaced and which will keep their current ones. Confirming replaces the old records with the new ones for every rerun message, all together or not at all. The old records are kept as history, and your choices are applied.
Confirming changes the Review Queue:
- The reprocessing review card closes.
- A Which category? card that held only replaced records closes.
- A new Which category? card opens for any new record that still needs a category. The result screen says how many, and links to them.
Discard opens Discard this rerun?. It keeps the current records and throws away the rerun (kept as history). The card closes and nothing else changes.
The project's section then shows when the last reprocess was confirmed or discarded.
Based on after a reprocess
A record's Based on list follows a cited record that was replaced to its successor and marks it as updated by reprocessing. Where there is no successor, it shows the cited record as an earlier version. See Artifacts for the detail.
What it costs
Reprocessing uses the same AI allowance as new messages. A large project can use a noticeable share of it, and there is no separate allowance for reprocessing. If the allowance runs out, organizing stops for new messages as well, until it is restored.