Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The root page System Design could not be found in space Chronopolis System Documentation.

The Chronopolis project has two sets of software which interact with each other in order to provide bit level preservation. The first is a set of services which distribute data throughout the Chronopolis Network, which are Intake, Ingest, and Replication. The second is the Audit Control Environment (ACE) which continually audits data in Chronopolis to ensure the integrity of both the checksums and files which we keep track of.

In addition to the software used for distributing data through the network, there are additional services for tertiary tasks:

  • Repair - automates the workflow for correcting file errors within the Chronopolis Network
  • Restore - automates the workflow for returning data back to a Depositor



Data in Chronopolis is packaged using the BagIt specification.



An institution, person, or conglomerate which is a part of Chronopolis and has data to be stored for bit level preservation


An organization which is part of the Chronopolis Network and stores data for Depositors

Staging Storage

A filesystem which can be used for transient data; not guaranteed to have bit level preservation

Preservation Storage

A filesystem which is used for holding data long term; is continually checked for bit rot


The first distribution service layer which brings external data into Chronopolis


The second distribution service layer which acts as a registry of content and manages where data is distributed in Chronopolis


The final distribution service layer which transfers data from a staging area in to a Preservation storage filesystem


A service which takes actions to correct any data which has become corrupt at a Chronopolis Node


The action of returning data to a Depositor

  • No labels