On Tue, Aug 6, 2013 at 10:14 AM, <[email protected]> wrote: > Still not working...
Did you use the patch from here? https://github.com/DSpace/DSpace/pull/255 > Is there anything specific that need to be done while creating community or > collection for this to take effect? Yes, the item you're testing with has to have READ access for the MY_UNIVERSITY group if you use this: ip.MY_UNIVERSITY = 10.1.2.3 In DSpace, permissions are not hierarchical, they're only on items. An item inherits collection's permissions only when it's created. If you want to modify them afterwards, you have to change them on specific items. If you want to change them on a whole group of items, Wildcard Policy Admin can help with that. See: https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-Ichangedaccessrestrictionsonacollection,butrestrictionsdidn'tchangeonitsitems Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
