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
>> [email protected]
>> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to