[
http://jira.dspace.org/jira/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11656#action_11656
]
Jim Ottaviani commented on DS-587:
----------------------------------
As the person who initiated this discussion here at Univ. of Michigan, here's
why we coded and implemented the functionality we're talking about. I hope it
will help clarify why we found the current functionality incomplete.
Because we tell people (via DSpace.org and everywhere else!) that DSpace is a
preservation system, we need to at least provide the option of showing both a
reason for withdrawal and some metadata for an item. I think that's true even
if that metadata is searchable by Google and others. We've made this clear to
our users here, and everyone is fine with that, because it makes sense to
scholars and researchers: they want to be able to view the persistent URLs as
having the strength of a citation in the published literature.
A citation in the physical world is never the equivalent of a 403, 404, or even
410. Granted, it's also very difficult to withdraw and/or expunge all copies of
something from the physical world...but that's actually a further strength of
DSpace, since if a person really wants an item gone they can use the expunge
feature and it really is gone, for good.
With the option of leaving a real tombstone behind, we offer the best of both
worlds. But the current behavior does not produce real tombstones; they're more
like unmarked graves, telling someone who either got to an item some time in
the past or was pointed to it by someone else that DSpace buried something, but
won't let them see what it was. No access to the item (specifically, the
bitstream(s)) is fine, but no possibility of validation that they really did go
to the right place looking for it is not.
Again, I can understand wanting an unmarked grave option, but it shouldn't be
the only one.
> 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
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
