Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
2003-05-22
2004-10-12
Channavajjala, Srirama (Department: 2177)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C705S051000, C705S052000
Reexamination Certificate
active
06804687
ABSTRACT:
TECHNICAL FIELD
The present invention relates generally to electronic file systems. More specifically, the present invention relates to a system and method for managing files using a token action log.
BACKGROUND OF THE INVENTION
In the 1980s, personal computers of various types became popular in business and home settings. Originally, a person's electronic files could be kept on removable “floppy disks” that had limited storage. Soon, higher-density disk storage became popular since it allowed people to store larger quantities of files. The cost of disk storage continues to drop, providing little incentive to curb the proliferation of files.
However, the incentive to curb the proliferation of files is that file systems can become unmanageable. Finding files can be a major chore. The systems for indexing files on content or other information are less than fulfilling. Such systems require that the user at least know enough about the file to find it. Unspecific searches can result in numerous files to sort through before finding the file or files of interest.
File systems can also require great effort to maintain because files and other stored entities have differing value to the system operators. What is needed is a way to identify which files have what value.
Most file systems allow a specific set of attributes to be attributed to individual files. For example, some files may be marked “read-only,” meaning that they can be read but not overwritten. Other files may be marked “hidden,” meaning that they are not to appear on normal directory listings.
Many files systems also allow other file attributes such as the author or the modification date. Such attributes are primarily informational, not functional. For example, a file by one author does not automatically behave differently in the file system from a file by another author. Informational attributes can nevertheless be useful as a file search criteria (e.g. searching for files by a particular author).
SUMMARY OF THE INVENTION
The present invention extends files systems or programs that operate on file systems by allowing individual files to possess arbitrary attributes that point to customizable actions. These attributes control the behavior of the file system under specified conditions.
In one embodiment, a file system includes a method for creating and storing one or more tokens and a token action log to associate each token with a customizable set of one or more actions. Each token is to trigger the associated set of one or more actions in response to accompanying a file-system entity that experiences an event. File events occur in conjunction with usual functions of the file system or in conjunction with programs that utilize the file system. Events might include accessing a file, deleting a file, opening a file, copying a file, printing a file, emailing a file, backing up a file, moving a file, creating a file, receiving a file from an external source, overwriting a file, modifying a file, etc. Other events might be time dependent, such as a certain period of time passing since an event occurred.
The “token action log” that associates tokens with actions could be called by other names, such as “token repository,” “token registery,” “token register,” etc. However, the name “token action log” (abbreviated: TAL) will be used herein, or “token log” for short.
In one embodiment, the operator of the file system instructs a program that might be called a “token log manager” (TLM) to store a token as a meaningful or arbitrary symbol. For example, a token might be created to flag all files pertaining to a certain project. The token would be stored in the token action log (TAL), along with desired actions corresponding to given file events. For example, when the project is completed, any files pertaining to that project should be archived and deleted from the file system. The event is the completion of the project, which may be indicated by passing a certain time, or indicated by the operator. The token for that project would therefore be attached to or otherwise associated with any files pertaining to that project. At the event signifying the completion of the project, the TLM would initiate the actions recorded in the TAL for the relevant files.
Other tokens might be created for files of a particular worth. For example, a token might be created for “temporary” files. The corresponding action recorded in the TAL might be to delete the file if five days have passed since the last time the file was accessed. As such, any file associated with the “temporary” token will be automatically deleted if not accessed for five days, freeing up disk space.
As another example, a token might be created for “important” files. The corresponding action recorded in the TAL might be to not allow the file to be deleted without first confirming with the file system operator, or automatically backing up the file if modified and not backed up within a pre-specified interval.
As still another example, a token might be created for “confidential” files. The corresponding action recorded in the TAL might be prompting the user before allowing the file to be transmitted outside of the file system (such as via email), or requiring that the user be authenticated before allowing him or her to open the file, or automatically printing the word “confidential” on the paper when the file contents are printed.
As yet another example, a token might be created to automate functions of program execution within the file system. A token might be created with actions to open a task list upon the event of a program file being executed. That “open task list” token might then be attached to program files that the operator would like to be used with the task list. When those program files are executed, the token log manager would identify the “open task list” token and open the task list, perhaps even highlighting those activities within the task list pertaining to the attached program file.
Alternatives to the “open task list” token concept may be “open recently-edited files list” token (to automatically show a list of recent files that can be edited by the program file), or an “open bookmarks list” token (to automatically show a list of files or other documents that have been bookmarked by the operator).
Additional aspects and advantages of this invention will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.
REFERENCES:
patent: 5063523 (1991-11-01), Vrenjak
patent: 5499358 (1996-03-01), Nevarez
patent: 5628007 (1997-05-01), Nevarez
patent: 5958005 (1999-09-01), Thorne et al.
patent: 6032216 (2000-02-01), Schmuck et al.
patent: 6088720 (2000-07-01), Berkowitz et al.
patent: 6122631 (2000-09-01), Berbec et al.
patent: 6301608 (2001-10-01), Rochkind
patent: 6324569 (2001-11-01), Ogilvie et al.
patent: 6397261 (2002-05-01), Eldridge et al.
patent: 6484197 (2002-11-01), Donohue
patent: 6505300 (2003-01-01), Chan et al.
patent: 6549950 (2003-04-01), Lytle et al.
patent: 6618716 (2003-09-01), Horvitz
patent: 2002/0049961 (2002-04-01), Fang et al.
patent: 2002/0099665 (2002-07-01), Burger et al.
patent: 2002/0174010 (2002-11-01), Rice
patent: 2003/0182332 (2003-09-01), McBrearty et al.
Channavajjala Srirama
Christensen Kory D.
Pham Khanh
Stoel Rives LLP
LandOfFree
File system management with user-definable functional... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with File system management with user-definable functional..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and File system management with user-definable functional... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3314341