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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
