Hi Shrilatha, I think that the caveat here is that you need to remember that access is not inherited (e.g. from collection to items) for existing items, it's inherited only during submission. So you have to set it for every _existing_ item and bitstream individually. AFAIK there's no way how to do that from the user interface.
I think this snippet from @Mire describes it quite succintly: When a new item gets archived in the repository, it inherits the default policies for an item, defined by the collection in which the item is archived. It's important to realize that these policies can altered for each item, bundle or bitstream, without altering other items or collection properties. Policies are really tied to items, bundles and bitstreams. http://www.facebook.com/note.php?note_id=180273568767 I hope that explains your question. Regards, ~~helix84 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
