Title: Message Title
|
|
|
|
I've been thinking about this issue. Indexing restricted items was not a missing requirement, it was, in fact, a decision.
Basically, there are scenarios where the user wants to use the OAI interface even for restricted content.
What is missing is the proper filter by default. So, to fix it, the easies simple solution would be to add the anonymous access filter in the default context, just like the driver context (https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51).
|
|
|
|
|
|
|
How to reproduce:
1) Create a Collection where DEFAULT_READ access is limited to a non-Anonymous group (e.g. Administrators or similar)
2) Submit an Item to that Collection
3) Run "./dspace oai import"
The Result:
* The Item will be access restricted from the UI (XMLUI or JSPUI), and will not be accessible to Anonymous Users
* HOWEVER, the I...
|
|
|
|
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
