Abstract: Data elevation architecture for automatically and dynamically surfacing to a user interface (UI) context-specific data based on specific workflow or content currently being worked on by a user. Data is broken down into data elements and stored at a data element level in a data catalog using metadata, attributes, and relationships. Data elements are automatically selected from a comprehensive collection of the data catalogs based on relevancy and correlation to the current user task. The data catalog stores and relates the data elements and metadata based on criteria specified by content matching based on business terms or specified in a business process in predefined relationships between forms or specified by the user as correlated. The UI displays the data automatically in forms dynamically selected, populated, and presented at the point of focus or user activity so that the user can interact or take action immediately.

Abstract: Systems and methods that enable conference attendee(s) to invite others to the conference and provide a rich set of contextual information about the conference upfront to the invitee(s). A communicator component enables document related to the conference to be automatically shared and can further supply the name of the document and the location of the document. Hence, an invitee can make an informed decision about joining the conference and evaluate relevance of the conference up front (e.g., prior to joining).

Abstract: Data elevation architecture for automatically and dynamically surfacing to a user interface (UI) context-specific data based on specific workflow or content currently being worked on by a user. Data is broken down into data elements and stored at a data element level in a data catalog using metadata, attributes, and relationships. Data elements are automatically selected from a comprehensive collection of the data catalogs based on relevancy and correlation to the current user task. The data catalog stores and relates the data elements and metadata based on criteria specified by content matching based on business terms or specified in a business process in predefined relationships between forms or specified by the user as correlated. The UI displays the data automatically in forms dynamically selected, populated, and presented at the point of focus or user activity so that the user can interact or take action immediately.

Abstract: Data elevation architecture for automatically and dynamically surfacing to a user interface (UI) context-specific data based on specific workflow or content currently being worked on by a user. Data is broken down into data elements and stored at a data element level in a data catalog using metadata, attributes, and relationships. Data elements are automatically selected from a comprehensive collection of the data catalogs based on relevancy and correlation to the current user task. The data catalog stores and relates the data elements and metadata based on criteria specified by content matching based on business terms or specified in a business process in predefined relationships between forms or specified by the user as correlated. The UI displays the data automatically in forms dynamically selected, populated, and presented at the point of focus or user activity so that the user can interact or take action immediately.

Abstract: Architecture that defines a document or portions thereof as data elements that are related and categorized. A data catalog is created that uses a schema for the data elements and a set of relationships, attributes and values that further define the data elements, all stored as metadata about the data elements. The metadata is employed to enable the application, display surface, and user to see only data relevant to the task at hand. The positioning and grouping of controls, control characteristics, and control behavior at the display surface is facilitated by forms which are dynamically populated for presentation and which are driven directly by the data catalog. The catalog can be made aware of device parameters, for example, the display size and resolution thereby enabling data to be displayed differently based upon the device parameters.

Abstract: Systems and methods that enable conference attendee(s) to invite others to the conference and provide a rich set of contextual information about the conference upfront to the invitee(s). A communicator component enables document related to the conference to be automatically shared and can further supply the name of the document and the location of the document. Hence, an invitee can make an informed decision about joining the conference and evaluate relevance of the conference up front (e.g., prior to joining).

Abstract: Consultation architecture that allows a call assistant to use modes of consultation with the call recipient other than voice calls or vocal contact. The receptionist can place the incoming call (or message) on hold and send an instant message (IM) to the call recipient that informs the recipient about the call and/or who is calling. The recipient can then acknowledge and respond via the IM or another mode, and agree to accept the call, refuse the call, or request the call be routed to another destination, for example. Other non-voice consultation modes include paging technology by sending a short page to the call recipient, sending an SMS (short message service) or MMS (multimedia messaging service) message to the call recipient, and/or sending an e-mail message to the call recipient that provides information about the call and/or the caller.

Abstract: Data elevation architecture for automatically and dynamically surfacing to a user interface (UI) context-specific data based on specific workflow or content currently being worked on by a user. Data is broken down into data elements and stored at a data element level in a data catalog using metadata, attributes, and relationships. Data elements are automatically selected from a comprehensive collection of the data catalogs based on relevancy and correlation to the current user task. The data catalog stores and relates the data elements and metadata based on criteria specified by content matching based on business terms or specified in a business process in predefined relationships between forms or specified by the user as correlated. The UI displays the data automatically in forms dynamically selected, populated, and presented at the point of focus or user activity so that the user can interact or take action immediately.

Abstract: Architecture that defines a document or portions thereof as data elements that are related and categorized. A data catalog is created that uses a schema for the data elements and a set of relationships, attributes and values that further define the data elements, all stored as metadata about the data elements. The metadata is employed to enable the application, display surface, and user to see only data relevant to the task at hand. The positioning and grouping of controls, control characteristics, and control behavior at the display surface is facilitated by forms which are dynamically populated for presentation and which are driven directly by the data catalog. The catalog can be made aware of device parameters, for example, the display size and resolution thereby enabling data to be displayed differently based upon the device parameters.