Hi Susan, hmm, that seems a bit weird. Basically, if you want to set up a collection with it's content both item and bitstreams restricted this is done during the creation of the collection. Uncheck the first box in the "Describe the collection" page which states "New items should be publicly readable". In the next step enter your Collection information, then you got to "Authorization to Read". There select the group which should be able to access (read) the items. Finish your collection creation and this will result in the appropriate rights of DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ set to the group you selected. Note the READ on the collection itself remains anonymous.
Claudia Susan Teague Rector schrieb: > > I got it working...How or why? I'm not sure, but it's working :) > > I created another collection with defaults and imported my items into > that collection (i.e., change all the instances of VCU users in the > table below to anonymous) > then, I went back and set gave all read auths to my VCU users group on > the collection > then, I went into the authorization tool and cleared all policies. > > Somehow that worked...I have no idea how this is working (as logically > this makes absolutely no sense to me - I should have been able to import > using the permissions below, no?)... > > thanks, > Susan > > Susan Teague Rector wrote: >> Thanks Claudia, >> >> >> So, I just set up a new collection to start fresh. Here's what I have >> for authorizations: >> >> Action Group >> collection_admin collection_167_admin >> add collection_167_submit >> default_bitstream_read VCU users >> default_item_read VCU users >> read VCU users >> >> When I try to import, everything goes in fine, except that I can't see >> the item's file. What am I missing in the permissions? >> Do I still need anonymous in there? >> >> Thanks for all your help! >> >> >> >> >> >> Claudia Jürgen wrote: >> >>> Hi Susan, >>> >>> you should have set >>> DEFAULT_BITSTREAM_READ >>> and >>> DEFAULT_ITEM_READ on the COLLECTION before importing. From these the >>> READ rights for the items and their bitstreams are derived during >>> submission. >>> >>> If you want to use the advanced authorization tool to achieve the >>> job, you got to >>> a) clear the policies for item/bitstreams >>> b) then add READ rights for item/bitstreams >>> per collection. >>> >>> Just adding a new right won't remove the old one. >>> >>> hope that helps >>> >>> Claudia >>> >>> >>> Susan Teague Rector schrieb: >>> >>>> Hi folks, >>>> >>>> Happy Friday... >>>> >>>> I'm using Dspace 1.4.1 and need help with authorizations... >>>> >>>> I'm importing ETDs into a collection that needs to be ultimately >>>> restricted to a group of local users (VCU community users). >>>> >>>> Here's what I've done so far: >>>> >>>> - I've created a collection that is now open and readable by anonymous >>>> - I've imported by ETDs into this collection >>>> - I now need to use the advanced/wildcard authorization (at least I >>>> think I do) to take anonymous out of the policies and make this >>>> collection readable only by my VCU group (which is defined in the >>>> system per the MIT model of checking for emails & IPs). >>>> >>>> The advanced/item wildcard policy tool does not seem to be working - >>>> From looking online, this should change the permissions for all >>>> items in a collection, no? >>>> >>>> In the tool I'm setting the following policies on my populated >>>> collection: >>>> >>>> content type: item >>>> group: VCU users >>>> action: READ >>>> >>>> content type: item >>>> group: VCU users >>>> action: DEFAULT_BITSTREAM_READ >>>> >>>> content type: item >>>> group: VCU users >>>> action: DEFAULT_ITEM_READ >>>> >>>> Does anyone know why these aren't sticking? Where are these policies >>>> stored in the database? resourcepolicy table? >>>> >>>> Thanks for any help you can provide >>>> cheers, >>>> >>>> susan >>>> >>>> ------------------------------------------------------------------------- >>>> >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> _______________________________________________ >>>> DSpace-tech mailing list >>>> DSpace-tech@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >>>> >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> DSpace-tech mailing list >> DSpace-tech@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
