Microsoft Technology Licensing, LLC

John Lincoln DeMaris

Alexandru Dan Burst

Janet Longhurst

Alin Sirbu

Zachary J Shallcross

Steve Rayson

Dieter P Jansen

Tejas Pravin Mehta

Michael Robert Van Waardhuizen

Mary Ellen Arndt

Sooraj Ashutosh Purandare

Wenvi Hidayat

Mary David Pasch

Benjamin N Truelove

Victor Poznanski

Carlos G Perez

Jeremy Mazner

Melissa Torres

Dmitriy Meyerzon

Nikita Voronkov

Omar H Shahine

Zhenguang Chen

Frederico A Mameri

Constantin Stanciu

Aditi Mandal

Anthony Lawrence Jackson

Nicholas Anthony Buelich, Ii

Ajey Pankaj Shah

Kristofer D Hoffman

Kerem Yuceturk

Michael Brandon Silverstein

Yubo Jia

David Timothy Chan

Adam Ford

Yimin Wu

Sujata Suresh Adgaonkar

Elias David Block

Christopher F McNulty

Kathryn Bergina Dramstad

Dwayne Wensley Ricardo Codrington

Alexandra Leewon Schultz

Onur Dagci

Kenneth Charles LaToza

Kirill Novichikhin

Melissa Torres Acosta

Techniques are described herein that are capable of iteratively updating a collaboration site or a template that may be used to create a new collaboration site. The collaboration site or the template may be updated to include new features based on (e.g., based at least in part on) a likelihood that the new features will be valuable to users. The likelihood that new features will be valuable to the users may be determined (e.g., derived) using heuristics, machine learning, intelligent user experiences, and/or an understanding of user behavior gathered by a service that provides the collaboration site or the template. The likelihood may be compared to a likelihood threshold to determine whether the collaboration site or the template is to be updated. In accordance with this example, the update may be made if the likelihood is greater than or equal to the likelihood threshold.

Iteratively updating a collaboration site or template

Systems, components, devices, and methods for privately editing shared files in a collaborative space are provided. A non-limiting example includes a server computing device for allowing a user to privately edited shared files in a collaborative space. The server computing device includes an interface engine configured to generate a user interface. The user interface includes a listing of a plurality of shared files accessible in the collaborative space and an edit privately control to privately edit an identified shared file of the plurality of shared files. When the edit privately control is actuated, the server computing device generates a personal copy of the identified shared file and updates metadata associated with the identified shared file to indicate that the personal copy has been generated.

Private editing of shared files

A system and method for management of remote metadata-based activities while accessing electronic content via a local application. The system is configured to receive a user input that triggers a signal for communicating with a remote server. The remote server can provide options to the client system that are related to or based on metadata for the currently viewed electronic content. The disclosed system and method significantly improve efficiency and ease-of-use for document development and synchronization systems.

Remote access of metadata for collaborative documents

Techniques directed to applying metadata to content items are described herein. The techniques may include displaying a graphical element associated with a metadata attribute(s) and displaying a visual representation for a content item(s). The graphical element may be associated with a group of content items that have a common metadata attribute. In some instances, the graphical element may be dragged and dropped onto the visual representation to associate the content item(s) with the metadata attribute(s). In other instances, the visual representation may be dragged and dropped on the graphical element to associate the content item(s) with the metadata attribute(s).

Using drag and drop to apply metadata

Techniques are described herein that are capable of intelligently updating a collaboration site or a template that may be used to create a new collaboration site. The collaboration site or the template may be updated to include new features based on (e.g., based at least in part on) a likelihood that the new features will be valuable to users. The likelihood that new features will be valuable to the users may be determined (e.g., derived) using heuristics, machine learning, intelligent user experiences, and/or an understanding of user behavior gathered by a service that provides the collaboration site or the template. The likelihood may be compared to a likelihood threshold to determine whether the collaboration site or the template is to be updated. In accordance with this example, the update may be made if the likelihood is greater than or equal to the likelihood threshold.

