Extending a content repository using an auxiliary data store

• US 9,613,041 B2
• Filed: 10/03/2013
• Issued: 04/04/2017
• Est. Priority Date: 10/03/2013
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Desai, Rajesh M., Jayapandian, Magesh, Jennery, Aidon P., Perez, Justo L.
• Primary Examiner(s): Kim, Taelor
• Application Number:
  US14/045,089
• Publication Number:
  US 20150100549A1
• Time in Patent Office: 1,279 Days
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• 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 16/93 Document management systems

Abstract

According to one embodiment of the present invention, a system extends a content repository by creating an auxiliary data store outside of the content repository and storing auxiliary data in the auxiliary data store, wherein the auxiliary data is associated with a collection of documents in the content repository. The system stores version information for the auxiliary data store and records of operations against the auxiliary data store in a log in the repository. In response to receiving a request for an operation against the auxiliary data store, the system determines that the auxiliary data store and repository are consistent based on the version information and applies the operation against the auxiliary data store. Embodiments of the present invention further include a method and computer program product for extending a content repository data model in substantially the same manners described above.

Claims

1. A system for extending a content repository comprising:

at least one processor configured to;

create an auxiliary data store outside of a content repository, wherein the content repository includes a data model for defining attributes to be stored for data objects in the content repository, and wherein the attributes for data objects stored in the content repository are only those attributes defined by the data model;

extend the data model of the content repository by storing, in the auxiliary data store, auxiliary data for data objects in the content repository, wherein the auxiliary data includes one or more attributes for the data objects of the content repository that are not defined by the data model;

store version information for the auxiliary data store in the auxiliary data store and content repository; and

in response to receiving a request for an operation against the auxiliary data store;

determine consistency between the auxiliary data store and content repository by comparing the version information in the auxiliary data store against the version information in the content repository;

apply the operation against the auxiliary data store and store a record of the operation including an object identifier and operands in a log in the content repository in response to the version information in the content repository and auxiliary data store indicating a same version, wherein the object identifier comprises an identifier of a collection of data objects in the content repository; and

reconstruct the auxiliary data store in entirety based on records of operations against the auxiliary data store in the log in response to the version information in the auxiliary data store and the content repository indicating a different version.

2. The system of claim 1, wherein the records of operations against the auxiliary data store are appended to the log in the content repository and are immutable.

3. The system of claim 1, wherein the at least one processor includes a framework that mediates interaction between the auxiliary data store and content repository, and the storing the record of the operation comprises storing, via the framework, auxiliary data objects in serialized form.

4. The system of claim 3, wherein the at least one processor is further configured to:

delete from the auxiliary data store the auxiliary data corresponding to a collection of data objects in the content repository; and

delete, via the framework, records of operations in the log in the content repository comprising an identifier of the collection of data objects.

5. The system of claim 4, wherein the framework mediates interaction between a plurality of auxiliary data stores and the content repository, and the framework stores version information for each of the plurality of auxiliary data stores in the log.

6. A computer program product for extending a content repository comprising:

a non-transitory computer program storage medium having computer readable program code embodied therewith for execution on a processing system, the computer readable program code comprising computer readable program code configured to;

create an auxiliary data store outside of a content repository, wherein the content repository includes a data model for defining attributes to be stored for data objects in the content repository, and wherein the attributes for data objects stored in the content repository are only those attributes defined by the data model;

extend the data model of the content repository by storing, in the auxiliary data store, auxiliary data for data objects in the content repository, wherein the auxiliary data includes one or more attributes for the data objects of the content repository that are not defined by the data model;

store version information for the auxiliary data store in the auxiliary data store and content repository; and

in response to receiving a request for an operation against the auxiliary data store;

determine consistency between the auxiliary data store and content repository by comparing the version information in the auxiliary data store against the version information in the content repository;

apply the operation against the auxiliary data store and store a record of the operation including an object identifier and operands in a log in the content repository in response to the version information in the content repository and auxiliary data store indicating a same version, wherein the object identifier comprises an identifier of a collection of data objects in the content repository; and

reconstruct the auxiliary data store in entirety based on records of operations against the auxiliary data store in the log in response to the version information in the auxiliary data store and the content repository indicating a different version.

7. The computer program product of claim 6, wherein the records of operations against the auxiliary data store are appended to the log in the content repository and are immutable.

8. The computer program product of claim 6, wherein the computer readable program code comprises a framework that mediates interaction between the auxiliary data store and content repository, and the records of operations against the auxiliary data store are stored, via the framework, as auxiliary data objects in serialized form.

9. The computer program product of claim 8, wherein the computer readable program code is further configured to:

delete from the auxiliary data store the auxiliary data corresponding to a collection of data objects in the content repository; and

delete, via the framework, records of operations in the log in the content repository comprising an identifier of the collection of data objects.

10. The computer program product of claim 9, wherein the framework mediates interaction between a plurality of auxiliary data stores and the content repository, and the framework stores version information for each of the plurality of auxiliary data stores in the log.