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.
Chronopolis also has internal services which can handle errors within the network (Repair) and returning data to a Depositor (Restore). <--- still reword
Services
Packaging
Data in Chronopolis is packaged using the BagIt specification.
Glossary
Depositor
An institution, person, or conglomerate which is a part of Chronopolis and has data to be stored for bit level preservation
Node
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
Intake
The first distribution service layer which brings external data into Chronopolis
Ingest
The second distribution service layer which acts as a registry of content and manages where data is distributed in Chronopolis
Replication
The final distribution service layer which transfers data from a staging area in to a Preservation storage filesystem
Repair
A service which takes actions to correct any data which has become corrupt at a Chronopolis Node
Restore
The action of returning data to a Depositor
