Readable in Forty Years, Not Just Stored
This connector is not prebuilt. It would be built per engagement on the platform's export architecture and its REST and webhook APIs, with scope and effort agreed there. Preservica is a digital preservation system used by archives, libraries and government bodies to keep records readable for decades. The distinction it rests on is one operational systems tend to blur: keeping a file is not the same as keeping it readable, and a permanent retention obligation is a preservation problem rather than a storage one.
How it connects
Material would be exported to Preservica on a stored query, such as one matching a retention class held as a custom attribute, so anything carrying a permanent or long obligation moves into a system built for it rather than ageing in an operational one. Existing material would be backfilled, and material already on the archive storage tier is rehydrated before it can be read, which the export would allow for.
What Preservica does on the other side is the reason for the handover, and it is worth naming rather than implying. Format migration, OAIS packages and fixity checking are its work, not the platform's. An engagement would establish which of those obligations the organization actually has, because a body with a statutory permanent record has different requirements from one simply keeping things a long time, and the second sometimes does not need a preservation system at all.
An engagement would also settle the post-export action on this side: whether the operational copy is disposed of under the retention rule, retained as a working copy, or kept until Preservica confirms receipt. Those are three different answers and only one of them is safe by default.
What you can do together
- Move material under a permanent or long retention obligation into a system built to keep it readable.
- Select what moves by stored query on a retention class, including material already held, rather than by hand.
- Let format migration, OAIS packaging and fixity be done by the system whose job they are.
- Decide what happens to the operational copy after export, rather than leaving it to a default.
A scenario
- ScopingThe engagement would establish which preservation obligations actually apply and what happens to the operational copy.
- SetupThe export would be configured against Preservica as a stored query on the hearings' retention class.
- SelectionThe query would pick up hearings as they are classed and backfill those already held, rehydrating any on the archive tier first.
- HandoverThose records would export to Preservica, which would take on format migration, packaging and fixity.
- AfterwardsThe operational copy would be disposed of or retained according to the rule agreed, not by default.
What stays where
Preservica does the preservation
Format migration, OAIS packages and fixity checking are its work, not the platform's.
Which obligations apply is established first
A statutory permanent record and a long retention period are different requirements, and the second may not need a preservation system.
What happens to the operational copy is decided
Disposal, retention as a working copy, or holding until receipt is confirmed are three answers, and only one is safe by default.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud subscription, or on premises.
Products and solutions
Next step
See it on your own Preservica instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/preservica