Tracking content attribution in online collaborative electronic documents

By generating a lightweight attribution model on the collaborative electronic document server and tracking attribution information, the problems of attribution information tracking delay and resource consumption in collaborative electronic document are solved, and efficient presentation of attribution on client devices is achieved The ability to information.

CN112654995BActive Publication Date: 2024-11-08GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980057904.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-04-08
Publication Date
2024-11-08
Estimated Expiration
2039-04-08

AI Technical Summary

Technical Problem

The prior art has problems of delay and resource consumption when tracking attribution information of content in collaborative electronic documents, especially when identifying and retrieving the correct attribution information of coordinate positions, and it is difficult for user equipment to retrieve and present it by the user. attribution information as part of the collaborative electronic document.

Method used

Receive change requests through a server hosting collaborative electronic documents, apply changes to the server model, and generate a lightweight attribution model to track attribution information, including revision identifiers associated with coordinate locations, reduce resource consumption, and in the customer Attribution information is presented at the end device.

Benefits of technology

Reduces the delay in determining the attribution information of the coordinate position and reduces the consumption of computing and storage resources, allowing the user equipment to provide attribution information as part of the collaborative electronic document selected by the user.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112654995B_ABST
    Figure CN112654995B_ABST
Patent Text Reader

Abstract

An indication of a first change is received at a first coordinate location of a client model of a collaborative electronic document. The first coordinate location is within a coordinate structure of the collaborative electronic document. The first change is applied at a second coordinate location of a server model of the collaborative electronic document. The first change is associated with a first revision identifier. An attribution model is generated, the attribution model including a coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document and including a third coordinate location corresponding to the first coordinate location and the second coordinate location. The third coordinate location of the attribution model is updated with the first revision identifier. Attribution information for the first change is stored in association with the first revision identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects and embodiments of the present disclosure relate to electronic documents, and more particularly, to generating an attribution model to track attribution information for content in a collaborative electronic document and to provide the attribution information for presentation at a client device. Background Art

[0002] Electronic document processing applications (e.g., word processing applications, spreadsheet applications, presentation applications) can be used to manipulate (e.g., create, edit, view, print, etc.) electronic documents. When editing an electronic document, a user changes the content of the electronic document by removing text, typing new text, or otherwise changing the content of the electronic document. Summary of the invention

[0003] An aspect of the present disclosure provides a method, comprising: receiving, by a server hosting a collaborative electronic document, an indication of a first change at a first coordinate location of a client model of the collaborative electronic document, wherein the first coordinate location is within a coordinate structure of the collaborative electronic document; applying the first change at a second coordinate location of a server model of the collaborative electronic document, wherein the second coordinate location of the server model corresponds to the first coordinate location of the client model, and wherein the first change is associated with a first revision identifier; generating an attribution model, the attribution model including a coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document and including a third coordinate location corresponding to the first coordinate location and the second coordinate location; updating the third coordinate location of the attribution model with the first revision identifier; and storing attribution information for the first change in association with the first revision identifier.

[0004] Some optional features that may form part of the method are as follows. The method may include receiving an attribution query from a client device, the attribution query requesting the attribution information associated with a first coordinate position of the client model of the collaborative electronic document. The method may include identifying the first revision identifier associated with a third coordinate position of the attribution model using a coordinate identifier of the first coordinate position of the client model of the collaborative electronic document. The method may include retrieving the attribution information associated with the first revision identifier from a data store. The method may include providing the attribution information to the client device in response to the attribution query. The indication of the first change at the first coordinate position of the client model of the collaborative electronic document may be provided with a command having a command type. The method may further include determining whether the command type of the command satisfies a command type condition, wherein the attribution model is generated in response to determining that the command type of the command satisfies the command type condition. The attribution information may include an indication of a user account associated with the first change and a timestamp associated with the first change. The method may include storing a revised copy of the server model of the collaborative electronic document having the first change at the second coordinate position, wherein the revised copy is associated with the first revision identifier. Generating an attribution model including the coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document and including the third coordinate position corresponding to the first coordinate position and the second coordinate position may include generating the attribution model including a coordinate structure smaller than the coordinate structure of the collaborative electronic document. The method may include receiving a command from a client device indicating a change to the coordinate structure of the collaborative electronic document. The method may include applying, by the server, the change to the coordinate structure of the collaborative electronic document, wherein the change to the coordinate structure of the collaborative electronic document is associated with a second revision identifier. The method may include modifying the coordinate structure of the attribution model to reflect the change to the coordinate structure of the collaborative electronic document, wherein a position of content of the attribution model is adjusted in view of the modified coordinate structure of the attribution model. The method may include storing a revised copy of the server model of the collaborative electronic document having the change to the coordinate structure of the collaborative electronic document, wherein the revised copy including the change to the coordinate structure is associated with the second revision identifier. The method may include suppressing updating the third coordinate position of the attribution model with the second revision identifier. The method may include.The step of updating the third coordinate position of the attribution model with the revision identifier may further include: updating the third coordinate position of the attribution model with the coordinate identifier of the third coordinate position, wherein the content of the third coordinate position of the attribution model is moved to the fourth coordinate position of the attribution model in view of the adjusted coordinate structure of the attribution model. The method may include receiving, by the server, a command indicating a second change at a fifth coordinate position of the client model of the collaborative electronic document. The method may include applying the second change at a sixth coordinate position of the server model of the collaborative electronic document according to the command, wherein the sixth coordinate position of the server model corresponds to the fifth coordinate position of the client model, and wherein the second change is associated with the third revision identifier. The method may include updating the fourth coordinate position of the attribution model with the second updated revision identifier and the coordinate identifier of the fourth coordinate position. The method may include storing attribution information for the second change in association with the third revision identifier in a data store. The method may include receiving, from a client device, a request for the attribution information associated with the fifth coordinate position of the client model of the collaborative electronic document. The method may include identifying the first revision identifier, the third revision identifier, and the coordinate identifier of the third coordinate location associated with a fourth coordinate location of the attribution model using the coordinate location of the fifth coordinate location of the client model of the collaborative electronic document. The method may include retrieving the attribution information associated with the third revision identifier. The method may include retrieving a first revised copy of the server model of the collaborative electronic document using the first revision identifier. The method may include identifying the first change at a second coordinate location of the server model of the collaborative electronic document using the coordinate identifier of the third coordinate location of the attribution model. The method may include providing the attribution information to the client device in response to the request, wherein the attribution information includes the first change.

[0005] One aspect of the present disclosure provides a method, comprising: receiving, via a graphical user interface (GUI) presented at a client device, a user selection of a portion of a client model of a collaborative electronic document, wherein the collaborative electronic document is hosted by a cloud-based document editing system, and wherein the collaborative electronic document is concurrently editable by a plurality of users including the user; receiving a user request for attribution information of changes to content within the portion of the client model selected by the user among the plurality of users; and in response to receiving the user request for the attribution information, presenting, via a graphical user interface element in the GUI, the attribution information including a user account identifier of a user who made changes to content of the portion of the client model of the collaborative electronic document.

[0006] Some optional features that may form part of the method are as follows. The collaborative electronic document may include a collaborative spreadsheet document having a collaborative structure including one or more rows and one or more columns, wherein the portion of the client model of the collaborative electronic document selected by the user includes a cell of the collaborative spreadsheet document. Optionally, none of the multiple users may have invoked a command to track changes applied to the portion of the collaborative electronic document. The method may include, in response to receiving the user request for the attribution information; sending an attribution query to the cloud-based document editing system requesting the attribution information, wherein the attribution query includes a coordinate identifier of a first coordinate location, wherein the coordinate identifier identifies the portion of the client model of the collaborative electronic document. The method may include receiving, via the graphical user interface, a subsequent user request for additional attribution information for another change to the content within the portion of the client model selected by the user of the multiple users. The method may include, in response to receiving the subsequent user request for the additional attribution information, presenting the additional attribution information at the graphical user interface element in the GUI, the additional attribution information including a user account identifier of a user who provided the other change to the content of the portion of the client model of the collaborative electronic document.

[0007] Another aspect of the present disclosure provides a system, comprising: a memory; and a processing device, the processing device being coupled to the memory, the processing device performing a method according to any aspect or embodiment described herein. Another aspect of the present disclosure provides a computer program product (such as a tangible computer-readable medium or software product that can be downloaded without having to be stored in a non-transitory manner), the computer program product comprising instructions, the instructions being responsive to execution of a processing device, causing the processing device to perform operations including the method according to any aspect or embodiment described herein.

[0008] Some optional features that may be incorporated into the system are as follows. The processing device may be configured to receive an attribution query from a client device, the attribution query requesting the attribution information associated with a first coordinate position of the client model of the collaborative electronic document. The processing device may be configured to use the coordinate identifier of the first coordinate position of the client model of the collaborative electronic document to identify the first revision identifier associated with a third coordinate position of the attribution model. The processing device may be configured to retrieve the attribution information associated with the first revision identifier from a data store. The processing device may be configured to provide the attribution information to the client device in response to the attribution query. The processing device may be configured such that an indication of the first change at the first coordinate position of the client model of the collaborative electronic document is provided with a command having a command type. The processing device may be configured to determine whether the command type of the command satisfies a command type condition, wherein the attribution model is generated in response to determining that the command type of the command satisfies the command type condition. The processing device may be configured to store a revised copy of the server model of the collaborative electronic document having the first change at the second coordinate position, wherein the revised copy is associated with the first revision identifier. The processing device may be configured to receive a command from a client device indicating a change to a coordinate structure of the collaborative electronic document. The processing device may be configured to apply the change to the coordinate structure of the collaborative electronic document, wherein the change to the coordinate structure of the collaborative electronic document is associated with a second revision identifier. The processing device may be configured to modify the coordinate structure of the attribution model to reflect the change to the coordinate structure of the collaborative electronic document, wherein a position of content of the attribution model is adjusted in view of the modified coordinate results of the attribution model. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The aspects and embodiments of the present disclosure will be more fully understood through the detailed description given below and the accompanying drawings of various aspects and embodiments of the present disclosure, however, they should not be understood as limiting the present disclosure to specific aspects or embodiments, but are only for explanation and understanding.

[0010] Figure 1 An example of a system architecture according to an embodiment of the present disclosure is illustrated.

[0011] Figure 2A is a diagram of operations for generating an attribution model according to an embodiment of the present disclosure.

[0012] Figure 2B is a diagram of operations for updating an attribution model according to an embodiment of the present disclosure.

[0013] Figure 2Cis a diagram of operations for updating an attribution model according to an embodiment of the present disclosure.

[0014] Figure 2D is a diagram of operations for updating an attribution model according to an embodiment of the present disclosure.

[0015] Figure 3A is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure.

[0016] Figure 3B is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure.

[0017] Figure 3C is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure.

[0018] Figure 3D is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure.

[0019] Figure 4 is a diagram of operations for providing attribution information to a client device in accordance with an embodiment of the present disclosure.

[0020] Figure 5 is a diagram illustrating a system that provides attribution information to a client device according to an embodiment of the present disclosure.

[0021] Figures 6A-6C is a diagram illustrating a server model and an attribution model for providing previous content of a collaborative electronic document to a client device according to an embodiment of the present disclosure.

[0022] Figure 7 is a diagram of operations for providing attribution information of previous content comprising a portion of a collaborative electronic document to a client device according to an embodiment of the present disclosure.

[0023] Figures 8A-8B Illustrated is a graphical user interface that allows a user to retrieve attribution information according to an embodiment of the present disclosure.

[0024] Fig. 9 is a flow chart illustrating a method for generating an attribution model to track attribution information of content in a collaborative electronic document and providing the attribution information to a client device according to an embodiment of the present disclosure.

[0025] Fig.10 is a flow chart illustrating a method for presenting attribution information at a user device according to an embodiment of the present disclosure.

[0026] Fig.11 A block diagram depicts an example computing system operating in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0027] Electronic documents may refer to media content used in electronic form. Media content may include text, tables, videos, audio, images, graphics, slides, charts, software programming codes, designs, lists, plans, blueprints, maps, etc. Electronic document processing applications (e.g., word processing applications, electronic spreadsheet applications, presentation applications) may be used to manipulate (e.g., create, edit, view, print, etc.) electronic documents. Electronic document processing applications may be local applications hosted by user devices to manipulate local electronic documents stored on user devices. Alternatively, electronic document processing applications may be provided remotely from client devices, for example, electronic document processing applications may be provided by a cloud-based management platform operating in a cloud-based environment, which may enable users to store data files on one or more servers in a cloud-based environment, thereby synchronizing data files across various devices of users, and sharing data files with one or more other users. In some cases, a cloud-based content management platform may provide users with a single location for managing data files. A cloud-based content management platform may enable the author of an electronic document to invite other users as collaborators to join an electronic document stored at a cloud-based platform. In this document, an electronic document to which users have been granted concurrent access or editing rights may be referred to as a collaborative document.

