Title: Message Title
|
|
|
|
I suspect this is really an artifact of the fact that originally DSpace had no way to restrict READ access to Communities and Collections (it was assumed early on that Communities/Collections homepages would always be open access). In more recent years, I think this view has changed, but the software itself hasn't fully met that use case yet.
I know that in DSpace 3, Discovery (for XMLUI) had some enhancements that better handled READ permissions. I'm not sure how well that all was ported to JSPUI in DSpace 4 (where Discovery is now the default for search/browse). So, it's possible there's even a small bug here in the JSPUI that affects things.
In general though, it seems like a good idea to find a way to limit READ access to Communities/Collections in DSpace. But, as of yet, that idea is not well implemented in XMLUI or JSPUI (or even OAI-PMH and other machine interfaces).
This really seems to just need a volunteer to start to find ways to implement these improvements (preferably in a way that takes affect in all interfaces, if that's possible).
|
|
|
|
|
|
|
If an user browses a community or collection without having read permission XMLUI and JSPUI reacts differently. The XMLUI shows a note that the community or collection has limited access while ths JSPUI shows the community or collection like having read permissions. If a collection is browsed and the collection contains items which the user may read
the...
|
|
|
|
------------------------------------------------------------------------------
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
