Hardik, The 1.6.2 Authorization documentation gives a good overview of these policies and their usage:
http://www.dspace.org/1_6_2Documentation/ch02.html#N102CE Essentially, the DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ are only used on Collections. These define the default permissions for *new items* submitted to that collection and whether those items are publicly available (DEFAULT_ITEM_READ), or their bitstreams are publicly available (DEFAULT_BITSTREAM_READ). The READ policy is used for both Items and Bitstreams, and can be used to limit access to either one. So, if you want to limit who can view a particular Item, you'd change the READ policy for that Item to the group you want to limit to. I hope that helps, - Tim On 8/6/2010 9:03 AM, Hardik Mishra wrote: > Hi All > > I have some confusion on collection policies. > > Can i have brief explanation ? > > DEFAULT_ITEM_READ > DEFAULT_BITSTREAM_READ > READ > > I want a particular group of users to view item-display page. > > > Thanks & Regards > Hardik Mishra > Software Engineer > > Give a man a fish, and you feed him for a day. Teach a man to catch fish > and you feed him for a lifetime. > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > > > > _______________________________________________ > Dspace-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-general ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
