System Error on approval (previous Author no longer exists)

[Richard H.]

The document in question had previously belonged to a user who has since left the employ of the University. Her email account is disabled and her email alias has been deleted.

The document has been reassigned to another author (who is a recent new employee but who exists in LDAP and can login to the DL) and the document itself has been updated. Submission was accepted by the DL weeks ago, but the system will not allow the document to be approved! It reports a System Error.

[Richard H. (richard-hewison)]

There's more to this problem.

If we submit the document from scratch (a new submission rather than replacing a previous submission) we still get a System Error. This might be related to the user or the document file rather than the fact that the previous document had belonged to a user who no longer exists at the University.

We will investigate further at this end.

[Richard H. (richard-hewison)]

Further information relating to this problem.

A document can be submitted on behalf of the user no problem at all. However, the System Error is encountered when I (a DL Manager) try and approve the submission.

The DL History reports the following...

History entry

title Workstation self assessment form
action that took place change_from_submitted
source workflow state 0
destination workflow state 0
id of actor documentlibraryRHewison
comment
date 3 Sep 2009 07:26:35
message

... which was when I sumbitted a change to the submission. Any of the approval attempts that elicit the System Error are not recorded in the DL History at all.

The question is this; how come the DL errors on an approval yet quite happily accepts a submission? What is the technical difference between the two?

[Richard H. (richard-hewison)]

It appears that the System Error was relating to the fact that the Librarian for the category being submitted to was the same person who had previously owned the document (and who has now left the employ of the Uni and has had her email alias disabled). Once a new Librarian was assigned, this problem went away.