Term | Definition |
---|---|
Chronopolis Staging Storage Provider | A DuraCloud storage provider (which is an integration with a back-end storage system in DuraCloud) which is used to provide a storage location for content that is destined to be stored in Chronopolis. |
Chronopolis Snapshot Storage Provider | A DuraCloud storage provider which is used to expose the data collections which have been stored in Chronopolis and the content items which are included in those collections |
Bridge Application | An application which is hosted on the Bridge Server and is responsible for moving content between DuraCloud storage and Bridge Storage, in both directions. |
Bridge Server | A server which is physically managed by Chronopolis, but is accessible to both the DuraCloud and Chronopolis teams and systems. This server acts as a "bridge" between the two systems by providing a set of applications which allow the systems to communicate and transfer data. |
Bridge Storage | A storage system mounted on the Bridge Server which is used to store user content as it move between the DuraCloud and Chronopolis systems |
Chronopolis Collection | A logical grouping of digital objects (content files, manifests, properties listing files, etc) form a collection in Chronopolis. This is the basic grouping unit of preservation organization in the system. |
Manifest | A listing of files. For this program, manifest means a correctly formed BagIt manifest. |
Snapshot | A set of files which have been selected by a user of DuraCloud to be moved as a group into Chronopolis. These files, along with a few system files (manifests, properties listing files, etc) form a collection in Chronopolis. |
Snapshot metadata | A set of metadata which is associated with a snapshot. This metadata is partially system generated and partially user defined. This information is stored as part of a snapshot, and may be used by DuraCloud and/or Chronopolis |
Snapshot Status | Properties describing the runtime state of a snapshot. |