I rewrote the checker so I can trigger checking such that I can select the bitstreams to be checked based on last checked date, or the last check result. The check can be limited to checking a max number of bitstreams. I added a CLI utility that can list the check status of bitstreams or count the number of bitstreams in a given status - aka DELETED or NOT_FOUND. The output of the 2 CLIs is easy to grep through, aka it makes it easy to look for relevant info. I use them in my daily cronjob to go round robin through bitstreams such that all my bitstreams are checked every 3 weeks.
Here a two example usages with corresponding output: > $DSPACE_HOME/bin/dspace checksum -d check -c 4000 -x BITSTREAM_MARKED_DELETED # org.dspace.checker.CheckBitstreamIterator(without_result=[BITSTREAM_MARKED_DELETED]) # Action check # Max-Count 4000 # Printing m for CHECKSUM_MATCH, d for BITSTREAM_MARKED_DELETED, and E in all other cases mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm …. mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm # worked on 4000 bitstreams > $DSPACE_HOME/bin/dspace checksum -d print -c 1 -x BITSTREAM_MARKED_DELETED | > egrep -v '^#’ 1 BITSTREAM.39318 CHECKSUM_MATCH internalId=9128636048098563653161844066534785665 delete=false lastDate=2016-11-06 01:02:03.83 See documentation HERE <https://github.com/akinom/DSpace/blob/DS-2492-checksum_checker_reporter/dspace-api/src/main/java/org/dspace/app/checker/Readme.md> There is a JIRA HERE <https://jira.duraspace.org/browse/DS-2492> And a PR THERE <https://github.com/DSpace/DSpace/pull/882> I’d be happy to help if you want to try this out Monika ________________ Monika Mevenkamp Digital Repository Infrastructure Developer Princeton University Phone: 609-258-4161 Skype: mo-meven > On Nov 24, 2016, at 11:58 AM, do...@uoguelph.ca wrote: > > Hi all, > > We'll occasionally get bitstreams showing up in this report, but I'm really > unclear on why or what it is that we should be doing to address it. > > What conditions cause a bitstream to be skipped and included in this report? > > As an administrator, what actions should I take when this occurs? > > The report itself says "To add these bitstreams to be checked run the > checksum checker with the -u option" but the checker doesn't seem to have a > -u option > <http://mirror.swem.wm.edu/DSDOC/wiki.duraspace.org/display/DSDOC5x/Validating%2BCheckSums%2Bof%2BBitstreams.html>. > Running the checker with the -u option doesn't seem to make any noticeable > difference. > > Digging into the most recent report where this occurred, I can see that the > item associated to the unchecked bitstreams has finished its workflow and has > been accepted to our repository. > > Any help or guidance that you folks could provide would be greatly > appreciated! > > Thanks, > -Adam > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com > <mailto:dspace-tech+unsubscr...@googlegroups.com>. > To post to this group, send email to dspace-tech@googlegroups.com > <mailto:dspace-tech@googlegroups.com>. > Visit this group at https://groups.google.com/group/dspace-tech > <https://groups.google.com/group/dspace-tech>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
