Maintaining document identity across hierarchy and non-hierarchy file systems

1. A mechanism for maintaining a document identity during a translation instruction from a hierarchical file system based application to a document management system which separates a content of a document from properties of the document, wherein the properties of the document are attached to the document by a user, the mechanism comprising: a means for receiving, from the application, a rename or delete operation in connection with an original document; a means for maintaining name information, location information and properties of the original document; a means for retrieving the name information, location information, and properties of the original document, upon a predetermined event; and, a means of copying new content to the original document.

2. The mechanism according to claim 1 wherein the predetermined event is a rename or delete operation issued by the application within a predetermined time period.

3. The mechanism according to claim 1 wherein when the original document is deleted, information as to the maintained data is not visible to a user.

4. The mechanism according to claim 1 wherein the original document within a collection of documents is maintained even when the content of the original document is changed.

5. The mechanism according to claim 1 wherein the properties which are attached to the document by the individual user, are appropriate for the individual user, without needing to be appropriate for the overall document management system.

6. A system which maintains a document identity when a document is translated, the system comprising: a hierarchical file system; a document management system which separates a content of a document from the document and where properties are attached to the document by an individual user; a means for sensing issuance of an instruction from a hierarchical application to delete or rename an original document; a means for maintaining properties of an original document which is to be deleted or renamed; a means for maintaining a name and location of the original document which is being deleted or renamed; a means for determining receipt of (i) an instruction to create a new document with the name of the original document or (ii) an instruction to attempt to rename the original document; a means for determining if either one of the instructions are received within a predetermined amount of time following the original delete or rename instruction; a means for resurrecting the original document in its original location, including having its original name and the attached properties; and, a means for adding new content to the original document, wherein the original document maintains properties attached by the document management system.

7. The system according to claim 6 wherein the properties which are attached to the document by the individual user appropriate for the individual user, without needing to be appropriate for the overall document management system.

8. A method of maintaining a document identity during a translating operation from a hierarchical file system application which treats a document as a single repository of unified data, to a document management system which adds additional information to a document thereby enhancing interactions with documents being managed, the method comprising: receiving an instruction from an application of a hierarchical file system to rename or delete an original document; maintaining at least name information, location information and properties of the original document upon a rename or delete instruction; retrieving the name information, location information, and properties of the original document, upon a predetermined event; and, copying new content to the original document.

9. The method according to claim 8 wherein the properties which are attached to the document by the individual user are appropriate for the individual user, without needing to be appropriate for the overall document management system.