EXTENDING APPLICATION BEHAVIOR THROUGH ACTIVE PROPERTIES ATTACHED TO A DOCUMENT IN A DOCUMENT MANAGEMENT SYSTEM

BACKGROUND OF THE INVENTION

[0001] The following applications are related to the present invention: U.S. Ser. No. ______ (XER 2 198/D/98497), Anthony G. LaMarca, et al., entitled USER LEVEL ACCESSING OF LOW-LEVEL COMPUTER SYSTEM OPERATIONS; U.S. Ser. No. ______ (XER 2 199/D/98495), Karin Petersen, et al., entitled PROPERTY-BASED USER LEVEL DOCUMENT MANAGEMENT; U.S. Ser. No. ______ (XER 2 200/D/98499), Douglas B. Terry, et al., entitled A PROPERTY-BASED MECHANISM FOR FLEXIBLY SUPPORTING FRONT-END AND BACK-END COMPONENTS HAVING DIFFERENT COMMUNICATION PROTOCOLS; U.S. Ser. No. ______ (XER 2 201/D/98500), Warren K. Edwards, et al., entitled ATOMIC AND MOLECULAR DOCUMENTS; U.S. Ser. No. ______ (XER 2 202/D/98503), Michael P. Salisbury, et al, entitled VIRTUAL DOCUMENTS; U.S. Ser. No. ______ (XER 2 203/D/98496), John O. Lamping, et al, entitled SELF CONTAINED DOCUMENT MANAGEMENT BASED ON DOCUMENT PROPERTIES; U.S. Ser. No. _______ (XER 2 204/D/98498), James D. Thornton, et al., entitled SERVICE INTERACTION USING PROPERTIES ATTACHED TO DOCUMENTS; U.S. Ser. No. ______ (XER 2 205/D/98501), James P. Dourish, et al., entitled ACTIVE PROPERTIES FOR DYNAMIC SYSTEM CONFIGURATION; U.S. Ser. No. _______ (XER 2 207/D/98493), Michael P. Salisbury, et al., entitled MAINTAINING DOCUMENT IDENTITY ACROSS FILE SYSTEM INTERFACES; U.S. Ser. No. ______ (XER 2 208/D/98494), Anthony G. LaMarca, et al, entitled CLUSTERING RELATED FILES IN A DOCUMENT MANAGEMENT SYSTEM.

[0002] Each of the above applications filed Aug. 31, 1998 and assigned to a common assignee are hereby incorporated by reference.

[0003] The present invention is directed to document management systems. It finds particular application to a system and method which allows a document application to attach properties to a document for controlling document state and behavior when the document application is not running and will be described with particular reference thereto.

[0004] The inventors have recognized that a large amount of a user's interaction with a computer has to do with document management, such as storing, filing, organizing and retrieving information from numerous electronic documents. These documents may be found on a local disc, on a network system file server, an e-mail file server, the world wide web, or a variety of other locations. Modem communication delivery systems have had the effect of greatly increasing the flow of documents which may be incorporated within a user's document space, thereby increasing the need for better tools to visualize and interact with the accumulated documents.

[0005] The most common tools for organizing a document space rely on a single fundamental mechanism known as hierarchical storage systems, wherein documents are treated as files that exist in directories or folders, which are themselves contained in other directories, thereby creating a hierarchy that provides the structure for document space interactions. Each directory in a hierarchy of directories, will commonly contain a number of individual files. Typically, files and directories are given alpha-numeric, mnemonic names in large storage volumes shared via a network. In such a network, individual users may be assigned specific directories.

[0006] A file located in a sub-directory is located by its compound path name. For example, the character string D:\TREE\LIMB\BRANCH\TWIG\LEAF.FIL could describe the location of a file LEAF.FIL whose immediate directory is TWIG and which is located deep in a hierarchy of files on the drive identified by the letter D. Each directory is itself a file containing file name, size, location data, and date and time of file creation or changes.

[0007] Navigation through a file system, to a large degree, can be considered as navigation through semantic structures that have been mapped onto the file hierarchy. Such navigation is normally accomplished by the use of browsers and dialog boxes. Thus, when a user traverses through the file system to obtain a file (LEAF.FIL), this movement can be seen not only as a movement from one file or folder to another, but also as a search procedure that exploits features of the documents to progressively focus on a smaller and smaller set of potential documents. The structure of the search is mapped onto the hierarchy provided by the file system, since the hierarchy is essentially the only existing mechanism available to organize files. However, documents and files are not the same thing.

[0008] Since files are grouped by directories, associating a single document with several different content groupings is cumbersome. The directory hierarchy is also used to control the access to documents, with access controls placed at every node of the hierarchy, which makes it difficult to grant file access to only one or a few people. In the present invention, separation of a document's inherent identity from its properties, including its membership in various document collections, alleviates these problems.

