Microsoft Technology Licensing, LLC

Darrin N Hatakeda

Dag Steinnes Eidesen

Adrian Fanaru

John D Fan

Krister Mikalsen

Benjamin C Chamberlain

Cameron Stillion

Theodore Ludovicus Michel

Ralph Abdo

Eric F Wong

Gunnar Ljosdahl Rasmussen

Robert C Collie

Vegar Skjaerven Wang

Rune Devik

Magnus Mortensen

Juha P Niemisto

Ronald A Fein

Russell S Johnson

Ronald Stephen Giesen

D Gordon Hardy

Howard W Cherry, Iv

John P O'Neill

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

Selectively shared and filtered personal information collections are provided. Personal information collections include calendars, task lists, address books, and other collections of information that may be provided by personal information manager (PIM) software. Personal information collections published on a server may be limited on a user-by-user basis as to who may access the collections. Furthermore, collections may be automatically filtered based on a rolling window of dates, reducing file size and maintaining privacy of items outside the rolling window.

Secured and filtered personal information publishing

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

Setting options for publishing calendar

Methods, systems, and computer readable media are provided for managing and securing personal information. Personal information is stored in a central repository (personal information store) for a given personal information owner. As personal information is changed, the owner of the personal information may access the personal information store to update information stored therein. Access codes may be established for all personal information, and the use of the codes may be restricted by application of one or more rules or permissions applied to the information requesters. Alternatively, special access codes may be established for one or more pieces or combination of pieces of personal information data contained in the personal information store. Upon request or requirement for personal information, information requesters may be provided one or more access codes to allow the information requester to receive only that personal information for which they are authorized. Encrypted keys may be provided from the personal information store to information requesters instead of financial information or address information for a given personal information owner. Use of the encrypted address keys allows an information requester process a transaction or to contact a personal information owner without receiving actual financial information or contact information for the personal information owner.

Management and security of personal information

A method and computer-readable medium for upgrading an application program, and making an installer program aware that an application has been upgraded is disclosed. The method recognizes that an upgrade to the application has been initiated. The upgrade includes an identifier for the application to be upgraded, as well as information required for the installer to perform the upgrade. The installer program accesses the upgrade information, which includes instructions necessary for installing the upgrade. The installer program also accesses information related to the installed state of the application and related applications. The installer program determines whether or not the upgrade should be performed. If the upgrade should be performed, the installer program performs the upgrade and stores the fact that the application has been upgraded. If the application should not be upgraded, the installer program stores information reflecting the fact that the upgrade is available but not installed.

Method and computer-readable medium for installing an upgrade to an application program

Providing custom content that supplements static content displayed in an alert message. In response to detecting a predetermined condition, such as an error condition, the alert message is displayed to the user of a software program module. The alert message typically presents the static content and a control object, such as a button or a hyperlink. In response to the user's selection of the control object, an external information source, typically a remote server hosting a Web page, is accessed. The external information source maintains the custom content, which can include supplemental information that is related to the detected predetermined condition.

Method and system for customizing alert messages

A method and computer-readable-medium for installing a patch to a computer application program based on the criticality of the patch and the execution format of the computer application are disclosed. An installer program installs application programs. The installer program also-stores related information, including an execution format, in a configuration database. The execution format is either Run-Locally or Run-From-Source. If the execution format is Run-From-Source, the application or features that are designated as Run-From-Source are read-only and are executed from a source, such as from a CD-ROM. Since Run-From-Source executions run from a read-only source, patches cannot be directly applied. When a patch is authored, information as to the criticality of the patch is stored with the patch. Preferably, the criticality is specified based on a feature. When an installer program applies a patch, the installer program queries the execution format. Any features that are Run-Locally can be patched. If a feature is Run-From-Source, a query is made as to whether the feature is critical. If the patch is critical for a feature, the feature is installed, the execution format is changed to Run-Locally, and the patch is applied. If the patch is not critical for a Run-From-Source feature, the patch is not applied. The configuration database is updated during processing to reflect what features have been patched, and what features have not been patched.

Method for installing a patch based on patch criticality and software execution format

Manipulating an object that is dependent upon one or more cells in a spreadsheet is facilitated by manipulating indicators that bound the relevant cells. The object can be a spreadsheet cell formula that contains a reference to one or more cells. The object can also be a graph object that is dependent upon one or more cells. In response to the selection of one of the objects, an indicator is displayed proximate to the cell or cells that the object is dependent upon. If the selected object is dependent upon multiple ranges of cells, then multiple indicators are displayed. Each indicator is displayed proximate to a cell or range of cells for the purpose of highlighting or identifying that the object is dependent upon that cell or range of cells. The highlighting or identifying is acceptably achieved with on-screen indicators that are color-coded. Each indicator can border a cell or a range of cells that the object is dependent upon. Each indicator can be moved, expanded or contracted so that it includes a different cell or range of cells. The selected object is updated to be dependent upon the cells currently identified by the associated indicator or indicators.

Growing community of inventors

Redmond, WA, United States of America

Darrin N Hatakeda