AUTO-UPDATABLE DOCUMENT PARTS WITHIN CONTENT MANAGEMENT SYSTEMS

• US 20120284225A1
• Filed: 07/19/2012
• Published: 11/08/2012
• Est. Priority Date: 03/11/2011
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Man, Kwai H., So, Wai K.
• Application Number:
  US13/553,199
• Publication Number:
  US 20120284225A1
• Time in Patent Office: Days
• US Class Current: 707/608
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/93 Document management systems

Abstract

Techniques are described for managing relationships between entities in a content management system. Embodiments of the invention identify a relationship between a first entity and a second entity in the content management system. Embodiments monitor the first entity in the content management system to detect an occurrence of a triggering event specified in one or more management rules. One or more actions specified by the one or more management rules are then performed on the second entity in the content management system, responsive to the detected occurrence of the triggering event.

Claims

1. A method for managing relationships between entities managed by a content management system, comprising:

identifying a relationship between a first entity managed by the content management system and a second entity managed by the content management system;

providing a set of rules for managing the relationship between the first entity and the second entity, wherein each rule specifies at least (i) a triggering event and (ii) one or more actions to be performed responsive to an occurrence of the triggering event;

monitoring the first entity in the content management system to detect an occurrence of the triggering event associated with at least one rule in the set of rules; and

upon detecting the triggering event associated with at least one rule has occurred with respect to the first entity, and by operation of one or more computer processors, performing the corresponding one or more actions specified in the rule against the second entity managed by the content management system.

2. The method of claim 1, wherein at least one of the first entity and the second entity comprises metadata associated with a content object managed by the content management system.

3. The method of claim 1, wherein at least one of the first entity and the second entity comprises one of a document, an image, audio content, and video content.

4. The method of claim 1, wherein performing the corresponding one or more actions specified in the rule against the second entity managed by the content management system further comprises:

identifying content associated with the first entity managed by the content management system that was modified by the triggering event;

applying one or more filters to the identified content associated with the first entity to create transformed content;

modifying the second entity managed by the content management system based on the transformed content.

5. The method of claim 1, wherein at least one of the set of rules is specified using extensible markup language (“

XML”

).

6. The method of claim 1, wherein one of the corresponding one or more actions for at least one of the rules comprises updating at least one of metadata associated with the second entity and second content associated with the second entity, based on modifications to first content associated with the first entity.

7. The method of claim 1, wherein determining a relationship exists between a first entity in the content management system and a second entity in the content management system further comprises receiving a request from a user specifying the relationship between the first entity managed by the content management system and the second entity managed by the content management system.

8. The method of claim 1, wherein determining a relationship exists between a first entity managed by the content management system and a second entity managed by the content management system further comprises:

analyzing the first entity managed by the content management system to determine a first one or more characteristics of the first entity;

analyzing the second entity managed by the content management system to determine a second one or more characteristics of the second entity; and

wherein the relationship between the first entity and the second entity is determined based on the both the first one or more characteristics of the first entity and the second one or more characteristics of the second entity.

9. A method for managing relationships between documents managed by a content management system, comprising:

determining a relationship exists between a first document managed by the content management system and a second document managed by the content management system;

providing a set of rules for managing the relationship between the first document and the second document, wherein each rule specifies at least (i) a triggering event and (ii) one or more actions to be performed responsive to an occurrence of the triggering event;

monitoring the first document in the content management system to detect an occurrence of the triggering event associated with at least one rule in the set of rules, wherein the triggering event associated with the at least one rule comprises at least one of updating content of the first document and updating metadata associated with the first document; and

upon detecting the triggering event associated with at least one rule has occurred with respect to the first document, performing the corresponding one or more actions specified in the rule against the second document managed by the content management system.