[0009] Other drawbacks include that existing hierarchical file systems provide a “single inheritance” structure. Specifically, files can only be in one place at a time, and so can occupy only one spot in the semantic structure. The use of links and aliases are attempts to improve upon such a limitation. Thus, while a user's conception of a structure by which files should be organized may change over time, the hierarchy described above is fixed and rigid. While moving individual files within such a structure is a fairly straightforward task, reorganizing large sets of files is much more complicated, inefficient and time consuming. From the foregoing it can be seen that existing systems do not address a user's need to alter a file structure based on categories which change over time. At one moment a user may wish to organize the document space in terms of projects, while at some time in the future the user may wish to generate an organization according to time and/or according to document content. A strict hierarchical structure does not allow management of documents for multiple views in a seamless manner resulting in a decrease in the efficiency of document retrieval.

[0010] Existing file systems also support only a single model for storage and retrieval of documents. This means a document is retrieved in accordance with a structure or concepts given to it by its author. On the other hand, a user—who is not the author—may wish to retrieve a document in accordance with a concept or grouping different from how the document was stored.

[0011] Further, since document management takes place on a device having computational power, there would be benefits to harnessing the computational power to assist in the organization of the documents. For example, by attaching a spell-checker property to a document, it can extend the read operation of a document so that the content returned to the requesting application will be correctly spelled.

[0012] The inventors are aware that others have studied the area of document management/storage systems.

[0013] DMA is a proposed standard from AIIM designed to allow document management systems from different vendors to interoperate. The DMA standard covers both client and server interfaces and supports useful functionality including collections, versioning, renditions, and multiple-repository search. A look at the APIs show that DMA objects (documents) can have properties attached to them. The properties are strongly typed in DMA and must be chosen from a limited set (string, int, date . . . ). To allow for rich kinds of properties, one of the allowable property types is another DMA object. A list type is allowed to build up big properties. Properties have a unique IDs in DMA. Among the differences which exist to the present invention, is the properties are attached to documents without differentiation about which user would like to see them; properties are stored in the document repository that provides the DMA interface, not independently from it. Similarly, DMA does not provide support for active properties.

[0014] WebDAV is another interface designed to allow an extended uniform set of functionality to be attached with documents available through a web server. WebDAV is a set of extensions to the HTTP 1.1 protocol that allow Web clients to create and edit documents over the Web. It also defines collections and a mechanism for associating arbitrary properties with resources. WebDav also provides a means for creating typed links between any two documents, regardless of media type where previously, only HTML documents could contain links. Compared to the present invention, although WebDAV provides support for collections, these are defined by extension (that is all components have to be explicitly defined); and although it provides arbitrary document properties, these live with the document itself and cannot be independently defined for different users, furthermore there is no support for active properties and are mostly geared toward having ASCII (or XML) values.

[0015] DocuShare is a simple document management system built as a web-server by Xerox Corporation. It supports simple collections of documents, limited sets of properties on documents and support for a few non-traditional document types like calendars and bulletin boards. It is primarily geared toward sharing of documents of small, self-defined groups (for the latter, it has support to dynamically create users and their permissions.) DocuShare has notions of content providers, but these are not exchangeable for a document. Content providers are associated with the type of the document being accessed. In DocuShare properties are static, and the list of properties that can be associated with a document depends on the document type. Users cannot easily extend this list. System administrators must configure the site to extend the list of default properties associated with document types, which is another contrast to the present invention. Also, in DocuShare properties can be visible to anyone who has read access for the collection in which the document is in. Properties are tightly bound to documents and it is generally difficult to maintain a personalized set of properties for a document, again a different approach than the one described in the present invention.

[0016] An operating system “SPIN” from the University of Washington allows users to inject code into the kernel that is invoked when an appropriate system call or system state occurs. (For example, users can inject code that alters paging decisions.) If it has already been done, their technology could be used to make it possible to inject code into the file system to invoke a user's code on read and write. Among the differences between SPIN and the concepts of present invention are that code injected into SPIN runs at the kernel level and users can only express their behaviors in a restricted, safe language in which it is not possible to do “bad things.” As such, expressiveness is limited. On the other hand, the properties in the present invention run at the user level, and can have GUIs call out to third party libraries and in general be far more expressive than a kernel injected spindle. Further, the properties of the present invention are expressed in terms of documents, as in “I attach property X to Document Y.” The SPIN system, on the other hand, extends a system call such as “read”. The example behaviors mentioned above are more easily mapped into a system such as the present invention in which properties are explicitly attached to individual documents.

[0017] Other work which allows operating system calls to be extended into user's code include, the article “Interposition Agents: Transparently Interposing User Code and System Interface,” by Michael B. Jones in Proceedings of the 14th Symposium on Operating Systems, Principles, Asheville, N.C., December, 1993, pages 80-93. The article “SLIC: An Extensibility System for Commodity Operating Systems,” by Douglas P. Ghormley, Steven H. Rodriguez, David Petrou, Thomas E. Anderson, which is to appear in the USENIX 1998 Annual Technical Conference, New Orleans, La., June 1998.

