Deposit as a service
The deposit is used by different clients and should be monitored for errors or misbehavior.
Also the deposit should be tested periodically and after deployment.
Vigilance points that need to be monitored:
- when a 'good' status is exceeding a certain time [deposited, verified, loading]
- when an error has occurred and a 'failed' status was attributed to a deposit
- test and make sure that the deposit that arrived is the deposit that was ingested (with all data and metadata)
- have a cron 'fake' deposit that arrives each day to see the service is up and running