1. Field of the Invention
The present invention relates to a method, system, and article of manufacture for promoting content from one content management system to another content management system.
2. Description of the Related Art
A computer user community comprises a network computing environment where users collaborate to add and edit content. For instance, in message forums, one user may pose a technical or other type of question, and other users respond. The content of such message forums can contain fragments of information that may be useful to users of other content management systems. Often users of different content management systems, such as message forums, Wikis, Blogs, and other collaborative systems, etc., may have to separately visit different content management systems to obtain the information they need.
There is a need in the art for improved techniques for managing content from different content management systems.
Provided are a method, system, and program for promoting content from one content management system to another content management system. Content from a first content management system satisfying a content criteria is determined. The first content management system includes content objects added by users in a collaborative environment. A second content management system providing content objects associated with content categories is processed to determine one of the content categories relevant to the determined content from the first content management system. The determined content is added to the second content management system and the content added to the second content management system is associated with the determined content category.
A content server 14 runs a content management system 16 managing content objects 18 having information on various topics or categories of information. A content object 18 may comprise a document (e.g., a word processing document, Hypertext Markup Language (HTML) page, Extended Markup Language (XML) page, etc.), multimedia file (still images, motion picture), database table or data, spreadsheet, etc. The content objects 18 may be organized according to categories of information created in the content management system 4. The content objects 18 may be created and edited by users at user systems 8 in a collaborative environment, such as a Wiki, Blog, or other content management systems 2. The content management system 16 may further include content information 20 providing information on the content objects. A message promoter 22 comprises a program that selects content, e.g., messages, from the message forum 4 to promote to content objects 18 in the content management system 16. For instance, the content of a message thread 6 may be inserted into a content object 18, such as a content page.
In the embodiment of
The message promoter 22 program may process one or more message forums 4 over the network 10, such as the Internet, to locate message threads 6 to promote to the content management system 16. The message promoter 22 may be provided a list of web sites or network addresses of message forums 4 to access or may crawl the network 10 (e.g., the Internet) for message forums 4 having message threads 6 on topics relevant to content in the content management system 16 to determine whether to promote the message threads to the content management system 16.
If (at block 206) the rating of the determined thread satisfies the rating criteria (or the user has selected to promote the message), then the message promoter 22 determines (at block 208) a content category 72 (
Once a category relevant to the content of the determined message thread 22 is determined (from the yes branch of block 208) or created (from block 210), the message promoter 22 adds (at block 212) all or part of the determined message thread 6 to the content management system 16 and associates (at block 214) the determined message 6 in the content management system with the relevant category. In one embodiment, the determined message thread 6 may be added to the content management system 16 by inserting some or all of the message thread content into a new or preexisting content object 18. For instance, the message thread content can be inserted into a content page associated with the same category as the message thread. Alternatively, message thread content can be added to a separate content object and a reference (e.g., link) to the message thread content may be added to one or more content objects in the relevant content category.
Described embodiments provide techniques to promote messages (or other content) from one content management system, such as a message form, to another content management system, such that the promoted message is associated with a relevant category of content objects in the content management system and available for review and further editing by users of the content management system.
The described operations may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a “computer readable medium”, where a processor may read and execute the code from the computer readable medium. A computer readable medium may comprise media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, etc.), etc. The code implementing the described operations may further be implemented in hardware logic in a hardware device (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.). Still further, the code implementing the described operations may be implemented in “transmission signals”, where transmission signals may propagate through space or through a transmission media, such as an optical fiber, copper wire, etc. The transmission signals in which the code or logic is encoded may further comprise a wireless signal, satellite transmission, radio waves, infrared signals, Bluetooth, etc. The transmission signals in which the code or logic is encoded is capable of being transmitted by a transmitting station and received by a receiving station, where the code or logic encoded in the transmission signal may be decoded and stored in hardware or a computer readable medium at the receiving and transmitting stations or devices. An “article of manufacture” comprises computer readable medium, hardware logic, and/or transmission signals in which code may be implemented. A device in which the code implementing the described embodiments of operations is encoded may comprise a computer readable medium or hardware logic. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise suitable information bearing medium known in the art.
In one embodiment, if multiple content categories in the content management system 16 are relevant to one message thread, then the content of the method thread may be associated with multiple of those categories, such as added to content objects in the multiple categories.
In the described embodiment of
The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.
The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.
The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.
The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.
The variable “n” when used to represent a variable number of an element may indicate any number of instances of the element, and may indicate different integer numbers when used with different elements.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.
A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.
Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order practical. Further, some steps may be performed simultaneously.
When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.
The illustrated operations of
The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
5724567 | Rose et al. | Mar 1998 | A |
5781732 | Adams | Jul 1998 | A |
5867799 | Lang et al. | Feb 1999 | A |
6493703 | Knight et al. | Dec 2002 | B1 |
6571234 | Knight et al. | May 2003 | B1 |
6582472 | Hart | Jun 2003 | B2 |
6584471 | Maclin et al. | Jun 2003 | B1 |
6807566 | Bates et al. | Oct 2004 | B1 |
6826596 | Suzuki | Nov 2004 | B1 |
6851087 | Sibert | Feb 2005 | B1 |
6865572 | Boguraev et al. | Mar 2005 | B2 |
6938203 | Dimarco et al. | Aug 2005 | B1 |
7031952 | Heumann et al. | Apr 2006 | B1 |
7043492 | Neal et al. | May 2006 | B1 |
7185065 | Holtzman et al. | Feb 2007 | B1 |
7197470 | Arnett et al. | Mar 2007 | B1 |
7200606 | Elkan | Apr 2007 | B2 |
7203704 | Stern et al. | Apr 2007 | B1 |
7418437 | Marks | Aug 2008 | B1 |
7596578 | Marks | Sep 2009 | B1 |
20010018698 | Uchino et al. | Aug 2001 | A1 |
20010056371 | Shuster | Dec 2001 | A1 |
20020062368 | Holtzman et al. | May 2002 | A1 |
20020099731 | Abajian | Jul 2002 | A1 |
20030004909 | Chauhan et al. | Jan 2003 | A1 |
20030014311 | Chua | Jan 2003 | A1 |
20030018658 | Suermondt et al. | Jan 2003 | A1 |
20030093478 | Hughes | May 2003 | A1 |
20030164849 | Barrie et al. | Sep 2003 | A1 |
20030208535 | Appleman et al. | Nov 2003 | A1 |
20040128673 | Fuchs et al. | Jul 2004 | A1 |
20050050444 | Vasey | Mar 2005 | A1 |
20050248790 | Ornstein et al. | Nov 2005 | A1 |
20060004601 | Marks | Jan 2006 | A1 |
20060074846 | Feinberg et al. | Apr 2006 | A1 |
20060095830 | Krishna et al. | May 2006 | A1 |
20060155809 | Arav | Jul 2006 | A1 |
20060167737 | Muller et al. | Jul 2006 | A1 |
20060173985 | Moore | Aug 2006 | A1 |
20060242554 | Gerace et al. | Oct 2006 | A1 |
20070078675 | Kaplan | Apr 2007 | A1 |
20070124432 | Holtzman et al. | May 2007 | A1 |
20070208614 | Arnett et al. | Sep 2007 | A1 |
20070214097 | Parsons et al. | Sep 2007 | A1 |
20080071929 | Motte et al. | Mar 2008 | A1 |
20080077574 | Gross | Mar 2008 | A1 |
20080168045 | Suponau et al. | Jul 2008 | A1 |
20080244438 | Peters et al. | Oct 2008 | A1 |
20080320090 | Bryan | Dec 2008 | A1 |
Number | Date | Country |
---|---|---|
WO2007135436 | Nov 2007 | EP |
Number | Date | Country | |
---|---|---|---|
20080243877 A1 | Oct 2008 | US |