Intelligently updating a collaboration site or template

An item is shared based on an information boundary and access control settings. An application such as a document management application detects a selection of an information boundary to manage a sharing action associated with the item. The information boundary includes rules to define how the item is shared. A selection of an access control list is also detected to manage recipients who have an access to the item. The access control list allows a recipient in the list an ability to search and discover the item. In response to a detection of the sharing action to share the item, the information boundary and the access control list is applied to the item. The item is then shared based on the information boundary and the access control list through a link of the item transmitted to a recipient.

Item sharing based on information boundary and access control list settings

In one example, an activity feed server may describe events in a project by collecting events from across multiple services into an activity feed personalized to the user. The activity feed server may store an event set describing activities related to the project. The activity feed server may rank a mature event set from the event set of events older than a period matching a processing delay based on a relevance weighting for a user to generate a curated event list. The activity feed server may queue a recent event set of events younger than the processing delay in chronological order to generate a recent event list. The activity feed server may generate an event list having the curated event list and the recent event list. The activity feed server may send the activity feed having the event list to a client device for presentation to the user.

Personalized aggregated project team activity feed

Providing an automatic detection and an optimization of user experience upgrades based on detected customization may be described. A new version of an application may be executed on a computing device in conjunction with a detection services. The new version of the application may include user experience changes. Customizations associated with a user experience of a previous version of the application for users may be determined. In response to a determination that at least one customized feature of the previous version of the application is incompatible with the new version of the application, the user experience of the previous version of the application may be provided to the users. In response to a determination that the customizations of the previous version of the application are compatible with the new version of the application, the user experience of the new version of the application may be provided to the users.

Providing automatic detection and optimization of user experience upgrades based on detected customization

A notification based on a destination of a file operation is provided. A file management service initiates operations to provide the move notification upon detecting the move operation to move the file from a source location to a destination location. A stakeholder is identified with an access to the destination location prior to executing the move operation to move the file from the source location to the destination location. After executing the move operation, a move notification is generated to inform the stakeholder of the move operation. The move notification provides information such as a description of the file, the source location, the destination location, and/or an identification of an initiator of the move operation. Furthermore, the move notification is transmitted to the stakeholder.

Providing notification based on destination of file operation

Techniques are described herein that are capable of using relevant objects to add content to a collaborative repository. The relevant objects are selected from URI-addressable objects based on each relevant object satisfying one or more relevance criteria. The relevant objects are recommended via a user interface. A determination is made that a specified relevant object is selected from the relevant objects. In one example, the content may be added to (e.g., created in) the collaborative repository based on the specified relevant object. In another example, the specified relevant object may be used to represent a new object type in a new content menu. For instance, the new object type may be selectable to cause an object of the new object type to be created in the collaborative repository.

Using relevant objects to add content to a collaborative repository

A collaboration service is disclosed that hosts various collaboration sites. Each of the sites includes desktop pages and mobile pages. A routing service redirects mobile requests for the desktop pages to the mobile pages in accordance with a desktop-to-mobile mapping that defines an unbalanced correspondence between the desktop pages and the mobile pages. The routing service also redirects desktop requests for the mobile pages to the desktop pages in accordance with a mobile-to-desktop mapping that defines a balanced correspondence between them desktop pages and the mobile pages.

Unbalanced mapping between desktop and mobile pages

Embodiments are provided to maintain templates associated with a client. New and updated templates can be provided to the client and accessed by a user. In an embodiment, a system can be configured to automatically update locally stored templates with updated templates associated with a library. The updated templates can replace or be used to update the locally stored templates and be used by an application user. In one embodiment, a client can be configured to automatically initiate an update process to retrieve and/or receive new and updated templates from an associated document library. The update process can also be used to provide additional information associated with a template, such as metadata describing aspects of an associated template.

Discovering and updating templates

Growing community of inventors

Seattle, WA, United States of America

John Lincoln DeMaris