| Patent application number | Description | Published |
|---|
| 20100010980 | CONTEXT SENSITIVE TERM EXPANSION WITH DYNAMIC TERM EXPANSION - Methods, articles of manufacture and systems for searching collections of data using context sensitive expanded term searching using dynamic term expansion are provided. The collection of data may be a relational database, text document, or any other type of searchable collection of data. In either case, a query including a search condition based on a specified search term may be modified to include additional conditions based on a set of expanded (e.g., conceptually-related) search terms dynamically linked with the query. For some embodiments, a user may be given the ability to choose whether the set of expanded search terms are dynamically linked with the query or not. | 01-14-2010 |
| 20100057811 | CONTEXT-SENSITIVE TERM EXPANSION WITH MULTIPLE LEVELS OF EXPANSION - Articles of manufacture and systems for searching collections of data using context sensitive expanded term searching are provided. The collection of data may be a relational database, text document, or any other type of searchable collection of data. In either case, a query including a search condition based on a specified search term may be modified to include additional conditions based on a set of expanded (e.g., conceptually-related) search terms. For some embodiments, a user may be given the ability to control the level of expansion and the context in which the terms may be expanded. | 03-04-2010 |
| 20110067025 | AUTOMATICALLY GENERATING COMPOUND COMMANDS IN A COMPUTER SYSTEM - A computer system provides a way to automatically generate compound commands that perform tasks made up of multiple simple commands. A compound command generation mechanism monitors consecutive user commands and compares the consecutive commands a user has taken to a command sequence identification policy. If the user's consecutive commands satisfy the command sequence identification policy the user's consecutive commands become a command sequence. If the command sequence satisfies the compound command policy, the compound generation mechanism can generate a compound command for the command sequence automatically or prompt an administrator to allow the compound command to be generated. Generating a compound command can be done on a user by user basis or on a system wide basis. The compound command can then be displayed to the user to execute so that the command sequence is performed by the user selecting the compound command for execution. | 03-17-2011 |
| 20110078114 | Independently Variably Scoped Content Rule Application in a Content Management System - A content management system (CMS) synchronization mechanism synchronizes content attributes, preferably in metadata, with content documents. For each of one or more content attributes (e.g. metadata fields), a respective content document context is associated. Each attribute is synchronized to content in the content document according to the associated context. Preferably, the content document contains multiple nested files, and context limits synchronization to a subset of files. Synchronization rules, enforced by a synchronization engine, define respective attributes and content to be synchronized, each rule having an associated context in the content document. Rules are preferably created in XML format, and parsed to produce a document object model upon which the synchronization engine operates. | 03-31-2011 |
| Patent application number | Description | Published |
|---|
| 20090070288 | METHOD AND SYSTEM FOR UPDATING DOCUMENT CONTENT AND METADATA VIA PLUG-IN CHAINING IN A CONTENT MANAGEMENT SYSTEM - Embodiments of the invention provide a method for managing and updating documents containing specialized content in a content management system (CMS) by chaining plug-ins. Rather than create a unique rule for each specialized scenario, a CMS may be configured to apply a plug-in chain in an order based upon a type of document encountered and/or configured criteria. | 03-12-2009 |
| 20100030816 | Bursting in a Content Management System - When a document is checked into a content management system repository, parts of the document may be stored as separate chunks in the repository based on bursting rules associated with that document. These chunks may be associated with chunk-specific bursting rules several levels deep. A granular bursting mechanism processes each chunk in the repository using the applicable bursting rule. One suitable implementation to determine the applicable bursting rule is to recursively decide whether to use the rules for the parent document, or the chunk-specific bursting rules. Another suitable implementation to determine the applicable bursting rule is for each chunk, to check the parent document's child processing policy. If the parent document's child processing policy allows specific rules to be overwritten, the chunk-specific bursting rules for the chunk are used. If the parent document's child processing policy does not allow rules to be overwritten, the parent document's bursting rules are used. | 02-04-2010 |
| 20100235327 | INTELLIGENT DELETION OF ELEMENTS TO MAINTAIN REFERENTIAL INTEGRITY OF DYNAMICALLY ASSEMBLED COMPONENTS IN A CONTENT MANAGEMENT SYSTEM - A content management system (CMS) uses an element deletion mechanism to maintain referential integrity of dynamically assembled elements in a repository. Element properties such as probability, popularity and recent usage that are not explicit relationships between parent documents and child elements are logged. A deletion policy is then defined in terms of the logged element properties. When a request to delete an element is received, the deletion mechanism checks the logged properties against the deletion policy. If the element's logged properties satisfy the deletion policy, the element is deleted from the repository. If the element's logged properties do not satisfy the deletion policy, the element is not deleted. In this manner referential integrity may be enforced for elements that are dynamically assembled. | 09-16-2010 |
| 20110029861 | Generating Simulated Containment Reports of Dynamically Assembled Components in a Content Management System - A content management system (CMS) uses a simulated containment report generation mechanism to generate a simulated containment report for elements in the repository based on logged properties that represent potential use of the element during dynamic content delivery that are not represented in formal relationships in the content management system. Properties such as probability, popularity, and recent usage that are not explicit relationships between parent documents and child elements are logged and used to determine which document maps may potentially reuse a selected element. In this manner a simulated containment report can be created for an element that allows the user to see the document maps that are most likely to include the element. | 02-03-2011 |
