Abstract: Systems and processes for managing a data warehouse using an activity graph are disclosed. One example process may include selectively tracking new versions of an entity based on a tracking type, removing entities based on data retention rules, removing entities based on data decay rules, and summarizing decayed data.

Abstract: Systems and processes for managing a data warehouse using an activity graph are disclosed. One example process may include selectively tracking new versions of an entity based on a tracking type, removing entities based on data retention rules, removing entities based on data decay rules, and summarizing decayed data.

Abstract: Systems and processes for accessing data from a graph database are described. The system receives a request comprising time-based information. Time-based information of the request is compared with a first time interval, which is associated with at least one node of a graph. The node of the graph is matched based on the time-based information being at least partially within the first time interval. The system returns a result comprising an indicator of the node of the graph, wherein the node of the graph is associated with an entity, and the node of the graph includes an attribute of the entity.

Abstract: Systems and processes for accessing data from a graph database are described. The system receives a request comprising time-based information. Time-based information of the request is compared with a first time interval, which is associated with at least one node of a graph. The node of the graph is matched based on the time-based information being at least partially within the first time interval. The system returns a result comprising an indicator of the node of the graph, wherein the node of the graph is associated with an entity, and the node of the graph includes an attribute of the entity.

Abstract: Systems and processes for storing correlated data in a graph database are described. A first user node may be stored. In response to a request, a first event node and a second user node may be stored. The first event node may be associated with the first user node through an edge indicating participation. The first event node may be associated with the second user node through an edge indicating participation. In response to a content access, a second event node and a content node may be stored. The second event node may be associated with the first user node through an edge indicating participation. The second event node may be associated with the content node through an edge indicating usage. The first user node may be associated with the content node through an edge indicating the first user node handles the content node.

Abstract: Systems and processes for managing data in a data warehouse using an activity graph are described. The activity graph may include nodes representing entities (or versions thereof) interconnected by edges representing relationships (or versions thereof) between those entities. The nodes representing versions of an entity may be captured as a directed acyclic graph (DAG). New nodes and edges may be added to the activity graph as new entities and relationships are formed. As changes are made to an entity or relationship, new nodes or edges representing new versions of the entity or relationship may be created and added to the activity graph based on the entity's or relationship's tracking type. Existing nodes and edges may be removed from the activity based on data retention rules and/or data decay rules. In some examples, nodes and edges may be summarized by collapsing multiple nodes or multiple edges into a single node or edge.

Abstract: Recommendation systems and processes for generating recommendations within the context of a socially-enabled human workflow system are provided. The processes may include accessing workflow data, such as social graphs, organization graphs, collaboration graphs, content data, utilization data, ratings data, and the like, associated with a user requesting a recommendation. The process may further include determining one or more of a user similarity score, task similarity score, goal similarity score, and content similarity score. The process may further include generating one or more recommendations based at least in part on one or more of the user similarity score, task similarity score, goal similarity score, and content similarity score.

Abstract: Systems and processes for managing a data warehouse using an activity graph are disclosed. One example process may include selectively tracking new versions of an entity based on a tracking type, removing entities based on data retention rules, removing entities based on data decay rules, and summarizing decayed data.

Abstract: Systems and processes for presenting event notifications to a target user based on the context of the user are disclosed. The event notification can be selectively presented to the target user based on a comparison between the event and the context of the user. If the event and the context of the user meet predefined criteria, the event notification can be presented to the target user. If the event and the context of the user do not meet the predefined criteria, the event notification may be stored for later delivery to the target user.

Abstract: Systems and processes for displaying a graphical user interface control are described. API indicators may be displayed in response to a request for an API listing. A selection of an API indicator may be detected, the API indicator associated with one API of a plurality of APIs. A plurality of user interface control indicators may be displayed in response to the selection of the API indicator. The selection of a first user interface control indicator of the plurality of user interface control indicators may be detected, the first user interface control indicator associated with the graphical user interface control. The graphical user interface control may be compatible with the one API. An API call may be initiated using the one API. Response data may be received in response to the API call. The graphical user interface control may be displayed using at least a subset of the received response data.

Abstract: Systems and processes for providing an application development tool are disclosed. The application development tool may include a user interface that allows a user to select and modify widgets, map API properties to widget attributes, and create application user interfaces using the widgets. To modify the widgets and create applications, the application development tool may edit the source code associated with the widget or application based on input received from the user via the application development tool interface.

Abstract: Systems and processes for storing correlated data in a graph database are described. A first user node may be stored. In response to a request, a first event node and a second user node may be stored. The first event node may be associated with the first user node through an edge indicating participation. The first event node may be associated with the second user node through an edge indicating participation. In response to a content access, a second event node and a content node may be stored. The second event node may be associated with the first user node through an edge indicating participation. The second event node may be associated with the content node through an edge indicating usage. The first user node may be associated with the content node through an edge indicating the first user node handles the content node.

Abstract: Systems and processes for determining a contextual status of a resource, such as a user, using a contextual presence framework are described. A plurality of modes may be associated with the resource, where each mode represents a context of the resource. A presence value of the resource may be determined for each mode, which represents the extent to which the resource is engaged in the mode. An availability value of the resource may be determined for each mode, which represents the extent to which the resource is willing to be interrupted in the mode. A contextual presence status summary having a status summary availability value and a status summary presence value may be determined based on, for example, a weighted average of the presence values and a weighted average of the availability values of multiple modes of the resource.