Page History

...

Story/Feature	RipRap	UMD	Camel Toolbox
Scheduling and Coordination
Check all resources every n months (not appropriate for very large repos)			M
Run continual fixity checks			M
Only alert me when are there failures			E
Call an arbitrary HTTP endpoint on success and/or failure			E
Send a (jms,stomp) message to a endpoint on success and/or failure			E
Call an arbitrary HTTP endpoint on success and/or failure			E
Perform fixity check on most recent version of resource only			S
Perform fixity check on all versions of resource	S	S	S
Check entire repo			S
Deliver fixity requests in batches			M
Check resources based on query			M
Scaling
Set rate limits (max bits/second) for checks			M
Set rate limits (max bits/second) for each task processor			M
Allow checks to be scaled horizontally across multiple instances			H
Run fixity against on disk representation			H
Reporting
Generate list of resources checked since X date			M
Generate list of resources not checked X date			M
Generate a fixity audit report by resource			M
Generate a csv of fixity audit results showing resource id, date checked, checksum, and the result based on resource, date, and result parameters			M
Storage options
Store fixity results in triplestore
Store fixity results in text file			S
Store fixity results in sql			E
Store fixity results in nosql			E	Deliver fixity requests in batches	M

Components

...