Knowledge provider with logical hyperlinks
First Claim
1. An information repository system for managing, storing and retrieving a computer data file comprising:
- a content server for storing said file;
content model means for defining a three-tiered content model which comprises nested tiers including component classes, physical object classes, and relations classes, and wherein a logical object contains a reference to said file and describes said file in generic terms and with reference to at least one attribute, and further wherein said logical object contains a reference to at least one physical object associated with said logical object, and contains a reference to at least one component associated with said at least one physical object, and wherein relations from said relations classes are used to connect logical objects and physical objects with other logical objects or physical objects;
an administration data table which contains administration data associated with physical objects;
logical hyperlink means for resolving, in context-based indirect runtime resolution, the logical object, to a physical destination of the file associated with the at least one physical object associated with the logical object;
context resolution means, enabled by said logical hyperlink means, for context-based resolution of a particular physical object associated with the logical object on the basis of the context attributes of a request as determined by correlating requested context attributes against attributes of physical objects associated with the logical object and attributes of a front-end client application; and
a management agent for managing said logical objects and physical objects using said content model means in conformance with said administration data and for identifying and retrieving the physical object resolved via said logical hyperlink means and said context resolution means.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method is described for the efficient management and storage of documents in a multi-user environment by implementing a three-tiered content model for storage and a context resolution mechanism for retrieval. Source objects may logically reference target objects where the target objects dynamically exist in different versions. In particular, the content model contains three classes in a collection wherein each subsequent class inherits the properties of the previous class. The classes comprise logical objects, physical objects, and components. All physical objects that belong to the same logical object are context specific variants, such as different versions of each other. Physical objects in a collection can be related by different criteria, as well as by user-defined relations. The system provides for versioning of objects, such as variations based on content, format, language, etc., to create variants of objects in the same collection, however variance among physical objects which belong to one logical object is not limited to different versions. Such versioning is controlled through a check-in/-out mechanism to allow use in a multi-user environment. The context resolution mechanism is used to retrieve the most accurate version of an object pursuant to certain user-supplied criteria in response to a call from a client front-end application. The system is linked to various independent front-end editor/browser applications through application programming interfaces. The system also provides for references between various objects in the Knowledge Provider. A dynamic logical hyperlink mechanism is provided to maintain references from source to target objects while a different version of the target object is being created.
284 Citations
30 Claims
-
1. An information repository system for managing, storing and retrieving a computer data file comprising:
-
a content server for storing said file; content model means for defining a three-tiered content model which comprises nested tiers including component classes, physical object classes, and relations classes, and wherein a logical object contains a reference to said file and describes said file in generic terms and with reference to at least one attribute, and further wherein said logical object contains a reference to at least one physical object associated with said logical object, and contains a reference to at least one component associated with said at least one physical object, and wherein relations from said relations classes are used to connect logical objects and physical objects with other logical objects or physical objects; an administration data table which contains administration data associated with physical objects; logical hyperlink means for resolving, in context-based indirect runtime resolution, the logical object, to a physical destination of the file associated with the at least one physical object associated with the logical object; context resolution means, enabled by said logical hyperlink means, for context-based resolution of a particular physical object associated with the logical object on the basis of the context attributes of a request as determined by correlating requested context attributes against attributes of physical objects associated with the logical object and attributes of a front-end client application; and a management agent for managing said logical objects and physical objects using said content model means in conformance with said administration data and for identifying and retrieving the physical object resolved via said logical hyperlink means and said context resolution means. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A method for managing, storing and retrieving a computer data file comprising the steps of:
-
providing said file; defining a three-tiered content model which comprises nested tiers including component classes, physical object classes, and relations classes, and wherein a logical object contains a reference to said file and describes said file in generic terms and with reference to at least one attribute, and further wherein said logical object contains a reference to at least one physical object associated with said logical object, and contains a reference to at least one component associated with said at least one physical object, and wherein relations from said relations classes are used to connect logical objects and physical objects with other logical objects or physical objects; defining administration data associated with physical objects; targeting the logical object with context attributes; resolving, in context-based resolution, a particular physical object associated with the logical object on the basis of the context attributes of a request as determined by correlating requested context attributes against attributes of physical objects associated with the logical object and attributes of a front-end client application; enabling said step of resolving by resolving indirectly in runtime, via context-based indirect runtime resolution, the logical object to a physical destination of the file associated with the at least one physical object associated with the logical object; identifying the particular physical object so resolved by context based resolution; and managing said resolved object using said three-tier content model in conformance with said administration data. - View Dependent Claims (24, 25, 26, 27, 28, 29)
-
-
30. A method for defining and managing a file stored at a physical storage location, which method allows identical filenames for a plurality of files of different physical objects and comprises the steps of:
-
creating at least one physical object which refers to components which represent the file, said components forming a content component record; defining an absolute path in a content repository, said content repository containing at least one content category which provides a logical description of the physical file storage location and refers to the content repository; grouping said plurality of files into said content category; defining a path relative to the absolute path based on said content component record; creating a unique object ID; and defining the location of the file by combining said absolute path, said relative path and said unique object ID.
-
Specification