Dynamically generating shared spreadsheets according to user references in spreadsheet data

Editing and sharing spreadsheets of a spreadsheet editor system are disclosed. Interactions pertaining to requests of users of the spreadsheet editor system may be treated via natural language queries that are received at an interface of said system. When a first user attempts to share a spreadsheet with a second user, various spreadsheet filtering techniques may cause a new version of the given spreadsheet to be generated for the second user depending on permissions and metadata of one or both users of the editable spreadsheet system. References of the second user may additionally be used to modify a spreadsheet for viewing by the second user.

BACKGROUND

As the technological capacity for organizations to create, track, and retain information continues to grow, a variety of different technologies for managing and storing data in a collaborative way have developed. Demand for customizable features of spreadsheets and tables that allow for quick and easy sharing of data has increased. For example, tabular-formatted spreadsheets and tables are an effective way for employees to organize, view, manipulate, and share data that is relevant to their titles and/or positions within a company.

DETAILED DESCRIPTION OF EMBODIMENTS

Various techniques of dynamically generating shared spreadsheets according to user references in spreadsheet data are disclosed. Spreadsheets may comprise data of multiple datatypes organized in a tabular format with rows and columns. In some embodiments disclosed herein, it may be advantageous for a user to formulate a natural language query to generate a spreadsheet, which can be used to search various data sources to obtain data and populate the spreadsheet in satisfaction of the natural language query. Then, the generated spreadsheet can be shared with other users of the spreadsheet editor. In this way, spreadsheets can be quickly generated from one or multiple data sources without relying upon specific data store knowledge or expertise (e.g., experience with creating Structured Query Language (SQL) queries to obtain and combine data from across multiple database systems). Moreover, once a useful spreadsheet has been generated (e.g., which could occur after trying various different natural language queries), the spreadsheet can be shared with other users and dynamically customized for the users of the shared spreadsheet.

For example, in various embodiments, techniques for dynamically generating shared spreadsheets according to user references in spreadsheet data may provide an efficient way for an employee to redact particularly sensitive information or include only pertinent information prior to sharing a given spreadsheet to another employee without requiring the employee to manually delete or identify certain rows or columns. Instead, user references, user-generated data, and other metadata, as discussed in detail below, may be used to dynamically generate a version of the spreadsheet that does not provide the sensitive information (or includes the pertinent information). Additionally, users may create and edit tables for planning events, tracking metrics, or managing other data that require either involvement, organization, or input from other users. Techniques for dynamically generating shared spreadsheets according to user references in spreadsheet data may provide a secure way to guarantee that the distribution of and updates to data is securely coordinated between different users. For instance, a dynamically generated version of a spreadsheet may only include information that is editable by the user associated with that version of the spreadsheet. In this way, edits to other user's data may be blocked as they are not visible or editable by that user. Moreover, the techniques for dynamically generating shared spreadsheets according to user references in spreadsheet data may provide a scalable way to produce custom spreadsheets in scenarios for a large number of shared users without increasing the creation or maintenance costs of enforcing access controls on the data.

This specification begins with a general description of a spreadsheet editor system that supports natural language querying and dynamic spreadsheet generation. Then various examples of spreadsheet editor implementations including different components, or arrangements of components that may be employed as part of implementing the spreadsheet editor system, such as may be used to implement a spreadsheet editor service in a provider network, are discussed. A number of different methods and techniques to implement dynamically generating shared spreadsheets according to user references in spreadsheet data are then discussed, some of which are illustrated in accompanying flowcharts. Finally, a description of an example computing system upon which the various components, modules, systems, devices, and/or nodes may be implemented is provided. Various examples are provided throughout the specification.

FIG.1is a logical block diagram illustrating the process of sharing a spreadsheet of a spreadsheet editor with another user, according to some embodiments.

InFIG.1, spreadsheet editor system100may comprise an interface, such as interface110, to display one or more editable spreadsheets to users of spreadsheet editor system100. Interface110may comprise at least interface for User A112and interface for User B114, wherein Users A and B are users of spreadsheet editor system100. In some embodiments, interface for User A112and interface for User B114may resemble User A profile650, User B profile652, and User A profile750(see descriptions forFIGS.6A-7Dherein).

Spreadsheet editor system100may also comprise user-generated data, such as user-generated data120, associated to users of spreadsheet editor system100. In some embodiments, user-generated data120may comprise user-specific data within user information122, such as User A information124, User B information126, and User C information128. In some embodiments, user-generated data120may comprise other types of data and/or metadata that are relevant to the spreadsheet editor system100, such as sharing rules330, filtering rules332, or viewing rules334(see the description ofFIG.3herein).

In some embodiments, interface110may be used to make, write, and send requests associated to spreadsheets of spreadsheet editor system100via natural language queries. Interface110is configured to receive one or more criteria pertaining to generating and/or sharing spreadsheets, according to some embodiments. In some embodiments, request from User A to share spreadsheet with User B116may comprise a natural language request. A natural language query of spreadsheet editor system100may not conform to any specify query language or other structured language, protocol, or parameters for interfacing with specific data storage systems for data stores140and/or spreadsheet editor system100, but instead may exhibit natural human language features including various verbs, nouns, clauses, phrases, or other human syntax for expressing a query for a result generated or returned from data stores140, in various embodiments. As a result, natural language queries may include multiple formulations of input words that may query for the same result.

In some embodiments, request from User A to share spreadsheet with User B116may pass through user-generated data120before a data pull via data stores140is made. For example, spreadsheet editor system100may verify, via User A information124, that User A has an appropriate level of permission to share the spreadsheet with User B. Data in data stores140, such as data142, data144, data146, and data148, may comprise data associated with spreadsheets of spreadsheet editor system100that may be requested via interface110, such as request from User A to share spreadsheet with User B116.

