[ 
http://jira.dspace.org/jira/browse/DS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10594#action_10594
 ] 

Tim Donohue commented on DS-245:
--------------------------------

Graham,

That'd make a lot of sense.  I think if the Checksum Checker reporting could 
more clearly identify the "status" of the bitstream, it would be very helpful.  
As it stands now, you are just provided a list of unmatching checksums, or more 
likely, bitstreams that have been deleted, without any contextual information 
regarding that bitstream.

Unfortunately, after a bitstream has been deleted, it no longer retains any of 
its links back to the bundle/item it was associated with.  So, it becomes very 
difficult to determine its prior status (unless you go digging through your 
dspace.log files).

As I see it there are four main "statuses" of bitstreams, all of which are 
tracked by the Checksum Checker:
* in archive
* in progress
* withdrawn
* Community/Collection logo





> 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

Reply via email to