Personal file version archival management and retrieval

• US 20070271303A1
• Filed: 05/18/2006
• Published: 11/22/2007
• Est. Priority Date: 05/18/2006
• Status: Abandoned Application

• Current Assignee: Joaquin Higinio De Soto, Jorge Francisco Miranda, Manuel Emilio Menendez
• Original Assignee: Joaquin Higinio De Soto, Jorge Francisco Miranda, Manuel Emilio Menendez
• Inventors: Menendez, Manuel Emilio, de Soto, Joaquin Higinio, Miranda, Jorge Francisco
• Application Number:
  US11/436,285
• Publication Number:
  US 20070271303A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71

Abstract

A method for file version control, including intercepting a command to access a target file within a computer file system, determining whether or not the intercepted command is directly related to a user editing session, based on at least one behavioral rule, if the determining is affirmative, then storing a copy of the target file within a file version history archive, and adding a reference to the target file to a queue of active files, when the target file is closed, searching the queue of active files for an entry to the target file, if an entry to the target file in the queue of active files is found, then comparing the target file against the stored copy, if the target file is identical to the stored copy, then deleting the copy of the target file from the file version history archive, and clearing the reference to the target file from the queue of active files. A system and a computer-readable storage medium are also described and claimed.

Claims

1. A method for file version control, comprising:

intercepting a command to access a target file within a computer file system;

determining whether or not the intercepted command is directly related to a user editing session, based on at least one behavioral rule;

if said determining is affirmative, then;

storing a copy of the target file within a file version history archive; and

adding a reference to the target file to a queue of active files;

when the target file is closed, searching the queue of active files for an entry to the target file;

if an entry to the target file in the queue of active files is found, then;

comparing the target file against the stored copy;

if the target file is identical to the stored copy, then deleting the copy of the target file from the file version history archive; and

clearing the reference to the target file from the queue of active files.

2. The method of claim 1 wherein said storing a copy of the target file within a file version history archive comprises storing the copy of the target file within a temporary memory buffer, and wherein the method further comprises moving the copy of the target file from the temporary buffer to a non-temporary location within the file version history archive if the target file is not identical to the stored copy.

3. The method of claim 1 further comprising determining whether or not the target file should be tracked, based on user preference settings.

4. The method of claim 3 wherein the user preference settings include file types to be tracked.

5. The method of claim 3 wherein the user preference settings include file types not to be tracked.

6. The method of claim 3 wherein the user preference settings include directories to be tracked.

7. The method of claim 3 wherein the user preference settings include directories not to be tracked.

8. The method of claim 1 further comprising storing a pointer to the target file in the file version history archive.

9. The method of claim 1 further comprising storing comment data in the file version history archive.

10. The method of claim 1 further comprising storing a pointer to comment data in the archive.

11. The method of claim 1 further comprising assigning a name to the archived file, the name including the target file name, the target file type, and a unique identifier.

12. The method of claim 1 wherein the file version history archive is a relational database.

13. The method of claim 1 wherein the file version history archive is a file system archive.

14. The method of claim 1 wherein the file version history archive is a hierarchical database.

15. The method of claim 1 wherein the file version history archive is a hosted service remote from the computer.

16. A system for file version control, comprising:

a file access interceptor, for intercepting a command to open a target file within a computer file system;

an access filter coupled with said file access interceptor, for determining whether or not the intercepted command is directly related to a user editing session, based on at least one behavioral rule; and

an archive manager coupled with said access filter, (i) for storing a copy of the target file within a file version history archive, (ii) for adding a reference to the target file to a queue of active files, (iii) for searching the queue of active files for an entry to the target file, and (iv) for comparing the target file against the stored copy when the target file is closed.

17. The system of claim 16 wherein said archive manager stores a copy of the target file within a temporary memory buffer, and moves the copy of the target file from the temporary memory buffer to a non-temporary location within the file version history archive.

18. The system of claim 16 wherein said access filter determines whether or not the target file should be tracked, based on user preference settings.

19. The system of claim 18 wherein the user preference settings include file types to be tracked.

20. The system of claim 18 wherein the user preference settings include file types not to be tracked.

21. The system of claim 18 wherein the user preference settings include directories to be tracked.

22. The system of claim 18 wherein the user preference settings include directories not to be tracked.

23. The system of claim 16 wherein said archive manager stores a pointer to the target file in the file version history archive.

24. The system of claim 16 wherein said archive manager stores comment data in the file version history archive.

25. The system of claim 16 wherein said archive manager stores a pointer to comment data in the file version history archive.

26. The system of claim 16 wherein said archive manager assigns a name to the archived file, the name including the target file name, the target file type, and a unique identifier.

27. The system of claim 16 wherein said archive manager is a relational database manager.

28. The system of claim 16 wherein said archive manager is a file system manager.

29. The system of claim 16 wherein said archive manager is a hierarchical database manager.

30. The system of claim 16 wherein said archive manager is a hosted service remote from the computer.

31. A computer-readable storage medium storing program code for causing at least one computing device to:

intercept a command to access a target file;

determine whether or not the intercepted command is directly related to a user editing session, based on at least one behavioral rule;

if said determining is affirmative, then;

store a copy of the target file within a file version history archive; and

add a reference to the target file to a queue of active files;

when the target file is closed, search the queue of active files for an entry to the target file;

if an entry to the target file in the queue of active files is found, then;

compare the target file against the stored copy;

if the target file is identical to the stored copy, then delete the copy of the target file from the file version history archive; and

clear the reference to the target file from the queue of active files.