Hi all

We need a leg-up on setting some permissions for a sub-community - at the moment all attempts to do the intuitive thing don't succeed.

We have a Sub-Community (called HOUP) and we want access to the bit-streams restricted to one Group of users (apart from Administrator). (It's not important whether or not the abstract/metadata view gets restricted too.)

So I've done what you'd expect: removed the Anonymous "READ" action from the Sub-Community; created a group called HOUP-Read; added that group to the Sub-Community policy with "READ" action.

But when I add ordinary e-people to this HOUP-Read group, they still can't access abstracts or bitstreams in the Sub-Community when logged in.

Should this work? Is there a reason this doesn't work as expected? Would it work at Collection level? Have I missed some crucial step? Feel free to point me at any coherent documentation on the subject.

Thanks in advance

Richard

(We're still running 1.4 btw - maybe 1.5.1 handles this better?)






begin:vcard
fn:Richard M. Davis
n:Davis;Richard
org:ULCC;Digital Archives Department
adr:;;20 Guilford Street;London;;WC1N 1DZ;United Kingdom
email;internet:[EMAIL PROTECTED]
tel;work:020 7692 1350
tel;cell:079 30 40 61 97
x-mozilla-html:FALSE
url:http://dablog.ulcc.ac.uk/
version:2.1
end:vcard

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to