Microsoft Technology Licensing, LLC

Maura FitzGerald

Nathan Fink

Dustin G Friesenhahn

Nithya Ramkumar

Ethan Gur-esh

Manoj Sharma

Douglas Lane Milvaney

Lidiane Jones

Matt McNeill

Joshua Jones

Andrew W Harris

Thomas McNeill

Ethan D Lexington

Aspects of the present disclosure relate to systems and methods for merging versions and activities associated with a file into a history feed and displaying the history feed on a user interface of a client computing device. In one aspect, a file is identified and activities associated with the file are also identified. It may be determined whether the file has at least one activity. When it is determined that the file has at least one activity, at least one actionable history element for the at least one activity is generated. Additionally, the generated history elements are merged to generate a history feed. The history feed is displayed on a user interface. The history feed may be displayed with an application that has opened the file.

Merged and actionable history feed

Document version discoverability and persistence are provided. A version history of a document includes snapshots of the document as it is created and edited over time. When a version history for a document is invoked, a list of the previous versions of the document is generated for display. Certain versions may be more important to a user. Upon selection of a version, an option to append identification metadata to the selected version is displayed. Received text input is appended to the version of interest, and stored as identification metadata. When a user subsequently selects to view the version history of the document, the identification metadata are displayed with the version of interest, enabling the user to quickly and easily identify the version of interest. Additionally, the version of interest is prioritized, ensuring that it is persisted and not purged when older versions are removed from storage.

Document version of interest discoverability and persistence

Various technologies and techniques are disclosed for creating and managing persistent document collections. A data store is used for storing one or more persistent document collections. A content management application is used for managing documents for users, for creating one or more persistent document collections of a sub-set of the documents upon user request, and for storing the one or more persistent document collections in the data store. Users can create one or more persistent document collections from a sub-set of the documents. Users can also modify the one or more persistent document collections. A requested portion of one or more persistent document collections can be output upon request from an external application so that the external application can download one or more of the documents that are represented by the persistent document collection for further modification by the user.

Techniques for managing persistent document collections

To enable prompt presentation of a user interface that displays documents that other users have accessed or edited, distribution of document activity indicators is performed in a proactive manner such that the document activity indicators are already available at a time when such a user interface is to be presented. Document activity triggers the creation of corresponding document activity identifiers, which are distributed to the workspaces of one or more users in accordance with document activity itself, the type of activity, the user performing the activity, a user who initially created the document, or combinations thereof. When another user utilizes a content creation computer application program, the activity by other users is selectively reflected within the user interface presented by such a content creation computer application program.

Proactive staged distribution of document activity indicators

Growing community of inventors

Swampscott, MA, United States of America

Maura FitzGerald