The Bridge Intake Service provides data pulled down from the Duracloud Bridge App a path into Chronopolis. It currently handles bagging of snapshots, which includes validating files from the manifest given by Duracloud.
Installation
Prereqs
- Running Duracloud Bridge App to connect to
- Staging area for creating bags
Install
- Get the latest rpm from http://adaptci01.umiacs.umd.edu/resource/bridge-intake/master/
- yum install
Installed files are as follows:
- /usr/lib/chronopolis/bridge-intake.jar
- /etc/chronopolis/application.yml
- /etc/init.d/bridge-intake
Configuration
Depending on where the data is bound, there are several configuration options available
Chronopolis
Prefix
Specifying Replicating Nodes
DPN
Sample application.yml with all properties
Release Notes
Release 2.0.3
29 November, 2017
- Query on Bags we created when running Tokenization
Release 2.0.2
9 November, 2017
- Remove creation of /var/log/chronopolis from rpm and instead create it on application startup
Release 2.0.1
8 November, 2017
- Use correct properties when creating Ingest Requests to Chronopolis
Release 2.0.0
30 October, 2017
- Integrate Chronopolis 2.0.0 Changes
- Import tokenization module in order to create ACE Tokens for incoming data
- Use new properties classes for configuration of storage and api communication
- Capture basic metrics when creating bags
- Update ingest flow to create bag and fixity
- Updates to build and init scripts
- Support EL6 and EL7
- Quality of life changes to the sysv init script based on rpmlint
Release 1.5.1
30 June, 2017
- Fix bug that caused replications to be created for each node in DPN
Release 1.5.0
26 June, 2017
- Add a prefix for chronopolis bound collections
- When creating replications for dpn, choose replicating nodes in a deterministic manner per snapshot so that all bags in a snapshot end up at the same DPN nodes.