In some embodiments, user-generated data120may also be used to verify, via User B information126, that User B has an appropriate level of permissions to view the spreadsheet. In some embodiments of this example, portions of the spreadsheet as viewed by User A may be removed or deleted before generate spreadsheet for User B118is complete if it is found via user-generated data120that User B does not have the same level of permissions for viewing the spreadsheet as viewed by User A. This may be referred to as a version of the spreadsheet, or User B's version of the spreadsheet. The processes described inFIG.1may also resemble Request430(see description forFIG.4herein), according to some embodiments.

FIG.2is a logical block diagram illustrating a request from a user of a spreadsheet editor to view a spreadsheet, according to some embodiments.

InFIG.2, spreadsheet editor system200may comprise an interface, such as interface210, to display one or more editable spreadsheets to users of spreadsheet editor system200. Interface210may comprise at least interface for User A212, wherein User A is a user of spreadsheet editor system200. In some embodiments, interface for User A212may resemble User A profile650and User A profile750(see descriptions forFIGS.6A-7Dherein).

Spreadsheet editor system200may also comprise user-generated data, such as user-generated data220, associated to users of spreadsheet editor system200. In some embodiments, user-generated data220may comprise user-specific data and/or metadata within user information222, such as User A information224, User B information226, and User C information228. In some embodiments, user-generated data220may comprise other types of data and/or metadata that are relevant to the spreadsheet editor system200, such as sharing rules330, filtering rules332, or viewing rules334(see the description ofFIG.3herein).

The processes described inFIG.2may also resemble Editable spreadsheet function450(see description forFIG.4herein), according to some embodiments. User A may send a natural language request (see description ofFIG.1herein) via interface for User A, such as request from User A pertaining to spreadsheet display216. Example embodiments of such a request may comprise a request for re-organizing data in a given spreadsheet, or updating (adding, deleting, copying, moving) data in the given spreadsheet. Spreadsheet editor system200may then verify, via User A information224, that User A has permission to re-organize and/or update data in the given spreadsheet. In some embodiments, user-generated data220may be used to verify that User A is the spreadsheet manager of the given spreadsheet and therefore has permission to perform one or more of said editable spreadsheet functions on the given spreadsheet. Data in data stores240, such as data242, data244, data246, and data248, may comprise data associated with the given spreadsheet and therefore may be used to complete the request. Finally, User A may be provided with the updated table at interface for User A212via generate table for User A based on table display request218.

FIG.3is a logical block diagram illustrating types of user-generated data that may be used to generate user-specific versions of spreadsheets, according to some embodiments.

FIG.3demonstrates types of elements that may be stored in user-generated data320. In some embodiments, user-generated data320may comprise similar elements as user-generated data120and user-generated data220, and may be incorporated into the processes shown inFIG.1andFIG.2. Various synonyms, alias, descriptions, possible cell values, or other metadata that describes the content of given spreadsheets may be included in user-generated data320. In addition, user information322comprises data specific to users of the spreadsheet editor, such as User A information324, User B information326, and User C information328. It should be understood by the reader that user information322may comprise user information for each user of the spreadsheet editor, or only certain relevant users, according to some embodiments. Such data may comprise information that is relevant to the spreadsheet editor, such as a given user's name and role within the company, such as “Name: John Doe” and “Role: Marketing employee” shown in User C information328. In some embodiments, user information322may comprise additional company-specific information, such as email addresses of the employees, a list of spreadsheet users with a security clearance, or a list of spreadsheet users that are allowed to view sensitive information, such as an accounting department who is allowed to view a column of social security numbers. User information322may additionally comprise company structure, company hierarchy, employee roles and/or titles (e.g. Sales, Marketing, Finance, Project Management, etc.), or other data specific to a given user set of the spreadsheet editor.

User information322may be used as input(s) to sharing rules330, filtering rules332, and viewing rules334. For example, in embodiments in which only the accounting department may view the column of social security numbers, and in which User C information328labels User C as a marketing employee, User C information328may be used as input to viewing rules330, sharing rules332, or filtering rules334if an accounting employee tries to share a spreadsheet containing the column of social security numbers with User C. In some embodiments, the one or more references to a given user within user information322may be used to generate a version of a given spreadsheet that includes portions of the data in the spreadsheet that reference the given user.

In some embodiments, viewing rules330, sharing rules332, or filtering rules334may comprise user-defined rules or definitions for the spreadsheet editor. For example, a given user of the spreadsheet editor may define, via viewing rules330, that only employees within the accounting department may view data pertaining to social security numbers. In such embodiments, data pertaining to social security numbers would be filtered from view before a version of the spreadsheet comprising at least the social security numbers is generated for a user who is not in the accounting department. In second example in which user information322comprises email addresses of each user, a given user of the spreadsheet editor may define, via sharing rules332, that a given spreadsheet may not be shared with any user who does not have a company email address (e.g. johndoe@company.com). In such embodiments, upon receiving a request to share the given spreadsheet with a user of the spreadsheet editor that does not have the specified company email address (e.g. marybeth@enterprise.com), the spreadsheet is not shared. In a third example, a given user of the spreadsheet editor may define, via filtering rules334, that employee names are filtered from view when a given spreadsheet is shared with a user who is not employed by the company. It should be understood by the reader that combinations of such rules, additional rules, or no user-defined rules may be placed in viewing rules330, sharing rules332, and334, and that these examples are meant to be embodiments of features and options that are customizable to each set of users of the spreadsheet editor.

In addition, user-generated data320may comprise (or be linked to) one or more spreadsheet definitions for a given user. For example, a spreadsheet definition associated with User A may be stored as part of User A information324which may be referenced when User A either creates a spreadsheet or requests to share a spreadsheet with another user via one or more criteria received at the interface. For example, a spreadsheet definition may be a natural language query (or the one or more queries determined from the natural language query) used to create the spreadsheet.

User-generated data120and user-generated data220may similarly comprise such elements as those shown inFIG.3, according to some embodiments. It should be understood by the reader thatFIG.3represents some embodiments of user-generated data320. However, other embodiments specific to the given user set for a spreadsheet editor may also apply and are meant to be encompassed in the disclosure herein. Additionally, filtering may refer to redacting, removing, or otherwise altering the spreadsheet for view by the respective user.

