Abstract: A motion-activated dispenser includes a housing having a base and top defining a gap sized to receive a human hand. The top portion defining cavity sized to receive a fluid reservoir and an opening extending directly through a lower surface of the top portion to the cavity, a neck of the fluid reservoir extending through the opening. A pressing member is positioned within the cavity and an actuator is coupled to the pressing member and configured to urge the pressing member toward and away from the opening. The pressing member may include, for example, a sliding member positioned opposite a stop face; a roller moved by the actuator toward the opening; a plunger positioned above the opening and driven by an actuator toward the opening; or a pair of rods spanning the cavity and urged by the actuator through the cavity, the rods pressing against sides of the reservoir.

Abstract: A motion-activated dispenser includes a housing having a base and top defining a gap sized to receive a human hand. The top portion defining cavity sized to receive a fluid reservoir and an opening extending directly through a lower surface of the top portion to the cavity, a neck of the fluid reservoir extending through the opening. A pressing member is positioned within the cavity and an actuator is coupled to the pressing member and configured to urge the pressing member toward and away from the opening. The pressing member may include, for example, a sliding member positioned opposite a stop face; a roller moved by the actuator toward the opening; a plunger positioned above the opening and driven by an actuator toward the opening; or a pair of rods spanning the cavity and urged by the actuator through the cavity, the rods pressing against sides of the reservoir.

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: An installation and configuration system consolidates workloads of multiple applications and services, including applications or services that may be installed or configured on multiple server devices or remotely hosted services. The system gathers environmental information, analyzes dependencies among the workloads, and populates the input data used by the workloads from a common database. The system then executes the workloads, allowing branching within the workloads or the sequence of workloads. An example of branching may include detecting an error condition, pausing the sequence, and presenting alternative fixes to a user.

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: A system that can identify, create, update and/or process a workflow based upon a current, past or future activity is disclosed. A ‘workflow’ can be defined as an activity flow that includes interaction with, or assignment of work to, people, devices, or services by a single individual or a group of individuals. Once a workflow is determined in accordance with the innovation, the system can inform other users or groups that are performing, or intend to perform, a similar or like activity. In establishing the workflow, the innovation can operate in an ad hoc or authored manner. As well, the system can employ a combination of either ad hoc or authored mechanisms in establishment of the workflow.

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: An installation and configuration system consolidates workloads of multiple applications and services, including applications or services that may be installed or configured on multiple server devices or remotely hosted services. The system gathers environmental information, analyzes dependencies among the workloads, and populates the input data used by the workloads from a common database. The system then executes the workloads, allowing branching within the workloads or the sequence of workloads. An example of branching may include detecting an error condition, pausing the sequence, and presenting alternative fixes to a user.

Abstract: A user interface displays multiple steps in sequential relationship to each other, and may group various steps together and provide completion indicators for each step as well as an overall completion indicator. Error conditions, status information, queries, and details about a particular step or group of steps may be displayed inline with the steps in a task detail portion of the user interface. The task detail portion may be collapsible and expandable by the user. Progress and completion indicators may be updated for each step, groups of steps, and the overall sequence. In a typical use, a software installation sequence may comprise installation steps from multiple software components. The user interface may illustrate the status of individual tasks, groups of task, and the overall sequence as the tasks are performed, and enable errors to be resolved by displaying queries and other information inline with the steps.

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: A unified workspace (UWS) design that provides a single system-wide display and interaction surface, and a set of tools that allow a user to discover relevant information. Data is surfaced across boundaries of applications and documents and stored implicitly from preset business logic or explicitly from user demand. Data can be implicitly and explicitly queried and aggregated from many different data sources such as various content types that are created in different formats and displayed on a single interaction surface. The UWS surfaces the required application functionalities to perform the tasks by partial launch of the associated application. Data elevation surfaces only the relevant amount of information, based on the context and activity, to assist the completion and decisionmaking process. Private and shared workspaces can be employed with object passing therebetween. The UWS provides a visual representation of each element such as information or relationship and allows direct user interaction.

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: Described is a technology by which support information (e.g., help and/or other information) related to a computer program is automatically and dynamically searched with respect to a task of that program, with the results of the search aggregated for output in relation to the program. For example, the search may be based on active context data of the task (e.g., such as error data and the current operating environment), so that the support information that is located matches what is likely relevant. User preference data and default data may be used to narrow the search to specific sites, such as community forums that have been deemed to be valuable. Other input used to generate the query or queries may include historical and/or statistical data, and/or explicit user input.

Abstract: The innovation enables “total system” experiences for activities and activity-specialized experiences for applications and gadgets that allow them to align more closely with the user, his work, and his goals. In particular, the system provides for dynamically changing the user interface (UI) of the system level shell (“desktop”), of applications, and of standalone UI parts (“gadgets”), based upon a current (or future) activity of the user and other context data. The system can consider context data that includes extended activity data, information about the user's state, and information about the current environment. Preprogrammed and/or inferred rules can be used to decide how to adapt the UI based upon the activity. These rules can include, user rules, group rules, and device rules. Additionally, activities and applications can also participate in the decision of how to adapt the UI.

Abstract: A system that can identify, create, update and/or process a workflow based upon a current, past or future activity is disclosed. A ‘workflow’ can be defined as an activity flow that includes interaction with, or assignment of work to, people, devices, or services by a single individual or a group of individuals. Once a workflow is determined in accordance with the innovation, the system can inform other users or groups that are performing, or intend to perform, a similar or like activity. In establishing the workflow, the innovation can operate in an ad hoc or authored manner. As well, the system can employ a combination of either ad hoc or authored mechanisms in establishment of the workflow.

Abstract: User introspection is provided to help users achieve goals (e.g., work goals, personal goals) and become more effective at performing tasks. Activities can be monitored, logged, and compared to a set of goals or tasks. Feedback can be provided if a user has deviated from a specified goal or task, in the form of a recommendation as to a next action, or based upon user-defined criteria. Feedback can also be provided based on a multitude of parameters that can include prioritized goal definition and refinement, task avoidance behavior detection, baseline activity analysis (e.g. historical data), base-line capacity (personal and/or comparison to others), task reacquisition, etc.

Abstract: A system that can log user actions associated with an activity is disclosed. For example, the system can maintain a log of user keystrokes, files accessed, files opened, files created, websites visited, communication events (e.g., phone calls, instant messaging communications), etc. Additionally, the system can log extrinsic data (e.g., context data) associated with the user actions. As well, these logged actions can be aggregated, synchronized and/or shared between multiple users and/or devices.

Abstract: A system that enables generation and/or modification of an activity template is disclosed. The activity template describes overall actions and resources associated with an activity. The system can automatically convert activity logs into recipes thereby reducing effort in activity reproduction. Self-tuning via machine learning-based algorithms can be employed thereby dynamically altering the template in accordance with on-going or historical user action.

Abstract: A unique system and method is provided that facilitates managing an activity centric environment via a master profile (which includes user, group, and device profiles). The master profile follows or stays with the user and can be applied universally across devices and activities (activity templates). When profile data does not currently exist (e.g., a new activity or a new device), portions of the existing profile data can be applied to such new activities or device as appropriate. Thus, current profile data for existing or known user interactions and devices can be inferentially extended to new user interactions and devices. When conflicts arise between applicable profile data, they can be solved by applying the profile data in accordance with their priority. User intervention can be requested whereby the system can adapt previous user-based resolutions to future conflicts. Profile data can also be scaled according to the context of the user-device-activity interaction.