[0018] Further, the Windows NT (from Microsoft) has a function called “Filter Drivers” which, once installed, can see the accesses made to a file system. Installing filter drivers is a privileged operation, not available to normal users. As such, a user level mechanism, such as the document properties of the present invention and event dispatching architecture would be needed to allow users to express their desired behaviors.

[0019] There are also systems which, in a very specific domain, allow users to apply behaviors when documents are accessed. An example is the Tandem e-mail system, which has a “screen cobal” language and has hooks to find out when events occur. This system allows users to code filters to do custom operations when documents arrive and/or read. One of the differences between this system and the present invention, is that the Tandem system solves the problem in a specific domain and invokes only the user's behaviors when the documents are accessed via the mail application. In the present invention, the behaviors are invoked regardless of the application and regardless of the interface.

[0020] The paper, “Finding and Reminding: File Organization From the Desktop”, D. Barreau and B. Nardi, SIGCHI Bulletin, 27 (3) July, 1995, reviews filing and retrieval practices and discusses the shortcomings of traditional file and retrieval mechanisms. The paper illustrates that most users do not employ elaborate or deep filing systems, but rather show a preference for simple structures and “location-based searches”, exploiting groupings of files (either in folders, or on the computer desktop) to express patterns or relationships between documents and to aid in retrieval.

[0021] In response to the Barreau article, the article, “Find and Reminding Reconsidered”, by S. Fertig, E. Freeman and D. Gelernter, SIGCHI Bulletin, 28(1) January, 1996, defends deep structure and search queries, observing that location-based retrieval is, “nothing more than a user-controlled logical search.” There is, however, one clear feature of location-based searching which adds to a simple logical search-in a location-based system, the documents have been subject to some sort of pre-categorization. Additional structure is then introduced into the space, and this structure is exploited in search and retrieval.

[0022] The article “Information Visualization Using 3D Interactive Animation”, by G. Robertson, S. Card and J. Mackinlay, Communications of the ACM 36 (4) April, 1993, discusses a location-based structure, an interesting feature is that it is exploited perceptually, rather than cognitively. This moves the burden of retrieval effort from the cognitive to the perceptual system. While this approach may be effective, the information that the systems rely on is content-based, and extracting this information to find the structure can be computationally expensive.

[0023] The article “Using a Landscape Metaphor to Represent a Corpus of Documents,” Proc. European Conference on Spatial Information Theory, Elba, September, 1993, by M. Chalmers, describes a landscape metaphor in which relative document positions are derived from content similarity metrics. A system, discussed in “Lifestreams: Organizing your Electronic Life”, AAAI Fall Symposium: AI Applications in Knowledge Navigation on Retrieval (Cambridge, Mass.), E. Freeman and S. Fertig, November, 1995, uses a timeline as the major organizational resource for managing document spaces. Lifestreams is inspired by the problems of a standard single-inheritance file hierarchy, and seeks to use contextual information to guide document retrieval. However, Lifestreams replaces one superordinate aspect of the document (its location in the hierarchy) with another (its location in the timeline).

[0024] The article “Semantic File Systems” by Gifford et al., Proc. Thirteenth ACM Symposium of Operating Systems Principals (Pacific Grove, Calif.) October, 1991, introduces the notion of “virtual directories” that are implemented as dynamic queries on databases of document characteristics. The goal of this work was to integrate an associating search/retrieval mechanism into a conventional (UNIX) file system. In addition, their query engine supports arbitrary “transducers” to generate data tables for different sorts of files. Semantic File System research is largely concerned with direct integration into a file system so that it could extend the richness of command line programming interfaces, and so it introduces no interface features at all other than the file name/query language syntax. In contrast, the present invention is concerned with a more general paradigm based on a distributed, multi-principal property-based system and with how interfaces can be revised and augmented to deal with it; the fact that the present invention can act as a file system is simply in order to support existing file system-based applications, rather than as an end in itself.

[0025] DLITE is the Stanford Digital Libraries Integrated Task Environment, which is a user interface for accessing digital library resources as described in “The Digital Library Integrated Task Environment” Technical Report SIDL-WP-1996-0049, Stanford Digital Libraries Project (Palo Alto, Calif.) 1996, by S. Cousins et al. DLITE explicitly reifies queries and search engines in order to provide users with direct access to dynamic collections. The goal of DLITE, however, is to provide a unified interface to a variety of search engines, rather than to create new models of searching and retrieval. So although queries in DLITE are independent of particular search engines, they are not integrated with collections as a uniform organizational mechanism.

[0026] Multivalent documents define documents as comprising multiple “layers” of distinct but intimately-related content. Small dynamically-loaded program objects, or “behaviors”, activate the content and work in concert with each other and layers of content to support arbitrarily specialized document types. To quote from one of their papers, “A document management infrastructure built around a multivalent perspective can provide an extensible, networked system that supports incremental addition of content, incremental addition of interaction with the user and with other components, reuse of content across behaviors, reuse of behaviors across types of documents, and efficient use of network bandwidth.”

