Page History

The Intake services are a gateway for data to come into Chronopolis. Intake can be handled either by a service or can be performed manually. 

Depending on the route of intake, different tasks may be performed, including but not limited to:

• bagging
• tarring/untarring
• notification to the ingest-server

Note: The intake-shell serves as a sample intake service which notifies the ingest service that a package is ready to go into chronopolis.

Implementations

1. Duracloud transfer service
   
   1. REST API
   2. service should be expanded to perform pull and create local bag
      1. pulls to local disk, easy to create bag
   3. Support more source repositories (s3,duracloud general)
   4. How do we handle Metadata?
      1. Duracloud writes it for us
2. DPN direct notification
   1. See replication request in DPN REST API
   2. Pull via https/rsync

Open questions

• Creating BagIt Bags from a set of files 
• Creating ACE Tokens
• Deserialization (e.g. extracting a tarball)
• Notification of the existing package to the Ingest service

Links

• Chronopolis Bagger

Implementations

• Bridge Intake
  • Snapshot Lifecycle
• Do we query systems for advanced metadata or do we require producers to serialize metadata prior to ingest
• Chronopolis should limit to bags only ??