Subject: RE: User Interface Disasters in Lotus Notes
First I want to make it clear that my direct influence at this point is pretty much limited to Designer features, not the Notes client, but I can talk to those people.
Sorry, do you mean you would want to disable the Edit attachment feature altogether with a policy, or you would want to have a choice between the “forced save as” behavior and the current behavior?
I’ve been giving the matter some more thought. As I and others have mentioned, it’s a challenge to know when someone is done editing a file, given the great variety of editing programs out there, and consistency is desirable, so a solution should not depend on being able to detect this.
It’s also a consideration that the files in question may contain private information, stored under access control in Notes and under database-level encryption if using a local replica. In which case, leaving the file anywhere on the disk in “clear text” would be potentially a security risk. However, if the user saves the file now after the Notes document is closed, there’s nothing to delete it. I think it would be acceptable for the file to remain on the disk for a limited period of time – adjustable by policy, default 48 hours – to allow retrieval in case the user is a fathead.
As I noted, the detached edit file is deleted when the Notes document is closed. If the editing program saves the file after the Notes document is closed, recreating the just-deleted file, then the data can be retrieved. When Mr. Schend’s users are losing data, I can only think it’s because they save the file they’re editing, then fail to save the Notes document.
Perhaps the user experience could be improved as follows:
When the Edit Attachment function is used, the temporary file is created in a directory identified by the UNID of the document.
As the temporary file is created, Notes records its timestamp in memory.
Upon saving the document, the temp file is grabbed and the timestamp compared – if it’s different, the attachment is updated.
On exiting the document without saving, the timestamp is compared. If it’s different, the existing save prompt has text added warning the user that their document changes that they are about to not save include edits to an attachment.
Just in case the user cannot read, if they exit without saving changes, and the timestamp is different, the file is not immediately deleted.
On closing the Notes client, there’s a scan thru the temporary directories used for attachment editing. Any files there that have not been modified for longer than the policy-specified cutoff are deleted, and empty subdirectories pruned.
If the user uses the edit attachment function again in the same document, and the file is already present in the directory identified by the document UNID, they are advised that there appear to be recoverable changes from a previous editing session and would they prefer to edit that file, or the current attachment contents?
Does that sound like a significant improvement?