Handling Orphaned Documents - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

7 Determine where you backed up the archive set, then copy either the archive set or the
individual BLOB file to the archive directory specified in the Current Location field that you
noted earlier.
8 You can now notify the user that the requested document is available.
9 When you are sure the user has opened the document (causing it to be unarchived), you should
delete any files remaining in that archive directory because you have already backed them up.

23.4.3 Handling Orphaned Documents

If you remove public rights for a library, some documents might become inaccessible. For example,
if a user who has been denied access to the library is the only user who had access to certain
documents, those documents become orphaned. No other user can access or search for those
orphaned documents. This is because document security is controlled by the user listed in the
Author and Creator fields in the document's properties. In other words, if the author or creator no
longer has access to a document, neither does anyone else.
However, orphaned documents can be reassigned to another author so that someone can access them
again. This can be done in one of two ways:
In ConsoleOne, the Analyze/Fix Library action in Mailbox/Library Maintenance can reassign
orphaned documents to a specified user. Then, the new user has access to all orphaned
documents in that library. For more information, see
Library and Document Information," on page
A librarian has the ability to alter the Author field of documents. Therefore, a librarian can
replace the previous user's GroupWise ID with his or her own ID. In doing so, the librarian
becomes the new author of the document. This can also be done as a mass operation for
multiple documents with varying user IDs in the Author field. For more information, see
Section 22.6.4, "Adding and Training Librarians," on page
378 GroupWise 8 Administration Guide
Section 28.2, "Analyzing and Fixing
408.
341.