[
https://jira.duraspace.org/browse/DS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22077#comment-22077
]
Mark H. Wood commented on DS-996:
---------------------------------
Well, there are two kinds of information being discussed here. Current state
of an Item is one, and that clearly belongs to the Item. But the record of
state transitions is (in potential) multiply valued, and I don't know what to
call it if not metadata. And the metadata table is designed for capturing
multiple values. There may not be a 1:1 correspondence between state
transitions and provenance, either.
I think I disagree: the record of state transitions is exactly the place to
put reasons for those transitions. It's not a good place to put the current
state, though. The state of an Item w.r.t. visibility without regard to
permissions ought to be a simple indicator telling the UI what to *do*, and
that should be in the Item. If you want to show why it is in that state, the
latest state transition record should be holding the reason. But we may need
another type for capturing transition records -- IIRC the metadata table is too
simple for this. (I think we need a more structured type for provenance, too,
although those data will often be inherently somewhat messy and indefinite.)
An interim solution that we can get out the door quickly seems like a good
first step. But I think we are going to need some time, after that, to step
back and think about how well our current data model fits what we are trying to
accomplish today.
> 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
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
