Content management system that retrieves data from an external data source and creates one or more objects in the repository

#1. Technical Field

#This disclosure generally relates to content management systems, and more specifically relates to a content management system that creates an object in its repository from data external to the content management system.

#2. Background Art

#The disclosure will be described in conjunction with the appended drawings, where like designations denote like elements, and:

#FIG. 1 is a block diagram of a networked computer system that includes a server computer system that has a content management system that includes an external data mechanism that stores data from an external source as an object in the repository;

#FIG. 2 is a flow diagram of a prior art method for using data from an external source;

#The claims and disclosure herein provide a content management system (CMS) that creates one or more objects in the repository containing data returned from a query to an external data source according to the type of the data returned by comparing the data returned against classification rules.

#Many known content management systems use extensible markup language (XML) due to its flexibility and power in managing diverse and different types of content. One known content management system that uses XML is Solution for Compliance in a Regulated Environment (SCORE) developed by IBM Corporation. XML is growing in popularity, and is quickly becoming the preferred format for authoring and publishing. While the disclosure herein discusses XML documents as one possible example of content that may be managed by a content management system, the disclosure and claims herein expressly extend to content management systems that do not use XML.

#Referring to FIG. 1, networked computer system 100 includes multiple clients, shown in FIG. 1 as clients 110A, . . . , 110N, coupled to a network 130. Each client preferably includes a CPU, storage, and memory that contains a document editor and a content management system (CMS) plugin. Thus, client 110A includes a CPU 112A, storage 114A, memory 120A, a document editor 122A in the memory 120A that is executed by the CPU 112A, and a CMS plugin 124A that allows the document editor 122A to interact with content 152 in the repository 150 that is managed by the CMS 170 in server 140. In similar fashion, other clients have similar components shown in client 110A, through client 110N, which includes a CPU 112N, storage 114N, memory 120N, a document editor 122N, and a CMS plugin 124N.