Content management via configuration set relationships in a content management system

• US 7,954,048 B2
• Filed: 09/21/2006
• Issued: 05/31/2011
• Est. Priority Date: 09/21/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Summer, Gary R., Gauthier, Charles S., Herbeck, David G., Petri, John E.
• Primary Examiner(s): Hong; Stephen S
• Assistant Examiner(s): HASTY, NICHOLAS
• Application Number:
  US11/533,811
• Publication Number:
  US 20080077850A1
• Time in Patent Office: 1,713 Days
• Field of Search: 715/234, 715/229, 715/239, 715/236, 715/255, 707/203, 707/102, 707/999.1, 707/17.006, 707/E17.006, 707/E17.008
• US Class Current: 715/229
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]

Abstract

Method, system, and article of manufacture for a content management system (CMS) to bind a data object (typically, an XML document) to an associated configuration set (or sets) are disclosed. The configuration set may reference a set of configuration files such as XML schemas/DTDs, style sheets, CMS processing rules, and the like. The CMS may store bindings between a data object and a given configuration set in a CMS repository.

Claims

1. A method of managing documents in a content management system (CMS), the method comprising:

receiving a request to create a document of a specified document type;

prompting a user to specify one or more attributes associated with the document;

based on the specified attributes and the specified document type, selecting a configuration set for the document, wherein the configuration set specifies one or more configuration files that include content for managing the document;

determining whether the selected configuration set has a planned obsolescence, and upon determining that the selected configuration set has a planned obsolescence, warning the user of the planned obsolescence;

generating the requested document by;

generating a root document including references to one or more child documents,

selecting a configuration set for each of the one or more child documents, and

binding the root document to the configuration set selected for each of the one or more child documents, wherein the root document remains independent from the one or more child documents; and

binding the document to the selected configuration set.

2. The method of claim 1, wherein selecting a configuration set for the document comprises prompting the user to select from two or more configuration sets.

3. The method of claim 1, wherein binding the document to the selected configuration set comprises generating a repository relation specifying the document and the selected configuration set.

4. The method of claim 1, wherein the method further comprises updating at least one of the configuration files of the selected configuration set with a new version, and wherein the binding between the document and the selected configuration set automatically reflects the new version when the document is subsequently accessed.

5. The method of claim 1, wherein the configuration files include at least one of an XML schema, a document type definition (DTD), an XSL style sheet, an XML catalog, and an XSLT transform.

6. The method of claim 1, wherein the selected configuration set includes one or more processing rules used by the CMS to manage the document.

7. The method of claim 1, further comprising:

transitioning a state of the selected configuration set to an obsolete state;

identifying a document managed by the CMS bound to the selected configuration set; and

notifying an owner of the document managed by the CMS bound to the selected configuration set that the selected configuration set is obsolete.

8. A computer-readable storage medium containing a program which, when executed, performs an operation for managing documents in a content management system (CMS), the operation comprising:

receiving a request to create a document of a specified document type;

prompting a user to specify one or more attributes associated with the document;

based on the specified attributes and the specified document type, selecting a configuration set for the document, wherein the configuration set specifies one or more configuration files that include content for managing the document;

determining whether the selected configuration set has a planned obsolescence, and upon determining that the selected configuration set has a planned obsolescence, warning the user of the planned obsolescence;

generating the requested document by;

generating a root document including references to one or more child documents,

selecting a configuration set for each of the one or more child documents, and

binding the root document to the configuration set selected for each of the one or more child documents, wherein the root document remains independent from the one or more child documents; and

binding the document to the selected configuration set.

9. The computer-readable storage medium of claim 8, wherein selecting a configuration set for the document comprises prompting the user to select from two or more configuration sets.

10. The computer-readable storage medium of claim 8, wherein binding the document to the selected configuration set comprises generating a repository relation specifying the document and the selected configuration set.

11. The computer-readable storage medium of claim 8, wherein the operation further comprises updating at least one of the configuration files of the selected configuration set with a new version, and wherein the binding between the document and the selected configuration set automatically reflects the new version when the document is subsequently accessed.

12. The computer-readable storage medium of claim 8, wherein the configuration files include at least one of an XML schema, a document type definition (DTD), an XSL style sheet, an XML catalog, and an XSLT transform.

13. The computer-readable storage medium of claim 8, wherein the selected configuration set includes one or more processing rules used by the CMS to manage the document.

14. The computer-readable storage medium of claim 8, wherein the operation further comprises:

transitioning a state of the selected configuration set to an obsolete state;

identifying a document managed by the CMS bound to the selected configuration set; and

notifying an owner of the document managed by the CMS bound to the selected configuration set that the selected configuration set is obsolete.

15. A system comprising:

a processor; and

a memory including a content management system (CMS) configured to perform a method for managing documents in a content management system, the method comprising;

receiving a request to create a document of a specified document type;

prompting a user to specify one or more attributes associated with the document;

based on the specified attributes and the specified document type, selecting a configuration set for the document, wherein the configuration set specifies one or more configuration files that include content for managing the document;

determining whether the selected configuration set has a planned obsolescence, and upon determining that the selected configuration set has a planned obsolescence, warning the user of the planned obsolescence;

generating the requested document by;

generating a root document including references to one or more child documents,

selecting a configuration set for each of the one or more child documents, and

binding the root document to the configuration set selected for each of the one or more child documents, wherein the root document remains independent from the one or more child documents; and

binding the document to the selected configuration set.

16. The system of claim 15, wherein binding the document to the selected configuration set comprises generating a repository relation specifying the document and the selected configuration set.

17. The system of claim 15, wherein the method further comprises updating at least one of the configuration files of the selected configuration set with a new version, and wherein the binding between the document and the selected configuration set automatically reflects the new version when the document is subsequently accessed.

18. The system of claim 15, wherein the configuration files include at least one of an XML schema, a document type definition (DTD), an XSL style sheet, an XML catalog, and an XSLT transform.

19. The system of claim 15, wherein the selected configuration set includes one or more processing rules used by the CMS to manage the document.

20. The system of claim 15, wherein the CMS is further configured to:

transition a state of the selected configuration set to an obsolete state;

identify a document managed by the CMS bound to the selected configuration set; and

notify an owner of the document managed by the CMS bound to the selected configuration set that the selected configuration set is obsolete.