Microsoft Technology Licensing, LLC

Krister Mikalsen

Dag Steinnes Eidesen

Adrian Fanaru

Darrin N Hatakeda

John D Fan

Gunnar Ljosdahl Rasmussen

Amund Kronen Johansen

Vegar Skjaerven Wang

Rune Devik

Magnus Mortensen

Ashok Kuppusamy

Jon Meling

Scott M Stiles

Michael Francis Palermiti, Ii

Susan Marie Grimshaw

Amy Harilal Rambhia

A system and method for surfacing content relevant is described. The system computes a rank score for each item of a plurality of items that are accessible from a user of an enterprise application. The system identifies a set of relevant items from the plurality of items based on the rank score for each item of the plurality of items. The system surfaces the set of relevant items within a context of a communication application of the user without receiving, from the user, a query for any of the items in the set of relevant items.

Preemptively surfacing relevant content within email

A high percentage of received communications are from external entities. In response to receiving a communication from a sender associated with an entity, the entity may be authenticated and contextualized by retrieving and processing contact information for people at the entity that are directly and/or indirectly associated with a recipient of the communication. For example, contact information for people at the entity who have previously communicated with and/or are connected to the recipient or users related to the recipient, for example, may be retrieved from one or more directory services, social networks, and/or professional networks. The contact information may be processed to create corresponding contact objects, and the contact objects may be processed to create an entity object for the entity that comprises one or more connections between the recipient and the people at the entity. The entity object may be provided to the recipient for display.

External contact connections to authenticate and contextualize entity

Collected usage information relating to interaction with content is integrated with operation of a system, such as a content management system. The usage information is collected in response to occurrences of usage events. A user may create, configure and define the usage events according to their needs. The user may also configure/define different values that are associated with the different events. For example, a user may specify: when to count a view (e.g. unique user view or each view); what period of time to collect counts; aggregation of counts (e.g. tenant, site, collection); a weighting for the event; a trim value; when to provide the parameter to a search index of the system such that the value is considered by the search engine of the system; whether or not a parameter is configurable by other users, and the like.

Extensibility model for usage analytics used with a system

Configuring usage events that affect analytics of usage information

Search results returned by ad hoc queries integrate search results with usage analytics calculated from collected usage information for a system, such as a content management system. In response to receiving a query, the query is submitted to the system to obtain search results. Information from the usage analytics is integrated with the obtained search results. A search index of the system may include all/portion of the usage analytics such that the obtained results from the system may already be integrated with the usage analytics. The system is configurable such that users of the system may configure the usage events that are used to collect the usage information. The users may also configure parameters relating to the usage events and when/how the collected information is stored. The usage analytics may also be used to filter, collapse and boost different items in the search results.

Ad-hoc queries integrating usage analytics with search results

Usage information relating to interaction with content is integrated with operation of a system, such as a content management system. The usage information is collected, stored and provided to the system. The usage information may be integrated with the operation of the system in many different ways (e.g. recommendations for other content, most viewed content, most 'liked' content, content viewed by a type of user, and the like). The usage information may also be used to adjust different operations of the service. For example, the usage information may be used to adjust: a retention time of content (e.g. don't delete a recently viewed document), a crawl policy of content; a backup policy of content; restore schedules; identification of storage tier levels; and the like.

Integrating usage information with operation of a system

Growing community of inventors

Tromso, Norway

Krister Mikalsen