Page History

User Stories

...

and Features 

...

(YS = supported) or  easy of adding = 1 effort required to support = E (easy) - 5 ) M (medium) H (hard)

Priority = 1 must have, 2 should have, 3 nice to have

Story/Feature	Priority	RipRap	UMD	Camel Toolbox

Ensure that

Scheduling and Coordination
Check all resources

are checked

every n months (not appropriate for very large repos)		S		M
Run continual fixity

checks

checks		S		M
Only alert me when are there failures		S	S	E
Call an arbitrary HTTP endpoint on success and/or failure		S		E
Send a (jms,stomp) message to a endpoint on success and/or failure		M	S	E
Call an arbitrary HTTP endpoint on success and/or failure		M		E
Perform fixity check on

HEAD

most recent version of resource only		S	S	S
Perform fixity check on all versions of resource		S		S
Check entire repo		S	S	S
Deliver fixity requests in batches		S		M
Check resources based on query		S		M
Scaling
Set  rate limits (max bits/second) for checks		H		M
Set  rate limits (max bits/second) for each task processor		H		M
Allow checks to be scaled horizontally across multiple instances		M		H
Run fixity against on disk representation		S		H
Reporting
Generate list of resources checked since X date		S	S	M
Generate list of resources not checked X date		S	S	M
Generate a fixity audit report by resource		S	S	M
Generate a csv of fixity audit results showing resource id, date checked, checksum, and the result based on resource, date, and result

Set  rate limits (max bits/second) for checksAllow checks to be scaled horizontally

parameters		S	S	M
Storage options
Store fixity results in triplestore		M	S
Store fixity results in

external datastore

1. triplestore
2. sql database
3. no-sql db 

text file		S		S
Store fixity results in sql		S		E
Store fixity results in nosql		M		E

Deliver fixity requests in batches

Components

Fixity Checker 

...