[0028] A collaborative electronic document may have a coordinate structure. A coordinate structure may refer to an organization of objects. A coordinate structure allows for the use of coordinate identifiers to identify elements or locations within the coordinate structure. For example, a coordinate structure may include a number of coordinate locations, each of which may be identified by a coordinate identifier. For example, a collaborative spreadsheet document may have a coordinate structure that includes a plurality of rows and a plurality of columns organized in a particular manner such that each cell may be identified by a row coordinate and a column coordinate.

[0029] The collaborative electronic document may be edited by multiple users concurrently or at different times. Each user of the collaborative electronic document may have a local model of the collaborative electronic document (e.g., a client model) at the client device of the corresponding user. The cloud-based document editing system may also include a local model of the collaborative electronic document (e.g., a server model). As the users of the collaborative electronic document modify the collaborative electronic document, the cloud-based document editing system and the client device work together to synchronize the local model at the corresponding client device with the local model at the cloud-based document editing system.

[0030] The cloud-based document editing system may implement a revision scheme that assists in synchronization between local models of collaborative electronic documents. The revision scheme may save a collaborative electronic document (or changes to a collaborative electronic document) as multiple revisions (e.g., versions), each of which captures the state of the collaborative document at a given instance. For example, when a user changes a corresponding local model of a collaborative electronic document, the user's client device may send a change request to the cloud-based document editing system. The change request may indicate one or more of the change type, change value, change location, and current revision number (e.g., revision 1) of the local model. In response to the change request, the cloud-based document editing system may update the server model of the collaborative electronic document so that the server model reflects the latest changes. The cloud-based document editing system may also save a revised copy of the updated server model of the collaborative electronic document and associate the revised copy with a revision identifier, such as the current revision (e.g., revision 1). After updating the server model, the cloud-based document editing system may increase the revision number of the server model (e.g., revision 2). The cloud-based document editing system may send a confirmation to the client device that has submitted the change request that the change has been applied to the server model. In response to receiving the confirmation, the client device may increase the revision number of the local model (Revision 2). The cloud-based document editing system may send the changes to other client devices. The other client devices may update their corresponding local models with the changes and increase the current version number (Revision 1) to the next revision (Revision 2). As a result, the cloud-based document editing system and the client have synchronized the content of the collaborative electronic document. If any user enters another value in the corresponding local model of the collaborative electronic document, the process may be repeated.

[0031] The number of revisions to a particular collaborative electronic document may be numerous throughout the lifecycle of the document. For example, in order to provide real-time changes to various client devices, the changes sent in the change request may be atomic. For example, each word or even each character may be sent to the cloud-based document editing system in a discrete change request. For each change request, the cloud-based document editing system may apply the atomic changes and save a revised copy of the collaborative electronic document with the atomic changes.

[0032] Each revision of a collaborative electronic document may be associated with attribution information (e.g., metadata). Attribution information may refer to information that attributes an action (e.g., editing) on ​​a collaborative electronic document to a particular user, author, or device, or information that provides context for an action. For example, attribution information for a revised copy of a collaborative electronic document may include one or more of the author of the change, a timestamp indicating when the cloud-based document editing system applied the change to the server model, a previous value before the change, information in the change request, and the like.

[0033] Tracking attribution information for content in a collaborative electronic document throughout its lifecycle, identifying the correct attribution information for a particular coordinate location, and providing the attribution information for presentation at one or more client devices is a beneficial service, but presents some challenges.

[0034] In some systems, in order to identify the correct attribution information (such as author and time) for a specific location of a collaborative electronic document (such as a specific cell in a collaborative spreadsheet document), the system can load each of the revised copies of the collaborative electronic document starting from the most recent revision, and check a specific portion of the revised copy to determine whether the specific portion has been modified. If it is determined that the specific portion of the revised copy has not been modified, the system proceeds to the next most recent revision until the system finds a revision that modifies the specific portion. Once the revision that modifies the specific portion is found, the associated revision identifier can be used to retrieve the corresponding attribution information. The aforementioned process is slow (e.g., several minutes) and consumes a large amount of computing, memory, and storage resources.

[0035] In addition, it may also be challenging to track attribution information of content in a collaborative electronic document during the life cycle of the collaborative electronic document, identify the correct attribution information for a specific coordinate location, and provide the attribution information for presentation at one or more client devices, because a specific location in the collaborative electronic document may not be associated with a universally unique identifier, and the specific location and the content therein may change and move throughout the life cycle of the collaborative electronic document. For example, a user may edit a specific cell of a collaborative spreadsheet document. A cell and its content may move multiple times and may be edited multiple times throughout the life cycle of a collaborative spreadsheet document. For example, one or more other users may modify a collaborative spreadsheet document by adding columns or deleting rows, which may cause the cell and its content to move in the collaborative spreadsheet document. The user may also change the value in the cell before and after the cell moves. In this way, locating a specific cell in each revision of the collaborative spreadsheet document and determining the attribution information of the specific cell in each revision of the collaborative spreadsheet document may be a computationally intensive and lengthy process.

[0036] Aspects of the present disclosure address the above and other challenges by generating (e.g., dynamically generating) an attribution model to track attribution information for content throughout the lifecycle of the attribution model, identifying attribution information associated with coordinate locations using the attribution model, and providing the attribution information for presentation at one or more client devices. In an embodiment, the attribution model can be a lightweight index that tracks attribution information by coordinate locations as the collaborative electronic document moves throughout its lifecycle and its content changes.

[0037] In some embodiments, a server hosting a collaborative electronic document receives a change request. The change request may include an indication of a change to a coordinate position of a client model of the collaborative electronic document (e.g., as part of a command). In response to receiving the change request, the server may apply the change to a corresponding coordinate position of a server model of the collaborative electronic document. The server may store a revised copy of the server model including the latest changes and associate the revised copy with the current revision number. The server may also store attribution information and associate the attribution information with the current revision number. The server may generate (e.g., dynamically generate) an attribution model to track the attribution information. The attribution model may have a coordinate structure corresponding to the coordinate structure of the collaborative electronic document and include coordinate positions corresponding to the coordinate positions of the collaborative electronic document to which the changes were entered.

[0038] For example, a collaborative spreadsheet document may have many rows and many columns that intersect to form cells. An attribution model may also have many rows and columns that intersect to form cells. Cells of the collaborative spreadsheet document and cells of the attribution model may have corresponding coordinate identifiers. For example, cell A2 in the collaborative spreadsheet document has a corresponding cell A2 in the attribution model located in an equivalent position.

[0039] In some embodiments, the server may update the corresponding coordinate position of the attribution model with information (e.g., tracking information) that can be used to track attribution information of the content of the collaborative electronic document throughout the life cycle of the collaborative electronic document. The coordinate position of the attribution model corresponding to the coordinate position where the change was applied in the server model of the collaborative electronic document may be associated with a revision identifier of the revised copy of the server model to which the change was applied. In some embodiments, a coordinate identifier (e.g., A2) identifying the coordinate position where the change was entered may be associated with the corresponding coordinate position of the attribution model. If the same coordinate position of the collaborative electronic document is changed at a later time, the tracking information of the corresponding coordinate position of the attribution model may be updated.

[0040] In an embodiment, a server may receive an attribution query requesting attribution information associated with a coordinate position of a client model of a collaborative electronic document. A coordinate identifier identifying the coordinate position of the client model may also be used to identify a corresponding coordinate position of an attribution model. In response to identifying the corresponding coordinate position of the attribution model, the server may retrieve tracking information associated with the corresponding coordinate position of the attribution model. The tracking information may be used to retrieve the requested attribution information.

[0041] For example, a user may request the author and timestamp of a most recent edit at a particular cell in a collaborative spreadsheet document. The server may identify the corresponding cell in the attribution model and retrieve a most recent revision identifier associated with the corresponding cell in the attribution model. The server may use the most recent revision identifier to retrieve attribution information corresponding to the most recent revision identifier and provide the attribution information to the client device. If the user requests attribution information for a second most recent edit of a particular cell in the collaborative spreadsheet document, the server may retrieve the second most recent revision identifier and retrieve the attribution information associated with the second most recent revision identifier.

[0042] In another example, a user may request the value of a cell before a most recent edit. The server may identify the corresponding cell in the attribution model and retrieve a second most recent revision identifier and a coordinate identifier corresponding to a coordinate location in the server model of the collaborative electronic document where the second most recent change was applied. The server may load the corresponding revision copy using the second most recent revision identifier and read the value at the coordinate location identified at the coordinate location, which is the value of the cell before the most recent edit.

[0043] In some embodiments, if the coordinate structure of the collaborative electronic document changes, the coordinate structure of the attribution model can be similarly changed. For example, if a column is added to the collaborative electronic document, the same column can be added to the attribution model. The coordinate position of the attribution model can be shifted accordingly, but the content of the coordinate position of the attribution model cannot be adjusted based on the change in the coordinate structure.

[0044] In some embodiments, a graphical user interface (GUI) may be presented at a client device. A user may select a portion of a collaborative electronic document. For example, a user may select a cell of a collaborative spreadsheet document. A client may request to receive attribution information for the selected portion of the collaborative electronic document. The server may return attribution information, which is presented at a graphical user interface element in the GUI at the client device.

[0045] As noted, the technical problem addressed by embodiments of the present disclosure is the latency in identifying and retrieving the correct attribution information for a coordinate location and providing the attribution information for presentation at a client device or providing the attribution information to other processes or services.

[0046] As also noted, another technical problem addressed by embodiments of the present disclosure is the use of significant computing and storage resources in identifying and retrieving attribution information for a coordinate location by loading a series of revisions to determine which revision includes a change at the coordinate location.

[0047] In addition, another technical problem solved by the embodiments of the present disclosure is that a user device is unable to retrieve and present attribution information of a portion of a collaborative electronic document selected by a user.

[0048] A technical solution to the technical problem identified above may include: receiving, by a server hosting a collaborative electronic document, an indication of a first change at a first coordinate location of a client model of the collaborative electronic document, wherein the first coordinate location is within a coordinate structure of the collaborative electronic document; applying the first change at a second coordinate location of a server model of the collaborative electronic document in accordance with a command, wherein the second coordinate location of the server model corresponds to the first coordinate location of the client model, and wherein the first change is associated with a first revision identifier; generating an attribution model including a coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document and including a third coordinate location corresponding to the first coordinate location and the second coordinate location; updating the third coordinate location of the attribution model by the first revision identifier; and storing attribution information for the first change in association with the first revision identifier.

[0049] A technical solution to the technical problem identified above may include: receiving, via a graphical user interface (GUI) presented at a client device, a user's selection identifying a portion of a client model of a collaborative electronic document, wherein the collaborative electronic document is hosted by a cloud-based document editing system, and wherein the collaborative electronic document is editable concurrently by multiple users; receiving a user request for attribution information for content changes within the portion of the client model selected by the user; and in response to receiving the user request for attribution information, presenting, via a graphical user interface element in the GUI, the attribution information, the attribution information including a user identifier of a user who made a change to content of the portion of the client model of the collaborative electronic document.

[0050] Thus, technical effects may include reducing latency in determining attribution information for a coordinate location and providing the attribution information to a client device or other process or service.

[0051] Further technical effects may include reducing the amount of computational and memory storage resources used to determine attribution information for a coordinate location by loading a series of revisions to determine which revision includes a change at the coordinate location. For example, the technical effect may relate to an attribution model and / or a method of embodying an attribution model, resulting in a smaller, minimized, or acceptably small storage requirement or footprint.

[0052] Additional technical effects may include allowing a user device to provide attribution information for a portion of a collaborative electronic document selected by the user.

[0053] Figure 11 is an example of a system architecture 100 according to an embodiment of the present disclosure. The system architecture 100 includes a cloud-based environment 101 connected to client devices 110A-110Z (generally referred to herein as "client devices 110") via a network 130. Although the system architecture 100 is described in the context of a cloud-based environment 101, which can enable communication between servers 112A-112Z (generally referred to herein as "servers 112") in the cloud-based environment 101 and communication with client devices 110A-110Z via the network 130 to store and share data, it is understood that the embodiments described herein can also be applied to locally interconnected systems. In an embodiment, the cloud-based environment 101 refers to a collection of physical machines that host applications (e.g., word processing applications, spreadsheet applications, slide presentation applications, web page applications, etc.) that provide one or more services (e.g., word processing, spreadsheet processing, slide generation included in a slide presentation, web page processing, etc.) to multiple client devices 110A-110Z via the network 130.

[0054] The network 130 may be a public network (e.g., the Internet), a private network (e.g., a local area network (LAN) or a wide area network (WAN)), or a combination thereof. The network 130 may include a wireless infrastructure that may be provided by one or more wireless communication systems such as a Wireless Fidelity (Wi-Fi) hotspot connected to the network 130 or a wireless carrier system that may be implemented using various data processing equipment, communication towers, etc. Additionally or alternatively, the network 130 may include a wired infrastructure (e.g., Ethernet).

[0055] The cloud-based environment 101 may include one or more servers 112A-112Z and a data store 114. In an embodiment, the data store 114 may store data files 116, collaborative electronic document revisions 117, and attribution information 119. The contents of the data store 114 may be further described in subsequent figures.

