...
- starts with cron job to kick off the checking.
- nightly fixity checking window - avoids putting undue load on Fedora during peak usage times
- uses activemq - originally used camel but moved away and just uses activemq directly
- separate audit triplestore - tracks premis events
- generating the list of candidates was tricky with the bottleneck (solved with list caching) - not currently using a relational database
- continuous checking model - everything checked every 6 months or so
- checker is python based
- goes through Fedora API’s fixity checker
- fixity checker sends an event to success or failure queues where they are split into different queues - write to triple store, send email
Actions: Mark Jordan and Joshua Westgard will update the matrix on the desired feature page to clarify what currently exists and what could easily be added to complete the feature set.