Hi, On 22/04/15 02:49, Tim Donohue wrote: > You should be able to just enable that Access Step. Setting the embargo > via that step applies to the entire Item (including metadata), if I > recall correctly. By default, if you use the "Simple" version, it'll > limit Anonymous READ access (on the Item) so that it starts on the date > the embargo ends. If you use the "Advanced" version, you can specify > exact groups whose READ access should be limited (just be sure to click > the "Confirm Policy & add another" for each embargo policy).
This is what we're doing for some of "my" repositories; however I also have a pile of customisations in place (since at least DSpace 1.6.x) to make sure the policies are respected everywhere. I don't know whether all of these customisations are still needed, perhaps some are overkill. I should review these at some point. With the Discovery rights awareness functionality, you (=the current user) will see an item in search/browse etc only when you have READ permissions for the item. Viewing the item page is also controlled by the item's READ permission; if you don't have that permission then you'll get a message / be prompted to log in. So the READ permissions definitely cover the basics. cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ 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