[0056] In embodiments, data store 114 may store one or more data files 116, which may include content (e.g., text, data tables, images, video, audio, etc.). In an embodiment, data file 116 may be any suitable data file, including content uploaded to cloud-based environment 101 by client devices 110A-110Z or from a server inside or outside of cloud-based environment 101. In some embodiments, data file 116 may be an attribution model 132 associated with a collaborative electronic document (also referred to herein as a "collaborative document"). In embodiments, data file 116 may be an electronic document, such as a collaborative electronic document that may be shared with or concurrently editable by a user. In embodiments, the term "concurrently editable" may refer to a user concurrently modifying (e.g., adding, deleting, changing, etc.) content (e.g., text, cells, images, data, slides, etc.), concurrently suggesting changes to content, concurrently commenting on content, etc.

[0057] In embodiments, changes to collaborative electronic documents may be provided to or presented on client devices 110A-110Z in real-time. In embodiments, real-time may refer to changes to collaborative electronic documents being transmitted, presented, or displayed to one or more client devices 110 as the changes are made on different client devices. For example, real-time changes (e.g., edits) to collaborative electronic documents may be displayed on a display of client device 110A substantially simultaneously with a user editing the collaborative electronic document using client device 110Z (at least within technical limitations for displaying real-time changes, e.g., a user's edits to a collaborative electronic document may be displayed within milliseconds of the user's input and may appear to the receiving user to be in absolute real-time).

[0058] In an embodiment, the collaborative electronic document can be a collaborative word processing document, a collaborative spreadsheet document, a collaborative slide presentation document, a collaborative web page document, or any suitable electronic document that can be shared with users (e.g., an electronic document including content such as text, data tables, videos, images, graphics, slides, charts, software programming code, designs, lists, plans, blueprints, maps, etc.).

[0059] A collaborative electronic document may be created by an author, and the author may share the collaborative electronic document with other users (e.g., collaborators). Sharing a collaborative electronic document may refer to granting other users permission to access (view and / or edit) the collaborative electronic document. Sharing a collaborative electronic document may include notifying other users of the collaborative electronic document via a message (e.g., an email, a text message, etc.) that includes a link to the collaborative electronic document. The level of permission granted to each user may be based on the user type of each particular user. For example, a user with an editor user type may be able to open a collaborative electronic document and make changes to the collaborative electronic document directly. To this end, numerous collaborators may make changes to the content presented in the collaborative electronic document.

[0060] The servers 112A-112Z may be physical machines (e.g., server machines, desktop computers, etc.) each of which includes one or more processing devices communicatively coupled to memory devices and input / output (I / O) devices. The processing devices may include computers, microprocessors, logic devices, or other devices or processors configured with hardware, firmware, and software to implement some of the embodiments described herein. Each of the servers 112A-112Z may host an attribution module 118A-118Z (generally referred to herein as "attribution module 118"). The attribution module 118A may be implemented as computer instructions that may be executed by one or more processing devices on each of the servers 112A-112Z. The attribution module 118A may perform operations described with respect to the following figures.

[0061] In an embodiment, one or more servers 112A-112Z may provide a collaborative electronic document environment 122A-122Z (generally referred to herein as a "collaborative electronic document environment 122") to client devices 110A-110Z. The server 112A-112Z selected to provide the collaborative electronic document environment 122A-122Z may be based on certain load balancing techniques, service level agreements, performance indicators, etc. The collaborative electronic document environment 122A-122Z may provide a user interface 124A-124Z that displays a collaborative electronic document generated based on content in one or more data files 116. The collaborative electronic document environment 122A-122Z may enable users using different client devices 110A-110Z to concurrently access the collaborative electronic document to review, edit, view, and / or propose changes to the collaborative electronic document in the corresponding user interfaces 124A-124Z.

[0062] In an embodiment, the user interface 124A-124Z may be a web page rendered by a web browser and displayed in a web browser window on the client device 110A-110Z. In another embodiment, the user interface 124A-124Z may be included in a standalone application (also referred to as a "native application" or "native client application") that is downloaded to the client device 110A-110Z and runs locally on the client device 110A-110Z.

[0063] The client devices 110A-110Z may include one or more processing devices that are communicatively coupled to a memory device and an I / O device. The client devices 110A-110Z may be desktop computers, laptop computers, tablet computers, mobile phones (e.g., smart phones), or any suitable computing devices. The client devices 110A-110Z may include components such as input devices and output devices. The servers 112A-112Z may authenticate the user using a username and password (or other identification information) provided by the user via the user interface 124A-124Z, so that the same client device 110A-110Z may be used by different users at different times.

[0064] As discussed above, client devices 110A-110Z can each include a web browser or a native client application. A user who is invited and becomes a collaborator of a collaborative electronic document can request access to the collaborative electronic document via a web browser or a native client application. For example, a user can select a collaborative electronic document from a user interface 124A provided by a cloud-based environment 101 and presented by a web browser or a native client application. To this end, a client device 110A associated with a user can request a collaborative electronic document from a cloud-based environment 101. Collaborative electronic document environments 122A-122Z can enable users to view and / or manage their associated collaborative electronic documents within corresponding user interfaces 124A-124Z.

[0065] The collaborative electronic document environments 122A-122Z may also enable users using different client devices 110A-110Z to simultaneously access the collaborative electronic document to comment on, edit (e.g., modify or suggest changes), or view the collaborative electronic document in corresponding user interfaces 124A-124Z of corresponding collaborative applications (e.g., collaborative slide presentation applications, collaborative word processing applications, collaborative spreadsheet applications, collaborative web applications, etc.) that present the collaborative electronic document.

[0066] In some embodiments, the attribution modules 118B-118Z may be part of the client devices 110A-110Z. For example, in some embodiments, the client devices 110A-110Z may have a locally installed application that includes the attribution modules 118B-118Z to generate (e.g., dynamically generate) an attribution model to track attribution information for content in a collaborative electronic document and provide the attribution information to one or more client devices 110A-110Z. The attribution modules 118B-118Z at the client devices 110A-110Z may be the same or similar to the attribution module 118 at the server 112. In some embodiments, one or more of the data files 116, the collaborative electronic document revisions 117, or the attribution information 119 may be stored locally on the client devices 110A-110Z. In some embodiments, the client devices 110A-110Z may collectively execute the attribution modules 118B-118Z to generate an attribution model to track attribution information of content in a collaborative electronic document, identify correct attribution information for a specific coordinate location, and provide the attribution information to one or more client devices 110A-110Z.

[0067] In some embodiments, the cloud-based environment 101 may execute the attribution module 118A as a whole to generate an attribution model to track attribution information for content in a collaborative electronic document, identify the correct attribution information for a specific coordinate location, and provide the attribution information to one or more client devices 110A-110Z. In other embodiments, the operations of the attribution modules 118A-118Z may be divided among the servers 112A-112Z or the client devices 110A-110Z.

[0068] As described above, a collaborative electronic document may have a coordinate structure. A coordinate structure may refer to the organization of an object. A coordinate structure allows the use of coordinate identifiers to identify an element or position within a coordinate structure. For example, a coordinate structure may include a number of coordinate positions, each of which may be identified by a coordinate identifier. For example, a collaborative electronic spreadsheet document may have a coordinate structure including a plurality of rows and a plurality of columns organized in a particular manner, such that each cell may be identified by a row coordinate and a column coordinate. A coordinate position may refer to an element or position in a coordinate structure. A coordinate position may store content or be associated with content. A coordinate position may be identified by a coordinate identifier (e.g., a row coordinate and a column coordinate). A coordinate identifier may identify a location or position within a coordinate structure, and may reference the location or position of a coordinate position relative to a coordinate structure. A coordinate identifier may change a position within a coordinate structure, and may change the coordinate position of a given element, respectively.

[0069] In an example, a collaborative word processing document may have an array-type coordinate structure. It may be noted that different coordinate structures may be used for the same type of collaborative electronic document, and the foregoing is for illustration only and not limitation.

[0070] In some embodiments, each client device stores a client model of a collaborative electronic document. For example, client device 110A stores client model 125A of a collaborative electronic document, and client device 110Z stores client model 125Z of a collaborative electronic document (generally referred to herein as "client model 125"). When a user edits client model 125 at client device 110, a change request is sent to server 112. The change request may include a command that may describe the type of change, the location of the change (e.g., coordinate location), and the content of the change (if applicable). For example, if a user types a value in a cell of a collaborative spreadsheet document, the command "set cell properties" is sent to server 112 along with the value typed into the cell and the coordinate location of the cell. In an embodiment, changes to client model 124 sent to the server are atomic in nature. For example, each character typed into a collaborative word processing document may be sent as a command to server 112. In another example, the value typed into a cell of a collaborative spreadsheet document may be sent to server 112 as part of a command.

[0071] In an embodiment, server 112A may receive a change request from client device 110A. Server 112A may apply the changes described by the commands in the change request to server model 131 of the collaborative electronic document. In some embodiments, server 112A may retain a copy (e.g., a revised copy) of the current revision (e.g., revision 1) of the collaborative electronic document including the added changes. The revised copy may be stored at data store 114 as part of collaborative electronic document revisions 117 (e.g., revised copy). In an embodiment, the server may store a revised copy of each revision of the collaborative electronic document.

[0072] In an embodiment, after applying the changes to the server model 131 (and in some embodiments, after storing a revised copy of the current revision (e.g., revision 1)), the server 112A increments the revision number associated with the server model 131 (e.g., revision 2). After applying the changes to the server model 131, the server 112 may send a confirmation to the client device 110A indicating that the changes have been applied to the server model 131. It may be noted that the server model 130 may be continuously updated so that it reflects the latest revisions of the collaborative electronic document. The client device 110A may update the revision number associated with the client model 125A so that the server model 131 and the client model 125A are synchronized. The server 112A may also send the changes to the client device 110Z. The client device 110Z may update the client model 125Z based on the changes received from the server 112A, and may also update the revision number associated with the client model 125Z to synchronize the client model 125Z with the server model 130.

[0073] In some embodiments, the server 112 may generate and update an attribution model 132. The attribution model 132 is associated with a particular server model 131 and may be used to track attribution of content in a collaborative electronic document and identify attribution information associated with a particular coordinate location of the collaborative electronic document. The attribution module 132, the operation of the attribution module 118, and the attribution information 119 are further described in conjunction with the following figures.

[0074] In situations where the systems discussed herein collect personal information about a user or may utilize personal information, the user may be provided with an opportunity to control whether the cloud-based environment 101 collects user information (e.g., information about the user's social network, social actions or activities, occupation, user preferences, or the user's current location) or to control whether and / or how content is received from content servers that may be more relevant to the user. In addition, certain data may be processed in one or more ways before it is stored or used so that personally identifiable information is removed. For example, the user's identity may be processed so that no personally identifiable information about the user can be determined, or the user's geographic location may be summarized (such as, summarized to a city, zip code, or state level) where location information is obtained so that the user's specific location cannot be determined. Thus, the user may control how information about the user is collected and used by the cloud-based environment 101.

[0075] Figure 2A is a diagram of operations for generating an attribution model according to an embodiment of the present disclosure. System 200 may include Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 The components can be used to help describe Figure 2A For purposes of illustration and not limitation, operations of system 200 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or any combination thereof, unless otherwise specified. For purposes of illustration and not limitation, operations of system 200 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or any combination thereof. Figure 2A The operations described are shown to be performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, less or more operations can be performed in any order. Figure 3A is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure. Figure 3A The components are used to help describe Figure 2A For the purpose of illustration and not limitation, a collaborative spreadsheet document is used herein as an example of a collaborative electronic document. It can be noted that aspects of the present disclosure can be applied to other types of collaborative electronic documents, such as but not limited to collaborative word processing documents and collaborative slide documents.

[0076] At operation 201, the client device 110Z makes changes to the client model of the collaborative electronic document. Figure 3A , a user of client device 110Z types a value (eg, "lorem") in a particular cell A2 of a collaborative spreadsheet document.

[0077] At operation 202, client device 110Z displays an updated client model of the collaborative electronic document including the change. For example, client device 110Z displays an updated client model of the collaborative spreadsheet document in a graphical user interface (GUI) that includes the content "lorum" in cell A2.

[0078] At operation 203, client device 110Z sends a change request to server 112A. The change request may include a command indicating a change to a coordinate location within a coordinate structure of a client model of a collaborative electronic document at client device 110Z. For example, server 112A may receive a change request including a command indicating a change to a particular cell of a client model of a collaborative spreadsheet document stored at client device 110Z.

[0079] In some embodiments, a change request may include or be associated with various information. For example, a change request may include or be associated with a command (e.g., an action to be performed), an identifier of a revision number of a client model (e.g., the current revision to make the change), typed content (e.g., a value), a location of the change (e.g., a coordinate identifier), a session identifier, a user identifier, and one or more of other information.

