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