[
http://jira.dspace.org/jira/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11658#action_11658
]
Tim Donohue commented on DS-587:
--------------------------------
Hi Jim,
First, thanks for the comments. They are much appreciated.
I think the DSpace Developers are in agreement that this seems like a good
feature to add to DSpace. I think the main concerns were just that the code is
not exactly as configurable or enhanced as we'd like it to be. So, at this
point in time, we need to find someone who is willing to enhance it a bit, to
better meet the diverse needs of our community.
More specifically, it seems like there are two main desires out of a tombstone.
As Michigan, some people would rather keep the full metadata in place (and
just hide the files). Others seem to want the item, including all metadata, to
disappear entirely. Both of these scenarios could however benefit from
displaying a "reason" why an item was withdrawn.
So, it sounds like (unless we are able to rule out one of these two scenarios),
we probably need two configuration options:
Option #1: Tombstone hides all metadata & files (but, displays a reason for
removal) -- this is like DSpace currently handles tombstones, but adds a reason
for removal.
Option #2: Tombstone only hides files, and displays both a reason and full
metadata
In both of these options, we'd likely want the tombstone page to return a 404
Status code, as this will ensure Google & other major search engines stop
indexing that page within DSpace (and also remove it from their search results).
Currently, the Michigan code looks to be heading in the right direction, but we
just need to locate someone to enhance it a bit. Specifically, it needs to
also support "Option #1" above, and make sure to return a 404 status code
(currently, it looks to be returning a 200 OK status code, which will encourage
Google to keep indexing that page). Finally, if we can find an interested
XMLUI developer, I'd also like to see it implemented for the XMLUI.
To be clear, I'm not staying that Michigan has to make these changes -- I just
wanted to be clear what seems to still be missing. It may be possible that we
can find an interested committer (or another developer) who wants to work to
enhance this code. Speaking of which, are there any volunteers who'd like to
help enhance this code?
(Other opinions on this feature are definitely welcome! I'm just trying to
summarize the developer discussions from last week.)
> 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