[0080] In some embodiments, a command may be associated with a command type in a plurality of command types. For example, a first command type may change a value at a coordinate position within a collaborative electronic document. For example, a first command type may add a value to a cell in a collaborative electronic table document. A second command type may change a coordinate structure of a collaborative electronic document. For example, a second command type may add one or more rows or columns to a collaborative electronic table document. A third command type may change the format of a value at a coordinate position within a collaborative electronic document. For example, a third command type may change a font in a cell from a first font type to a second font type. The command types described herein are provided for illustration and not limitation. Additional or different command types may be used for any collaborative electronic document. In an embodiment, server 112A may perform one or more different operations in view of the command type received.

[0081] Referring to the current example, server 112A may receive a change request that includes a command of a first command type (e.g., "set cell property") indicating a change to a value of a particular cell of a client model of a collaborative spreadsheet document stored at client device 110Z. The change request identifies a coordinate identifier A2 that identifies a coordinate location of the client model of the collaborative spreadsheet document, a cell at A2. The change request also identifies a change value ("lorem"), a current revision number of the client model, and a session identifier.

[0082] At operation 204, server 112A applies the change at the corresponding coordinate location of the server model of the collaborative electronic document in accordance with the command. In an embodiment, the coordinate structure of the client model and the server model of the collaborative electronic document are similar or identical, so that the coordinate location of the client model corresponds to the coordinate location of the server model. In some embodiments, the change is associated with a revision identifier. In some embodiments, the revision identifier may identify a revision number that is incremented after the change is applied to the server model of the collaborative electronic document (e.g., operation 211). In some embodiments, the version identifier identifies the current version before the version number is incremented.

[0083] For example, in Figure 3A, the user types "lorem" at the coordinate location of the client model of the collaborative spreadsheet document, cell A2. To apply the changes to the server model 310 of the collaborative spreadsheet document, the value "lorem" is typed into the corresponding coordinate location of the server model 310 of the collaborative spreadsheet document, cell A2. The current version number is version 1, and the revision identifier may be rev.1.

[0084] At operation 205, server 112A stores a revised copy of the server model of the collaborative electronic document and the applied changes at the corresponding coordinate locations. The revised copy is associated with a revision identifier. For example, server 112A stores a revised copy of the current state of the server model of the collaborative electronic spreadsheet document, which includes the change "lorem" at the coordinate location, cell A2. The server associates the revised copy with the current revision ID (rev.1).

[0085] At operation 206, server 112A determines whether the command type of the command satisfies the command type condition. In some embodiments, to determine whether the command type of the command satisfies the command type condition, server 112A determines whether the command type is one of predefined command types (e.g., a first command type, a second command type, a third command type, etc.). In response to determining that the command type of the command is a specific command type, server 112A performs a specific action. In the current embodiment, server 112A determines that the command type of the command is a first command type that changes a value at a coordinate location of a collaborative electronic document. For example, the command "set cell property" is a first command type that adds a value to a cell in a collaborative electronic spreadsheet document.

[0086] At operation 207, in response to determining that the command type of the command satisfies the command type condition (e.g., belongs to the first command type), the server 112A generates an attribution model. The attribution model tracks attribution of content in the collaborative document. In an embodiment, the attribution model includes a coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document. The attribution model may include at least a coordinate position corresponding to the coordinate position of the server model to which the change is applied. The corresponding coordinate position of the attribution module may be identified using a coordinate identifier associated with the coordinate position of the server model to which the change is applied.

[0087] In some embodiments, server 112A may generate an attribution model having a coordinate structure that is smaller than the coordinate structure of the collaborative electronic document (e.g., including only a portion of the coordinate structure of the collaborative electronic document). The attribution model may have a similar coordinate structure, but exclude some coordinate locations to which no changes have been applied. A smaller attribution model may be an optimization to reduce the amount of storage and memory resources used to generate, save, and load the attribution model.

[0088] For example, in Figure 3A , the attribution model 320 is generated to have one column (column A) and four rows (rows 1-4). In contrast, the server model 310 of the collaborative spreadsheet document has five columns (columns AE) and four rows (rows 1-4). The coordinate structure of the attribution model 320 is similar to that of the server model 310 in that both coordinate structures have the same structure type (e.g., rows and columns) and both include coordinate structures (e.g., A2) that can address corresponding coordinate locations by the same coordinate identifier. The generated attribution model 320 reflects a portion of the server model of the collaborative spreadsheet document, but the coordinate structure of the server model 310 is sufficient so that the attribution model 320 includes the coordinate locations to which the changes are applied. This approach may be beneficial in reducing data storage and other resources required to store and use the attribution model 320. It may be noted that the sizes of the coordinate structures provided are exemplary and non-limiting. In other embodiments, the coordinate structure of the attribution model 320 may be smaller by, for example, eliminating rows 3 and 4, or larger by, for example, adding column B.

[0089] In other embodiments, the attribution model 320 may have the same coordinate structure (eg, the same dimensions and the same number of rows and columns) as the server model of the collaborative electronic document.

[0090] At operation 208, server 112A updates the corresponding coordinate location of the attribution module with the revised identifier. Figure 3A 1, server 112A associates revision identifier rev.1 with the coordinate location of attribution module 320 corresponding to the coordinate location of server model 310 where change "lorem" was added to server model 310. In server model 310 and attribution module 320, the cell at A2 has been adjusted.

[0091] At operation 209, the server 112A generates attribution information associated with the change to the collaborative electronic document. The attribution information may refer to information that attributes an action (e.g., an edit) to a particular user or author on the collaborative electronic document, or information that provides context for the action. In some embodiments, the attribution information may include one or more of an indication of a user account (with the cloud-based system 101) associated with the change and a timestamp associated with the change. In some embodiments, the indication of the user account associated with the change may include an identifier of the author who made the change to the client model of the collaborative electronic document. In some embodiments, the timestamp associated with the change may indicate the time when the server 112A applied the change to the server model of the collaborative electronic document. The timestamp may include one or more of a date of the change (e.g., day, month, or year) or a time of the change (e.g., hours, minutes, seconds).

[0092] In some embodiments, the attribution information may include more, less, or different information. For example, the attribution information may include the value at the coordinate location before the change (e.g., the contents of the cell before the change was applied), such as referring to Figures 6A-6C 7A-7C further described. In some embodiments, the client device can generate one or more elements of the attribution information. For example, the change request can include an identifier of a user who made the change to the client model of the collaborative electronic document.

[0093] At operation 210, server 112A stores at least some attribution information associated with changes to the collaborative electronic document. The attribution information may be associated with a revision identifier of the current revision. For example, in Figure 3A In the example embodiment, the attribution information may be stored in a data store (eg, data store 114) and linked or otherwise associated with (eg, stored together with) a current revision identifier rev.1 of the server model of the collaborative spreadsheet document.

[0094] At operation 211, the server 112A may update the current revision number of the server model of the collaborative electronic document. For example, the server 112A increments the revision number of the server model to the next revision number. For example, the server 112A may increment the version number of the server model from version 1 (rev. 1) to version 2 (rev. 2).

[0095] At operation 212, server 112A may send an indication to client device 110Z that the changes submitted in the change request have been applied to the server model of the collaborative electronic document.

[0096] At operation 213, in response to receiving an indication that the changes submitted in the change request have been applied to the server model of the collaborative electronic document, the client device 110Z updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110Z may increment the revision number of the client model from revision 1 (rev. 1) to revision 2 (rev. 2). After updating the current revision number, the client model of the collaborative electronic document at the client device 110Z is synchronized with the server model of the collaborative electronic document.

[0097] At operation 214, server 112A sends an indication of the change to client device 110A. For example, the indication of the change may indicate that the cell at A2 of the collaborative spreadsheet document has a new value of "lorem".

[0098] At operation 215, in response to receiving the indication of the change, client device 110A applies the change to the client model of the collaborative electronic document at client device 110A. For example, client device 110A applies the value "lorem" to cell at A2 of the client model of the collaborative spreadsheet document.

[0099] At operation 216, the client device 110A updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110A may increment the revision number of the client model from revision 1 (rev. 1) to revision 2 (rev. 2). After updating the current revision number, the client model of the collaborative electronic document at the client device 110A is synchronized with the server model of the collaborative electronic document.

[0100] Figure 2B is a diagram of operations for generating an attribution model according to an embodiment of the present disclosure. System 200 may include Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 The components can be used to help describe Figure 2B For purposes of illustration and not limitation, operations of system 200 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or may be performed by any component unless otherwise specified. ... Figure 2B The operations described are shown to be performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, less or more operations can be performed in any order. Figure 3B FIG. 1 is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure. Figure 3B components to help describe Figure 2B In the embodiment, Figure 2B The operation can be similar to that of Figure 2A Describes the operation and Figure 2A The description can be used to Figure 2B The operations described provide additional details.

[0101] At operation 220, the client device 110A makes changes to the client model of the collaborative electronic document. Figure 3B As illustrated in , a user of client device 110A types a value (eg, "ipsum") into a particular cell of the collaborative spreadsheet document, cell at D3.

[0102] In operation 221, the client device 110A displays the updated client model of the collaborative electronic document including the changes. For example, the client device 110A displays in the GUI the updated client model of the collaborative spreadsheet document including the content "ipsum" at the cell at D3.

[0103] At operation 222, client device 110A sends a change request to server 112A. The change request may include a command indicating a change at a coordinate location within a coordinate structure of a client model of a collaborative electronic document at client device 110A. For example, server 112A may receive a change request including a command indicating a change to a particular cell of a client model of a collaborative spreadsheet document stored at client device 110A.

[0104] In the current example, server 112A may receive a change request that includes a command of a first command type (e.g., "set cell property") indicating a change to a value at a particular cell of a client model of a collaborative spreadsheet document. The change request identifies a coordinate location of the client model of the collaborative spreadsheet document (cell at D3), a change value ("ipsum"), a current revision number of the client model (e.g., rev. 2), and a session identifier.

[0105] At operation 223, server 112A applies the changes at the corresponding coordinate positions of the server model of the collaborative electronic document according to the command. Figure 3B , the user types "ipsum" at the coordinate location (cell at D3) of the client model of the collaborative spreadsheet document. To apply the changes to the server model 310 of the collaborative spreadsheet document, the value "ipsum" is entered into the corresponding coordinate location (cell at D3) of the server model 310 of the collaborative spreadsheet document. The current revision number is revision 2, and the revision identifier may be rev.2.

[0106] At operation 224, server 112A stores a revised copy of the server model of the collaborative electronic document and the applied changes at the corresponding coordinate locations. The revised copy is associated with the identified revision. For example, server 112A stores a revised copy of the current state of the server model of the collaborative electronic spreadsheet document, the revised copy including the change "ipsum" at the cell at coordinate location D3. The server associates the revised copy with the current revision ID, rev.2.

[0107] At operation 225, server 112A determines whether the command type of the command satisfies the command type condition. In the current embodiment, server 112A determines that the command type of the command is a first command type that adds a value to a coordinate location of a collaborative electronic document. For example, a "set cell property" command is a first command type that adds a value to a cell in a collaborative electronic table document.

[0108] At operation 226, in response to determining that the command type of the command satisfies the command type condition (eg, belongs to the first command type), the server 112A modifies the attribution model document associated with the server model of the cooperating electronic device. In particular, in some embodiments, the coordinate structure of the attribution model is modified.

[0109] For example, in Figure 3B , the coordinate structure of the attribution module 320 is modified by adding columns B, C, and D. Note that the coordinate structure of the attribution module 320 is still smaller than the coordinate structure of the server model 310. The modified attribution module 320 reflects a portion of the server model 310 of the collaborative spreadsheet document, but the coordinate structure of the server model 310 is sufficient so that the attribution model 320 can include the modified coordinate locations.

[0110] At operation 227, server 112A updates the corresponding coordinate position of the attribution module with the current revision identifier. Figure 3B , server 112A associates revision identifier rev.2 with the coordinate position of attribution model 320 corresponding to the coordinate position of server model 310 where change “ipsum” is added to server model 310. In server model 310 and attribution model, the cell at D3 has been updated, but has different information. It can be noted that attribution module 320 does not include the value “ipsum” that has been included in the cell at D3 of server model 310, which reduces the storage and memory overhead of attribution module 310.

[0111] At operation 228 , the server 112A generates attribution information for the changes to the collaborative electronic document. For example, the attribution information may include the author of the changes (eg, user A of the client device 110A) and a timestamp when the server 112A applied the changes to the server model 310 .

[0112] At operation 229, server 112A stores the attribution information for the change in association with the revision identifier of the current revision. Figure 3B In the example embodiment, the attribution information may be stored at a data store (eg, data store 114) and linked or otherwise associated with (eg, stored together with) a current revision identifier rev.2 of the server model of the collaborative spreadsheet document.

[0113] At operation 230, the server 112A may update the current revision number of the server model of the collaborative electronic document. For example, the server 112A may increment the revision number of the server model from revision 2 (rev. 2) to revision 3 (rev. 3).

[0114] At operation 231 , server 112A may send an indication to client device 110A that the changes submitted in the change request have been applied to the server model of the collaborative electronic document.

