[Dspace-tech] Collection Administrators
Hello, We are running 1.5.2 using Manakin. I have set up a collection and created a group. I have assigned two people to the group and also assigned the group the collection administration role. The two users in the collection administrator group can do what I would expect, except for the following: They cannot delete or upload bitstreams on an existing item in the collection. Is this by design or should they be able to do this? If they should be able to do it, how do I fix it so that it works for all existing items and any items that will be added later to that collection? Richard Jizba -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Collection Administrators
Hi Richard, This is straight from the (DSpace 1.5.x) documentation, although I'm not sure it answers your question: i. Collection Administrators can: 1. edit Collection description 2. edit Submitters to a Collection 3. map other Items into a Collection 4. edit Item metadata in a Collection 5. withdraw Items from a Collection ii. Collection Administrators can't: 1. edit Authorization Policies at the Collection, Item, or Bitstream Levels 2. edit the Workflow (change Workflow steps) 3. edit Groups 4. delete a Collection Cheers, Sue From: Jizba, Richard [mailto:richardji...@creighton.edu] Sent: Tuesday, January 19, 2010 1:33 PM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Collection Administrators Hello, We are running 1.5.2 using Manakin. I have set up a collection and created a group. I have assigned two people to the group and also assigned the group the collection administration role. The two users in the collection administrator group can do what I would expect, except for the following: They cannot delete or upload bitstreams on an existing item in the collection. Is this by design or should they be able to do this? If they should be able to do it, how do I fix it so that it works for all existing items and any items that will be added later to that collection? Richard Jizba -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Collection Administrators
But in the DSpace 1.5.1 the collection administration role doesn,t work. --- Victoria Rasero Biblioteca de la Universidad Carlos III de Madrid 2010/1/20 Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY] > Hi Richard, > > This is straight from the (DSpace 1.5.x) documentation, although I’m > not sure it answers your question: > > > > > i. Collection Administrators *can*: > > 1. edit Collection description > > 2. edit Submitters to a Collection > > 3. map other Items into a Collection > > 4. edit Item metadata in a Collection > > 5. withdraw Items from a Collection > > > > > ii. Collection Administrators *can’t:* > > 1. edit Authorization Policies at the Collection, Item, or Bitstream > Levels > > 2. edit the Workflow (change Workflow steps) > > 3. edit Groups > > 4. *delete* a Collection > > > > > > Cheers, > > Sue > > > -- > > *From:* Jizba, Richard [mailto:richardji...@creighton.edu] > *Sent:* Tuesday, January 19, 2010 1:33 PM > *To:* dspace-tech@lists.sourceforge.net > *Subject:* [Dspace-tech] Collection Administrators > > > > Hello, > > We are running 1.5.2 using Manakin. I have set up a collection and created > a group. I have assigned two people to the group and also assigned the > group the collection administration role. The two users in the collection > administrator group can do what I would expect, except for the following: They > cannot delete or upload bitstreams on an existing item in the collection. > > Is this by design or should they be able to do this? If they should be > able to do it, how do I fix it so that it works for all existing items and > any items that will be added later to that collection? > > Richard Jizba > > > -- > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > -- - -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Collection Administrators
Victoria & Richard, We actually ran across several issues with Collection Administration in the XMLUI in 1.5.x. This functionality has been almost completely re-built in the upcoming 1.6.0 release -- both for the XMLUI and the JSPUI. In the upcoming 1.6.0 release, there will be both Community and Collection Administrators possible. By default, a Community Administrator will be able to perform any actions within that Community (including in any sub-communities or sub-collections). In the same manner, by default, a Collection Administrator will be able to perform any actions (add/withdraw/delete) to any item within that collection. In 1.6, you will also be able to make your own policies around what Community and Collection Administrators are allowed to do within your DSpace installation. So, if you wanted to, you could disable a Collection Admins ability to delete items (by setting a new flag in the dspace.cfg). So, I'd recommend upgrading to 1.6 once it is released (likely in mid-Feb), for a more stable Delegated Administration system. - Tim On 1/21/2010 8:16 AM, Victoria Rasero wrote: > But in the DSpace 1.5.1 the collection administration role doesn,t work. > --- > Victoria Rasero > Biblioteca de la Universidad Carlos III de Madrid > > > 2010/1/20 Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES > COMPANY] mailto:susan.m.thorn...@nasa.gov>> > > Hi Richard, > > This is straight from the (DSpace 1.5.x) documentation, > although I’m not sure it answers your question: > > i. Collection Administrators *_can_*: > > 1. edit Collection description > > 2. edit Submitters to a Collection > > 3. map other Items into a Collection > > 4. edit Item metadata in a Collection > > 5. withdraw Items from a Collection > > ii. Collection Administrators *_can’t:_* > > 1. edit Authorization Policies at the Collection, Item, or Bitstream > Levels > > 2. edit the Workflow (change Workflow steps) > > 3. edit Groups > > 4. *delete* a Collection > > Cheers, > > Sue > > > > *From:* Jizba, Richard [mailto:richardji...@creighton.edu > <mailto:richardji...@creighton.edu>] > *Sent:* Tuesday, January 19, 2010 1:33 PM > *To:* dspace-tech@lists.sourceforge.net > <mailto:dspace-tech@lists.sourceforge.net> > *Subject:* [Dspace-tech] Collection Administrators > > Hello, > > We are running 1.5.2 using Manakin. I have set up a collection and > created a group. I have assigned two people to the group and also > assigned the group the collection administration role. The two users > in the collection administrator group can do what I would expect, > except for the following: They cannot delete or upload bitstreams on > an existing item in the collection. > > Is this by design or should they be able to do this? If they should > be able to do it, how do I fix it so that it works for all existing > items and any items that will be added later to that collection? > > Richard Jizba > > > > -- > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important > issues through > interactions with peers, luminaries and emerging and established > companies. > http://p.sf.net/sfu/rsaconf-dev2dev > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > <mailto:DSpace-tech@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > > > -- > - > > > > -- > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > > > > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech -
Re: [Dspace-tech] Collection Administrators
Hello Richard, I don't know yet how it should work in DSpace 1.5.2, but what you describe is how it works in earlier versions. They can do most of the admin tasks, but can not replace bitstreams. Only site-wide admins can do that. Best wishes, Francis Van: Jizba, Richard [mailto:richardji...@creighton.edu] Verzonden: dinsdag 19 januari 2010 19:33 Aan: dspace-tech@lists.sourceforge.net Onderwerp: [Dspace-tech] Collection Administrators Hello, We are running 1.5.2 using Manakin. I have set up a collection and created a group. I have assigned two people to the group and also assigned the group the collection administration role. The two users in the collection administrator group can do what I would expect, except for the following: They cannot delete or upload bitstreams on an existing item in the collection. Is this by design or should they be able to do this? If they should be able to do it, how do I fix it so that it works for all existing items and any items that will be added later to that collection? Richard Jizba -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Collection Administrators can not ADD bitstreams to new batch imported items.
Hello, In version 1.6.1 we created a sub-community and a collection in that sub-community. The same persons & group were given Administrative rights to the sub-community and collection. Next we used the batch metadata load to create new records in the collection (therefore these have no attached bitstreams). The Collection Administrators can do everything to the new records (edit metadata, delete the records) except adding a new bitstream. When they attempt to Upload a new bitstream, they receive this message: "You need the ADD & WRITE privilege on at least one bundle to be able to upload new bitstreams." If we manually create a record and include a bitstream during the submission process, then the collection administrator upload a new bitstream and also delete bitstreams. It appears that if the all the bitstreams are deleted, that person can not then upload a new bitstream. Only full DSpace Administrators can upload bitstreams to "empty" items. This is a real problem, because we envision a workflow where the metadata is batch imported and student-workers/staff then attach the file(s) or bitstreams. (We have the meta-data in another system which easily generates csv files. But that old system was just a 'finding aid' and did not include the bitstreams.) Is there a work around to this issue? Can this be fixed in later releases? Richard Jizba Creighton University -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
