Hi! Naveed, Thanks for sharing the details.
I was following the steps given below to enable the "Accept/Reject/Edit Metadata Step" for a collection administrator. (1) Created 2 normal accounts, JCK and ABC (2) Created a collection, CX (3) Using a DSpace admin account, "EDIT" the collection CX (4) In the Submission Workflow, selected the Collection Administrator as JCK (5) In the Submission Workflow, selected the Accept/Reject/Edit Metadata Step and assigned the E-PERSON as JCK (6) In the Submission Workflow, selected Submitters as JCK and ABC (7) Submitted an item to the collection CX using the account ABC (8) Logged in as JCK. The task pool shows the submission from ABC. (9) The collection administrator JCK can Accept/Reject/Edit the submission of ABC. I was just wondering whether this can be implemented on the production server if the steps look fine. Please suggest since here we have many collections and the DSpace admin account can't manage all submissions. Thanks, Jayan -----Original Message----- From: NS Hashmi, Information Systems and Computing [mailto:[EMAIL PROTECTED] Sent: Friday, July 06, 2007 1:44 AM To: Jayan Chirayath Kurian; [EMAIL PROTECTED] Cc: [email protected] Subject: RE: [Dspace-tech] Collection Administrator Hi Jayan I'm running dspace-1.4.1, neither the dspace administrator or collection administrator have by default the permission to manage/review a submission in workflow. A collection admin also (by default) does not have the right to submit to the collection they are administering. A collection admin can only modify the collection home page, create an item template (not sure what this is supposed to do), map items from other collections and add/edit submitters. I think a collection administrator should be able to manage all aspects of their collection (this shouldn't be the sole remit of the DSpace administrator). It would make sense for collection admin's to have the following additional permissions controlled from within the collection edit page: - Create/edit submitters - Accept/Reject Step - Accept/Reject/Edit Metadata Step - Edit Metadata Step - Delete a workflow - Collection's Authorizations Perhaps a community administrator (non existent in DSpace?) should have the right to delete a collection? Devolving these tasks to (trained) community and collection administrators where possible would free the DSpace administrator of these chores and thus assist with managing the repository. Naveed --On 05 July 2007 23:16 +0800 Jayan Chirayath Kurian <[EMAIL PROTECTED]> wrote: > > > hi! Naveed, > > By following the steps given below the collection administrator account > works with submission workflow. Jus want to clarify whether any one is > using this way for collection workflows rather than using DSpace admin > account. > > thanks, > jayan > > > __________________________________________________ > From: NS Hashmi, Information Systems and Computing > [mailto:[EMAIL PROTECTED] > Sent: Thu 7/5/2007 7:57 PM > To: Jayan Chirayath Kurian; [EMAIL PROTECTED] > Cc: [email protected] > Subject: Re: [Dspace-tech] Collection Administrator > > > > Hi, > > Jayan: this is a good idea, re: giving DSpace collection administrators > the > rights to manage individual collection work flows. I suggest you file this > as a feature request via the DSpace Tracker: > <http://sourceforge.net/tracker/?group_id=19984&atid=369984> > > Claudia: it would be useful to add the procedures for submitting feature > requests, patches and bugs to: > <http://wiki.dspace.org/index.php/EndUserFaq>, shall I do this? > > Naveed > > > Message: 6 > Date: Thu, 5 Jul 2007 16:35:39 +0800 > From: "Jayan Chirayath Kurian" <[EMAIL PROTECTED]> > Subject: Re: [Dspace-tech] Collection Administrator > To: Claudia J?rgen <[EMAIL PROTECTED]> > Cc: [email protected] > Message-ID: > > <[EMAIL PROTECTED] s > g> > > Content-Type: text/plain; charset="iso-8859-1" > > Hi! Claudia, > > Here each school is represented by a community and individual divisions > are > represented by collections. Although DSpace administrator account can > manage submission workflow to collections (i.e. edit metadata, accept, and > reject submission), it would be quite useful if individual collection > administrators can manage this workflow. > > For managing individual collection "C" using an account "X" apart from the > Administration account > > (1) Added the account X to the Collection administrator list of > collection C > (2) Added the account X to the Collection Submitter group. (without this > authorization error is given) > >> From the task pool of account X, workflow of collection C can be managed > (i.e. metadata editing, accept, reject submission etc) > > Is this the right way to allocate a collection administration other than > the administration account? We want the DSpace administration account to > be > relieved from managing individual collection workflows. Please suggest > > > Thanks, > Jayan > > > -------------------------------------------------------- > Naveed Hashmi > Information Systems and Computing > University of Bristol > [EMAIL PROTECTED] > > -------------------------------------------------------- Naveed Hashmi Information Systems and Computing University of Bristol [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