[0115] At operation 232, in response to receiving an indication that the changes submitted in the change request have been applied to the server model, the client device 110A updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110A may increment the revision number of the client model from revision 2 (rev. 2) to revision 3 (rev. 3). After updating the current revision number, the client model of the collaborative electronic document at the client device 110A is synchronized with the server model of the collaborative electronic document.

[0116] At operation 233, server 112A sends an indication of the change to the server model to client device 110Z. For example, the indication of the change may indicate that the cell at D3 of the collaborative spreadsheet document has a new value of "ipsum".

[0117] At operation 234, in response to receiving the indication of the change at the server model, client device 110Z applies the change to the client model of the collaborative electronic document at client device 110Z. For example, client device 110Z applies the value "ipsum" at cell at D3 of the client model of the collaborative spreadsheet document at client device 110A.

[0118] At operation 235, client device 110Z updates the current revision number of the client model of the collaborative electronic document. For example, client device 110Z may increment the revision number of the client model from revision 2 (rev. 2) to revision 3 (rev. 3). After updating the current revision number, the client model of the collaborative electronic document at client device 110Z is synchronized with the server model of the collaborative electronic document.

[0119] Figure 2C is a diagram of operations for updating an attribution model according to an embodiment of the present disclosure. System 200 may include Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 The components can be used to help describe Figure 2CFor purposes of illustration and not limitation, operations of system 200 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or may be performed by any component thereof unless otherwise specified. ... Figure 2C The operations described are shown as being performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, fewer, or more operations can be performed in any order. Figure 3C is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure. Figure 3C The components are used to help describe Figure 2C In the embodiment, Figure 2C The operation is similar to that of Figure 2A Describes the operation and Figure 2A The description can be used to provide information about Figure 2C Additional details of the operation described.

[0120] At operation 240, the client device 110Z makes changes to the client model of the collaborative electronic document. Figure 3C As illustrated in , a user of client device 110Z types a value (eg, "Hello") in a particular cell (the cell at A2) of the collaborative spreadsheet document, which replaces the original value "lorem".

[0121] At operation 241, the client device 110Z displays the updated client model of the collaborative electronic document including the change. For example, the client device 110Z displays in the GUI the updated client model of the collaborative spreadsheet document including the content "Hello" in the cell at A2.

[0122] At operation 242, client device 110Z sends a change request to server 112A. The change request may include a command indicating a change at a coordinate location within a coordinate structure of a client model of a collaborative electronic document at client device 110Z. For example, server 112A may receive a change request including a command indicating a change to a particular cell of a client model of a collaborative spreadsheet document stored at client device 110Z.

[0123] In the current example, server 112A may receive a change request that includes a command of a first command type (e.g., "set cell property") indicating a change to a value at a particular cell of a client model of a collaborative spreadsheet document. The change request identifies a coordinate location of the client model of the collaborative spreadsheet document (the cell at A2), a change value ("Hello"), a current revision number of the client model, and a session identifier.

[0124] At operation 243, server 112A applies the changes at the corresponding coordinate positions of the server model of the collaborative electronic document according to the command. Figure 3C , the user types "Hello" at the coordinate location (cell at A2) of the client model of the collaborative spreadsheet document. To apply the changes to the server model 310 of the collaborative spreadsheet document, server 112A replaces the value "lorem" with the new value "Hello". "Hello" is typed into the corresponding coordinate location (cell at A2) of the server model 310 of the collaborative spreadsheet document. The current version number is version 3, and the version identifier may be rev.3.

[0125] At operation 244, server 112A stores the revised copy of the server model of the collaborative electronic document and the applied changes at the corresponding coordinate locations. The revised copy is associated with the revision identifier. For example, server 112A stores a revised copy of the current state of the server model of the collaborative electronic spreadsheet document, which includes the change "Hello" at the coordinate location (cell A2). The server associates the revised copy with the current revision ID, rev.3.

[0126] At operation 245, the server 112A determines whether the command type of the command satisfies the command type condition. In the current embodiment, the server 112A determines that the command type of the command is a first command type that adds a value to a coordinate location of a collaborative electronic document. For example, the "Set Cell Properties" command is a first command type that adds or changes a value to a cell in a collaborative electronic table document.

[0127] At operation 246, in response to determining that the command type of the command satisfies the command type condition (e.g., belongs to the first command type), the server 112A updates the corresponding coordinate location of the attribution module with the revision identifier. Figure 3B, server 112A associates the current revision identifier rev.3 at the coordinate position of attribution module 320 corresponding to the coordinate position of server model 310 with the change “Hello”. As illustrated, the coordinate position of attribution model 320 (cell at A2) includes two revision identifiers rev.1 and rev.3. It can be noted that because attribution module 320 already includes the cell at A2, the coordinate structure of attribution module 320 does not need to be modified again.

[0128] At operation 247, server 112A generates attribution information for modifications to the collaborative electronic document.

[0129] At operation 248, server 112A stores attribution information for the change in association with the revision identifier of the current revision. Figure 3C In , the attribution information may be stored at a data store (eg, data store 114) and linked to or otherwise associated with (stored with) a current revision identifier, rev. 3, of the server model of the collaborative spreadsheet document.

[0130] At operation 249, the server 112A may update the current revision number of the server model of the collaborative electronic document. For example, the server 112A may increment the version number of the server model from version 3 (rev. 3) to version 4 (rev. 4).

[0131] At operation 250 , server 112A may send an indication to client device 110Z that the changes submitted in the change request have been applied to the server model of the collaborative electronic document.

[0132] At operation 251, in response to receiving an indication that the changes submitted in the change request have been applied to the server model of the collaborative electronic document, the client device 110Z updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110Z may increment the version number of the client model from version 3 (rev. 3) to version 4 (rev. 4). After updating the current revision number, the client model of the collaborative electronic document at the client device 110Z is synchronized with the server model of the collaborative electronic document.

[0133] At operation 252, server 112A sends an indication of the change to the server model to client device 110A. For example, the indication of the change may indicate that the cell at A2 of the collaborative spreadsheet document has a new value of "Hello", which replaces the old value of "ipsum".

[0134] At operation 253, in response to receiving the indication of the change to the server model, the client device 110A applies the change to the client model of the collaborative electronic document at the client device 110A. For example, the client device 110A applies the value "Hello" to the cell at A2 of the client model of the collaborative spreadsheet document at the client device 110A.

[0135] At operation 254, the client device 110A updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110A may increment the version number of the client model from version 3 (rev. 3) to version 4 (rev. 4). After updating the current revision number, the client model of the collaborative electronic document at the client device 110A is synchronized with the server model of the collaborative electronic document.

[0136] Figure 2D is a diagram of operations for updating an attribution model according to an embodiment of the present disclosure. System 200 may include Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 The components can be used to help describe Figure 2B For purposes of illustration and not limitation, operations of system 200 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or may be performed by any component thereof unless otherwise specified. ... Figure 2D The operations described are shown as being performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, fewer, or more operations can be performed in any order. Figure 3D is a diagram illustrating a server model and an attribution model according to an embodiment of the present disclosure. Figure 3D The components are used to help describe Figure 3D In the embodiment, Figure 2D The operation is similar to that of Figure 2A Describes the operation and Figure 2A The description can be used to Figure 2D The operations described provide additional details.

[0137] At operation 260, the client device 110A makes changes to the client model of the collaborative electronic document. Figure 3D As illustrated in FIG. 8 , a user of client device 110A adds a column between original columns C and D of the collaborative spreadsheet document.

[0138] At operation 261, client device 110A displays an updated client model of the collaborative electronic document including the change. For example, client device 110A displays in the GUI an updated client model of the collaborative spreadsheet document including the new column D. The other columns and associated cells to the right of the new column D have been adjusted accordingly.

[0139] At operation 262, client device 110A sends a change request to server 112A. The change request may include a command indicating a change to a coordinate structure of a client model of a collaborative electronic document at client device 110A. For example, server 112A may receive a change request including a command indicating a change to a size of a coordinate structure of a client model of a collaborative electronic document stored at client device 110A.

[0140] In the current example, server 112A may receive a change request including a command of the second command type (e.g., "add column") indicating a change to the coordinate structure of the client model of the collaborative spreadsheet document stored at client device 110A. The change request identifies the coordinate location of the client model of the collaborative spreadsheet document, column C and column D between which the new column is added. The change request also identifies the number of columns added, the current revision number of the client model (e.g., rev. 4), and the session identifier.

[0141] At operation 263, server 112A applies the changes to the coordinate structure of the server model of the collaborative electronic document in accordance with the command. Figure 3D , a user inserts a new column between the original columns C and D of the client model of the collaborative spreadsheet document. To apply the changes to the coordinate structure of the server model 310 of the collaborative spreadsheet document, the new column D is added to the server model 310 of the collaborative spreadsheet document, and the columns to the right of column D are shifted to the right and associated with new coordinate identifiers. The current version number is version 4, and the version identifier may be rev.4.

[0142] At operation 264, server 112A stores a revised copy of the server model of the collaborative electronic document with the changes applied to the coordinate structure of the server model of the collaborative electronic document. The revised copy is associated with the current version identifier. For example, server 112A stores a revised copy of the current state of the server model of the collaborative electronic table document with the newly inserted column. The server associates the revised copy with the current revision identifier rev.4.

[0143] At operation 265, the server 112A determines whether the command type of the command satisfies the command type condition (e.g., belongs to one of the predefined command types). In the current embodiment, the server 112A determines that the command type of the command is a second command type that changes the coordinate structure of the collaborative electronic document. For example, the command "add column" is a second command type that changes the size of the coordinate structure of the collaborative electronic table document.

[0144] At operation 266, in response to determining that the command type of the command satisfies the command type condition (e.g., belongs to the second command type), the server 112A modifies the coordinate structure of the attribution model to reflect the change to the structure of the server model of the coordinate collaborative electronic document. In view of the modified coordinate structure of the attribution model, the position of the attribution model content is adjusted.

[0145] For example, in Figure 3D , the coordinate structure of the attribution module 320 is modified by adding a new column D and adjusting the coordinate identifiers of the cells to the right of the new column D. It is noted that the coordinate structure of the attribution module 320 is smaller than the coordinate structure of the server model 310. It may also be noted that the contents of the cells of the attribution model are not updated. It may also be noted that no attribution information is generated for a particular command type. It may be noted that the contents of the coordinate locations of the attribution model are not updated. In other embodiments, attribution information for a second command type is generated and stored in a manner similar to that described herein. It may be further noted that different applications may have different command types for which attribution information is generated, stored, and subsequently retrieved in response to an attribution query.

[0146] At operation 267, the server 112A may update the current revision number of the server model of the collaborative electronic document. For example, the server 112A may increment the revision number of the server model from revision 4 to revision 5.

[0147] At operation 268 , server 112A may send an indication to client device 110A that the changes submitted in the change request have been applied to the server model of the collaborative electronic document.

[0148] At operation 269, in response to receiving an indication that the changes submitted in the change request have been applied to the server model of the collaborative electronic document, the client device 110A updates the current revision number of the client model of the collaborative electronic document. For example, the client device 110A may increment the version number of the client model from version 4 (rev. 4) to version 5 (rev. 5). After updating the current revision number, the client model of the collaborative electronic document at the client device 110A is synchronized with the server model of the collaborative electronic document.

[0149] At operation 270, server 112A sends an indication of the change to the server model to client device 110Z. For example, the indication of the change may indicate that a column was added between original columns C and D of the collaborative electronic document.

[0150] At operation 271, in response to receiving an indication of a change to the server model, the client device 110Z applies the change to the client model of the collaborative electronic document at the client device 110Z. For example, the client device 110Z inserts a new column D between the original column C and the original column D, and shifts the columns and values ​​to the right of column D.

[0151] At operation 272, client device 110Z updates the current revision number of the client model of the collaborative electronic document. For example, client device 110Z may increment the revision number of the client model from revision 4 (rev.4) to revision 5 (rev.5). After updating the current revision number, the client model of the collaborative electronic document at client device 110Z is synchronized with the server model of the collaborative electronic document.

[0152] Figure 4 is a diagram of operations for providing attribution information to a client device according to an embodiment of the present disclosure. System 400 may include Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 and Figure 3D The components can be used to help describe Figure 4 For purposes of illustration and not limitation, operations of system 400 are described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or may be performed by any component thereof unless otherwise specified. ... Figure 4 The operations described are shown as being performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, fewer, or more operations can be performed in any order. Figure 5 is a diagram illustrating a system 500 for identifying and providing attribution information to a client device according to an embodiment of the present disclosure. Figure 5 The components are used to help describe Figure 4 Describes the operation.

[0153] At operation 401, the client device 110Z receives a user's selection identifying a portion of a client model of a collaborative electronic document via a graphical user interface (GUI) presented at the client device 110Z. Figure 5 , a user selects a specific cell of a collaborative spreadsheet document.

[0154] At operation 402, the client device 110Z receives a user request for attribution information for changes to content within the portion of the client model selected by the user. For example, the user may right-click while selecting a cell of the collaborative spreadsheet document, or perform other similar actions. A graphical user interface element (e.g., a drop-down menu, a list of check boxes or radio buttons, etc.) may be displayed that allows the user to request attribution information for the selected cell.

