[ 
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22801#comment-22801
 ] 

Tim Donohue commented on DS-587:
--------------------------------

Mark,

I don't think we should be consolidating DS-135 into this DS-587.  To be clear, 
they are actually *different*.   DS-135 is a subset of DS-587, and we 
specifically rescheduled DS-587 (and it's related issues: DS-996 and DS-1004) 
for post-1.8.0.

The difference is this:
* DS-135 is just a bug fix to ensure that XMLUI has a tombstone page  (this is 
scheduled for 1.8.0)
* DS-587 requests the addition of *both* an XMLUI tombstone page, as well as an 
extra feature -- the ability to add a customizable withdrawal message to that 
tombstone page. (this has been delayed until after 1.8.0 because there were 
concerns about the implementation of the extra feature)

I hope that makes sense.  I should be clear that I'm OK with consolidating 
DS-996 and DS-1004 into this issue (DS-587).  But, I think we should keep 
DS-135 separate, as it is the only one (of these 4 related issues) that will be 
released as part of 1.8.0.
                
> add the capability to indicate a withdraw reason to an item ( tombstone )
> -------------------------------------------------------------------------
>
>                 Key: DS-587
>                 URL: https://jira.duraspace.org/browse/DS-587
>             Project: DSpace
>          Issue Type: New Feature
>          Components: JSPUI, XMLUI
>    Affects Versions: 1.6.0
>         Environment: This is a change to the base functionality of the jspui.
>            Reporter: Jose Blanco
>            Assignee: Mark Diggory
>         Attachments: Clean_Tombstone_Via_Restricted_Item.patch, 
> confirm-withdraw-item.jsp, embargo.jsp, tombstone.jsp, tombstone_xmlui.zip, 
> tombstone.zip
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have already made the changes to our instance of dspace.  Here is an 
> explanation of what the tombstone functionality works at our instance.
>  When an item is withdrawn the user is presented with these options for 
> the reason of withdraw ( these reasons live in the file 
> tools/confirm-withdraw-item.jsp ):
> Removed from view by legal order.
> Removed from view by the University of Michigan.
> Removed from view at request of the author.
> The user makes his selection and the item is withdrawn.  When the item is 
> accessed the reason for the withdraw is 
> displayed in the box containing the bitstreams. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to