Microsoft Technology Licensing, LLC

Derik Bjorn Stenerson

Bernhard Kohlmeier

Victor Poznanski

Shikha Devesh Desai

Suzan Marashi

Theresa Ann Estrada

Sian Elizabeth Lindley

Yibing Zhu

Erin M O'Connell

Keith Arthur Fournier, Ii

Robyn Sambo

Harold S Gomez

David Robert Shutt

Benjamin Gustav Wilde

Gary Caldwell

Rolf Arnold Ebeling

Ruth Kikin-Gil

Patrick Michael Gan

Shashi Ranjan

Taili Feng

Sung Joon Won

Prabhat Kumar Pandey

Joan Catharine Weaver

Robin Emily Wakefield

Paul Anthony Scudieri

Jignesh Shah

Sophia Isabel Vennix

Nicholas Michael Simons

Andrew G Bybee

Jade Kessler

Eugene Y Suh

Patrick Davis

Sandhya Vankamamidi

Tobin James Zerba

Niraj Yadav

YuBeen Lee

Sutirtha Saha

Daniel John Niezgocki Chattan

Michael Augustine Tavis

Hongqiao Li

Sneha Jayaprakash

Apurv Suman

Ehud Pardo

Dan Grunspan

Kathleen Anna Cachel

Navneet Singh Kambo

Sharad Sharma

Lin Song

Le Yu

Xiaosong Yang

Riyang Liu

Hao Mi

HongQiao Li

Seok Woo John Kim

Denis Seniuc

Kalmadi Santhosh Rao

Ramesh Prasad Pandey

Kulo Rajasekaran

Abhishek Kumar Gupta

Dheeraj Agarwal

Zachary Burstain

Maria Isabel-Rodriguez Carpenter

Erin M O'CONNELL

An in-application search service receives a query from a user attempting to locate information within a document. If a current index and current vector table do not exist, a content indexing service produces an index and a vector table based on the current content of the document. The vector table is based on semantic models that have been pre-trained. The query is tokenized and one of three different processing paths are taken based on the length of the tokenized query. For a single term query, a semantic search and prefix search are performed and the results are combined. If the length of tokenized query exceeds a threshold, a semantic search produces the results. Otherwise, search results are produced based on both prefix fanout and semantic fanout. Results are deduplicated, snippets are extracted, and the results and/or snippets are presented to the user.

Smart find for in-application searching

A method and system for providing one or more suggested application features to a user of an application may include receiving an indication of a user action in a document, accessing contextual document data associated with the document, providing at least one of information about the user action or the contextual document data as input to a machine-learning (ML) model to predict a desired intent for the document, obtaining the predicted desired intent as an output from the ML model, identifying based on the predicted desired intent one or more application features that fulfil the desired intent, and providing data about the one or more application features for display.

Intelligent feature identification and presentation

Described herein is a system and method for displaying annotation(s) of an electronic document. User input to review (e.g., scroll) the electronic document is received, until a selected portion of the electronic document is displayed within a viewport pane of a display. In response to the review input, annotation(s) (e.g., comment(s), comment thread(s), annotation thread(s)) anchored within the selected portion of the electronic document displayed within the viewport pane are identified. Which annotation of the annotation(s) to visually distinguish for a focus of the user is determined. The identified annotation(s) are displayed in an annotation pane, with the determined annotation visually distinguished (highlighted) for the focus of the user. In some embodiments, the anchor associated with the determined annotation is also visually distinguished to provide a contextual link to the user and/or hint(s) that provided a visual signal of annotation(s) associated with an anchor on a particular line are displayed.

Top-align comments: just-in-time highlights and automatic scrolling

Non-limiting examples of the present disclosure relate to fidelity management of an exemplary notecard item based on action(s) for movement that may re-locate notecard item(s) across any of: different content portions of a digital document, different digital documents of an application/service and digital documents of different applications/services. Specific data (and metadata) is collected and analyzed to enable determination of a level of fidelity for rendering of a notecard item, where a representation of a notecard item is generated to fit a context of a digital document in which the notecard item is being placed. A representation of a notecard item may be rendered at a first level of fidelity in one context but a different level of fidelity when the notecard item is moved to a different context. In other instances, evaluation of a notecard item yields a determination to maintain fidelity after an action that re-locates a notecard item.

Fidelity management and transformation of notecard items

A move hint for selecting and moving content is provided. When content is selected, a move option is displayed in a context menu. A user can select the move option to move the selected content to another location in the same document or in a different document. Selecting the move option removes the selected content, and a move hint is displayed at the location where the content was removed. The move hint provides a visual clue of what is removed from the content. To insert the removed content, the user is enabled to select an insertion point and then select the move hint. On placement of the insertion point, the move hint is available to give the user a visual clue as to what will be moved to that location. Responsive to the selection of the move hint, the removed content is inserted into the document at the insertion point.

Select and move hint

Non-limiting examples of the present disclosure relate to creation and management of exemplary notecard items that are reusable in different contexts and across different applications/services. Exemplary notecard items may be created and presented through a user interface of an application/service. A notecard item is individual, self-contained digital data object that provides content to supplement a digital document. Exemplary notecard items live outside of an application/service, in which the notecard item is created or used, where a notecard item may be linked to a digital document but also exists as a separate object. For instance, an exemplary notecard file may be created for management of a created notecard item, where the notecard file is stored in one or more data storages (e.g., a local cache of a computing device and/or a distributed data storage) that is accessible by applications/services.

Creation of notecard items and association with digital documents

Inline command functionality for automatically sharing a document with user access permissions is provided. Automatic sharing of a document is performed in response to a trigger entry within the document. When a trigger entry and a user identifier entry is received, an auto-share system automatically resolves user access permissions in the background, detects sharing permissions, and shares the document with user access permissions without requiring the user who is sharing the document to manually input data. A notification is provided to the sharing user informing the user that the document is being shared, and another notification is provided to the user with whom the document is being shared including a link to the document. If the document was unintentionally shared, the sharing user is enabled to select the notification, and quickly and easily make modifications to the user access permissions for the document.

Automatically sharing a document with user access permissions

Collaboration cards are provided to enable people to collaborate and receive instant replies to comments or questions from anywhere in a collaboratively generated document. A collaborator may add somebody's name to a collaboration card and ask that person for information, for example. That person may receive the question/comment via an email, a text message, a posting, or comparable communication methods, and respond back with the requested information through the same communication channel or another communication channel. The replied content may be placed into the collaboration card created in the document, and the original sender may be enabled to accept a change to the document content based on the collaboration card.

Collaboration cards for communication related to a collaborated document

Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

Managing recurring appointments

Users are enabled to quickly and easily associate records representing entities such as themselves, other users, contacts, accounts, teams/groups, and similar ones employing a record of the association and assign each entity a role or other attributes as a part of this association. Relationship records and attributes preserving entity association information allow teamwork, communication, and collaboration for effective management of business processes. The records and attributes also enable visualization and facilitate deeper understanding of the relationships between people, data, and business processes.

Creating ad hoc relationships between entities

The present invention describes the scheduling requirements if a business to an automatic scheduling system in a way which allows efficient automatic scheduling of appointments for resources of the business. In one embodiment, the scheduling system schedules the resources based not only on total capacity, but based on how many appointments can be initiated at a given time.

Resource-based capacity scheduling system

Growing community of inventors

Redmond, WA, United States of America

Derik Bjorn Stenerson