Abstract: Emotion across voice and text communication channels are abstracted, preserved and translated. A voice communication is received and analyzed for emotion content. The textual content of the communication is realized summarily using word recognition techniques. The textual content is then analyzed for emotion content. Words and phrases derived from the word recognition are compared emotion words and phrases in a text mine database. The emotion from the two analyses is then used for marking up the textual content as emotion metadata. The text and emotion markup abstraction for a voice communication can also be translated into a using text and emotion translation definitions. The translated emotion metadata is used to emotion mine words that have an emotion connotation in the culture of the second language. Those words are then substituted for corresponding words in the translated text.

Abstract: A computer implemented method, apparatus, and computer usable code for managing instant messages. An instant message is received at a client. A set of parameters in the instant message is identified. The instant message on a display in the client is presented, and the instant message is removed from the display after a period of time defined by the set of parameters.

Abstract: A portlet state maintenance system can include a portal page setup component configured to generate a logical form in a single portal page from a multiplicity of forms defined within portlet markup aggregated into the single portal page. A portal state save component further can be configured to save state values for selected portlets defined within the logical form. Finally, a portal state restore component can be configured to restore the saved state values in refreshed portlet markup for the selected portlets. Notably, a refresh timing component further can be configured to embed submit auto-initiation logic in the single portal page responsive to identifying a dynamic refresh requirement associated with the portlet markup in the single portal page. Finally, a portlet markup cache can be coupled to the portal state restore component.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to portal view rendering and provide a method, system and computer program product for portlet view processing with render-when-ready portlets. In one embodiment, a portal server system can be provided which can include a portal server configured to render a portal page, and a portlet aggregator configured to provide portlet markup for different portlets in different temporary documents linked to the portal page. The different temporary documents can be linked to the portal page through corresponding hidden frames disposed in the portal page. Moreover, each of the different temporary documents can include a script programmed to write contained portlet markup to an element in the portal page responsive to a triggering event. Finally, the portal page can include one or more span elements, each of the span elements being referenced by the script in a corresponding one of the different temporary documents.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to processing forms submissions in a portal environment and provide a method, system and computer program product for independently refreshing a forms submission in a portal view. In one embodiment, a system for independently submitting forms in a portal view can include a portal server configured to render a portal view and a portlet aggregator coupled to the portal server. The portal aggregator can be configured to provide portlet markup for different portlets in the portal view where at least one of the different portlets includes a visible form includes one or more form elements.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to portlet content refreshing and provide a novel and non-obvious method, system and apparatus for independently refreshing portlet content in a portal view. In an embodiment of the invention, a system for refreshing portlet content in a portal view can include a portal server configured to render a portal page, a portlet aggregator configured to provide portlet markup for different portlets in different refresh controllers having independently refreshable portions, and a refresh servlet coupled to the portlet aggregator that includes programming to configure the portal page with the different refresh controllers.

Abstract: A method, system and apparatus for configuring a page for drag and drop arrangement of content artifacts can include populating a content artifact registry with a plurality of content artifacts, each of the content artifacts defining a draggable and droppable form of a particular type of page content. The method further can include defining a drop zone within the page to receive a dragged and dropped one of the content artifacts, the drop zone defining a consumable type of page content and an action to undertake when consuming a dropped one of the content artifacts having a particular type of page content consistent with the consumable type of page content.

Abstract: A user interface mechanism that introduces a novel concept referred to as a “non-overlapping workspace”. A system user can switch between the traditional overlapping workspace and the novel non-overlapping workspace, depending upon how they wish to move and manage objects in the workspace. In the non-overlapping mode, as the user moves a selected object to relocate it within the work area, as its border touches another object, the selected object pushes the other object (rather than cover it). In an alternative embodiment, when the system is in the non-overlapping mode, objects on the desktop have “sticky” borders, that is, as the border of a selected object comes into contact with the border of another object, the two objects are coupled to each other as though they were glued together, forming an “object unit”.

Abstract: An improved solution for managing processes. In particular, resources are allocated to processes based on a determination of the available resources and an anticipated benefit for each process. The anticipated benefit can be derived from a current status of the process (e.g., lagging or accelerated) and/or benefit knowledge learned from past executions of the process using diverse resource sets. One or more additional attributes, such as resource dependency between processes, can also be considered before allocating resources.