[
https://jira.duraspace.org/browse/DS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22061#comment-22061
]
Tim Donohue commented on DS-996:
--------------------------------
Richard,
That change to the messages makes it a little better. I still worry slightly
about the difficulty of adding a completely custom reason. Though, I'm not
sure what others would think here -- if it's better to get something simple in
1.8.0 (and improve on it later), or wait until a later release altogether. I
think I'm now leaning slightly towards releasing something simple in 1.8.0, and
improve it later.
But, we will need to be very clear in our 1.8.0 documentation, that what we are
providing is:
* A "default" tombstone reason, that is easily customizable in
Messages.properties (or messages.xml)
* System Administrators can also manually add their own "one-off" custom
tombstone reasons (on individual items) by manually editing the appropriate
metadata field. (If the item is ever reinstated, they will also need to
manually remove that custom reason from the metadata field)
I'm going to send an email to the DCAT list (and copy you in), linking them
back to this particular issue & discussion. Hopefully we can get some
immediate feedback, and make sure that others are OK with this approach.
I'd say we should continue forward with this simple approach though, in the
assumption that it will be in 1.8.0.
> Add optional reason text to tombstone page
> ------------------------------------------
>
> Key: DS-996
> URL: https://jira.duraspace.org/browse/DS-996
> Project: DSpace
> Issue Type: Improvement
> Components: JSPUI
> Affects Versions: 1.8.0
> Reporter: Richard Rodgers
> Assignee: Richard Rodgers
> Attachments: handle-servlet.patch, msgs.patch, tombstone.patch
>
>
> Following the work at UMich (DS-587), this patch will cause the value of any
> configured item metadata field on the withdrawn item's tombstone page to
> display.
> It is configured by the optional property
> 'webui.tombstone.reason=<metadatafield>' in dspace.cfg
> If configuration property is not defined, the tombstone will appear without a
> reason display area.
> If a given item lacks a value for configured metadata field, the reason
> displayed will be the value of the message: 'jsp.tombstone.noreason'
> The prompt before the reason text is the value of the message:
> 'jsp.tombstone.reason'
> Patches below
--
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
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