FIG.4is a sequence diagram illustrating three possible scenarios that a client of a spreadsheet editor could request of a spreadsheet editor service, according to some embodiments.

FIG.4comprises Request410, Request430, and Editable spreadsheet function450, which exemplify example embodiments of interactions between Client400, Spreadsheet editor402, and Data stores404. In some embodiments, Client400may resemble clients570of provider network500, which will be discussed in more detail below. In some embodiments, Spreadsheet editor402may resemble spreadsheet editor service510within provider network500. It should be understood by the reader that clients570of spreadsheet editor service510within provider network500(see description forFIG.5herein) and users of a spreadsheet editor (see description forFIGS.6A-9herein) may be used interchangeably. For example, in the embodiments shown inFIG.4, User A and User B may be considered as clients of Client(s)400. In another example, a client of Client(s)400may refer to a company comprising multiple users of a spreadsheet editor service that together may be considered as one client of Client(s)400. Furthermore, in some embodiments, Data stores404may resemble data stores140and data stores240(see description forFIGS.1-2herein), and may also resemble data storage service(s)540(see description forFIG.5herein).

In Request410, a client of Client(s)400submits a request to create a spreadsheet for User A via412to Spreadsheet editor402. In some embodiments, request412may comprise one or more criteria specified via the interface, such as a natural language query. In other embodiments, however, a source spreadsheet with one or more filtering definitions may be already provided to the spreadsheet editor. As described above, User A may themselves be a client of Client(s)400, or User A's company may submit request412on behalf of User A as a client of Client(s)400. Once Spreadsheet editor402receives request412, Spreadsheet editor402sends a request to Data stores404to pull data via414. Data stores404then retrieves the data pertaining to the natural language query from one or more data storage locations (see descriptions forFIGS.1-2and3herein). Spreadsheet editor402may request to filter the data via416based on the user (client) that will be receiving and/or viewing the data. This filtering via416may comprise filtering via user-specific data (see descriptions for user-generated data120,220, and320inFIGS.1-3herein). Finally, the client of Client(s)400may receive the filtered spreadsheet via418, according to some embodiments. The client of Client(s)400may view the generated spreadsheet via an interface of the spreadsheet editor402, which is discussed in detail in descriptions forFIGS.1-2and5-9herein.

In Request430, a first client, such as User A of a spreadsheet editor service, may request to share a given spreadsheet with a second client, such as User B of the spreadsheet editor service via432. Once Spreadsheet editor402receives the request to share the given spreadsheet with a second client, Spreadsheet editor402sends a request to Data stores404to pull data via434. Data pull434may comprise pulling data pertaining to the given spreadsheet, according to some embodiments. Data stores404then retrieves the data pertaining to the request from one or more data storage locations (see descriptions forFIGS.1-2and3herein). Spreadsheet editor402then requests to filter the data via436based on the user (client) that will be receiving and/or viewing the data. This filtering via436may comprise filtering via user-specific data (see descriptions for user-generated data120,220, and320inFIGS.1-3herein). Furthermore, in some embodiments, such as those described in blocks808and910below, the filtering via436may occur according to respective references to the user (client) who will be receiving and/or viewing the data. In embodiments shown by Request430, said references refer to User B. Finally, the client of Client(s)400(User B) may receive the filtered spreadsheet via438, according to some embodiments. The client of Client(s)400may view the generated spreadsheet via an interface of the spreadsheet editor402, which is discussed in detail in descriptions forFIGS.1-2and5-9herein.

In Editable spreadsheet function450, a client of Client(s)400may request to add a new row of data in a given spreadsheet via452. In some embodiments, the client may interact with the spreadsheet editor via an interface, and make the request to add a new row via the interface, as shown in the embodiments ofFIGS.7A-7Dbelow. In response to a client of Client(s)400inputting one or more new portions of data into a given spreadsheet, Spreadsheet editor402requests, via454, that the new data be stored in data storage by Data stores404. In some embodiments, a filtered version of the spreadsheet for one or more other users of the spreadsheet may be updated via456based on the addition of the new row via452. For example, if User A completes Request430to share the spreadsheet with User B, and then User A completes Editable spreadsheet function450, the filtered version of the spreadsheet for User B in438will be updated via456. It should be understood by the reader that Editable spreadsheet function450is meant to be an exemplary editable spreadsheet function, and that other embodiments of Editable spreadsheet function450may comprise deleting a row of data in a given spreadsheet, editing data in an already-existing row in a given spreadsheet, or otherwise editing the tabular format(s) of a given spreadsheet.

FIG.5is a logical block diagram illustrating a provider network offering a spreadsheet editor service that implements natural language query processing, including various data storage and processing services, according to some embodiments.

