The Ingest service adds a layer between the Intake and Replication services. The main goal is to validate data which comes from bags and create tokens for that data.
Current Implementation
We use the Service/Ingset/Restful-Server as a means of performing the necessary tasks which include:
- Creating ACE Tokens for a bag
- Includes validating the manifest
- Creating Transfer Requests
- Cleaning the staging area after all replications finish successfully (??)
Open Questions
- How do we handle error’d bags? (hold, reject, ??)
- We bag the packages ourselves, so we should get no bags with errors
- What about malformed digests?
- The ingest-server stores a token for each valid digest, and ignores all others. Either manifest is not digested until 100% of the files are valid. Requests are not made until tokens have been created for each file in the bag.