[0155] At operation 403, the client device 110Z sends an attribution query to the server 112A of the cloud-based document editing system, the attribution query requesting attribution information associated with the selected portion of the collaborative electronic document. In an embodiment, the attribution query includes a coordinate identifier that identifies a portion of the client model of the collaborative electronic document. For example, in Figure 5 In, the query includes a coordinate identifier (eg, an x-coordinate and a y-coordinate) of the selected cell.

[0156] At operation 404, the server 112A identifies the coordinate location of the client model of the collaborative electronic document from the attribution query. For example, the server 112A identifies the x-coordinate and y-coordinate of the selected cell from the attribution query. For example, the coordinate location of the cell identified in the attribution is the cell located at A2.

[0157] At operation 405, server 112A identifies an attribution model associated with the collaborative electronic document. Figure 3D , server 112A identifies attribution model 320 as being associated with a particular collaborative electronic document.

[0158] At operation 406, server 112A uses the coordinate identifier of the client model from the attribution query to identify the revision identifier associated with the corresponding coordinate location of the attribution module. In some embodiments, the coordinate location of the attribution model may include multiple revision identifiers. The selected or identified revision identifier may depend on the content requested by the attribution query. If the attribution query requests attribution information for the last edit (e.g., the most recent edit), server 112A may identify the revision identifier at the specific coordinate location with the largest number. If the attribution query requests attribution information for the second to last edit, server 112A may use the second largest number to identify the revision identified at the specific coordinate location.

[0159] In the current example, Figure 5 In , the attribution query requests the attribution information for the last edit of cell A2. Figure 3D As illustrated in , server 112A identifies a revision identifier, rev.3.

[0160] At operation 407, server 112A retrieves attribution information associated with the revision identifier. For example, server 112A uses revision identifier rev.3 to find corresponding attribution information stored at the data store. The attribution information may indicate that user Z of client device 110Z made the last change to cell A2 at 7:40 PM on March 27, 2019.

[0161] At operation 408 , the server 112A provides attribution information to the client device in response to the attribution query.

[0162] At operation 409, client device 110Z presents the attribution information to a user of client device 110Z. In some embodiments, client device 110Z provides a graphical user interface element in a GUI that presents the attribution information. The attribution information may include a user identifier of a user who made a change to the content of a portion of the client model of the collaborative electronic document.

[0163] At operation 410, client device 110Z receives a subsequent user request for additional attribution information for another change (e.g., a second most recent change) of content within the portion of the client model selected by the user. For example, a previously displayed graphical user interface element may allow the user to retrieve additional attribution information for the selected cell.

[0164] At operation 411, the client device 110Z sends an attribution query to the server 112A of the cloud-based document editing system, the attribution query requesting additional attribution information associated with the coordinate location of the selected portion of the collaborative electronic document. In an embodiment, the attribution query includes a coordinate identifier that identifies a portion of the client model of the collaborative electronic document. For example, in Figure 5 In, the query includes a coordinate identifier (eg, an x-coordinate and a y-coordinate) of the selected cell.

[0165] At operation 412, the server 112A identifies a coordinate identifier of the client model of the collaborative electronic document from the attribution query. For example, the server 112A identifies the x-coordinate and y-coordinate of the selected cell (A2) from the attribution query.

[0166] At operation 413, server 112A identifies an attribution model associated with the collaborative electronic document. Figure 3D , the server 112A identifies the attribution model 320 as being associated with the particular collaborative electronic document.

[0167] At operation 414, server 112A uses the coordinate identifier of the client model obtained from the attribution query to identify the revision identifier associated with the corresponding coordinate location of the attribution module. In an embodiment, the attribution query requests attribution information for the second-to-last edit. Server 112A may use the second-largest number to identify the revision identified at the particular coordinate location. In the current example, Figure 3D , server 112A identifies revision identifier rev.1.

[0168] At operation 415, server 112A retrieves attribution information associated with the revision identifier. For example, server 112A uses revision identifier rev.1 to find corresponding attribution information stored in the data store. The attribution information may indicate that user Z of client device 110Z made the last change to cell A2 at 1:20 PM on March 26, 2019.

[0169] At operation 416 , the server 112A provides attribution information to the client device in response to the attribution query.

[0170] At operation 417, client device 110Z presents the attribution information to a user of client device 110Z. In some embodiments, client device 110Z presents the additional attribution information via a graphical user interface element in the GUI. The additional attribution information includes a user identifier of a user who made a change (e.g., the second most recent change) to the content of the portion of the client model of the collaborative electronic document.

[0171] It should be noted that in embodiments, attribution information may be provided to the client device 110Z regardless of whether any user of the collaborative electronic document invokes a track changes command (eg, a command to track changes to a document).

[0172] Figures 6A-6C is a diagram illustrating a server model and an attribution model for providing previous content of a collaborative electronic document to a client device according to an embodiment of the present disclosure. Figures 6A-6C The operations described are similar to those described for Figures 2A-2D and Figures 3A-3D For clarity, regarding Figures 2A-2D and Figure 3A-3D Many of the operations and components described are not repeated here. Figure 2A-2D and Figure 3A-3D The operations and components described can be applied to Figure 6A-6C , unless otherwise described. Figures 6A-6C The diagram illustrates how data associated with a coordinate location of an attribution model 620 is updated to allow previous content (eg, value) to be retrieved and provided to a client device as part of the attribution information.

[0173] Fig. 6A Corresponds to Figure 2B .exist Fig. 6A , a user of client device 110A types content "ipsum" into the client model of the collaborative spreadsheet document. In some embodiments, client device 110A may send a change request including a command of a first command type to server 112A. The command may indicate that the content "ipsum" has been added to the cell at D3 of the client model of the collaborative spreadsheet document. The current revision of the collaborative spreadsheet document is revision 2 (e.g., rev.2). Server 112A may apply the corresponding changes to the server model 610 of the collaborative spreadsheet document. Server 112A may store a revised copy of the server model and associate the revised copy with the current revision identifier rev.2. Server 112A may determine that the command satisfies the command condition (e.g., the command type of the command is the first command type). In response to determining that the command type of the command is the first command type, server 112A may update the corresponding coordinate position of the attribution module 620.

[0174] In some embodiments, to update the corresponding coordinate position of the attribution module 620, the server updates the corresponding coordinate position with the current revision identifier (e.g., rev. 2) and the coordinate identifier (e.g., D2) of the position coordinate to which the change is applied at the server model 610 of the collaborative spreadsheet document. In some embodiments, to update the corresponding coordinate position of the attribution module 620, the server updates the corresponding coordinate position with the current revision identifier (e.g., rev. 2) and the corresponding coordinate identifier (e.g., D2) of the updated (attribution model) coordinate position (same as the coordinate identifier (e.g., D2) to which the change is applied at the server model 610 of the collaborative spreadsheet document).

[0175] In some embodiments, server 112A generates attribution information corresponding to the current revision. For example, the attribution information may be to user A at time A. The attribution information is stored in association with the current version identifier.

[0176] In some embodiments, the current revision number used at the attribution module 620 is identified as the current revision number. For example, in the attribution model 620, the current revision number is identified by "R:2". In some embodiments, the coordinate identifier used at the attribution model 620 is identified as the current coordinate position. For example, in the attribution model 620, the current coordinate position is identified by "C:D2".

[0177] The server 112A may update the version number of the server model of the collaborative spreadsheet document from the current revision number 2 (rev. 2) to a revision number 3 (rev. 3).

[0178] Figure 6B Corresponds to Figure 2D .exist Figure 6B In FIG. 1 , the user of client device 110Z modifies the coordinate structure of the client model of the collaborative spreadsheet document. For example, the user of client device 110Z deletes column B of the client model of the collaborative spreadsheet document (instead of Figure 2D ). Client device 110Z sends a change request including a command of a second command type that changes the coordinate structure of the collaborative spreadsheet document to server 112A. Server 112A receives the command and applies the change to the server model 610 of the collaborative spreadsheet document. For example, column B of the server model 610 is removed, and the cells to the right of column B are shifted to the left, and the coordinate identifiers of the coordinate positions of the shifted cells are modified accordingly. Server 112A determines that the command type of the command meets the conditions of the second command type and takes appropriate action to modify the attribution module 620. For example, the coordinate structure of the attribution module 620 is modified to reflect the change in the coordinate structure of the server model 610 of the collaborative spreadsheet document. Column B of the attribution model 620 is removed, and the cells to the right of column B (and their contents) are shifted to the left, and the coordinate identifiers of the shifted cells are modified accordingly. It can be noted that the contents of the coordinate positions of the server model 610 and the attribution module 620 are not changed. Server 112A can store a revised copy of the server model and associate the revised copy with the current revision identifier rev.3. The server 112A may update the revision number of the server model of the collaborative spreadsheet document from the current revision number 3 (rev. 3) to a revision number 4 (rev. 4).

[0179] Figure 6C Corresponds to Figure 2C .exist Figure 6C , a user of client device 110Z types content "Lorem" into cell C2 of the client model of the collaborative spreadsheet document, which replaces the previous content "ipsum". In some embodiments, client device 110Z may send a change request including a command of a first command type to server 112A. The command may indicate that the content "Lorem" has replaced the previous content of the cell at C2 of the client model of the collaborative spreadsheet document. The current revision of the collaborative spreadsheet document is revision 4 (e.g., rev.4). Server 112A may apply the corresponding changes to the server model 610 of the collaborative spreadsheet document. Server 112A may store a revised copy of the server model and associate the revised copy with the current revision identifier rev.4. Server 112A may determine that the command satisfies the command condition (e.g., the command type of the command is the first command type). In response to determining that the command type of the command is the first command type, server 112A may update the corresponding coordinate position of the attribution module 620.

[0180] In some embodiments, to update the corresponding coordinate location of the attribution module 620, the server updates the corresponding coordinate location with the current revision identifier (e.g., rev. 4) and the coordinate identifier (e.g., C2) of the coordinate location of the server model 610 that applies the change to the collaborative spreadsheet document. In some embodiments, to update the corresponding coordinate location of the attribution module 620, the server updates the corresponding coordinate location with the current revision identifier (e.g., rev. 4) and the corresponding coordinate identifier (e.g., C2) of the coordinate location of the attribution model being updated.

[0181] In some embodiments, server 112A generates attribution information corresponding to the current revision. For example, the attribution information may be user Z at time Z. The attribution information is stored in association with the current version identifier.

[0182] In some embodiments, the current revision number associated with the coordinate position of the attribution model 620 is identified as the current revision number. For example, in the attribution model 620, the current revision number is identified by "R:4". In an embodiment, the previous revision number used at the attribution module 620 is retained and identified as the previous revision number. For example, in the attribution model 620, the previous revision number is identified as "PR:2". In some embodiments, the coordinate identifier used at the attribution model 620 is used to identify the current coordinate position. For example, in the attribution module 620, the current coordinate position is identified by "C:C2". In an embodiment, the previous coordinate identifier used in the coordinate position of the attribution model 620 is used to identify the previous coordinate position. For example, in the attribution module 620, the previous coordinate position is identified by "PC:D2". In some embodiments, one or more revised copies of the attribution module can be stored in a manner similar to that described for the revised copy of the server model of the collaborative electronic document. In some embodiments, in order to further trace the attribution history, an older revision of the attribution model can be loaded to determine the attribution information. In some embodiments, any number of previous revision numbers or previous coordinate identifiers may be stored at the coordinate location of the attribution model 620 .

[0183] Figure 7 7 is a diagram of an operation for providing attribution information of previous content including a portion of a collaborative electronic document for presentation at a client device according to an embodiment of the present disclosure. Figure 1 The system architecture 100 has similar components. It can be noted that Figure 1 as well as Figures 6A-6C and Figures 8A-8B The components can be used to help describe Figure 7For purposes of illustration and not limitation, the description of system 700 is described as being performed by attribution module 118A of server 112A, attribution module 118B of client device 110A, attribution module 118Z of client device 110Z, or may be performed by any component thereof unless otherwise specified. ... Figure 7 The operations described are shown to be performed sequentially. It can be noted that the operations can be performed in any order, and any operation can be performed concurrently with one or more other operations. In some embodiments, the same, different, less or more operations can be performed in any order. Figures 8A-8B FIG. 1 is a graphical user interface that allows a user to retrieve attribution information according to an embodiment of the present disclosure. It can be noted that, except for Figure 7 In addition to the operations described, Figure 8A-8B The described GUIs may also be used with any aspects of the present disclosure.

[0184] At operation 701, the client device 110Z receives a user's selection identifying a portion of a client model of a collaborative electronic document via a graphical user interface (GUI) presented at the client device 110Z. Fig. 8A In the example above, a user selects a specific cell of a collaborative spreadsheet document. The cell contains the content "Lorem".

