![]() |
|
|
Issue Type:
|
Bug
|
Affects Versions:
|
3.2, 3.1, 3.0 |
Assignee:
|
Unassigned |
Components:
|
XMLUI |
Created:
|
17/Oct/13 7:25 PM
|
Description:
|
In DSpace 3.x, whenever you mark an Item as "private" (whether during deposit or when editing the item), behind the scenes is it withdrawn from the system (i.e. in_archive=false).
This is problematic, as "private" and "withdrawn" do NOT mean the same thing. Withdrawn items are essentially removed from the system, and many of DSpace's tools (CheckSum checker, Curation Tasks, etc.) ignore any 'withdrawn' items.
However, a Private item is not being removed, it is just hidden from view/visibility. Therefore, it should still be processed by Curation Tasks, etc.
Therefore a private item should NOT be withdrawn. Instead a private item should have "discoverable=false" but "in_archive"=true.
Also see Andrea Bollini's good analysis of "private" vs. "withdrawn" items:
https://wiki.duraspace.org/display/~bollini/DSpace+Item+state+definitions
|
Fix Versions:
|
4.0 |
Project:
|
DSpace
|
Priority:
|
Major
|
Reporter:
|
Tim Donohue
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel