In development. What a version records can change, and history created now may not carry over.
Version history
What CampusMind records about a document's remediation, and how to use it as evidence.
Every remediated document carries a history of how it reached its current state — the original file, the settings each run used, every saved edit, and the validation score at each point. It is the record you reach for when someone asks what happened to a document.
What alpha means here
- What a version records can change. The table below is what a version captures today, not a committed format.
- History created now may not carry over. Do not treat it as your only record of a document.
- Not every institution has it yet. Version history is being enabled gradually alongside the Tag & Caption Editor.
What is recorded
Remediation output is stored as version v1, attributed to System (autotag). Every human edit in the Tag & Caption Editor stacks on top of it as a further version.
| Recorded | Detail |
|---|---|
| The original file | Kept alongside the remediated one; never overwritten |
| The remediation run | Stored as v1, attributed to System (autotag) |
| The settings used | Strategy, extraction engine, and thresholds for the run |
| Each saved edit | A new version, so earlier states remain visible |
| Validation results | The PDF/UA-1 score for the original and for each validated version |
Revalidate re-runs the PDF/UA-1 check against the current version, which is what lets you show a before-and-after for a document you edited by hand.
What you can evidence with it
- That a specific document was processed, when, and with which settings.
- What the score was before and after, for that document.
- An earlier state of the file, since saving stacks versions rather than replacing them.
Scope of the record
Version history is a per-document record kept inside CampusMind. Institutions that need a chain of custody spanning every system they run keep that in their own governance tooling, and use this history as the CampusMind entry in it.
What auditors usually ask for
Requests generally fall into three buckets, and the first two are answered from the document itself:
| The request | What you can produce |
|---|---|
| "Show me this document was remediated." | The version history and validation results, directly. |
| "Show me who worked on it and when." | Each version records the account that made the edit and the time it was saved. Institutions that track a named review stage of their own usually reference that alongside it. |
| "Show me coverage across the institution." | A reporting question rather than a per-document one — the analytics views cover it, and Export CSV is the route into a report. |
Related
- What a person decides — where edits are made.
- Accessibility standards — what the score measures.
- ADA Title II — what you may be asked to evidence, and when.