[0027] Multivalent document behaviors (analogs to properties) extend and parse the content layers, each of which is expressed in some format. Behaviors are tasked with understanding the formats and adding functionality to the document based on this understanding. In many ways, the Multivalent document system is an attempt at creating an infrastructure that can deal with the document format problem by incrementally adding layers of “understanding” of various formats. In contrast, the present invention has an explicit goal of exploring and developing a set of properties that are independent of document format. While properties could be developed that could parse and understand content, it is expected that most will be concerned with underlying storage, replication, security, and ownership attributes of the documents. Included among the differences between the present invention and the Multivalent concepts are that, the Multivalent document system focuses on extensibility as a tool for content presentation and new content-based behaviors; the present invention focuses on extensible and incrementally-added properties as a user-visible notion to control document storage and management.

[0028] File systems known as the Andrew File System (AFS), Coda, and Ficus provide a uniform name space for accessing files that may be distributed and replicated across a number of servers. Some distributed file systems support clients that run on a variety of platforms. Some support disconnected file access through caching or replication. For example, Coda provides disconnected access through caching, while Ficus uses replication. Although the immediately described distributed file systems support document (or file) sharing, they have a problem in that a file's hierarchical pathname and its storage location and system behavior are deeply related. The place in the directory hierarchy where a document gets stored generally determines on which servers that file resides.

[0029] Distributed databases such as Oracle, SQL Server, Bayou, and Lotus Notes also support shared, uniform access to data and often provide replication. Like some distributed file systems, many of today's commercial databases provide support for disconnected operation and automatic conflict resolution. They also provide much better query facilities than file systems. However, distributed databases suffer the same problems as file systems in that the properties of the data, such as where it is replicated and how it is indexed and so on, are generally associated with the tables in which that data resides. Thus, these properties cannot be flexibly managed and updated. Also, the set of possible properties is not extensible.

[0030] A digital library system, known as the Documentum DocPage repository, creates a document space called a “DocBase.” This repository stores a document as an object that encapsulates the document's content along with its attributes, including relationships, associated versions, renditions, formats, workflow characteristics, and security. These document objects can be infinitely combined and re-combined on demand to form dynamic configurations of document objects that can come from any source.

[0031] DocPage supports organization of documents via folder and cabinet metaphors, and allows searching over both document content and attributes. The system also provides checkin/checkout-style version control, full version histories of documents, and annotations (each with its own attributes and security rules). The system also supports workflow-style features including notification of updates. DocBase uses a replicated infrastructure for document storage (see: http://www.documentum.com).

[0032] Among the differences between Documentum DocPage and the present invention are: First, in the present system properties are exposed as a fundamental concept in the infrastructure. Further, the present system provides for a radically extensible document property infrastructure capable of supporting an aftermarket in document attributes. Documentum seems to be rather closed in comparison; the possible attributes a document can acquire are defined a priori by the system and cannot be easily extended. Additionally, Documentum does not have the vision of universal access to the degree of the present invention which supports near-universal access to document meta-data, if not document content. In comparison, the scope of Documentum narrows to document access within a closed setting (a corporate intranet).

[0033] Documents are generally inert units of data unless an appropriate application is running which manipulates the document. When an application is not running, a user can find out a document's size, last modified date and author, but beyond these types of factual properties, the user must execute the application and open the document in order to find out more about the document.

[0034] Documents may have a wide variety of states and behaviors which are controlled only through a document application such as a word processor. For example, a document may include a link to an external file containing a chart. In prior art systems, the external chart file could be deleted without causing an error or warning until the document application opens the document. Only at that time would it be realized that the external chart file was gone. It would be better if the user was warned of the implications of deleting the chart at deletion time.

[0035] The present invention contemplates a new and improved method and system for managing document states and behaviors while the document application is not running and which overcomes the above-referenced problems and others.

SUMMARY OF THE INVENTION

[0036] A document management system and method is provided which allows a document application to manage a document while the document application is not running. The application attaches an active property to the document. The active property includes executable code which performs a document management function for the document in accordance with the application. In response to a triggering event, the executable code of the active property is invoked to perform the document management function for the document.

[0037] In accordance with another aspect of the present invention, a method of managing a document having a state and a behavior is provided. A document application maintains at least one management function for controlling the state and behavior of the document in accordance with the document application. The document application attaches a management function to the document which includes executable code for controlling the state and behavior of the document. A triggering event is assigned to the management function such that in response to the triggering event, the executable code of the management function is executed. In response to the triggering event, the management function is activated to control the state and behavior of the document even when the document application is closed.

[0038] One advantage of the present invention is that the state and behavior of a document are accessible to a user even when the document application is not running.

[0039] Another advantage of the present invention is that the document application can control the state and behavior of a document when the application is not running by attaching an invocable property to the document which manages the document.

[0040] Still further advantages of the present invention will become apparent to those of ordinary skill in the art upon reading and understanding the following detailed description of the preferred embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The following is a brief description of each drawing used to describe the present invention, and thus, are being presented for illustrative purposes only and should not be limitative of the scope of the present invention, wherein:

[0042]
FIG. 1 shows a hierarchical storage mechanism compared to the concept of properties of the present invention;

[0043]
FIG. 2 is a block diagram of a document management system according to the present invention, interposed within a communication channel between a user and an operating system;

[0044]
FIG. 3 is a representation of a document management system of the present invention implemented in a computer system;

[0045]
FIG. 4 illustrates a system by which applications can attach a property for managing a document in accordance with the present invention; and

[0046]
FIG. 5 illustrates document management in response to a triggering event in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0047] Prior to discussing the present invention in greater detail, it is believed a glossary of terms used in the description would be beneficial. Therefore, the following definitions are set forth:

