[
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19933#action_19933
]
Tim Donohue commented on DS-587:
--------------------------------
The DSpace Developer revisited this issue during our Developers Mtg on April
13, 2011:
We did not have a chance to review the entire patch together (because of the
size of patch and lack of time left in meeting). However, both Richard Rodgers
(MIT) and Peter Dietz (Ohio State) volunteered to review the patch and provide
their feedback. (Other developers reading this should also take time to review
& provide their feedback to this important feature request)
Here's the full discussion:
[20:44] <tdonohue> Ok. moving on here. (sorry to change topics again
quickly...wanted to get to this): DCAT Review of DS-587
[20:45] <tdonohue> DCAT has done their initial review of Ds-587. They recommend
implementing it, but want us to review the newly updated patch from Michigan,
just posted to DS-587
[20:45] <kompewter> [ https://jira.duraspace.org/browse/DS-587 ] - [#DS-587]
add the capability to indicate a withdraw reason to an item ( tombstone ) -
DuraSpace JIRA
[20:46] * richardrodgers
([email protected]) has joined
#duraspace
[20:47] <tdonohue> I know the new patch is a bit larger, so it may be difficult
to do a thorough review now. But, does anyone want to volunteer to look into
this more closely and give more feedback on the suggested Tombstone changes?
[20:47] <kompewter> [ https://jira.duraspace.org/browse/DS-587 ] - [#DS-587]
add the capability to indicate a withdraw reason to an item ( tombstone ) -
DuraSpace JIRA
[20:47] <grahamtriggs> seems massively over complicated trying to pick out
information from the provenance
[20:48] <richardrodgers> I can have a look at it
[20:50] <tdonohue> Ok, richardrodgers, that'd be good. We basically are looking
for feedback to give back to both DCAT & Michigan. Suggesting changes, etc.
[20:50] <vhollister> Michigan is also willing to write the XML version -- but
needs some guidence
[20:50] <tdonohue> it'd probably be best to comment on Ds-587 with any feedback
directly. I know DCAT is following that issue
[20:50] <richardrodgers> yep - I just noticed that for Manakin at least,
Tombstones are a bit broken...
[20:51] <grahamtriggs> not to mention fragile... we've talked about an internal
metadata schema - shouldn't we just hold off until we've got that schema (1.8?)
and ensure that we've got appropriate field(s) that can be addressed directly.
More robust, and a shed load less code.
[20:51] <PeterDietz> my admins have also expressed interest in
tombstones/withdraw so I'll likely have a look too
[20:52] <tdonohue> If others have thoughts/suggestions, I'd encourage adding
them to Ds-587 comments. It'd be great to see some version of this make it into
1.8 (whether it's the michigan code or something slightly different that we
rework)
[20:52] <richardrodgers> yes grahamtriggs : the answer might be: we can do it
properly with internal metadata....
[20:52] <tdonohue> thanks to both PeterDietz & richardrodgers!
[20:52] <vhollister> agree w/tdonohue -- good if some version made it into 1.8
[20:52] <vhollister> yes, thx!
[20:53] <tdonohue> yes, I'd also agree that might be the answer grahamtriggs.
The main idea is not that we *have* to accept the patch as-is. More, that DCAT
sees this as an important feature worth gettting into 1.8. How it ends up in
1.8 could be different than the current patch
> 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
> Affects Versions: 1.6.0
> Environment: This is a change to the base functionality of the jspui.
> Reporter: Jose Blanco
> Attachments: confirm-withdraw-item.jsp, embargo.jsp, tombstone.jsp,
> 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 contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
