Automated method for detecting and repairing configuration conflicts in a content management system

• US 8,417,676 B2
• Filed: 11/06/2007
• Issued: 04/09/2013
• Est. Priority Date: 11/06/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Petri, John Edward
• Primary Examiner(s): Rostami, Mohammad S
• Application Number:
  US11/935,825
• Publication Number:
  US 20090119325A1
• Time in Patent Office: 1,981 Days
• Field of Search: None
• US Class Current: 707/694
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/81 Indexing, e.g. XML tags; Data structures therefor; Storage structures

Abstract

Embodiments of the invention provide for detecting and (in at least some cases) repairing XML configuration conflicts in a content management system (CMS). One method allows a CMS to evaluate various configuration components and determine when those components may conflict with one another. If a conflict is detected, the CMS may be configured to notify an administrator of the problem, and in some cases, correct the problem. As a result, administrators may not have to carefully evaluate each configuration file associated with a document type definition for a given document type before creating or modifying a content processing rule.

Claims

1. A method for detecting configuration conflicts between configuration files in a content management system (CMS), comprising:

storing a configuration set associated with one or more documents managed by the CMS, wherein each document of the one or more documents has a corresponding document type;

receiving a content processing rule to be applied to one or more documents, wherein the content processing rule defines an operation to be performed by the CMS whenever a document of a document type specified by the content processing rule is checked-in to or checked-out from the CMS, and wherein the operation to be performed by the CMS includes, at least in part, modifying at least one document attribute in the one or more documents;

determining that the at least one document attribute referenced by the content processing rule is a member of a repeating attribute group specified by a document type configuration associated with the document type specified in the content processing rule, wherein the repeating attribute group specifies a plurality of document attributes that should occur with the same number of values in instances of the document type;

upon determining that, when applied to a first instance of the document type, the content processing rule could modify the first instance of the document type to include a differing number of values for the plurality of document attributes specified in the repeating attribute group, notifying a system administrator;

generating an external schema validation rule configured to ensure that a number of occurrences of the plurality of document attributes in the first instance of the document type matches the number of occurrences of the plurality of document attributes in the modified first instance of the document type; and

accepting the received content processing rule, whereby the operation defined by the content processing rule will be performed by the CMS whenever documents of the document type associated with the content processing rule are checked-in to or checked-out of the CMS.

2. The method of claim 1, wherein the configuration set includes a collection of XML artifacts, including at least one of an XML schema, document type definition (DTD), XML stylesheet, and XSLT transform.

3. The method of claim 1, wherein the content processing rule is a synchronization rule specifying metadata maintained by the CMS to synchronize with metadata contained in documents of the document type whenever documents of the document type are checked-in to or checked-out from the CMS.

4. The method of claim 3, wherein the metadata contained in documents of the document type comprises an XML attribute.

5. The method of claim 1, wherein the external schema validation rule is an XML schema constraint.

6. A computer-readable storage device containing a program which, when executed, performs an operation for detecting configuration conflicts between configuration files in a content management system (CMS), the operation comprising:

storing a configuration set associated with one or more documents managed by the CMS, wherein each document of the one or more documents has a corresponding document type;

receiving a content processing rule to be applied to one or more documents, wherein the content processing rule defines an operation to be performed by the CMS whenever a document of a document type specified by the content processing rule is checked-in to or checked-out from the CMS, and wherein the operation to be performed by the CMS includes, at least in part, modifying at least one document attribute in the one or more documents;

determining that the at least one document attribute referenced by the content processing rule is a member of a repeating attribute group specified by a document type configuration associated with the document type specified in the content processing rule, wherein the repeating attribute group specifies a plurality of document attributes that should occur with the same number of values in instances of the document type;

upon determining that, when applied to a first instance of the document type, the content processing rule could modify the first instance of the document type to include a differing number of values for the plurality of document attributes specified in the repeating attribute group, notifying a system administrator;

generating an external schema validation rule configured to ensure that a number of occurrences of the plurality of document attributes in the first instance of the document type matches the number of occurrences of the plurality of document attributes in the modified first instance of the document type; and

accepting the received content processing rule, whereby the operation defined by the content processing rule will be performed by the CMS whenever documents of the document type associated with the content processing rule are checked-in to or checked-out of the CMS.

7. The computer-readable storage device of claim 6, wherein the configuration set includes a collection of XML artifacts, including at least one of an XML schema, document type definition (DTD), XML stylesheet, and XSLT transform.

8. The computer-readable storage device of claim 6, wherein the content processing rule is a synchronization rule specifying metadata maintained by the CMS to synchronize with metadata contained in documents of the document type whenever documents of the document type are checked-in to or checked-out from the CMS.

9. The computer-readable storage device of claim 8, wherein the metadata contained in documents of the document type comprises an XML attribute.

10. The computer-readable storage device of claim 6, wherein the external schema validation rule is an XML schema constraint.

11. A system, comprising:

a processor; and

a memory containing a content management system (CMS) program configured to detect configuration conflicts between configuration files in the CMS by performing the steps of;

storing a configuration set associated with one or more documents managed by the CMS, wherein each document of the one or more documents has a corresponding document type;

receiving a content processing rule to be applied to one or more documents, wherein the content processing rule defines an operation to be performed by the CMS whenever a document of a document type specified by the content processing rule is checked-in to or checked-out from the CMS, and wherein the operation to be performed by the CMS includes, at least in part, modifying at least one document attribute in the one or more documents;

determining that the at least one document attribute referenced by the content processing rule is a member of a repeating attribute group specified by a document type configuration associated with the document type specified in the content processing rule, wherein the repeating attribute group specifies a plurality of document attributes that should occur with the same number of values in instances of the document type;

upon determining that, when applied to a first instance of the document type, the content processing rule could modify the first instance of the document type to include a differing number of values for the plurality of document attributes specified in the repeating attribute group, notifying a system administrator;

generating an external schema validation rule configured to ensure that a number of occurrences of the plurality of document attributes in the first instance of the document type matches the number of occurrences of the plurality of document attributes in the modified first instance of the document type; and

accepting the received content processing rule, whereby the operation defined by the content processing rule will be performed by the CMS whenever documents of the document type associated with the content processing rule are checked-in to or checked-out of the CMS.

12. The system of claim 11, wherein the configuration set includes a collection of XML artifacts, including at least one of an XML schema, document type definition (DTD), XML stylesheet, and XSLT transform.

13. The system of claim 11, wherein the content processing rule is a synchronization rule specifying metadata maintained by the CMS to synchronize with metadata contained in documents of the document type whenever documents of the document type are checked-in to or checked-out from the CMS.

14. The system of claim 13, wherein the metadata contained in documents of the document type comprises an XML attribute.

15. The system of claim 11, wherein the external schema validation rule is an XML schema constraint.