[0185] At operation 702, client device 110Z receives a user request for attribution information for recent changes to content within a client model portion selected by the user. Fig. 8A In the embodiment of the present invention, a user can right-click when selecting a cell of a collaborative spreadsheet document. A graphical user interface element can be displayed, which provides one or more command options available to the user with respect to the selected cell. As illustrated, on the option "Show Edit History", the user can retrieve the history of attribution information for the selected cell. The user can select the "Show Edit History" command option to retrieve the attribution information associated with the selected cell.

[0186] At operation 703, the client device 110Z sends an attribution query to the server 112A of the cloud-based document editing system, the attribution query requesting attribution information associated with the selected portion of the collaborative electronic document. In an embodiment, the attribution query includes a coordinate identifier that identifies a portion of the client model of the collaborative electronic document. For example, in Fig. 8A In the query, the query includes a coordinate identifier (eg, x-coordinate and y-coordinate) of the selected cell. For example, the coordinate identifier is C2.

[0187] At operation 704, the server 112A identifies the coordinate location of the client model of the collaborative electronic document from the attribution query. For example, the server 112A identifies the x-coordinate and y-coordinate of the selected cell from the attribution query.

[0188] At operation 705, server 112A identifies an attribution model associated with the collaborative electronic document. Figure 6C , server 112A identifies attribution model 620 as being associated with a particular collaborative electronic document.

[0189] At operation 706, server 112A uses the coordinate identifier of the coordinate location of the client model identified from the attribution query to identify the most recent revision identifier associated with the corresponding coordinate location of the attribution model. Figure 6C In , the attribution query requests the attribution information for the last edit of cell C2. Figure 6C As illustrated in , server 112A identifies revision identifier rev.4 (eg, "R:4") as the revision identifier associated with the last edit.

[0190] At operation 707, server 112A retrieves attribution information associated with the revision identifier. For example, server 112A uses revision identifier rev.4 to find corresponding attribution information stored in the data store. The attribution information may indicate that user Z of client device 110Z made the last change to the cell at C2 at 2:36 PM on March 25, 2019.

[0191] At operation 708, the server identifies the second most recent revision identifier at the corresponding coordinate location of the attribution model. Figure 6C , server 112A reads the cell at C2 of attribution model 620 and identifies the previous revision number rev. 2 (eg, "PR: 2").

[0192] At operation 709, server 112A identifies the coordinate identifier associated with the second most recently revised identifier at the home model. Figure 6C , the server reads the cell at C2 of the attribution model 630 and identifies the coordinate identifier of the previous coordinate position (cell at D2) (eg, "PC:D2") associated with the previous revision number rev.2 (eg, "PR:2").

[0193] At operation 710, server 112A reads the content of the previous coordinate position of the revised copy of the server model of the collaborative electronic document associated with the previous revision number. For example, server 112A may find the revised copy of the server model of the collaborative electronic spreadsheet document associated with the previous revision number rev.2 (e.g., "PR:2"). Server 112A may read the content of the previous coordinate position of the revised copy (the cell at D2). In the current example, the content of the cell at D2 of the revised copy associated with rev.2 is "ipsum", such as Fig. 6A As shown in the figure.

[0194] At operation 711, server 112A provides attribution information to the client device in response to the attribution query. In some embodiments, the attribution information includes the author who made the change, the timestamp of the change, and the current content of the portion of the collaborative electronic document selected by the user, and the previous content of the portion of the collaborative electronic document selected by the user.

[0195] At operation 712, client device 110Z presents the attribution information to a user of client device 110Z. In some embodiments, client device 110Z provides a graphical user interface element in the GUI that presents the attribution information. Figure 8B , the graphical user interface element in the GUI shows that "User Z" made the last edit at 2:36 PM on March 25, and that the edit replaced the previous content "ipsum" with the current content "Lorem". It can be noted that the graphical user interface element includes a right arrow and a left arrow that allow the user to view the history of attribution information for a selected portion of the collaborative spreadsheet document. For example, the user can select the left arrow to determine the attribution information for the second-to-last edit (e.g., the second most recent edit), and so on. Figure 7 The described operations may be repeated to allow the user to receive a history of attribution information.

[0196] Fig. 9is a flowchart illustrating a method 900 for generating an attribution model to track attribution information for content in a collaborative electronic document and providing the attribution information to a client device according to an embodiment of the present disclosure. The method 900 may be performed by processing logic including hardware (e.g., circuits, dedicated logic, programmable logic, microcode), software (e.g., instructions running on a processing device to perform hardware emulation), or a combination thereof. In some embodiments, an attribution module 118 executed at a client device 110 may perform some or all of the operations. In other embodiments, an attribution module 118 executed at a server 112 may perform some or all of the operations. In some embodiments, an attribution module 118 executed at a client device 110 and one or more servers 112 may perform some or all of the operations. It may be noted that in some embodiments, the method 900 may include the same, different, fewer, or more number of operations performed in any order.

[0197] At block 902, processing logic executing method 900 receives an indication of a first change at a first coordinate location of a client model of a collaborative electronic document (e.g., as part of a command). The first coordinate location is within a coordinate structure of the collaborative electronic document. At block 904, processing logic applies the first change at a second coordinate location of a server model of the collaborative electronic document. The second coordinate location of the server model corresponds to the first coordinate location of the client model. The first change is associated with a revision identifier.

[0198] In some embodiments, processing logic stores a revised copy of the server model of the collaborative electronic document having the first change at the second coordinate location. The revised copy is associated with a revision identifier.

[0199] In some embodiments, processing logic determines whether a command type of the command satisfies a command type condition. In response to determining that the command type of the command satisfies the command type condition, an attribution model is generated.

[0200] At block 906, processing logic generates an attribution model that includes a coordinate structure corresponding to at least a portion of the coordinate structure of the collaborative electronic document. The attribution model includes a third coordinate position that corresponds to the first coordinate position and the second coordinate position.

[0201] In some embodiments, to generate an attribution module that includes a coordinate structure corresponding to at least a portion of a coordinate structure of a collaborating electronic document, processing logic generates an attribution module having a coordinate structure that is smaller than the coordinate structure of the collaborating electronic document.

[0202] At block 908 , processing logic updates the third coordinate position of the attribution model with the revision identifier.

[0203] At block 910, processing logic stores attribution information for the first change in association with the revision identifier. In some embodiments, the attribution information includes an indication of a user associated with the first change and a timestamp associated with the first change.

[0204] In some embodiments, processing logic receives a command indicating a change to a coordinate structure of a collaborative electronic document. Processing logic applies the change to the coordinate structure of a server model of the collaborative electronic document. The change to the coordinate structure of the collaborative electronic document is associated with a second revision identifier. Processing logic modifies the coordinate structure of the attribution model to reflect the change to the coordinate structure of the collaborative electronic document. Positions of attribution model content are adjusted in light of the modified coordinate structure of the attribution model.

[0205] In some embodiments, processing logic stores a revised copy of the server model of the collaborative electronic document and changes to the coordinate structure of the collaborative electronic document. The revised copy including the changes to the coordinate structure is associated with a second revision identifier. Given that the command type is the second command type, processing logic refrains from updating the third coordinate position of the attribution module using the first updated revision identifier.

[0206] At block 912, processing logic receives an attribution query. The attribution query requests attribution information associated with a first coordinate location of a client model of a collaborative electronic document.

[0207] At block 914, processing logic identifies a revision identifier associated with the third coordinate position of the attribution model.The revision identifier is identified using the first coordinate position of the client model of the collaborative electronic document.

[0208] At block 916 , processing logic retrieves attribution information associated with the revision identifier from the designated data store.

[0209] At block 918, in response to the home query, processing logic provides home information to the client device.

[0210] In some embodiments, updating the third coordinate position of the attribution module with the revision identifier further includes updating the third coordinate position of the attribution module with the coordinate identifier of the third coordinate position. In view of the adjusted coordinate structure of the attribution model, the content of the third coordinate position of the attribution model is moved to the fourth coordinate position of the attribution model. The processing logic receives a command indicating a second change at the fifth coordinate position of the client model of the collaborative electronic document. The processing logic applies the second change at the sixth coordinate position of the server model of the collaborative electronic document according to the command. The sixth coordinate position of the server model corresponds to the fifth coordinate position of the client model. The second change is associated with the third revision identifier. The processing logic updates the fourth coordinate position of the attribution module with the third revision identifier and the coordinate identifier of the fourth coordinate position. The processing logic stores the attribution information of the second change in association with the third revision identifier.

[0211] In an embodiment, processing logic receives a request for attribution information associated with a fifth coordinate location of a client model of a collaborative electronic document. Processing logic uses the fifth coordinate location of the client model of the collaborative electronic document to identify a first revision identifier, a third revision identifier, and a coordinate identifier of a third coordinate location associated with a fourth coordinate location of the attribution model. Processing logic retrieves attribution information associated with the third revision identifier. Processing logic uses the first revision identifier to retrieve a first revised copy of a server model of the collaborative electronic document. Processing logic uses the coordinate identifier of the third coordinate location of the attribution model to identify a first change to a second coordinate location of the server model of the collaborative electronic document. Processing logic provides the attribution information to the client device in response to the request. The attribution information includes the first change.

[0212] Fig.10 is a flow chart illustrating a method 1000 for presenting attribution information at a user device according to an embodiment of the present disclosure. The method 1000 may be performed by processing logic including hardware (e.g., circuits, dedicated logic, programmable logic, microcode), software (e.g., instructions running on a processing device to perform hardware emulation), or a combination thereof. In some embodiments, an attribution module 118 executed at a client device 110 may perform some or all of the operations. In other embodiments, an attribution module 118 executed at a server 112 may perform some or all of the operations. In some embodiments, an attribution module 118 executed at both a client device 110 and a server 112 may perform some or all of the operations. It may be noted that in some embodiments, the method 1000 may include the same, different, fewer, or more numbers of operations performed in any order.

[0213] At block 1002, processing logic executing method 1000 receives a user's selection of a portion of a client model identifying a collaborative electronic document via a graphical user interface (GUI) presented at a client device. The collaborative electronic document is hosted by a cloud-based document editing system. The collaborative electronic document can be edited concurrently by multiple users.

[0214] At block 1004 , processing logic receives a user request for attribution information for changes to content within a portion of a client model selected by a user among a plurality of users.

[0215] In some embodiments, in response to receiving a user request for attribution information, processing logic sends an attribution query to the cloud-based document editing system, the attribution query requesting the attribution information. The attribution query includes a first coordinate identifier that identifies a portion of a client model of the collaborative electronic document.

[0216] At block 1006, processing logic presents the attribution information via a graphical user interface element in the GUI. The attribution information includes a user identifier of a user who most recently modified content of a portion of the client model of the collaborative electronic document.

[0217] In some embodiments, the collaborative electronic document comprises a collaborative spreadsheet document having a coordinate structure including one or more rows and one or more columns arranged to create a plurality of cells. The client model portion of the collaborative electronic document selected by the user comprises a cell of the collaborative spreadsheet document.

[0218] In some embodiments, none of the plurality of users has invoked a command to track changes applied to the portion of the collaborative electronic document.

[0219] In some embodiments, processing logic receives, via the graphical user interface, a subsequent user request for additional attribution information for another change to content within a portion of a client model selected by a user of the plurality of users. In response to receiving the subsequent user request for additional attribution information, processing logic presents, at a graphical user interface element in the GUI, the additional attribution information, the additional attribution information including a user identification of a user who provided the other change to content within the portion of the client model of the collaborative electronic document.

[0220] Fig.11 A block diagram depicts an example computing system that operates in accordance with one or more aspects of the present disclosure. In various illustrative examples, computer system 1100 may be used with Figure 1 The computer system 1100 may correspond to any one of the computing devices within the system architecture 1100. In one embodiment, the computer system 1100 may be each of the servers 112A-112Z. In another embodiment, the computer system 1100 may be each of the client devices 110A-110Z.

[0221] In certain embodiments, computer system 1100 can be connected to other computer systems (e.g., via a network such as a local area network (LAN), an intranet, an extranet, or the Internet). Computer system 1100 can operate as a server or client computer in a client-server environment, or as a peer computer in a peer-to-peer or distributed network environment. Computer system 1100 can be provided by a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular phone, a web appliance, a server, a network router, a switch or a bridge, or any device that can execute a set of instructions (sequential or other) specifying the action to be taken by the device. In addition, the term "computer" should include any collection of computers that execute one (or more) sets of instructions to execute any one or more of the methods described herein, either individually or jointly.

[0222] In another aspect, the computer system 1100 may include a processing device 1102, a volatile memory 1104 (e.g., a random access memory (RAM)), a non-volatile memory 1106 (e.g., a read-only memory (ROM) or an electrically erasable programmable ROM (EEPROM)), and a data storage device 1116, which may communicate with each other via a bus 1108.

[0223] The processing device 1102 may be provided by one or more processors such as a general purpose processor (such as, for example, a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a microprocessor that implements other types of instruction sets, or a microprocessor that implements a combination of various types of instruction sets) or a special purpose processor (such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), or a network processor).

[0224] The computer system 1100 may also include a network interface device 1122. The computer system 1100 may also include a video display unit 1110 (eg, LCD), an alphanumeric input device 1112 (eg, keyboard), a cursor control device 1114 (eg, mouse), and a signal generating device 1120.

