Re: [Dspace-tech] Adding and removing bitstreams
You have right, DSpace authorization system is a complete mess.
In case someone face the same problem, we manage to solve the problem of
adding and removing bitstreams with the following steps:
1. The if statement in EditItemServlet.java around line 510 is
// only process bitstreams if admin
else if (p.startsWith(bitstream_name)
AuthorizeManager.isAdmin(context))
{
and must be
// only process bitstreams if admin
else if (p.startsWith(bitstream_name))
{
2. In resourcepolicy table the Group that will be able to perform the
deletions or additions must have following rights:
On the Collection of the item it must have READ, WRITE, ADD, REMOVE,
DEFAULT_BITSTREAM_READ, DEFAULT_ITEM_READ, COLLECTION_ADMIN rights.
You can give these rights with Manage Collection's Policies page in
Authorization menu.
On the Item it must have WRITE, ADD, REMOVE rights.
You can give these rights with Advanced/Item Wildcard Policy Admin
Tool page in Authorization menu.
After adding policies with wildcard policy admin tool is impossible to
see the changes unless you see the resourcepolicy table in the database.
Ilias Stavrakis
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Adding and removing bitstreams
I have no problem in deleting items using the configuration wrote earlier.
If the message you get is Authorization required, probably there are
some missing policies in resourcepolicy table.
Could you send the last lines of your log file?
Ilias Stavrakis
Mika Stenberg wrote:
This is great, since we are struggling with frustrated admins who cant
do the things they want to. Even after this, they still cant remove
the item from the collection, though, only withdraw it.
Any solution for this?
-Mika
You have right, DSpace authorization system is a complete mess.
In case someone face the same problem, we manage to solve the problem
of adding and removing bitstreams with the following steps:
1. The if statement in EditItemServlet.java around line 510 is
// only process bitstreams if admin
else if (p.startsWith(bitstream_name)
AuthorizeManager.isAdmin(context))
{
and must be
// only process bitstreams if admin
else if (p.startsWith(bitstream_name))
{
2. In resourcepolicy table the Group that will be able to perform the
deletions or additions must have following rights:
On the Collection of the item it must have READ, WRITE, ADD, REMOVE,
DEFAULT_BITSTREAM_READ, DEFAULT_ITEM_READ, COLLECTION_ADMIN rights.
You can give these rights with Manage Collection's Policies page
in Authorization menu.
On the Item it must have WRITE, ADD, REMOVE rights.
You can give these rights with Advanced/Item Wildcard Policy Admin
Tool page in Authorization menu.
After adding policies with wildcard policy admin tool is impossible
to see the changes unless you see the resourcepolicy table in the
database.
Ilias Stavrakis
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win
great prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Adding and removing bitstreams
Hi, i face a problem on adding and removing bitstreams in both dspace 1.4 and 1.5 and would like to ask the community and the developers of dspace for it. There is a defined Group containing some users. In the policies for a specific collection, this Group has all available permissions (DEFAULT_ITEM_READ,DEFAULT_BITSTREAM_READ,READ,WRITE,COLLECTION_ADMIN,REMOVE,ADD). But, for a user of this Group is impossible to delete a bitstream and add a new one. When trying to delete, there is no message and the page is reloaded without any change. When trying to upload, a message authorization required is prompted. On deletion, the problem exists in EditItemServlet.java. When the user choose to delete a bitstream there is the following check in line 506 // only process bitstreams if admin else if (p.startsWith(bitstream_name) * AuthorizeManager.isAdmin(context)* ) Why only administrators have the rights to delete bitstreams? Even if, we comment this extra check, there are points in Bundle.java and Bitstream.java that request to authorize the action with // Check authorisation AuthorizeManager.authorizeAction(ourContext, this, *Constants.WRITE*); But the users of the Group does not have permissions to perform the WRITE. Could anyone from the community give me any advice or comment? Furthermore, could anyone from the developers of security policies of dspace explain what is the proper policy that a group must have to add or remove bitstreams. I find out that the changes in authorization using wildcard policy admin tool don't add any lines in policies that are displayed in communities or collections. Moreover, there are a lot more choices in drop down menus when setting a policy using wildcard admin tool than using collection policy manager. Why? Thanks, Any comment would be helpful Ilias Stavrakis - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Adding and removing bitstreams
On Tue, 23 Sep 2008, Hlias Stavrakis wrote: Hi, i face a problem on adding and removing bitstreams in both dspace 1.4 and 1.5 and would like to ask the community and the developers of dspace for it. It's essentially broken. Like most of the authorization system. Some of our users are really fed up with this, but it's such a mess to sort out properly. -- Tom De Mulder [EMAIL PROTECTED] - Cambridge University Computing Service - 23/09/2008 : The Moon is Waning Gibbous (53% of Full) - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
