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

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

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

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

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

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

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

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

Abstract: The following indications can be collected: indications of strength of connection between interconnected user profile pairs for an active user profile and another user profile; indications of strength of affinity within user profile-computer resource pairs; and indications of a global level of affinity of a global group of user profiles for computer resources. Using these indications, the following values can be generated: a connection strength value for each of the user profile pairs; an affinity strength value for each of the user profile-computer resource pairs; and a global affinity level value for each of the resources. These values can be used to rank the resources, which can include generating a ranked resource data structure to be used in providing resource recommendations. Values representing usage of a computer resource by sub-groups of user profiles can be generated and a description of a comparison between the values can be provided.

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

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

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

Abstract: A query box application provides an inline and context aware query box. An interaction with a content displayed in a client application is detected, in which the interaction is interpreted to activate a query box. The query box is configured based on a context in response to a determination of the context associated with the content. A text of a part of the content may be used to search local and external sources to find resulting data associated with the text. The query box may be rendered with the resulting data in proximity to a location associated with the interaction.

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

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

Abstract: A search driven user interface (UI) is used for navigating content and usage analytics within a system. The system is configurable such that users of the system may configure the usage events that are used to collect the usage information and configure the display of the content and the usage analytics both in a navigation mode and in an analytics mode. For example, a user may configure an overview page on a product catalog to show main product categories and popular products when in navigation mode and when an analytics mode is selected, the page shows different usage analytics for the main product categories (e.g. view counts, purchase event counts, popularity, demographic information, and the like). A user may switch between the navigation mode and the analytics mode while exploring the content of the data selection.

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