FIG.5is a logical block diagram illustrating a provider network offering a spreadsheet editor service that implements natural language query processing, including various data storage and processing services, according to some embodiments. Provider network500may be a private or closed system or may be set up by an entity such as a company or a public sector organization to provide one or more services (such as various types of cloud-based storage) accessible via the Internet and/or other networks to clients570, in some embodiments. Provider network500may be implemented in a single location or may include numerous data centers hosting various resource pools, such as collections of physical and/or virtualized computer servers, storage devices, networking equipment and the like (e.g., computing system1000described below with regard toFIG.10), needed to implement and distribute the infrastructure and services offered by the provider network500. In some embodiments, provider network500may implement various computing systems, platforms, resources, or services, such as a spreadsheet editor service510, compute services, database service(s)530, (e.g., relational or non-relational (NoSQL) database query engines, map reduce processing, data flow processing, and/or other large scale data processing techniques), data storage service(s)540, (e.g., an object storage service, block-based storage service, or data storage service that may store different types of data for centralized access), data stream and/or event services, and other services (any other type of network based services (which may include various other types of storage, processing, analysis, communication, event handling, visualization charting, and security services not illustrated), including other service(s) of the provider network550that may provide additional functionalities for spreadsheet editor service510.

In various embodiments, the components illustrated inFIG.5may be implemented directly within computer hardware, as instructions directly or indirectly executable by computer hardware (e.g., a microprocessor or computer system), or using a combination of these techniques. For example, the components ofFIG.5may be implemented by a system that includes a number of computing nodes (or simply, nodes), each of which may be similar to the computer system embodiment illustrated inFIG.10and described below. In various embodiments, the functionality of a given system or service component (e.g., a component of data storage service(s)540) may be implemented by a particular node or may be distributed across several nodes. In some embodiments, a given node may implement the functionality of more than one service system component (e.g., more than one data store component).

In various embodiments, spreadsheet editor service510may provide a scalable, serverless, and machine-learning powered service to create visualizations and analysis for data (e.g., dashboards, charting, etc.) to include in various applications (e.g., websites) accessing various data stores, such as data stored in database service(s)530, data storage service(s)540, or other service(s) of the provider network550. Spreadsheet editor service510may implement interface518, which may be implemented as various types of programmatic (e.g., Application Programming Interfaces (APIs)), command line, and/or graphical user interfaces to support the management of data sets for analysis, request, configure, and/or otherwise obtain new or existing analysis, and/or perform natural language queries, as discussed below.

Spreadsheet editor service510may implement data management512, in various embodiments. Data management512may allow users to upload, identify, describe, augment, annotate, or otherwise prepare data sets for access, analysis, and/or visualization by spreadsheet editor service510. For example, various requests to describe data, such as provide descriptions of columns, field values, or other information, which may be used enhance information that may be found in a data storage system (e.g., data in addition to a database schema or other table description). As discussed above with regard toFIGS.1-3, such data management may be used as part of natural language query processing in some embodiments (e.g., as inputs to machine learning models). Data management512may additionally manage functions related to requests of users of spreadsheet editor service510. For example, if a first user requests to share a spreadsheet with a second user of spreadsheet editor survive510, data management512may create a copy of the spreadsheet and store it in one or more data stores via data storage service(s)540. In a second example, if a user adds a new row of data to a spreadsheet via interface518(see also the description forFIGS.7A-7D), data management512may group or organize the data for storage in one or more data stores via data storage service(s)540.

Spreadsheet editor service510may implement spreadsheet editor application514, which may perform the various operations to access data, analyze data, and/or generate a corresponding spreadsheet. For example, spreadsheet editor application514may understand and generate corresponding requests to obtain data from different database service(s)530, data storage service(s)540, or other service(s) of the provider network550according to the corresponding interfaces supported by those services (e.g., query language, API, protocols, etc.). Spreadsheet editor application514may be able to perform various data processing operations to determine and generate requested results (e.g., applying various aggregation, statistical analyses, or other operations), and also perform various data processing operations for natural language queries, in some embodiments. In some embodiments, spreadsheet editor application514may resemble the implementations discussed below with regard toFIGS.4and6A-9.

Spreadsheet editor service510may implement natural language query processing516, as discussed in detail below with regard toFIGS.4and6A-7D, in order to handle responses to natural language queries to perform analysis, visualization, and organization using spreadsheet editor service510, in some embodiments. For example, different data sets may be created, identified, or managed for access by natural language query processing516. Natural language query processing516may implement multiple processing stages for executing one or more natural language queries, according to some embodiments. For example, a first processing stage may involve determining or otherwise recognizing one or more entities within a natural language query as data stored in one or more data stores as well as mappings, matches, or other links to the data stored in the one or more data stores to respective columns of a given spreadsheet. In some embodiments, a machine learning model (e.g., a Deep Neural Network(DNN)) that has been trained to recognize the entities (e.g., databases, database columns, or other stored data) from a natural language text string may be implemented. Given a natural language query, such as “Show me monthly sales per product for the last 3 months,” the machine learning model can be applied to identify entities and entity types in the query: monthly, sales, product, months, and 3. These entities can then be matched with schema information stored for the various data stores (e.g., database table schemas) which can then be used to determine which data stores to query. In some embodiments, intent machine learning models (e.g., another DNN) may be trained to determine the various predicates or other features of a natural language query (e.g., “last 3 months”) and translate the recognized entities and intent of the natural language query into a query language (e.g., SQL).

Natural language query processing516may then retrieve, via data storage service(s)540, an initial selection of data in a second processing stage based on information gathered in the first processing stage. The second processing stage may also involve consulting metadata, such as user-generated data320, in order to prepare the result of a given natural language query. A third processing stage may comprise providing the result(s) of the natural language query to the user via interface518.

In various embodiments, database service(s)530may be various types of data processing services that perform general or specialized data processing functions (e.g., analytics, big data querying, time-series data, graph data, document data, relational data, structured data, or any other type of data processing operation) over data that is stored across multiple storage locations, in some embodiments. For example, in at least some embodiments, spreadsheet editor service510may include various types of database services (e.g., relational) for storing, querying, and updating data. Such services may be enterprise-class database systems that are scalable and extensible. Queries may be directed to a database in database service(s)530that is distributed across multiple physical resources, as discussed below, and the database system may be scaled up or down on an as needed basis, in some embodiments. The database system may work effectively with database schemas of various types and/or organizations, in different embodiments. In some embodiments, clients/subscribers may submit queries or other requests (e.g., requests to add data) in a number of ways, e.g., interactively via an SQL interface to the database system or via Application Programming Interfaces (APIs). In other embodiments, external applications and programs may submit queries using Open Database Connectivity (ODBC) and/or Java Database Connectivity (JDBC) driver interfaces to the database system.

In some embodiments, other service(s) of the provider network550may be various types of data processing services to perform different functions (e.g., query or other processing engines to perform functions such as anomaly detection, machine learning, data lookup, or any other type of data processing operation). For example, in at least some embodiments, other service(s) of the provider network550may include a map reduce service that creates clusters of processing nodes that implement map reduce functionality over data stored in one of data storage service(s)540. Various other distributed processing architectures and techniques may be implemented by database service(s)230(e.g., grid computing, sharing, distributed hashing, etc.). Note that in some embodiments, data processing operations may be implemented as part of data storage service(s)540(e.g., query engines processing requests for specified data).

Data storage service(s)540may implement different types of data stores for storing, accessing, and managing data on behalf of clients570as a network-based service that enables clients570to operate a data storage system in a cloud or network computing environment. For example, one data storage service of data storage service(s)540may be implemented as a centralized data store so that other data storage services of data storage service(s)540may access data stored in the centralized data store for processing and or storing within the other data storage services, in some embodiments. Such an implementation of data storage service(s)540may be implemented as an object-based data store, and may provide storage and access to various kinds of object or file data stores for putting, updating, and getting various types, sizes, or collections of data objects or files. Such data storage service(s)540may be accessed via programmatic interfaces (e.g., APIs) or graphical user interfaces. Data storage service(s)540may provide virtual block-based storage for maintaining data as part of data volumes that can be mounted or accessed similar to local block-based storage devices (e.g., hard disk drives, solid state drives, etc.) and may be accessed utilizing block-based data storage protocols or interfaces, such as internet small computer interface (iSCSI).

In various embodiments, data stream and/or event services may provide resources to ingest, buffer, and process streaming data in real-time, which may be a source of data. In some embodiments, data stream and/or event services may act as an event bus or other communications/notifications for event driven systems or services (e.g., events that occur on provider network500services and/or on-premise systems or applications).

Generally speaking, clients570may encompass any type of client configurable to submit network-based requests to provider network500via network580, including requests for spreadsheet editor service510. For example, a given client of clients570may include a suitable version of a web browser, or may include a plug-in module or other type of code module that may execute as an extension to or within an execution environment provided by a web browser. Alternatively, a client570may encompass an application such as a database application (or user interface thereof), a media application, an office application or any other application that may make use of resources in provider network500to implement various features, systems, or applications (e.g., to store and/or access the data to implement various applications). In some embodiments, such an application may include sufficient protocol support (e.g., for a suitable version of Hypertext Transfer Protocol (HTTP)) for generating and processing network-based services requests without necessarily implementing full browser support for all types of network-based data. That is, client570may interact directly with provider network500. In some embodiments, client570may generate network-based services requests according to a Representational State Transfer (REST)-style network-based services architecture, a document- or message-based network-based services architecture, or another suitable network-based services architecture.

In some embodiments, a client of clients570may provide access to provider network500to other applications in a manner that is transparent to those applications. For example, a client of clients570may integrate with an operating system or file system to provide storage on one of data storage service(s)540(e.g., a block-based storage service). However, the operating system or file system may present a different storage interface to applications, such as a conventional file system hierarchy of files, directories and/or folders. In such an embodiment, applications may not need to be modified to make use of the storage system service model. Instead, the details of interfacing to the data storage service(s)540may be coordinated by client570and the operating system or file system on behalf of applications executing within the operating system environment.

Clients570may convey network-based services requests (e.g., natural language queries) to and receive responses from provider network500via network580. In various embodiments, network580may encompass any suitable combination of networking hardware and protocols necessary to establish network-based-based communications between clients570and provider network500. For example, network580may generally encompass the various telecommunications networks and service providers that collectively implement the Internet. Network580may also include private networks such as local area networks (LANs) or wide area networks (WANs) as well as public or private wireless networks. For example, both a given client570and provider network500may be respectively provisioned within enterprises having their own internal networks. In such an embodiment, network580may include the hardware (e.g., modems, routers, switches, load balancers, proxy servers, etc.) and software (e.g., protocol stacks, accounting software, firewall/security software, etc.) necessary to establish a networking link between given client570and the Internet as well as between the Internet and provider network500. It is noted that in some embodiments, clients570may communicate with provider network500using a private network rather than the public Internet.

FIG.6Ais an example interface of a spreadsheet editor for User A illustrating a given spreadsheet with several editable spreadsheet functions and a natural language query prompt, according to some embodiments.

InFIG.6A, interface600represents a given set of spreadsheets, e.g.

Spreadsheets602, that may be viewed by User A. Spreadsheets602may comprise spreadsheets associated to User A, such as Booth Staffing, Breakout Agenda, and Speakers. Spreadsheets in Spreadsheets602may comprise data that are arranged or organized in tabular (e.g., data tables, such as large fact/dimension tables) formats with columns and rows, and/or multiple structural (e.g. structured, semi-structured, or unstructured) formats that may apply to different styles of categorical data. Spreadsheets in Spreadsheets602may comprise data of multiple datatypes (e.g. integers, floats, characters, strings, composite types, etc.) within a given spreadsheet.

In some embodiments, interface600is implemented as a graphical user interface. However, interface600may also be implemented as various types of programmatic (e.g., Application Programming Interfaces (APIs)) or command line interfaces to support the methods and systems described herein, according to some embodiments. In some embodiments, interface600may be implemented as a web-based graphical user interface, wherein a user profile may be loaded, such as User A profile650, and User A subsequently may view Spreadsheets602.

In the example shown inFIG.6A, the spreadsheet named Booth Staffing604may be selected from User A's Spreadsheets602for viewing and/or editing. Booth Staffing604may comprise data of the spreadsheet that is arranged in a tabular format, according to some embodiments. Such a tabular format may comprise columns, such as Row610, Name612, Supervisor614, Start Time616, and End Time618, and rows, such as rows1,2,3,4, and5of Row610. Spreadsheet Booth Staffing604may also comprise a natural language query prompt, such as natural language query prompt630, and one or more functions that allow Booth Staffing604to be edited by User A, such as “New row?”632. In some embodiments, functions such as “New row?”632are limited to use by the spreadsheet manager, or the user who has created the spreadsheet via one or more criteria specified via the interface of the spreadsheet editor. This may be advantageous for the methods and techniques described herein, as this prevents users who may have permission to view all or parts of Booth Staffing604from overwriting data of the spreadsheet. Functions such as “New row?”632will be further detailed inFIGS.7A-7D.

In the example shown inFIG.6A, User A may click on natural language query prompt630, which, by default, prompts User A to “Ask your data anything,” and begin to write a request to the spreadsheet editor service, according to some embodiments.FIG.6Bshows the response of the spreadsheet editor service to a request from User A via natural language query prompt630to “Show Booth Staffing by start time.”

FIG.6Bis an example interface of a spreadsheet editor for User A illustrating a given spreadsheet and a natural language request from User A for organizing data of the spreadsheet, according to some embodiments.

InFIG.6A, User A has written a natural language request pertaining to Booth Staffing604via natural language query prompt630requesting to “Show Booth Staffing by start time.” In response to this request,FIG.6Bshows that interface600displays the data in spreadsheet Booth Staffing604organized by the column Start Time616, instead of by Name612, as was shown inFIG.6A.

FIG.6Cis an example interface of a spreadsheet editor for User A illustrating a given spreadsheet and a natural language request from User A for sharing data of the spreadsheet with User B, according to some embodiments.

InFIG.6C, User A writes a new request via natural language query prompt630to “Share Booth Staffing with User B.” In some embodiments, User A may write this request via natural language query prompt630, and the spreadsheet editor service, via interface600, will recognize the component “Booth Staffing” as referring to one of User A's Spreadsheets602, and recognize the component “User B” as referring to one of the users of the spreadsheet service.

FIG.6Dis an example interface of a spreadsheet editor for User A illustrating a given spreadsheet and a natural language request from User A for sharing data of the spreadsheet with User B in which the interface of the spreadsheet editor provides options to autocomplete the natural language request from User A, according to some embodiments.

In addition to the embodiments shown inFIG.6C, the natural language query prompt630may attempt to autocomplete the natural language request from User A, according to some embodiments. In the example shown inFIG.6D, User A may begin to write “Share Booth Staffing with-” and interface600may recognize that User A intends to request that Booth Staffing604be shared with another user of the spreadsheet editor service, in which case interface600may provide User A with options to autocomplete the natural language request. In some such embodiments, interface600may provide a drop-down menu such as drop-down menu634in which User A may select the user that they would like to request that Booth Staffing604is shared with. Drop-down menu634may comprise exclusively the names of known users of the spreadsheet editor service. This may be advantageous for the methods and systems described herein, since there may be less ambiguity in the natural language request written into natural language query prompt630if User A is prompted to select from a pre-existing list of users of the spreadsheet editor service. In some embodiments, such a list of known users of the spreadsheet editor service may be pulled from user-generated data120, user-generated data220, or user-generated data320inFIG.1,FIG.2, orFIG.3, respectively. In some embodiments, drop-down menu634may comprise an option for “All users.” In such embodiments, “all users” may refer to users specified in user-generated data120, user-generated data220, or user-generated data320, and one or more filtering rules (see descriptions for Viewing rules330, Sharing rules332, and Filtering rules334herein) may be applied based on the users referenced in “All users.”

FIG.6Eis an example interface of a spreadsheet editor for User B illustrating a given spreadsheet that has been shared with them by request of User A, according to some embodiments.

InFIG.6E, interface600represents a given set of spreadsheets, e.g. Spreadsheets670, that may be viewed by User B. As described above forFIGS.6A-6D, interface600may be implemented as a web-based graphical user interface, wherein a user profile may be loaded. For the example shown inFIG.6E, User B profile652may be loaded, and User B subsequently may view spreadsheets listed in Spreadsheets670. In the example shown inFIG.6E, User A has sent User A's spreadsheet Booth Staffing604to User B, and now User B may view a version of Booth Staffing604called Booth Staffing672. Similar to Booth Staffing604, Booth Staffing672may comprise data of the spreadsheet that is arranged in a tabular format, according to some embodiments. Such a tabular format may comprise columns, such as Row680, Name682, Supervisor684, Start Time686, and End Time688, and rows, such as rows1and2of Row680. However, in the example shown inFIG.6E, rows3,4, and5of Row610, shown inFIGS.6A-6D, have been removed from Booth Staffing672according to viewing permissions of User B. The reader may refer to the description above for user-generated data120, user-generated data220, and/or user-generated data320for more information on such filtering processes.

In some embodiments, User B may not be able to use functions that would allow Booth Staffing672to be edited by User B, such as “New row?”632shown inFIGS.6A-6D, which is reserved for the user who has created the given spreadsheet, e.g. the spreadsheet manager User A in the examples shown inFIGS.6A-6E. However, Booth Staffing672may still comprise a natural language query prompt, such as natural language query prompt674in which User B may write a request to the spreadsheet editor service.

FIG.7Ais another example interface of a spreadsheet editor for User A illustrating a given spreadsheet with several editable spreadsheet functions and a natural language query prompt, according to some embodiments.

InFIG.7A, interface700represents a given set of spreadsheets, e.g. Spreadsheets702, that may be viewed by User A. In some embodiments, interface700is implemented as a graphical user interface. However, interface700may also be implemented as various types of programmatic (e.g., Application Programming Interfaces (APIs)) or command line interfaces to support the methods and systems described herein, according to some embodiments. In some embodiments, interface700may be implemented as a web-based graphical user interface, wherein a user profile may be loaded, such as User A profile750, and User A subsequently may view Spreadsheets702.

In the embodiments shown inFIG.7A, a spreadsheet named Booth Staffing704may be selected from User A's Spreadsheets702for viewing and/or editing. Booth Staffing604may comprise data of the spreadsheet that is arranged in a tabular format, according to some embodiments. Such a tabular format may comprise columns, such as Row710, Name712, Supervisor714, Start Time716, and End Time718, and rows, such as rows1,2,3,4, and5of Row710. Spreadsheet Booth Staffing704may also comprise a natural language query prompt, such as natural language query prompt730, and one or more functions that allow Booth Staffing704to be edited by User A, such as “New row?”732. In the example shown inFIG.7A, User A may click on “New row?”732in order to write new data into Booth Staffing704, according to some embodiments. This may also be considered as a new data entry.

FIG.7Bis an example interface of a spreadsheet editor for User A illustrating an editable spreadsheet function of adding data to a new row of a given spreadsheet, in which User A is prompted to choose from a pre-existing list in order to complete the “Name” column, according to some embodiments.

InFIG.7B, User A begins to fill in data to row6of Row710. In column Name712, User A is prompted to choose the name of a user that this row6of Row710pertains to. In some embodiments, User A is prompted to select from a pre-existing list of users of the spreadsheet editor service. As shown inFIG.7B, User A is prompted to select from a drop-down menu such as drop-down menu734which comprises a selection of users of the spreadsheet editor service. The reader may refer to the description above for user-generated data120, user-generated data220, and/or user-generated data320for more information on how the spreadsheet editor service may use user-specific data and/or metadata to create such lists. In the example shown inFIG.7B, User A selects User H from drop-down menu734. In some embodiments, User A may instead write the name of the user that they would like to add to row6of Row710.

FIG.7Cis an example interface of a spreadsheet editor for User A illustrating an editable spreadsheet function of adding data to a new row of a given spreadsheet, in which the “Supervisor” column is autocompleted by the spreadsheet editor based on User A's selection for the “Name” column, as shown inFIG.7B, according to some embodiments.

InFIG.7C, in response to User A selecting User H to be filled in column Name712for row6of Row710, data in row6of Row710is autocompleted for column Supervisor714. User A may then click on the remaining columns for row6of Row710in order to complete the data entry.

FIG.7Dis an example interface of a spreadsheet editor for User A illustrating an editable spreadsheet function of adding data to a new row of a given spreadsheet, in which the “Start Time” and “End Time” columns may be completed by User A, according to some embodiments.

InFIG.7D, data entry for row6of Row710is complete, and User A may choose to complete another data entry via clicking on “New row?”742, or choose to complete the one or more other functions that allow Booth Staffing704to be edited by User A. In some embodiments,FIGS.7A-7Dmay resemble Editable spreadsheet function450shown inFIG.4.

FIG.8is a high-level flowchart illustrating various methods and techniques to implement sharing, via a request from a first user of a spreadsheet editor, a given spreadsheet with a second user, according to some embodiments.

In some embodiments, the methods and techniques described herein may be implemented via the processes shown inFIG.8. In block800, a spreadsheet may be generated via one or more criteria specified via an interface of the spreadsheet editor to the spreadsheet editor. In some embodiments, the one or more criteria comprises a natural language query submitted to the spreadsheet editor. In some embodiments, the natural language query may be submitted via the interface by a user of the spreadsheet editor, such as via natural language query prompt630or natural language query prompt730. In some embodiments, block800may correspond to create a spreadsheet for User A412, inFIG.4.

It should be understood by the reader that block800encompasses both the generation of a new spreadsheet and the generation of a spreadsheet derived from a pre-existing spreadsheet of the spreadsheet editor. For example, the spreadsheet that will be discussed below in blocks802,804,806,808, and810may have already been previously created or otherwise already exist within the spreadsheet editor. In some embodiments, a source spreadsheet may be provided. For example, in the embodiments shown inFIG.6A-6E, User A may click on a given spreadsheet from Spreadsheets602, such as Booth Staffing604, and submit a natural language query pertaining to Booth Staffing604via natural language query prompt630. Such a natural language query may resemble a variation of the natural language query shown inFIG.6B, such as “Show Booth Staffing by start time and save the spreadsheet as Booth Staffing Schedule.”

In some embodiments, upon subscription to a spreadsheet editor, a user of a spreadsheet editor may be prompted to use one or more templates and/or styles of spreadsheets proposed by the spreadsheet editor, and the user may then decide to use one of said pre-existing spreadsheet templates and edit the template accordingly. Such proposed templates may cater to the field of business that the users of the spreadsheet editor are in, and may comprise suggested templates such as “Event Planning,” “Marketing Campaign Tracker,” and “Product Launch.” Proposed templates may also cater to the role (e.g. Sales, Marketing, Finance, Project Management, etc.) of a given spreadsheet manager or user of the spreadsheet editor. The proposed templates may represent broad business domains and various spreadsheet structures (e.g. structured, semi-structured, or unstructured setups) in order to encapsulate the breadth of options available in the spreadsheet editor to the user of the spreadsheet editor.

As denoted by the dashed line surrounding block800, this step may be considered as optional, according to some embodiments. For example, for the embodiments shown inFIGS.6A-6E, User A may skip the natural language request “Show Booth Staffing by start time,” as shown inFIG.6B, and directly request to “Share Booth Staffing with User B,” as shown inFIG.6C-6D. In block802, a first request associated with a first user of the spreadsheet editor is received, via an interface of the spreadsheet editor, to make the spreadsheet accessible to a second user of the spreadsheet editor. Block802may resemble the methods and techniques described by Request430and/or natural language query prompt630shown inFIGS.6C-6D. Block802may also comprise filtering the data in the given spreadsheet via user-generated data, such as user-generated data120, user-generated data220, and user-generated data320. For example, for the embodiments shown inFIGS.6C-6E, User A requests to share Booth Staffing604to User B, and, based at least in part on user-generated data for User B, such as user-generated data120, user-generated data220, and user-generated data320, User B may access the version of the Booth Staffing604shown inFIG.6Ecalled Booth Staffing672.

In some embodiments, the interface described in block802may resemble interface600and interface700. The interface described in block802may be implemented as a web-based graphical user interface, wherein a user profile may be loaded, such as User A profile650, User B profile652, and User A profile750, according to some embodiments. It should also be understood by the reader that the interface in block802may comprise user-specific interfaces, such as interface110which comprises at least interface for User A112and interface for User B114.

In block804, the spreadsheet is added to a set of available spreadsheets that are accessible to the second user via the spreadsheet editor. Then, in block806, a second request associated with the second user of the spreadsheet editor is received, via the interface of the spreadsheet editor, to display the spreadsheet. In some embodiments, the second request in block806may be received with or without the second user's direct request to display the spreadsheet. For example, the second user may be otherwise notified that the first user has requested to share a spreadsheet with them, and, upon loading their user profile, blocks804,806,808, and810are subsequentially completed via the spreadsheet editor.

In block808, a version of the spreadsheet is generated that includes data from the spreadsheet in the version of the spreadsheet according to respective references to the second user in the data. Block808may resemble Filter data for User B436and Generate the spreadsheet for User B438, as shown in Request430inFIG.4, according to some embodiments. In some embodiments, the process of block808may comprise that certain portions of the given spreadsheet be removed, redacted, or filtered according to user-generated data for the second user in comparison to the entirety of the original spreadsheet as viewed by the spreadsheet manager. For example, for the embodiments shown inFIG.6E, Booth Staffing672for User B comprises portions of Booth Staffing604for User A.

In block810, the version of the spreadsheet is provided for display. Block810may resemble generated spreadsheet for User B108, as shown inFIG.1, according to some embodiments. In some embodiments in which the interface described inFIG.8is a graphical user interface, the version of the spreadsheet generated for the second user may resemble interface600shown inFIG.6E.

FIG.9is a high-level flowchart illustrating various methods and techniques to implement creation of a spreadsheet for a first user of a spreadsheet editor and sharing of said spreadsheet with a second user, according to some embodiments.

In some embodiments, the methods and techniques described herein may be implemented via the processes shown inFIG.9. In block900, a first request associated with a first user of a spreadsheet editor is received, via an interface of the spreadsheet editor, which includes a natural language query to create a spreadsheet. In some embodiments, block900may resemble embodiments described in block800. It should be understood by the reader that block900encompasses both the generation of a new spreadsheet and the generation of a spreadsheet derived from a pre-existing spreadsheet of the spreadsheet editor, as described above.

In block902, data to be included in the spreadsheet is obtained from one or more data stores that satisfies the natural language query associated with the first user. In some embodiments, the data stores in block902may resemble data stores140, data stores240and data stores404. In some embodiments, interactions between users, a spreadsheet editor, and data stores may be done at least in part via data storage services, such as data storage service(s)540.

In block904, a second request, associated with the first user, to make the spreadsheet accessible to a second user of the spreadsheet editor, is received via the interface of the spreadsheet editor. Block904may resemble the methods and techniques described by Request430and/or natural language query prompt630shown inFIGS.6C-6D. Block904may also comprise filtering the data in the given spreadsheet via user-generated data, such as user-generated data120, user-generated data220, and user-generated data320.

In block906, the spreadsheet is added to a set of available spreadsheets that are accessible to the second user via the spreadsheet editor. Then, in block908, a third request, associated with the second user, to display the spreadsheet is received via the interface of the spreadsheet editor. Next, in block910, a version of the spreadsheet is generated that includes data from the spreadsheet in the version of the spreadsheet according to respective references to the second user in the data. In some embodiments, block910may resemble embodiments described in block808. Furthermore, in some embodiments, blocks906,908, and910comprise adding the spreadsheet to a list of spreadsheets that reference a given user and displaying a version of the spreadsheet generated for the given user. For example, Spreadsheets602comprises spreadsheets that are made available to User A inFIGS.6A-6D, while Spreadsheets670comprises spreadsheets that are made available to User B inFIG.6E. In particular, Spreadsheets670comprises Booth Staffing672which has been shared via the methods and techniques described inFIG.9, according to some embodiments.

In block912, the version of the spreadsheet is provided for display. Block912may resemble generated spreadsheet for User B108, as shown inFIG.1, according to some embodiments. In some embodiments, block912may resemble embodiments described in block810. In some embodiments in which the interface described inFIG.9is a graphical user interface, the version of the spreadsheet generated for the second user may resemble interface600shown inFIG.6E.

FIG.10illustrates an example system configured to implement the various methods, techniques, and systems described herein, according to some embodiments.

In the illustrated embodiment, computer system1000includes one or more processors1010coupled to a system memory1020via an input/output (I/O) interface1030. Computer system1000further includes a network interface1040coupled to I/O interface1030, and one or more input/output devices1050, such as cursor control device1060, keyboard1070, and display(s)1080. Display(s)1080may include standard computer monitor(s) and/or other display systems, technologies or devices. In at least some implementations, the input/output devices1050may also include a touch- or multi-touch enabled device such as a pad or tablet via which a user enters input via a stylus-type device and/or one or more digits. In some embodiments, it is contemplated that embodiments may be implemented using a single instance of computer system1000, while in other embodiments multiple such systems, or multiple nodes making up computer system1000, may host different portions or instances of embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of computer system1000that are distinct from those nodes implementing other elements.

System memory1020may store program instructions and/or data accessible by processor1010. In various embodiments, system memory1020may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions and data implementing desired functions, such as those described above are shown stored within system memory1020as program instructions1025and data storage1035, respectively. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory1020or computer system1000. Generally speaking, a non-transitory, computer-readable storage medium may include storage media or memory media such as magnetic or optical media, e.g., disk or CD/DVD-ROM coupled to computer system1000via I/O interface1030. Program instructions and data stored via a computer-readable medium may be transmitted by transmission media or signals such as electrical, electromagnetic, or digital signals, which may be conveyed via a communication medium such as a network and/or a wireless link, such as may be implemented via network interface1040.

As shown inFIG.10, memory1020may include program instructions1025, may implement the various methods and techniques as described herein, and data storage1035, comprising various data accessible by program instructions1025. In one embodiment, program instructions1025may include software elements of embodiments as described herein and as illustrated in the Figures. Data storage1035may include data that may be used in embodiments. In other embodiments, other or different software elements and data may be included.

The various methods as illustrated in the FIGS. and described herein represent example embodiments of methods. The methods may be implemented in software, hardware, or a combination thereof. The order of method may be changed, and various elements may be added, reordered, combined, omitted, modified, etc.