[
http://jira.dspace.org/jira/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11620#action_11620
]
Tim Donohue commented on DS-587:
--------------------------------
This was discussed in DSpace Developers Meeting on Aug 25 2010:
Main decisions were that we'd like to see Claudia's concerns addressed in the
patch. There are also concerns that the patch displays all metadata for
withdrawn items. Several of us feel that metadata for withdrawn items should
not be displayed by default. (We may need more feedback from Repository
managers about this). We also need to ensure that tombstone pages return a
404 response (this is also related to the
http://jira.dspace.org/jira/browse/DS-135 issue for XMLUI tombstones -- but
DS-135 should fix it for the XMLUI).
[20:28] <tdonohue> DS-587: add the capability to indicate a withdraw reason to
an item ( tombstone ) -- http://jira.dspace.org/jira/browse/DS-587
[20:29] <tdonohue> DS-587 -- looks like Claudia expressed some concerns about
the provided patch
[20:29] <PeterDietz> What currently happens when an item is withdrawn
[20:30] <mhwood> Sounds desirable but needs some elaboration.
[20:30] <tdonohue> PeterDietz -- currently, it just disappears -- "Page not
found" 404 error
[20:31] <bollini> mmm... it is showed a thumbnail page (and the 404 code is
supplied)
[20:31] <richardrodgers> I'm puzzled - I could swear tombstones used to work
(not 404s)
[20:31] <mhwood> Me too.
[20:31] <tdonohue> hmmm...maybe I'm mistaken? I think it's a 404 in XMLUI at
least
[20:32] <richardrodgers> Maybe it got lost in Manakin translation?
[20:32] <richardrodgers> Can we try in dspace.org demo (jsp)?
[20:32] <tdonohue> Here you go...a withdrawn item
[20:33] <tdonohue> XMLUI: http://demo.dspace.org/xmlui/handle/1842/187
[20:33] <tdonohue> JSPUI: http://demo.dspace.org/jspui/handle/1842/187
[20:33] <tdonohue> JSPUI does have a tombstone
[20:33] <richardrodgers> Right no 404
[20:33] <tdonohue> XMLUI says it's "restricted"
[20:33] <tdonohue> I was wrong on both counts :)
[20:34] <tdonohue> So, it looks like DS-587 is about being able to add a reason
*why* something was withdrawn (i.e. an improved tombstone msg)
[20:35] <mhwood> Wasn't there another issue about being asked to login to see
that an item is withdrawn?
[20:35] <mhwood> Improved tombstone page sounds good, if we are to have one at
all.
[20:36] <tdonohue> Yep -- DS-135: http://jira.dspace.org/jira/browse/DS-135
(Withdrawn items displayed as "restricted" rather than withdrawn)
[20:36] <joseblanco> the patch will show the item display page with a message
by the bitstream and right about the bitstream the reason for withdraw
[20:36] <bollini> some institutions can not like the idea to show the metadata
at all
[20:37] <tdonohue> joseblanco -- so, the patch actually displays all the item's
metadata?, despite it being withdrawn?
[20:37] <richardrodgers> Yes, the tombstone hid the metadata also
[20:37] <joseblanco> yes. I'm trying to find one here, but have not found one
yet.
[20:38] <mhwood> This may want to be configurable: either a noncommittal 404
page or a tombstone page with a reason. I feel that XMLUI is wrong either way
here.
[20:38] <tdonohue> ok -- this may need more work then -- I'm not sure we should
be switching functionality such that metadata is now displayed for withdrawn
items -- part of the reason for withdrawal is also to get them out of Google
(and other search engines), and leaving the metadata there encourages Google to
still link to it
[20:38] <joseblanco> I just found one:
http://deepblue.lib.umich.edu/handle/2027.42/48750
[20:39] <tdonohue> mhwood : I agree about XMLUI being "wrong" --- JSPUI is
"more right" (if that makes sense)
[20:40] <tdonohue> So, for DS-587, sounds like we need an improved patch (based
on Claudia's comments, and based on the metadata being displayed by default)
[20:41] <joseblanco> I am planning on cleaning it up a bit based on Claudia's
comments, probably in a couple of days. If that helps.
[20:41] <mhwood> So, DS-135 will take care of XMLUI. DS-587 can be just for
JSPUI.
[20:41] <bollini> mmm... I don't like the idea to show metadata for withdrawn
item at all
[20:42] <tdonohue> joseblanco -- that would help. we'd need a new patch to
review.
[20:42] <bollini> if you need to use withdrawn functionality to hide files just
remove policies on the bitstreams
[20:43] <tdonohue> bollini -- yea, I agree with you. I think you misunderstood
-- I agree that metadata should be hidden by default (perhaps there could be an
option to enable display of metadata, but it needs to be off by default)
[20:43] <bollini> tdonohue - we should be care about providing a such option
[20:43] <PeterDietz> I wonder if it should throw http 403 -- forbidden
[20:44] <mhwood> Yes, I thought the reason for a tombstone was to indicate,
"no, you're not crazy; we did have that, but we took it down."
[20:44] <tdonohue> PeterDietz -- probably should throw a 403, i'd agree
[20:44] <kshepherd> how permanent are withdrawals for most people?
[20:44] <joseblanco> In our case we wanted to give users a reason for the
reason coming down.
[20:44] <kshepherd> just as an aside, if you want google to de-index it, i
think a 410 (Gone) is best
[20:45] <mhwood> Shouldn't be 200, at any rate.
[20:45] <kshepherd> but 410 might be too strong if the item could be reinstated
within a short period of time
[20:45] <tdonohue> yea the 410 description says to use 404 if not permanent:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
[20:46] <kshepherd> yep true
[20:46] <tdonohue> So, it's probably either 403 or 404 -- but definitely not 200
[20:46] <tdonohue> Ok -- we'll leave it at that -- we are running long already
:)
[20:46] <mhwood> I think 403 ought to mean you need to login, or login as
someone else.
[20:47] * sandsfish_ ([email protected]) has joined
#duraspace
[20:47] <tdonohue> mhwood -- yea, I think 404 may be "best" for a tombstone,
and 403 is "best" for a restricted item
[20:47] <kshepherd> tdonohue: +1
[20:47] <kshepherd> and 410 for 'purged/deleted' tombstones if we ever do those
;)
> add the capability to indicate a withdraw reason to an item ( tombstone )
> -------------------------------------------------------------------------
>
> Key: DS-587
> URL: http://jira.dspace.org/jira/browse/DS-587
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: JSPUI
> Affects Versions: 1.6.0
> Environment: This is a change to the base functionality of the jspui.
> Reporter: Jose Blanco
> Priority: Minor
> Attachments: confirm-withdraw-item.jsp, embargo.jsp, tombstone.jsp
>
> 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 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
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
