As a matter of fact, there is an automated way of fixing the policies for
items from earlier versions of DSpace. Just go to the Authorization section
of the admin UI and run the 'Advanced/Item Wildcard Policy Admin Tool'.
It's a silly name, but it does allow you to do wildcard changes to item and
bitstream permissions within a collection. It acts on all of the items or
bitstreams within a collection, and you can use it to add in the policies
that are missing. Feel free to ask if you would like more help in using it.
HP Labs Cambridge / David.Stuve@... / 617-551-7632
From: Jennifer Ward [mailto:jlward1@...]
Sent: Wednesday, May 21, 2003 4:57 PM
Subject: Re: [Dspace-tech] authorization not working on v1.1
Thanks, Mark, for the clarification and apologies for not adding my own.
This is what we're seeing, too -- items uploaded in DSpace1.1 can be read by
anyone, but older submissions are problematic.
I just found a fix for items created in 1.0.1 -- but it's not terribly
practical as you have to set things in the GUI. If you go into the
Authorization interface > Manage an Item's policies, you have to reset the
policies at the item and bitstream level. I had set all bitstream authz to
anonymous read, but didn't set the item policy. I don't remember seeing
explicit bitstream level permissions in 1.0.1, but I could be wrong.
We only have two items in the system from 1.0.1, so my testing abilities are
somewhat limited. Surely there's a better (automated) way to take care of
On Wed, 21 May 2003, Mark O'Neil wrote:
:My bad - I need to clarify on my previous post.
:After looking into it a bit further I can access objects uploaded with :1.1
fine both as anonymous and as an EPerson.
:For objects uploaded using 1.0 I am not able to get an anonymous :bitstream
read, but can read the metadata - to access the bitstream I :must login.
:On Wednesday, May 21, 2003, at 03:52 PM, Jennifer Ward wrote:
:> Has anyone had problems with Anonymous Read not working? It makes some :>
sense that this could be related to the 'Administrators only can add :>
problem', but I wanted to check with others before assuming it's a :> local
:> issue. :> :> Thanks, :> Jennifer :>
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore. Now part
of Progress Software. http://www.objectstore.net/sourceforge
DSpace-tech mailing list