There are different Use Cases on the wiki that are related to this, and which would benefit from your input/suggestions, notably: https://wiki.duraspace.org/display/DSPACE/Admin+UI+-+Detect+and+re-assign+stalled+workflow+tasks
But there are many different workflow related suggestions in here as well: https://wiki.duraspace.org/display/DSPACE/Use+Cases As soon as we align on the use case / functionality, we can create the JIRA ticket and start building these improvements. -- [image: logo] *Bram Luyten* *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> On 17 December 2015 at 16:22, Anthony Petryk <[email protected]> wrote: > Hi, > > > > I think this use case, and many others, would be addressed if > administrators were able to manage all submissions (in workflow AND > workspace) via the admin UI. As an admin, it feels strange to have to > “Login As” someone in order to do something. > > > > We’re on DSpace 4.3 – my apologies if this has already been implemented in > later versions. > > > > Best, > > > > Anthony > > > > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Bram Luyten > *Sent:* Thursday, December 17, 2015 8:54 AM > *To:* Jonathan Blood <[email protected]> > *Cc:* DSpace Technical Support <[email protected]> > *Subject:* Re: [dspace-tech] Re: how to get to an item in a workflow > after originator retires? > > > > Hello, > > > > I'm not confident I fully understand the use case, but it sounds to me > that this could be addressed with enabling the "login-as" feature, that > allows an admin to login as a user. > > > > > https://wiki.duraspace.org/display/DSDOC5x/Configuration+Reference#ConfigurationReference-Loginasfeature > > > > I would be interested to learn how the admin "login-as" feature interacts > with the "can-login" checkbox. If the can-login feature prevents an admin > from using "login-as" as that user, I think it should be filed as a bug, > because if admins decide they want to login as a de-activated account, I > think they should be able to do this. > > > > rgds > > > > Bram > > > -- > > [image: logo] > > *Bram Luyten* > *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* > *Esperantolaan 4, Heverlee 3001, Belgium* > www.atmire.com > <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> > > > > > On 16 December 2015 at 15:51, Jonathan Blood <[email protected]> > wrote: > > Hi, > > I couldn't find a great solution for this out of the box. I achieved this > through customisations. > I created a customisation which would email administrators if items are > not actioned upon over a certain period of time (the time period was > configurable per collection). > This would send the administrator a link to the workflow in question. > > To compliment this I made a change to workflow authorisations so that an > administrator would be able to access all workflows. > > Regards, > Jonathan > > On Friday, December 11, 2015 at 10:11:55 PM UTC, Catherine Cronin wrote: > > Here is our scenario: > > > > A researcher has submitted an Item in Dspace 3.3 (JSPUI) which goes > through an approval process using the standard workflow (not customized). > > The Item has not been fully approved through all the steps yet. > > The researcher is going to retire on Dec 31st, and his account will be > "removed" from the system. (Actually, the "can login" switch will be > turned off and his single sign-on account will be removed from a > centralized DB) > > Once his account is removed, we are not sure what will happen to the Item > if one of the steps in the workflow doesn't approve and sends it back to > him. > > He won't have an email account, and he won't be able to login to the > Dspace website. > > > > Is there a way for an Admin to take control of the Item in the workflow? > > > > We tried to emulate this in our development system, however because of the > single sign-on setup (we are configured for shibboleth), even when I > uncheck the "Can Login" checkbox, the researcher can still login. I think > his single sign-on account would have to be disabled in order for him to > have access. > > > > Has this happened to anyone else and how did you handle the Items that may > not have been through the approval workflow prior to the originator leaving? > > > > Cathy Cronin > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