[0048] Action: The behavior part of a property.

[0049] Active Property: A property in which code allows the use of computational power to either alter the document or effect another change within the document management system.

[0050] Arbitrary: Ability to provide any property onto a document.

[0051] Base Document: Corresponds to the essential bits of a document. There is only one Base Document per document. It is responsible for determining a document's content and may contain properties of the document, and it is part of every principal's view of the document.

[0052] Base Properties: Inherent document properties that are associated with a Base Document.

[0053] Bit Provider: A special property of the base document. It provides the content for the document by offering read and write operations. It can also offer additional operations such as fetching various versions of the document, or the encrypted version of the content.

[0054] Browser: A user interface which allows a user to locate and organize documents.

[0055] Collection: A type of document that contains other documents as its content.

[0056] Combined Document: A document which includes members of a collection and content.

[0057] Content: This is the core information contained within a document, such as the words in a letter, or the body of an e-mail message.

[0058] Content Document: A document which has content.

[0059] Distributed: Capability of the system to control storage of documents in different systems (i.e., file systems, www, e-mail servers, etc.) in a manner invisible to a user. The system allows for documents located in multi-repositories to be provided to a principal without requiring the principal to have knowledge as to where any of the document's content is stored.

[0060] DMS: Document Management System

[0061] Document: This refers to a particular content and to any properties attached to the content. The content referred to may be a direct referral or an indirect referral. The smallest element of the DMS. There are four types of documents; Collection, Content Document, No-Content Document and Combined Document.

[0062] Document Handle: Corresponds to a particular view on a document, either the universal view, or that of one principal.

[0063] DocumentID: A unique identifier for each Base Document. A Reference Document inherits the DocumentID from its referent. Document identity is thus established via the connections between Reference Document References and Base Documents. Logically, a single document is a Base Document and any Reference Documents that refer to it.

[0064] Kernel: Manages all operations on a document. A principal may have more than one kernel.

[0065] Multi-Principal: Ability for multiple principals to have their own set of properties on a Base Document wherein the properties of each principal may be different.

[0066] Notification: Allows properties and external devices to find out about operations and events that occur elsewhere in DMS.

[0067] No Content Document: A document which contains only properties.

[0068] Off-the-Shelf Applications: Existing applications that use protocols and document storage mechanisms provided by currently existing operating systems.

[0069] Principal: A “User” of the document management system. Each person or thing that uses the document management system is a principal. A group of people can also be a principal. Principals are central because each property on a document can be associated with a principal. This allows different principals to have different perspectives on the same document.

[0070] Property: Some bit of information or behavior that can be attached to content. Adding properties to content does not change the content's identity. Properties are tags that can be placed on documents, each property has a name and a value (and optionally a set of methods that can be invoked).

[0071] Property Generator: Special case application to extract properties from the content of a document.

[0072] Reference Document: Corresponds to one principal's view of a document. It contains a reference to a Base Document (Reference Document A refers to Base Document B) and generally also contains additional properties. Properties added by a Reference Document belong only to that reference; for another principal to see these properties, it must explicitly request them. Thus, the view seen by a principal through his Reference Document is the document's content (through the Base Document), and a set of properties (both in the reference and on the Base Document). Even an owner of a Base Document can also have a Reference Document to that base, in which he places personal properties of the document that should not be considered an essential part of the document and placed in all other principal's view.

[0073] Space: The set of documents (base or references) owned by a principal.

[0074] Static Property: A name-value pair associated with the document. Unlike active properties, static properties have no behavior. Provides searchable meta-data information about a document.

[0075] Introduction

[0076] As discussed in the background of the invention, the structure that file systems provide for managing files becomes the structure by which users organize and interact with documents. However, documents and files are not the same thing. The present invention has as an immediate goal to separate management of properties related to the document or concerning the document from the management of the document content. Therefore, user-specific document properties are managed close to the document consumer or user of the document rather than where the document is stored. Separation of the management of user properties from the document content itself provides the ability to move control of document management from a closed file system concept to a user-based methodology.