[0225] The data storage device 1116 may include a computer-readable storage medium 1124 (which may be a non-transitory computer-readable storage medium, although the present disclosure is not limited thereto) storing instructions 1126 encoding any one or more of the methods or functions described herein, including instructions for implementing any of the methods described herein. Figure 1Instructions of the attribution module 118 (118A-118Z).

[0226] The instructions 1126 may also reside, completely or partially, within the volatile memory 1104 and / or within the processing device 1102 during execution thereof by the computer system 1100 , and thus the volatile memory 1104 and the processing device 1102 may also constitute machine-readable storage media.

[0227] Although the computer-readable storage medium 1124 is shown as a single medium in the illustrative example, the term "computer-readable storage medium" shall include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) that store one or more sets of executable instructions. The term "computer-readable storage medium" shall also include any tangible medium that can store a set of instructions or encode a set of instructions for execution by a computer, the instructions causing the computer to perform any one or more of the methods described herein. The term "computer-readable storage medium" shall include, but is not limited to, solid-state memories, optical media, and magnetic media.

[0228] In the foregoing description, many details are set forth. However, it will be apparent to those of ordinary skill in the art who benefit from the present disclosure that the present disclosure can be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring the present disclosure.

[0229] Some portions of the detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the art of data processing to most effectively communicate the essence of their work to other persons skilled in the art. An algorithm is here and generally considered to be a self-consistent sequence of steps leading to a desired result. These steps are steps requiring physical manipulation of physical quantities. Typically, although not necessarily, these quantities take the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated. For general reasons, it has proven convenient to sometimes refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.

[0230] It can be remembered, however, that all of these and similar terms will be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated as will be apparent from the following discussion, it should be apparent that throughout this specification, discussions utilizing terms such as "receive," "apply," "generate," "update," "store," "receive," "identify," "retrieve," "provide," "determine," "modify," "inhibit," "present," "send," and the like refer to the actions and processes of a computer system or similar electronic computing device that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission, or display devices.

[0231] For simplicity of explanation, method is depicted and described as a series of actions in this article. However, actions according to the present disclosure can occur in various orders and / or simultaneously and occur together with other actions not presented and described in this article. In addition, it is possible not to require all illustrated actions to realize the method according to the disclosed subject matter. In addition, it should be understood and apparent to those skilled in the art that these methods can be alternatively represented as a series of related states via state diagrams or events. Additionally, it should be apparent that the methods disclosed in this specification can be stored on articles of manufacture to facilitate the transport and transfer of such methods to computing devices. As used herein, the term article of manufacture is intended to include a computer program accessible from any computer-readable device or storage medium.

[0232] Certain embodiments of the present disclosure also relate to a device for performing the operations herein. This device can be constructed for a predetermined purpose, or it can include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer-readable storage medium, such as but not limited to any type of disk including a floppy disk, an optical disk, a CD-ROM, and a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card or an optical card, or any type of medium suitable for storing electronic instructions.

[0233] The words "example" or "exemplary" are used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as "example" or "exemplary" is not necessarily interpreted as being preferred or advantageous over other aspects or designs. On the contrary, the use of the words "example" or "exemplary" is intended to present concepts in a specific way. As used in this application, the term "or" is intended to mean an inclusive "or", not an exclusive "or". That is, unless otherwise specified or clear from the context, "X includes A or B" is intended to mean any natural inclusive replacement. That is, if X includes A; X includes B; or X includes both A and B, then "X includes A or B" satisfies any of the foregoing situations. In addition, the articles "one" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more", unless otherwise specified or clearly indicated from the context as a singular form. In addition, unless so described, the use of the terms "one embodiment" or "one embodiment" or "one embodiment" or "one embodiment" throughout the text is not intended to represent the same embodiment or implementation. One or more embodiments or embodiments described herein may be combined in a specific embodiment or embodiment. As used herein, the terms “first,” “second,” “third,” “fourth,” etc. are intended to be labels for distinguishing between different elements, and do not necessarily have ordinal meanings according to their numerical names.

[0234] It should be understood that the above description is intended to be illustrative, rather than restrictive. After reading and understanding the above description, many other embodiments will be apparent to those skilled in the art. Therefore, the scope of the present disclosure can be determined with reference to the attached claims and the full scope of equivalents given by such claims.

Claims

1. A method for tracking attribution information of a collaborative electronic document, comprising: receiving, by a server hosting the collaborative electronic document, an indication of a first change at a first coordinate location of a client model of the collaborative electronic document, wherein the first coordinate location is within a coordinate structure of the client model of the collaborative electronic document; applying the first change at a second coordinate position of a coordinate structure of a server model of the collaborative electronic document, wherein the second coordinate position of the server model corresponds to the first coordinate position of the client model, and wherein the first change is associated with a first revision identifier; generating an attribution model, the attribution model including a coordinate structure corresponding to at least a portion of a coordinate structure of a server model of the collaborative electronic document and including a third coordinate position corresponding to the first coordinate position and the second coordinate position, wherein the attribution model is a different model from the server model; Updating a third coordinate position of the attribution model with the first revision identifier; and Attribution information for the first change is stored in association with the first revision identifier.

2. The method according to claim 1, further comprising: receiving an attribution query from a client device, the attribution query requesting the attribution information associated with a first coordinate location of a client model of the collaborative electronic document; identifying the first revision identifier associated with a third coordinate location of the attribution model using a coordinate identifier of the first coordinate location of the client model of the collaborative electronic document; retrieving the attribution information associated with the first revision identifier from a data store; as well as The attribution information is provided to the client device in response to the attribution query.

3. The method of claim 1 , wherein the indication of the first change at the first coordinate location of the client model of the collaborative electronic document is provided with a command having a command type, wherein the method further comprises: A determination is made as to whether a command type of the command satisfies a command type condition, wherein the attribution model is generated in response to a determination that the command type of the command satisfies the command type condition. 4 . The method of claim 1 , wherein the attribution information includes an indication of a user account associated with the first change and a timestamp associated with the first change.

5. The method according to claim 1, further comprising: A revised copy of the server model of the collaborative electronic document having the first change at the second coordinate location is stored, wherein the revised copy is associated with the first revision identifier.

6. The method of claim 1 , wherein generating an attribution model including the coordinate structure corresponding to at least a portion of the coordinate structure of the server model of the collaborative electronic document and including the third coordinate position corresponding to the first coordinate position and the second coordinate position comprises: The attribution model is generated to include a coordinate structure that is smaller than a coordinate structure of the server model of the collaborative electronic document.

7. The method according to claim 1, further comprising: receiving, from a client device, a command indicating a change to a coordinate structure of the client model of the collaborative electronic document; applying, by the server, the change to the coordinate structure of the server model of the collaborative electronic document, wherein the change to the coordinate structure of the server model of the collaborative electronic document is associated with a second revision identifier, and The coordinate structure of the attribution model is modified to reflect changes to the coordinate structure of the server model of the collaborative electronic document, wherein a position of content of the attribution model is adjusted in view of the modified coordinate structure of the attribution model.

8. The method according to claim 7, further comprising: storing a revised copy of the server model of the collaborative electronic document having the changes to the coordinate structure of the server model of the collaborative electronic document, wherein the revised copy including the changes to the coordinate structure of the server model is associated with the second revision identifier; and Updating a third coordinate position of the attribution model with the second revision identifier is suppressed.

9. The method of claim 7, wherein updating the third coordinate position of the attribution model with the first revision identifier further comprises updating the third coordinate position of the attribution model with a coordinate identifier of the third coordinate position, wherein In view of the modified coordinate structure of the attribution model, moving the content of the third coordinate position of the attribution model to the fourth coordinate position of the attribution model, the method further includes: receiving, by the server, a command indicating a second change at a fifth coordinate location of the client model of the collaborative electronic document; applying the second change at a sixth coordinate position of the server model of the collaborative electronic document according to the command, wherein the sixth coordinate position of the server model corresponds to the fifth coordinate position of the client model, and wherein the second change is associated with a third revision identifier; updating a fourth coordinate position of the attribution model using the second revision identifier and a coordinate identifier of the fourth coordinate position; and Attribution information for the second change is stored in association with the third revision identifier in a data store.

10. The method according to claim 9, further comprising: receiving, from a client device, a request for the attribution information associated with a fifth coordinate location of a client model of the collaborative electronic document; identifying the first revision identifier, the third revision identifier, and the coordinate identifier of the third coordinate location associated with a fourth coordinate location of the attribution model using the coordinate location of the fifth coordinate location of the client model of the collaborative electronic document; retrieving the attribution information associated with the third revision identifier; retrieving a first revised copy of the server model of the collaborative electronic document using the first revision identifier; identifying the first change at a second coordinate location of a server model of the collaborative electronic document using a coordinate identifier of a third coordinate location of the attribution model; as well as The attribution information is provided to the client device in response to the request, wherein the attribution information includes the first change.

11. A method for presenting attribution information of a collaborative electronic document, comprising: receiving, via a graphical user interface (GUI) presented at a client device, a request for one or more command options associated with a cell among a plurality of cells of a client model of the collaborative electronic document, wherein the collaborative electronic document is hosted by a cloud-based document editing system, and wherein the collaborative electronic document is concurrently editable by a plurality of users; providing a first GUI element of the GUI identifying the one or more command options including an attribution information command corresponding to the cell; receiving a user selection of the attribution information command to request attribution information for changes to content within the cell of the client model; and In response to receiving the user selection of the attribution information command, presenting the attribution information via a second GUI element in the GUI, the attribution information including a user account identifier of a user who made changes to the content of the cell of the client model of the collaborative electronic document.

12. The method of claim 11, wherein the collaborative electronic document comprises a collaborative electronic spreadsheet document having a collaborative structure including one or more rows and one or more columns, wherein: The cell of the client model of the collaborative electronic document comprises the cell of the collaborative spreadsheet document.

13. The method of claim 11, wherein none of the plurality of users has invoked a command to track changes applied to the cell of the collaborative electronic document.

14. The method according to claim 11, further comprising: In response to receiving the user selection of the attribution information command to request the attribution information, sending an attribution query to the cloud-based document editing system requesting the attribution information, wherein the attribution query includes a coordinate identifier of a first coordinate location, wherein the coordinate identifier identifies the cell of the client model of the collaborative electronic document.

15. The method according to claim 11, further comprising: receiving, via the graphical user interface, a subsequent user selection of the attribution information command to request additional attribution information for another change to content within the cell of the client model; and In response to receiving the subsequent user selection of an attribution information command to request the additional attribution information, presenting, via the second GUI element in the GUI, the additional attribution information including a user account identifier of a user who provided the other change to the content of the cell of the client mode of the collaborative electronic document.

16. A system for tracking attribution information of a collaborative electronic document, comprising: Memory; and a processing device coupled to the memory, the processing device: receiving, by the processing device, an indication of a first change at a first coordinate location of a client model of the collaborative electronic document, wherein the first coordinate location is within a coordinate structure of the client model of the collaborative electronic document; applying the first change at a second coordinate position of a coordinate structure of a server model of the collaborative electronic document, wherein the second coordinate position of the server model corresponds to the first coordinate position of the client model, and wherein the first change is associated with a first revision identifier; generating an attribution model, the attribution model including a coordinate structure corresponding to at least a portion of the coordinate structure of the server model of the collaborative electronic document and including a third coordinate position corresponding to the first coordinate position and the second coordinate position, wherein the attribution model is a different model from the server model; Updating a third coordinate position of the attribution model with the first revision identifier; and Attribution information for the first change is stored in association with the first revision identifier.

17. The system according to claim 16, wherein the processing device further: receiving an attribution query from a client device, the attribution query requesting the attribution information associated with a first coordinate location of a client model of the collaborative electronic document; identifying the first revision identifier associated with a third coordinate location of the attribution model using a coordinate identifier of the first coordinate location of the client model of the collaborative electronic document; retrieving the attribution information associated with the first revision identifier from a data store; as well as The attribution information is provided to the client device in response to the attribution query.

18. The system of claim 16, wherein the indication of the first change at the first coordinate location of the client model of the collaborative electronic document is provided with a command having a command type, the processing device further: Determine whether the command type of the command meets the command type condition, wherein: The attribution model is generated in response to determining that a command type of the command satisfies the command type condition.

19. The system of claim 16, wherein the processing device further: A revised copy of the server model of the collaborative electronic document having the first change at the second coordinate location is stored, wherein the revised copy is associated with the first revision identifier.

20. The system of claim 16, wherein the processing device further: receiving, from a client device, a command indicating a change to a coordinate structure of the client model of the collaborative electronic document; applying the changes to a coordinate structure of the server model of the collaborative electronic document, wherein: The change to the coordinate structure of the server model of the collaborative electronic document is associated with a second revision identifier; and The coordinate structure of the attribution model is modified to reflect changes to the coordinate structure of the server model of the collaborative electronic document, wherein the position of the content of the attribution model is adjusted in view of the modified coordinate results of the attribution model.