At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| JSON archive | Choose it under Archive package | File ready for import | Administrator and active license required; the picker accepts .json only |
| File above 10 MiB | Select Import archive | "The archive exceeds the 10 MiB import limit." | Nothing is sent to the server |
| File that is not JSON | Select Import archive | "The archive package is not valid JSON." | Import reads JSON only |
| Manifest | Validate tenant, baseline, schema, part count, and root hash | Validation result on the server | A tenant mismatch fails validation |
| Ordered archive parts | Recalculate content and part hashes | Verified part chain or error codes | Missing, changed, or reordered parts fail validation |
| Archived records | Check schema, identity, order, and section counts | Isolated collections and a parity check | 5,000 declared records at most; nothing is promoted |
| Invalid package | Report the failed validation | Archive validation failed: followed by error codes such as PART_HASH_MISMATCH | Invalid evidence is not reconstructed |
| Parity mismatch | Compare imported records with the archive | "Archive parity check failed: the imported records do not match the archive." | Reported as an error, not a completion |
| Valid package | Report the import result | "Archive verified: N records imported, parity confirmed." | Records stay in isolated collections |
How it works
- Open Terminology Baseline and find Enterprise evidence workspace.
- Find Verification and portable evidence.
- Under Archive package, choose a JSON file of 10 MiB or less.
- Select Import archive.
- Read the result. Archive validation failed: lists the failed checks by code.
- A valid package shows Archive verified: with the record count. Interactive import still does not promote the evidence.
Example
An administrator holds a three-part JSON archive. The second part was replaced. Import recalculates its hashes, and validation fails on the server. The workspace shows Archive validation failed: with codes such as PART_HASH_MISMATCH and ROOT_HASH_MISMATCH. The untouched original shows Archive verified: with its record count and confirmed parity.
What this does not mean
Interactive import validates and rebuilds in isolation. It does not promote evidence into the workspace. It shows validation error codes and the parity result, not a per-record report. The workspace offers no archive download, so a package must come from outside the workspace. Import does not certify compliance, create legal WORM storage, or replace a Confluence backup.
Related questions
Next step
Use Import archive to check an archive package, and Run verification for the current freeze.
View on Atlassian Marketplace