[0077]
FIG. 1 illustrates a distinction between hierarchical storage systems whose documents are organized in accordance with their location described by a hierarchical structure and the present invention where documents are organized according to their properties (e.g. author=dourish, type=paper, status=draft, etc.). This means documents will retain properties even when moved from one location to another, and that property assignment can have a fine granularity.

[0078] To integrate properties within the document management system of the present invention, the properties need to be presented within the content and/or property read/write path of a computer system, with the ability to both change the results of an operation as well as take other actions. The outline of the concept is described in FIG. 2, where once user (U) issues an operation request (O), prior to that operation being performed by operating system (OS), a call is made to document management system (DMS) A of the present invention, which allows DMS A to function so as to achieve the intended concepts of the present invention. This includes having DMS A interact with operating system (OS), through its own operation request (O′). Once operation request (O′) is completed, the results are returned (R) to DMS A which in turn presents results (R′) to user (U).

[0079] With these basic concepts having been presented, a more detailed discussion of the invention is set forth below.

[0080] Document Management System (DMS) Architecture

[0081]
FIG. 3 sets forth the architecture of a document management system (DMS) A of the present invention in greater detail.

[0082] Document management system (DMS) A is shown configured for operation with front-end components B, and back-end components C. Front-end components B include applications 10a-10n and 11a-11n, such as word processing applications, mail applications among others. Some of the applications are considered DMS aware 10a-10n which means these applications understand DMS protocols for storing, retrieving and otherwise interacting with DMS A. Other components are considered non-DMS aware 11a-11n. Browsers 12a (DMS aware) and 12b (non-DMS aware) are considered specialized forms of applications. In order for the non-DMS-aware applications 11a-11n and 12b to be able to communicate with DMS A, front-end translator 13 is provided.

[0083] Similarly, back-end components C can include a plurality of repositories 14a-14n, where the content of documents are stored. Such repositories can include the hard disc of a principal's computer, a file system server, a web page, a dynamic real time data transmission source, as well as other data repositories. To retrieve data content from repositories 14a-14n, bit providers, such as bit provider 16, are used. These bit providers are provided with the capability to translate appropriate storage protocols.

[0084] Principals 1-n each have their own kernel 18a-18n for managing documents, such as documents 20a-20n. Documents 20a-20n are considered to be documents the corresponding principal 1-n has brought into its document management space. Particularly, they are documents that a principal considers to be of value and therefore has in some manner marked as a document of the principal. The document, for example, may be a document which the principal created, it may be an e-mail sent or received by the principal, a web page found by the principal, a real-time data input such as an electronic camera forwarding a continuous stream of images, or any other form of electronic data (including video, audio, text, etc.) brought into the DMS document space. Each of the documents 20a-20n have static properties 22 and/or active properties 24 placed thereon.

[0085] Document 20a, is considered to be a base document and is referenced by reference documents 20b-20c. As will be discussed in greater detail below, in addition to base document 20a having static properties 22 and/or active properties 24, base document 20a will also carry base properties 26 which can be static properties 22 and/or active properties 24. Static properties are shown with a “-” and active properties are shown with a “-o”.

[0086] Reference documents 20b-20c are configured to interact with base document 20a. Both base documents and reference documents can also hold static properties 22 and/or active properties 24. When principals 2,3 access base document 20a for the first time, corresponding reference documents 20b-20c are created under kernels 18b-18c, respectively. Reference documents 20b-20c store links 28 and 30 to unambiguously identify their base document 20a. In particular, in the present invention each base document is stored with a document ID which is a unique identifier for that document. When reference documents 20b-20c are created, they generate links to the specific document ID of their base document. Alternatively, if principal n references reference document 20c, reference document 20n is created with a link 32 to reference document 20b of Principal 3. By this link principal n will be able to view (i.e. its document handle) the public properties principal 3 has attached to its reference document 20c as well as the base properties and public reference properties of base document 20a. This illustrates the concept of chaining.

[0087] The above described architecture allows for sharing and transmission of documents between principals and provides the flexibility needed for organizing documents. With continuing attention to FIG. 3, it is to be noted at this point that while links 28-30 are shown from one document to another, communication within DMS A is normally achieved by communication between kernels 18a-18n. Therefore, when DMS A communicates with either front-end components B, back-end components C, or communication occurs between principals within DMS A, this communication occurs through kernels 18a-18n. It is however, appreciated the invention will work with other communication configurations as well.

[0088] Using the described architecture, DMS A of the present invention does not require the principal to operate within a strict hierarchy such as in file or folder-type environments. Rather, properties 22,24 which are attached to documents allows a principal to search and organize documents in accordance with how the principal finds it most useful.

[0089] For instance, if principal 1 (owner of kernel 18a) creates a base document with content, and stores it within DMS A, and principal 2 (owner of kernel 18b) wishes to use that document and organize it in accordance with its own needs, principal 2 can place properties on Reference Document 20b. By placement of these properties, principal 2 can retrieve the base document in a manner different than that envisioned by principal 1.

