Title: Message Title
|
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
4.1, 4.0
|
|
Assignee:
|
Unassigned
|
|
Components:
|
REST API
|
|
Created:
|
21/Apr/14 3:51 PM
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tim Donohue
|
|
If you mark an item as "private" in the Submission UI or the Admin UI, it is still visible in the browse functions of the REST API.
By definition, a "private" item should be hidden from all browse/search interfaces (including REST API). Private items are still potentially accessible via direct URL, but should not be discoverable through REST API, except by direct URL access.
https://wiki.duraspace.org/display/DSDOC4x/DSpace+Item+State+Definitions
To Reproduce this issue:
* Create a Item, and mark it as "private"
* That item will not be discoverable in the DSpace Browse or Search UIs
* However, it will still appear in the REST API under its parent Collection:
http://localhost:8080/rest/collections/:ID?expand=all
The correct result would be:
* The Private Item should NOT be visible under its parent Collection via REST API
* HOWEVER, the Private Item should still be accessible via REST by directly entering its identifier, e.g. http://localhost:8080/rest/items/:ID
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
