Abstract: Methods, systems, apparatuses, and computer program products are described for providing content recommendations to a requestor. In implementations, user event records associated with media items and content types may be stored, for instance, in an event catalog. A set of user scores may be generated based on a user-content score model and the user event records, where each generated user score represents an affinity between a user and a corresponding content type of the plurality of content types. A set of title scores may also be generated for a media item based on a title-content score model, where each generated title score represents an affinity between the media item and a corresponding content type. In response to a request, the sets of scores may be combined to generate a set of content recommendations to provide to the requestor.

Abstract: Methods, systems, apparatuses, and computer program products are described for providing content recommendations to a requestor. In implementations, user event records associated with media items and content types may be stored, for instance, in an event catalog. A set of user scores may be generated based on a user-content score model and the user event records, where each generated user score represents an affinity between a user and a corresponding content type of the plurality of content types. A set of title scores may also be generated for a media item based on a title-content score model, where each generated title score represents an affinity between the media item and a corresponding content type. In response to a request, the sets of scores may be combined to generate a set of content recommendations to provide to the requestor.

Abstract: Techniques to manage retention policy tags are described. A system may comprise a tagging component operative to tag a message with an expiration tag to form an expiration tagged message, the expiration tag having expiration information used to expire the expiration tagged message in accordance with a retention policy. The system may further comprise a presentation component communicatively coupled to the tagging component, the presentation component operative to present a view of the expiration tagged message with an expiration field having the expiration information for the expiration tagged message. Other embodiments are described and claimed.

Abstract: Architecture that employs machine-based learning to automatically categorize data on a per-user basis. Auto-tagging reduces the burden on infoworkers by creating a machine learning model to learn from user tagging behavior or preferences. Once this information is obtained, a trained model for this specific user is used to assign tags to incoming data, such as emails. The architecture finds particular applicability to compliance and message retention policies that otherwise would mandate extra work for the infoworker. The architecture learns the tagging behavior of a user and uses this learned behavior to automatically tag data based on the user's prior tagging habits. A regression algorithm is employed to process the training data according to an n-dimensional framework for prediction and application of the tag(s) to the incoming messages.

Abstract: Techniques to manage retention policy tags are described. A system may comprise a tagging component operative to tag a message with an expiration tag to form an expiration tagged message, the expiration tag having expiration information used to expire the expiration tagged message in accordance with a retention policy. The system may further comprise a presentation component communicatively coupled to the tagging component, the presentation component operative to present a view of the expiration tagged message with an expiration field having the expiration information for the expiration tagged message.

Abstract: Determining indicative features may be provided. First, a first set of features may be determined using a document frequency process. Then a second set of features may be determined using a boosting process. Using the boosting process may comprise using an approximation for a one-dimensional optimization. The approximation may include an upper bound. Next, the first set of features and the second set of features may be combined into a combined set of features. The combined set of features may comprise a union of the first set of features and the second set of features. At least one document may then be classified based on the combined set of features.

Abstract: This disclosure is directed to automatically moving message objects, such as email message objects, from online source mailbox databases to online archive mailbox databases. As described herein, each email message in a source mailbox database is directly or indirectly associated with a retention policy tag. The retention policy tag associated with a message object in a source mailbox database specifies a retention period. The message object remains in source mailbox database until the retention period expires for the message object. When the retention period for the message object expires, the message object is automatically moved to an archive mailbox database.

Abstract: Determining indicative features may be provided. First, a first set of features may be determined using a document frequency process. Then a second set of features may be determined using a boosting process. Using the boosting process may comprise using an approximation for a one-dimensional optimization. The approximation may include an upper bound. Next, the first set of features and the second set of features may be combined into a combined set of features. The combined set of features may comprise a union of the first set of features and the second set of features. At least one document may then be classified based on the combined set of features.

Abstract: This disclosure is directed to automatically moving message objects, such as email message objects, from online source mailbox databases to online archive mailbox databases. As described herein, each email message in a source mailbox database is directly or indirectly associated with a retention policy tag. The retention policy tag associated with a message object in a source mailbox database specifies a retention period. The message object remains in source mailbox database until the retention period expires for the message object. When the retention period for the message object expires, the message object is automatically moved to an archive mailbox database.

Abstract: Techniques to manage retention policy tags are described. A system may comprise a tagging component operative to tag a message with an expiration tag to form an expiration tagged message, the expiration tag having expiration information used to expire the expiration tagged message in accordance with a retention policy. The system may further comprise a presentation component communicatively coupled to the tagging component, the presentation component operative to present a view of the expiration tagged message with an expiration field having the expiration information for the expiration tagged message. Other embodiments are described and claimed.

Abstract: Architecture that employs machine-based learning to automatically categorize data on a per-user basis. Auto-tagging reduces the burden on infoworkers by creating a machine learning model to learn from user tagging behavior or preferences. Once this information is obtained, a trained model for this specific user is used to assign tags to incoming data, such as emails. The architecture finds particular applicability to compliance and message retention policies that otherwise would mandate extra work for the infoworker. The architecture learns the tagging behavior of a user and uses this learned behavior to automatically tag data based on the user's prior tagging habits. A regression algorithm is employed to process the training data according to an n-dimensional framework for prediction and application of the tag(s) to the incoming messages.

Abstract: Architecture for retention policy tagging of data items such as messages for expiring data items without data reorganization. Retention policy tags can be applied to items, conversations, folders, and/or distribution lists, for example. Retention policy tags provide a way to manage (e.g., expire) data items such as email, for example, and reduce the corporate burden for compliance in documents of all types. Tags can be applied to data items individually and in-place, and do not impose changes to the natural workflow of the user. The use of expiry policy tags provides a solution by removing the pain point around physically moving messages to an unfamiliar folder hierarchy.