[0090] Further, by interacting with browser 12, a principal may run a query requesting all documents having a selected property. Specifically, a user may run query language requests over existing properties.

[0091] Therefore, a point of the present invention is that DMS A manages a document space where properties are attached by different principals such that actions occur which are appropriate for a particular principal, and are not necessarily equivalent to the organizational structure of the original author of a document or even to other principals.

[0092] Another noted aspect of the present invention is that since the use of properties separates a document's inherent identity from its properties, from a principal's perspective, instead of requiring a document to reside on a single machine, documents in essence can reside on multiple machines (base document 20a can reside on all or any one of kernels 18a-18n). Further, since properties associated with a document follow the document created by a principal (for example, properties on document 20b of kernel 18b, may reference base document 20a), properties of document 20b will run on kernel 18b, even though the properties of document 20b are logically associated with base document 20a. Therefore, if a property associated with document 20b (which references base document 20a) incurs any costs due to its operation, those costs are borne by kernel 18b (i.e. principal 2), since properties are maintained with the principal who put the properties onto a document.

[0093] Support for Native Applications

[0094] A DMS document interface provides access to documents as Java objects. Applications can make use of this interface by importing the relevant package in their Java code, and coding to the API provided for accessing documents, collections and properties. This is the standard means to build new DMS-aware applications and to experiment with new interaction models. DMS Browser 12 (of FIG. 3) can be regarded as a DMS application and is built at this level. the DMS document interface provides Document and Property classes, with specialized subclasses supporting all the functionality described here (such as collections, access to WWW documents, etc.). Applications can provide a direct view of DMS documents, perhaps with a content-specific visualization, or can provide a wholly different interface, using DMS as a property-based document service back-end.

[0095] Support for Off-the-Shelf Applications

[0096] Another level of access is through translators (such as translator 13 of FIG. 3). In an existing embodiment, a server implementing the NFS protocol is used as the translator. This is a native NFS server implementation in pure Java. The translator (or DMS NFS server) provides access to the DMS document space to any NFS client; the server is used to allow existing off-the-shelf applications such as Microsoft Word to make use of DMS documents; on PC's, DMS simply looks like another disk to these applications, while on UNIX machines, DMS A looks like part of the standard network filesystem.

[0097] Critically, though, what is achieved through this translator is that DMS A is directly in the content and property read/write path for existing or off-the-shelf applications. The alternative approach would be to attempt to post-process files written to a traditional filesystem by applications, such as Word, that could not be changed to accommodate DMS A. By instead providing a filesystem interface directly to these applications, it makes it possible to execute relevant properties on the content and property read/write path. Furthermore, it is ensured that relevant properties (such as ones which record when the document was last used or modified) are kept up-to-date. Even though the application is written to use filesystem information, the DMS database remains up to date, because DMS A is the filesystem.

[0098] As part of its interface to the DMS database layer, NFS provides access to the query mechanism. Appropriately formatted directory names are interpreted as queries, which appear to “contain” the documents returned by the query. Although DMS provides this NFS service, DMS is not a storage layer. Documents actually live in other repositories. However, using the NFS layer provides uniform access to a variety of other repositories (so that documents available over the Web appear in the same space as documents in a networked file system). The combination of this uniformity along with the ability to update document properties by being in the read and write path makes the NFS service a valuable component for the desired level of integration with familiar applications. It is to be appreciated that while a server implementing NFS protocol is discussed other servers could also be used.

[0099] Property Attachment

[0100]
FIG. 4 shows an overall system for attaching properties to a selected document. For exemplary purposes, two documents 110 and 112 are shown and an application 115 which processes the documents. The document management system A locates and retrieves documents in accordance with a management system protocol. In the Preferred Embodiment, documents are managed based on their properties rather than hierarchial path and file names.

[0101] A property attachment mechanism 125 is provided by the document management system A which generates, configures and attaches properties in a document reference 130 to the document 110 represented by association links 135. In the preferred embodiment, the document 110 is identified by a unique ID and the document reference 130 refers to the document using the same unique ID. Properties 150 include static properties (represented by horizontal lines) and active properties (represented by circles). Static properties are simple name-value pairs on documents which are relevant to a user and can be used to expose application state, for example, “from=Joe” or “subject=patent application.” An active property 140 has a name-value and includes executable program code and/or instructions for automatically performing an operation or service without a user's involvement, and can be used to extend application behavior. Documents can be collected, searched and retrieved based on static properties and/or active properties. Properties are separately maintained per user per document.

[0102] The active property 140 is configured to be activated by a triggering event which is defined by the user. The triggering event can be any assigned operation or event which is initiated by any function or a timer in the system. For example, the triggering event can be initiated by an application, by the system, by another document, by another active property, by a timer or any mechanism desired by a user. Attaching the active property 140 to the document 110 forms an association between the property and the document. The association is external to the data that represents the content of the document 110. Thus, the association is independent of content type, the application format used to generate the document, and other characteristics of the document 110.

