[
http://jira.dspace.org/jira/browse/DS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10489#action_10489
]
Tim Donohue commented on DS-245:
--------------------------------
Stuart,
At the very least, I think the Checksum Checker should be configurable, so that
someone could run it on *just* the "in_archive" items (and not these other
types of files). Essentially, if you setup the Checksum Checker to send you
an email report of "problems" or deleted files, it ends up reporting mostly on
files that are not "in_archive".
As a simple example, whenever a submitter starts a submission, and then deletes
it (without completing it), the Checksum checker will report that a bitstream
has been deleted and a checksum didn't match. Another example is when a
Collection Administrator decides to change the logo for their collection, again
the Checksum checker will report a bitstream has been deleted and a checksum
didn't match.
Essentially, there should minimally be a way to turn off reporting of items
which do not have "in_archive" status...or report them in a different manner,
so that it doesn't take a human to dig into the reports and try to figure out
which deleted items were ok to be deleted, and which should not have been.
Does that make more sense?
- Tim
> Checksum Checker reports on bitstreams which do not have "in_archive" status
> ----------------------------------------------------------------------------
>
> Key: DS-245
> URL: http://jira.dspace.org/jira/browse/DS-245
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.5.0, 1.5.1, 1.5.2
> Reporter: Tim Donohue
> Priority: Minor
>
> The DSpace Checksum Checker currently reports on all bitstreams in the
> "bitstream" table, even if they are not officially "archived" (i.e. the
> "in_archive" status on the associated Item is set to true).
> I would propose that the Checksum Checker should *only* report on bitstreams
> which are within a bundle of an "in_archive" Item.
> Currently, the Checksum Check improperly (at least in my mind) also analyzes
> the following:
> (1) Bitstreams attached to items which are still "WorkspaceItems" or still
> going through Workflow processing (i.e. they haven't been officially
> archived yet)
> (2) Bitstreams which are actually images displayed on Collection/Community
> homepages
> (3) Bitstreams which are attached to items which have been withdrawn from
> the system
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
