daitss/core — Issue #599: collect-fixities: why can't collect-fixities report only "new" incorrect fixities?
Author: lydiam
Created: 2011-12-08 19:21:40+00:00
State: open

For possible discussion at some future time:

Since collect-fixities reports new correct fixities and presumably only writes new correct fixity events to the database, as in the following example from collect-fixities email:

7,115 new correct fixities
303,616 old correct fixities

can't it also do the same for "incorrect fixities" and write only new "fixity failure" events to the database? This may be a way to get around the fact that collect-fixities writes a new "fixity failure" event each time it runs, even though the last fixity checks on the silo side have not been updated since the last collect-fixities run.

An example of an email that reports "old" fixity errors as "new" fixity events:

CollectFixities started at Fri Nov 11 04:04:06 -0500 2011
Summary of DAITSS Package Fixity Checks: Requiring 2 Copies Per Package
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
307,681 ingested package records as of 2011-11-11 04:04:06

33,349 new correct fixities <---- correct
274,330 old correct fixities
2 incorrect fixities <---- "old" fixity failures, in that the silo with incorrect fixity hadn't been re-checked since the last c-f run
0 had missing copies
0 with the wrong number of copies in pools
-------
307,681 total events, 33,351 of which are new <---- old incorrect fixities considered "new" events