[0103] The content of document 110 is controlled by a bit provider 160 which identifies the location of the data (e.g. local disk, world wide web, a camera or any data supplying source). In this case, the content is an image file 170. The bit provider 160 indicates how the data from the sources are combined to form the content of the document 110, includes a translation interface to communicate to the data source, and other selected parameters which define the content. Document 112 includes a bit provider 162 which interfaces to a local disk forming the content of document 112 as text 165.

[0104] With further reference to FIG. 4, the application 115 includes one or more functions 180 which are designed to be active properties attachable to a document. The functions 180 are executable programs or routines which perform management functions for a document to which they are attached when the application 115 is not running. In other words, application 115 attaches a management function 185 as an active property for document 110 which is selected from the set of functions 180. In this manner, application 115 has the ability to control the state and/or behavior of document 110 even when application 115 is not processing document 110.

[0105] Management function 185 is attached as active property 140. As mentioned above, upon the occurrence of a triggering event, active property 140 executes the code of the management function 185. Note that these management properties are not limited to the document handled by the application but can be attached to any other document that is relevant.

[0106] Extending Application Behavior

[0107] With reference to FIG. 5, for exemplary purposes, suppose application 115 creates a relationship between document 110 and document 112 in that the text 165 imports the image 170 into its body. Since application 115 generated document 112 and created a relationship to the image 170, this relationship state and behavior is passed to management function 185 in order to manage the relationship even when application 115 is not running. Upon the occurrence of the assigned triggering event, such as operation or event 200, active property 140 initiates the management function 185. In this case, when application 115 is not running, the document management system A monitors the system in order to detect the operation/event 200. Once it is detected, the document management system A compares the event 200 to the active properties attached to document 110 to determine if the event 200 is a triggering event. In this case, event 200 is a triggering event for active property 140 and the management function 185 is executed. Management function 185 provides instructions to the document management system A which controls the manner that operation/event 200 is applied to document 110 or, controls a sequence of instructions which are executed in response to the triggering event. In other words, operation/event 200 is not simply applied to document 110, but rather is applied in accordance with document management rules of management function 185 which ensure that document 110 is processed according to the wishes of application 115 and the needs it has for document 112.

[0108] For example, suppose operation/event 200 is a delete operation performed by a user and that management function 185 is triggered in response to a delete operation applied to document 110. The user, while browsing files through the document management system A, locates image document 110 and initiates a delete operation unaware that image 170 forms a part of document 112. The document management system A detects the delete operation and before applying the operation, determines whether the delete operation is a triggering event for an active property attached to document 110. In this case, the delete operation 200 is a triggering event and management function 185 is activated.

[0109] Once triggered, management function 185 executes and becomes involved in applying the delete operation 200 to document 110 in accordance with a predefined set of instructions. For example, a warning may be given to the user that they are deleting a file which is part of another document; the delete operation may be prohibited; or document 110 may be copied for document 112, while the original file is deleted. One of ordinary skill in the art will appreciate that the management function 185 can be programmed to provide any management functions which control a document in response to a triggering event when the generating application is not running. Of course, if desired, the management functions can be programmed to execute even when the application is running.

[0110] By way of another example, suppose that the text 165 of document 112 is intended to be the OCRed (object character recognition) version of the contents of image document 110. Management function 185 is attached to document 110 and is configured to be triggered by an editing operation. In response to an editing operation, management function 185 ensures the correct state of document 112 by updating the contents of the text 165 based on changes made to image 170. Of course, if application 115 were running, this management could be performed by the application 115. However, since the application is not running, the management function 185 is configured to take the place of specific functionality for the application 115. Therefore, upon the occurrence of an editing operation 200, management function 185 activates to control the editing. Conversely, if the editing operation were applied to image document 110 without the existence of management function 185, the contents of image 170 would be modified without the user ever knowing that the operation could be creating errors in the dependency relationship to text 165. As mentioned above, the management function 185 can be programmed to perform any function which controls the state and/or behavior of a document in response to a selected event.

[0111] With the present invention, an application is provided with a mechanism to insert a piece of itself into a document and any number of dependent documents, which can have a variety of relationships to each other, to manage the document and its needs when the application is not present. In this manner, the state and behavior of a document is accessible by a user without having to run the application. Furthermore, the state and behavior of the document can be accurately maintained and changed in accordance with pre-defined rules made by the application which are attached to a document as active properties.

[0112] The invention has been described with reference to the preferred embodiment. Obviously, modifications and alterations will occur to others upon a reading and understanding of this specification. It is intended to include all such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof

EXTENDING APPLICATION BEHAVIOR THROUGH ACTIVE PROPERTIES ATTACHED TO A DOCUMENT IN A DOCUMENT MANAGEMENT SYSTEM

Information

Publication Number

Date Filed

Date Published

Inventors

CPC

US Classifications

International Classifications

Abstract

Description

Claims