Abstract: Embodiments include methods, systems and computer program products for performing named entity recognition. Aspects include obtaining a text having a plurality of words and comparing each of the plurality of words to a dictionary. Aspects also include creating, based on the comparison, an annotation for at least one of the plurality of words that the least one of the plurality of words refers to a named entity. Aspects further include parsing the text to identify a part of speech for each of the plurality of words and removing the annotations from each of the at least one of the plurality of words that has a part of speech that is not one or a noun and a noun supporting adjective.

Abstract: Embodiments include methods, systems and computer program products for performing named entity recognition. Aspects include obtaining a text having a plurality of words and comparing each of the plurality of words to a dictionary. Aspects also include creating, based on the comparison, an annotation for at least one of the plurality of words that the least one of the plurality of words refers to a named entity. Aspects further include parsing the text to identify a part of speech for each of the plurality of words and removing the annotations from each of the at least one of the plurality of words that has a part of speech that is not one or a noun and a noun supporting adjective.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: The present invention provides a method of improving the response time to IT problems and ensuring that some will respond to a problem. In one embodiment, a management system uses a monitoring system to detect problem conditions with a managed device. When such an event occurs, the managed device sends a message containing a description of the alert to an intelligent agent. In response, the intelligent agent selects an administrator who is both qualified and available to respond to the alert, and then sends an instant message containing the description of the alert to the selected administrator. The administrator may accept responsibility for the alert by sending an instant message acknowledgement back to the intelligent agent. If the intelligent agent does not receive an acknowledgement, it automatically finds another administrator to respond to the alert.

Abstract: 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.

Abstract: 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.

Abstract: In an embodiment, an upgrade rule associated with a configuration set is found, and a document associated with the upgrade rule is found. The configuration set includes a schema and an upgrade transformation, and the upgrade transformation specifies a change that was made to the schema. The document includes a lifecycle state and an element. If the upgrade rule indicates an automatic upgrade, then a mutability rule associated with the lifecycle state of the document is found and a decision is made whether the mutability rule allows the document to be changed. If the mutability rule allows the document to be changed, the element in the document is changed to include the change specified by the upgrade transformation at a time specified by the upgrade rule.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: In an embodiment, an upgrade rule associated with a configuration set is found, and a document associated with the upgrade rule is found. The configuration set includes a schema and an upgrade transformation, and the upgrade transformation specifies a change that was made to the schema. The document includes a lifecycle state and an element. If the upgrade rule indicates an automatic upgrade, then a mutability rule associated with the lifecycle state of the document is found and a decision is made whether the mutability rule allows the document to be changed. If the mutability rule allows the document to be changed, the element in the document is changed to include the change specified by the upgrade transformation at a time specified by the upgrade rule.

Abstract: The present invention provides a method of improving the response time to IT problems and ensuring that some will respond to a problem. In one embodiment, a management system uses a monitoring system to detect problem conditions with a managed device. When such an event occurs, the managed device sends a message containing a description of the alert to an intelligent agent. In response, the intelligent agent selects an administrator who is both qualified and available to respond to the alert, and then sends an instant message containing the description of the alert to the selected administrator. The administrator may accept responsibility for the alert by sending an instant message acknowledgement back to the intelligent agent. If the intelligent agent does not receive an acknowledgement, it automatically finds another administrator to respond to the alert.