WO2018169711A1 - Systèmes et procédés de traitement de texte multi-utilisateur - Google Patents

Systèmes et procédés de traitement de texte multi-utilisateur Download PDF

Info

Publication number
WO2018169711A1
WO2018169711A1 PCT/US2018/020897 US2018020897W WO2018169711A1 WO 2018169711 A1 WO2018169711 A1 WO 2018169711A1 US 2018020897 W US2018020897 W US 2018020897W WO 2018169711 A1 WO2018169711 A1 WO 2018169711A1
Authority
WO
WIPO (PCT)
Prior art keywords
document
feedback
user
items
versions
Prior art date
Application number
PCT/US2018/020897
Other languages
English (en)
Inventor
Cory ONDREJKA
Lisa Rutherford
Bruce Rogers
Lilli THOMPSON
Sam Thompson
Conor DICKINSON
Aaron Brady
Original Assignee
Ampersand Technologies, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ampersand Technologies, Inc. filed Critical Ampersand Technologies, Inc.
Publication of WO2018169711A1 publication Critical patent/WO2018169711A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/106—Display of layout of documents; Previewing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/169—Annotation, e.g. comment data or footnotes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/30—Semantic analysis

Definitions

  • a word processor is a software application or electronic device that allows a user to create, edit, format, and print an electronic document.
  • a user can generate text for an electronic document and can copy, paste, move, and/or delete text within the document.
  • Word processors generally include features that allow users to format text, for example, with different font types and sizes and/or by underling or italicizing.
  • Word processors can allow users to create and edit tables that can be inserted into the document. Elements from other software programs, such as pictures or illustrations, can also be inserted into the document. Tools that allow a user to check for spelling and grammar errors are typically included. In general, however, existing word processing tools lack features that facilitate collaboration among a group of authors, editors, and/or other users during the production of an electronic document.
  • Implementations of the systems and methods described herein provide improved word processing capabilities that allow multiple users to collaborate on the production of an electronic document.
  • the systems and methods provide tagging features that enable users to insert one or more types of tags into a document for future reference and/or for the attention of other users.
  • the tagging features can allow multiple authors, editors, and other users to effectively collaborate and communicate with work flows and styles when producing a document.
  • the work flows can be mapped naturally to both desktop and mobile interfaces. This provides a natural platform for sharing produced documents with a reading audience. It also allows visual and behavioral choices to be specified for readers and feedback options to be customized.
  • the systems and methods can also include search features that allow users to search for user feedback (e.g., tags) or document content in current and/or previous versions of a document.
  • the searching features can enable users to find specific elements in a document that may have changed substantially in the past.
  • a user can find, for example, previous versions of a prior paragraph or other specific portion of the document.
  • the user can filter the search to find prior versions of document portions prepared or edited by other users.
  • the searching features improve collaboration among users and allow earlier portions to be identified and retrieved, as needed. Due to the tagging capabilities of the systems and methods described herein, searching can capture tags and other forms of settings and user communication. Users can perform user-specific searches in an attempt to understand or determine any changes made by specific users.
  • the systems and methods can collect and analyze passive and/or active data associated with users and their interactions with a document.
  • the data collection and analysis capabilities can identify or determine when an author makes a change to address a previous comment or other feedback from another user. The other user can then be informed that the previous comment has been addressed.
  • an author's changes can be correlated to a sentiment associated with another user's feedback.
  • the method includes: receiving from a plurality of client devices feedback items for a document, each feedback item being of a respective type and associated with a user and a portion of the document; after receiving the feedback items, receiving modifications to a first portion of the document from a client device of an author and generating a modified first portion of the document; identifying one or more feedback items that are associated with the modifications to the first portion; and for at least one identified feedback item, sending a notification to the client device of the user associated with the at least one identified feedback item.
  • the respective feedback item type includes a comment, an edit to the document, a response to a question, a feedback tag, and/or a reading behavior.
  • the reading behavior can include, for example, a reading speed, a reading pause, a reading skip, a re-read, a reading abandonment, and any combination thereof.
  • the reading behavior can be determined from a rate at which a user scrolls through the document.
  • the method includes determining a respective issue associated with the feedback item, wherein the issue indicates a factual issue, a spelling issue, a grammatical issue, and/or an emotional response for the portion of the document associated with the feedback item.
  • Identifying the one or more feedback items can include, for example, performing a sentiment analysis and/or determining at least one change associated with the modifications.
  • the at least one change can include, for example, an edit distance, an addition of text, a deletion of text, a change in topic, a factual change, a sentiment change, a spelling change, a grammatical change, and any combination thereof.
  • the notification includes a message indicating that the modifications addressed the at least one feedback item.
  • the notification can include a request for additional feedback from the user associated with the at least one identified feedback item.
  • the portion of the document can corresponds to a document version and/or a location within the document version.
  • the method includes: evaluating a quality of feedback items associated with one or more users; and calculating a score for each of the one or more users based on the quality.
  • the method can include identifying, based on the feedback items, one or more users having a skill associated with finding factual errors, grammatical errors, and/or narrative issues.
  • the method can include: aggregating the feedback items associated with the first portion of the document; and providing a view of the first portion including a graphical representation based on the aggregated feedback items.
  • Aggregating the feedback items can include performing a sentiment analysis to determine a sentiment of at least one feedback item.
  • the graphical representation can provide an indication of the sentiment and/or an indication of user reading behavior.
  • the graphical representation can include coloration of text.
  • the subject matter of this specification relates to a system having one or more computer processors programmed to perform operations including: receiving from a plurality of client devices feedback items for a document, each feedback item being of a respective type and associated with a user and a portion of the document; after receiving the feedback items, receiving modifications to a first portion of the document from a client device of an author and generating a modified first portion of the document; identifying one or more feedback items that are associated with the modifications to the first portion; and for at least one identified feedback item, sending a notification to the client device of the user associated with the at least one identified feedback item.
  • the respective feedback item type includes a comment, an edit to the document, a response to a question, a feedback tag, a reading behavior, and any combination thereof.
  • the subject matter of this specification relates to an article.
  • the article includes a non-transitory computer-readable medium having instructions stored thereon that when executed by one or more computer processors cause the computer processors to perform operations including: receiving from a plurality of client devices feedback items for a document, each feedback item being of a respective type and associated with a user and a portion of the document; after receiving the feedback items, receiving modifications to a first portion of the document from a client device of an author and generating a modified first portion of the document; identifying one or more feedback items that are associated with the modifications to the first portion; and for at least one identified feedback item, sending a notification to the client device of the user associated with the at least one identified feedback item.
  • the subject matter of this specification relates to a computer- implemented method.
  • the method includes: obtaining a query for a document including a plurality of versions, each version representing a state of the document at a different point in time; identifying one or more search results in a plurality of the document versions, wherein each search result is associated with a location in a respective document version that satisfies the query; and providing a view of the search results.
  • the query includes a plurality of feedback items provided by one or more users, wherein the feedback items include a comment, a change to the document, a response to a question, a feedback tag, highlighting, and/or a reading behavior.
  • the method can include ordering the search results according to most recent, most significant, and/or closest match. Alternatively or additionally, the method can include filtering the search results by at least one of a specific user, a specific document portion, and a specific time.
  • the specific user is selected from a group of users who provided feedback for the document, wherein the feedback includes a user comment, a feedback tag, a document edit, and any combination thereof.
  • the specific document portion can be, for example, a paragraph, a page, and/or a section.
  • the specific time can include a prior period of time.
  • Providing the view of the search results can include displaying the search results adjacent to the document.
  • the method includes receiving user input selecting a first search result and, based thereon, providing a view of the document version identified by the first search result.
  • the subject matter of this disclosure relates to a system, including: one or more computer processors programmed to perform operations including: obtaining a query for a document including a plurality of versions, each version representing a state of the document at a different point in time; identifying one or more search results in a plurality of the document versions, wherein each search result is associated with a location in a respective document version that satisfies the query; and providing a view of the search results.
  • the query includes a plurality of feedback items provided by one or more users, wherein the feedback items include a comment, a change to the document, a response to a question, a feedback tag, highlighting, a reading behavior, and any combination thereof.
  • the operations can include ordering the search results according to most recent, most significant, and/or closest match. Alternatively or additionally, the operations can include filtering the search results by at least one of a specific user, a specific document portion, and a specific time.
  • the specific user is selected from a group of users who provided feedback for the document, wherein the feedback includes a user comment, a feedback tag, a document edit, and any combination thereof.
  • the specific document portion can be, for example, a paragraph, a page, and/or a section.
  • the specific time can include a prior period of time.
  • Providing the view of the search results can include displaying the search results adjacent to the document.
  • the operations includes receiving user input selecting a first search result and, based thereon, providing a view of the document version identified by the first search result.
  • the subject matter of this specification relates to an article.
  • the article includes a non-transitory computer-readable medium having instructions stored thereon that when executed by one or more computer processors cause the computer processors to perform operations including: obtaining a query for a document including a plurality of versions, each version representing a state of the document at a different point in time;
  • the query includes a plurality of feedback items provided by one or more users, wherein the feedback items include a comment, a change to the document, a response to a question, a feedback tag, highlighting, a reading behavior, and any combination thereof.
  • the subject matter of this specification relates to a computer- implemented method.
  • the method includes: providing a document including a plurality of different versions, wherein each version represents a state of the document at a different point in time; identifying a plurality of feedback items provided by one or more users in the document versions, wherein each feedback item is associated with one or more occurrences in the document versions; providing a view of the identified feedback items; receiving user selection of one or more of the identified feedback items; and based on the user selection, providing a view of occurrences of the selected feedback items organized according to the document versions.
  • the plurality of feedback items include a comment, a change or addition to content, a response to a question, a feedback tag, highlighted text, a point- of-interest (POI) marker, an automatically generated paragraph identifier, and any combination thereof.
  • the plurality of feedback items can include the POI marker, which can specify a location in at least one of the document versions, and the method can include: receiving data indicating user selection of the POI marker and, based thereon, presenting a view of the location in the at least one of the document versions specified by the POI marker.
  • the plurality of feedback items can include the feedback tag, and the feedback tag can specify like or dislike of content in at least one of the document versions.
  • providing the view of occurrences of the selected feedback item includes hiding document content that has not yet been read by the user who made the user selection.
  • Providing the view of occurrences of the selected feedback items can include an excerpt of content surrounding each occurrence of the selected feedback items.
  • the plurality of feedback items can be formatted to distinguish the one or more users who provided the feedback items. For example, the plurality of feedback items can be formatted by color.
  • the method includes: receiving user insertion of a feedback item in content of a current document version, wherein the feedback item identifies a particular user; and sending a notification identifying the feedback item to the particular user.
  • the subject matter of this specification relates to a system having one or more computer processors programmed to perform operations including: providing a document including a plurality of different versions, each version representing a state of the document at a different point in time; identifying a plurality of feedback items provided by one or more users in the document versions, each feedback item being associated with one or more occurrences in the document versions; providing a view of the identified feedback items;
  • the plurality of feedback items include a comment, a change or addition to content, a response to a question, a feedback tag, highlighted text, a point- of-interest (POI) marker, an automatically generated paragraph identifier, and any combination thereof.
  • the plurality of feedback items can include the POI marker, which can specify a location in at least one of the document versions, and the method can include: receiving data indicating user selection of the POI marker and, based thereon, presenting a view of the location in the at least one of the document versions specified by the POI marker.
  • the plurality of feedback items can include the feedback tag, and the feedback tag can specify like or dislike of content in at least one of the document versions.
  • providing the view of occurrences of the selected feedback item includes hiding document content that has not yet been read by the user who made the user selection.
  • Providing the view of occurrences of the selected feedback items can include an excerpt of content surrounding each occurrence of the selected feedback items.
  • the plurality of feedback items can be formatted to distinguish the one or more users who provided the feedback items. For example, the plurality of feedback items can be formatted by color.
  • the method includes: receiving user insertion of a feedback item in content of a current document version, wherein the feedback item identifies a particular user; and sending a notification identifying the feedback item to the particular user.
  • the subject matter of this disclosure relates to an article.
  • the article includes a non-transitory computer-readable medium having instructions stored thereon that when executed by one or more computer processors cause the computer processors to perform operations including: providing a document having a plurality of different versions, each version representing a state of the document at a different point in time; identifying a plurality of feedback items provided by one or more users in the document versions, each feedback item being associated with one or more occurrences in the document versions; providing a view of the identified feedback items; receiving user selection of one or more of the identified feedback items; and based on the user selection, providing a view of occurrences of the selected feedback items organized according to the document versions.
  • the plurality of feedback items includes a comment, a change or addition to content, a response to a question, a feedback tag, highlighted text, a point-of-interest (POI) marker, an automatically generated paragraph identifier, or any combination thereof.
  • a comment a change or addition to content
  • a response to a question a feedback tag
  • highlighted text a point-of-interest (POI) marker
  • POI point-of-interest
  • FIG. 1 is a schematic diagram of an example word processing system.
  • FIGS. 2-5 are screenshots of an example graphical user interface for the word processing system of FIG. 1.
  • FIGS. 6 and 7 are schematic diagrams illustrating an example method for inserting and using a hashtag in a document.
  • FIGS. 8 and 9 are schematic diagrams illustrating an example method of inserting and using an at-mention tag in a document.
  • FIG. 10 is a screenshot illustrating an example method of accessing and viewing an at-mention tag in a document.
  • FIG. 11 is a screenshot illustrating an example method of performing a search in a document.
  • FIG. 12 is a schematic diagram illustrating an example method in which document edits are grouped together, searched, and examined.
  • FIG. 13 is a screenshot illustrating an example method of adding a tag to a document using a mobile application.
  • FIG. 14 is an example screenshot from a client device showing the existence of a hashtag in a document.
  • FIGS. 15-17 are example screenshots illustrating methods for providing user feedback for a document.
  • FIG. 18 is a flowchart of an example method of aggregating a visualizing data for a document.
  • FIG. 19 is a flowchart of an example method of searching through previous versions of a document.
  • FIG. 20 is a flowchart of an example method of providing and using user feedback items for a document.
  • FIG. 1 illustrates an example word processing system 100 for multiple users to collaborate on the creation of a document.
  • a server system 112 provides word processing, tagging, search, and data functionality.
  • the server system 112 includes software components and databases that can be deployed at one or more data centers 114 in one or more geographic locations, for example.
  • the server system 112 software components can include a tagging module 116, a search module 118, and a data module 120.
  • the software components can include subcomponents that can execute on the same or on different individual data processing apparatus.
  • the server system 112 databases can include document data 122 and user data 124.
  • the databases can reside in one or more physical storage systems. The software components and data will be further described below.
  • An application such as a web-based application can be provided as an end-user application to allow users to interact with the server system 112.
  • the end-user applications can be accessed through a network 132 (e.g., the Internet) by users of client devices, such as a personal computer 134, a smart phone 136, a tablet computer 138, and a laptop computer 140.
  • client devices such as a personal computer 134, a smart phone 136, a tablet computer 138, and a laptop computer 140.
  • client devices are possible.
  • document data 122 and user data 124, or any portions thereof can be stored on one or more client devices.
  • software components for the system 100 e.g., the tagging module 116, the search module 118, and the data module 120
  • any portions thereof can reside on or be used to perform operations on one or more client devices.
  • FIG. 1 depicts the tagging module 116, the search module 118, and the data module 120 as being able to communicate with the databases (e.g., document data 122 and user data 124).
  • the document data 122 database generally includes information related to documents that are prepared using the system 100. Such data can include, for example, text data, image data, document history data (e.g., for multiple document versions), and/or feedback data (e.g., associated with one or more tags or user comments).
  • the user data 124 database can include, for example, information about one or more users of the system 100. Such information may be or include, for example, a user name, a nickname, user contact information, a user skill level, and/or an indication of a user's strengths and/or weaknesses as an author, editor, or
  • FIG. 2 is a screenshot of a graphical user interface 200 for an example word processing system 202.
  • the graphical user interface 200 includes a document region 204 where document text is presented.
  • the document text can include, for example, a title 206, one or more headers 208, and one or more tags inserted by users.
  • the tags can include, for example, a hashtag 210 and/or an at-mention tag 212.
  • a hashtag 210 includes a hash symbol followed by a word or brief message. For example, when a reader or other user considers a portion of the document to be unclear or worded poorly, the reader can insert
  • hashtags 210 are possible. For example, a user who wants to flag a portion of a document as being special can insert “#text this is special text” into that portion. In that case, the user inserts the hashtag "#text” followed by the "this is special text” comment. Other types of comments can be inserted using this hashtag approach.
  • a user can use an at-mention tag 212 to bring something to another user's attention. For example, a user can ask another user to fact-check a portion of the document by inserting "@mike are you sure?" In this case, at-mention tag identifies a specific user ("Mike") and asks Mike to confirm the accuracy of a statement. Likewise a user can insert "@mike please review for accuracy” in an effort to get Mike to review a portion of the document for accuracy.
  • the user is automatically informed about the tag (e.g., through an email, text, chat, or other type of message). This allows the tagged user to respond more quickly to any request associated with the tag.
  • the tags e.g., hashtags or at-mention tags
  • a tag can refer to a specific version of the document.
  • a user can associate a comment with a tag (e.g., a hashtag or at-mention tag followed by a written comment).
  • Tags can impart special formatting rules for a specific portion of text (e.g., color and/or font) and/or can control display and behavior on a client device.
  • Particular regions of text can be styled differently (e.g., with font or color) to distinguish tags and comments from the primary text. For example, tags and/or comments can be given a color (e.g., red or green) that distinguishes the color of the primary text (e.g., black).
  • tags can provide positional information to allow multiple documents to be interleaved and read together.
  • the hashtag #marginalia- document-2 could be used to insert a document named "document-2" into the current document, so that both documents could be read together (e.g., in a combined document or side-by-side).
  • Document-2 could contain, for example, notes, commentary, or other related, or unrelated information.
  • the inserted document can be added into the current document at a particular location in the current document (e.g., in-line), such that the text in the combined document transitions from the current text to the inserted text, and possibly back to the current text.
  • the inserted document could be added to a separate pane or section of the current document, such that the text from the two documents is displayed in separate windows or regions and not merged together.
  • tags include point-of-interest (POI) tags and/or feedback tags (e.g., like, dislike, etc.).
  • POI tag can be used to connect the document to another document in any way the author desires, thereby allowing flexible linking of documents by theme or interest in ways that can also be displayed to the reader.
  • an author can insert a POI tag that includes a link to a separate document and optionally a specific location in the separate document.
  • a feedback tag allows a user to insert comments, such as "like,” “dislike,” “confusing,” etc.
  • a feedback tag can be inserted by selecting an item from a graphical user interface and/or by typing #like, #dislike, #confusing, etc., for example, directly into the document.
  • the tags and comments are preferably viewable in a document inline, but can be automatically removed when the document is published.
  • tags can be visible, usable and searchable to support communication, collaboration, and editing among users.
  • tags can be automatically removed to provide a smooth reading experience and to prevent information leakage, for example, from authors to readers.
  • a tag and any associated content can be hidden from users who have not yet read certain document content.
  • any tags or comments from other users that relate to chapter 10 (or later chapters) can be hidden from the reader. This prevents the reader from inadvertently learning something about part of the document (e.g., an end of a story) that has not yet been read and/or that could cause the reader to lose interest in the document.
  • the word processing system 202 can monitor the reader's progress in the document and reveal only tags associated with portions that have already been read. Alternatively or additionally, the word processing system 202 can be configured to hide all user comments or tags, for example, in the reading view, described above.
  • users are sent notifications when they are at-mentioned (e.g., in an at-mention tag) or involved in a multi-tag conversation.
  • the collaborator can be automatically notified about the tag and can be directed to a location in the document corresponding to the tag.
  • the collaborator can select a link in the notification that directs the client device of the collaborator to the tagged location.
  • the tags in a document can facilitate or control the reading experience of a user.
  • tags provide a way to show this annotation information inline (e.g., rather than in a footnote or a margin). Tags can allow this annotation information to be viewed either inline or sequentially by a reader.
  • multiple documents can be displayed together via tags.
  • a tag can be inserted into multiple documents.
  • the reader can be directed to the tag in the multiple documents.
  • a margin tag can be inserted that, when selected, causes two documents to be combined or interleaved for reading. The margin tag can identify specific portions of the two documents that are combined when the tag is selected.
  • the word processing system uses identifiers for each paragraph in a document and/or tracks every keystroke made by users in the document. This provides the systems and methods with a complete lifecycle or history of the document. The systems and methods can use this information to determine exactly what was done to change a document from one version to the next, rather than simply identifying differences between two versions.
  • the document history information allows the systems and methods to track multiple versions of a section of text and know that the versions include the same section. This allows users to search for and review the section to determine how the section has changed over time.
  • Previous word processing systems by comparison, generally split chat and content production and/or move comments outside of the document flow. This removes the ability to determine changes made to a document by users and/or to search for such changes or user comments within the document. Additionally, prior tools are unable to anticipate flexibility in work flows and/or the need for authors to define styling and feedback options for readers directly. Examples of the systems and methods described herein use inline tooling for feedback and styling, which allows diffing and history tools to capture these choices.
  • the graphical user interface 200 can include a project bar 214, a navigation bar 216, a snippets bar 218, and a supporting documents bar 220. These bars can be expanded by a user to reveal additional information related to the document. For example, a user can select the snippets bar 218 to see information (e.g., text excerpts) in that bar. In the depicted screenshot, the project bar 214, the navigation bar 216, the snippets bar 218, and the supporting documents bar 220 are not expanded.
  • FIG. 3 is a screenshot of the graphical user interface 200 in which the navigation bar 216 and the snippets bar 218 are expanded.
  • the user has used the navigation bar 216 to select an "@mike" at-mention identifier 302. Doing so caused the snippets bar 218 to display text excerpts 304 (also referred to herein as "snippets") from the document where the "@mike" tag is located. Selecting the at-mention identifier 302 from the navigation bar 216 also reveals an index bar 306 that includes selectable items 308 (e.g., colored boxes). By selecting one of these snippets 304 from the snippets bar 218 or a selectable item 308 from the index bar 306, the corresponding "@mike" tag can be highlighted or otherwise identified in the document region 204. Alternatively or additionally, referring to FIG.
  • the user has selected a "#wordchoice” hashtag identifier 402 from the navigation bar 216, which caused the snippets bar 218 to display a snippet 304 from the document where the "#wordchoice” tag is located. Selecting the hashtag identifier 402 from the navigation bar 216 also reveals a selectable item 308 in the index bar 306, corresponding to a location in the document where the
  • FIG. 5 is an example screenshot of the graphical user interface 200 in which the supporting documents bar 220 is expanded.
  • the supporting documents bar contains a listing of references that are related to the document, for example, as decided by the author or other user.
  • the references can be, for example, sources of information (e.g., books, articles, images, notes, etc.) that support facts, opinions, pictures, or other content presented in the document.
  • the reference can be opened in an attached view (e.g., in the supporting documents bar 220), preferably adjacent to the document region 204, such that the document and the reference can be viewed at the same time.
  • the method 600 includes providing text in the document region 204 (step 602), typing a hashtag 210 (e.g., "#wordchoice") into the document text (step 604), and submitting the hashtag 210 (e.g., by pressing enter or a space bar) (step 606).
  • a hashtag identifier 402 for the hashtag 210 is added to the navigation bar 216 (step 608). Selecting the hashtag identifier 402 from the navigation bar 216 can cause document snippets 304 to be displayed in the snippets bar 218 and selectable items 308 (e.g., colored boxes) to be displayed in the index bar 306 (step 610).
  • Selecting a snippet 304 from the snippets bar 218 or a selectable item 308 from the index bar 306 causes the document region 204 to navigate to the corresponding location in the document and/or to highlight the hashtag 210 in the document body (step 612).
  • a type ahead or dropdown menu 702 appears with a listing of hashtag recommendations.
  • the recommendations may include, for example, hashtags previous used by the user or other users for the document or other document.
  • a user can select one of the listed hashtags to add the hashtag 210 to the document body.
  • FIG. 8 is a schematic diagram illustrating an example method 800 of inserting and using an at-mention tag.
  • the method 800 includes providing text in the document region 204 (step 802), typing the "@" symbol (step 804), and typing the name of a user (e.g., "matt") (step 806). A note can be added after the user name has been entered (step 808).
  • the at-mention tag 212 is then submitted, for example, by pressing enter or the space bar (step 810).
  • the person identified in the at-mention tag (in this case, "matt") is preferably notified (e.g., with a text or email message) about the existence of the at-mention tag 212 and/or an at-mention identifier 302 is added to the navigation bar 216 (step 812), where it can be selected by a user. Selecting the at-mention identifier 302 from the navigation bar 216 causes document snippets 304 to be displayed in the snippets bar 218 and selectable items 308 (e.g., colored boxes) to be displayed in the index bar 306.
  • selectable items 308 e.g., colored boxes
  • a type ahead or dropdown menu 902 appears with a listing of user names.
  • the recommendations may include, for example, the names of users who have previously worked on the document and/or who are available to work on the document.
  • a user can select one of the listed names to add the at- mention tag 212 to the document body.
  • the notification 1002 may be cleared from the navigation bar 216.
  • FIG. 11 is a schematic diagram illustrating an example method 1100 of performing a search in a document.
  • a user can select a search button (or press a keyboard key, e.g., ctrl+F) to display a search tool 1 102 (step 1104).
  • the search tool 1102 can reveal how many matches exist in the document (step 1106).
  • a user can step through the search results to automatically navigate to the location of each result in the document (step 1108). Search results can be reported in context in the index bar 306 (step 1110).
  • a user can select a selectable item 308 (e.g., a colored box) in the index bar 306 to navigate to the corresponding location in the document.
  • a selectable item 308 e.g., a colored box
  • search results can be reported in context in the snippets bar 218 (step 1112).
  • a user can select a snippet 304 to navigate to the corresponding location in the document. Search results can be highlighted in the document region 204.
  • the systems and methods described herein allow users to search all versions of a document at once. For example, a user can search for text or user activity that meets desired parameters (e.g., to determine that a user made extensive edits and to identify specific edits made by the user).
  • versions listed in an activity feed can be filtered according to the specified user activity.
  • Clicking on a version in the activity feed can display that version of the document along with the searched for activity highlighted inline and/or on the navigation bar 216 and/or the snippet bar 218.
  • the navigation bar 216 can show information or activity for a current view of the document. When the current view is the latest version of the document, for example, the navigation bar 216 can display information for the latest version. Likewise, when the current view includes changes or content from one or more previous versions of the document, the navigation bar 216 can display information for the one or more previous versions.
  • the systems and methods can display search results in a variety of orders, including most recent, most significant, and/or closest match.
  • the activity feed contains simple descriptions of the changes to the document, such as "Mike add 200 words” and/or author descriptions of a group of changes, such as "Sunday writing," which can be useful for exploring the history of the document and/or deciding whether or not to review the document.
  • the activity feed can be presented in a bar or window adjacent to the document region 204, for example, at or near the supporting documents bar 220.
  • Implementations of the systems and methods enable historical searching through the current and previous versions of a document simultaneously.
  • a user can search every edit made by users, including edits later deleted or further modified. In certain examples, this can be accomplished by maintaining a log that records each edit, change, deletion, insertion, etc., that is made by each user throughout an entire history of each version of the document.
  • the systems and methods described herein can use the log to reconstruct the document as it existed at any previous time, for example, by reversing or undoing each change that was made since the previous time.
  • the systems and methods can periodically save the document as a new version and use the saved versions and the log, as appropriate, to reconstruct previous states of the document.
  • the approach can allow a user to retrieve content from a prior version that was later changed or deleted.
  • a user can filter the search by author, by time, and/or by version. For example, a user can search for specific changes made by another user (e.g., Mike Spatula) during a specified time period (e.g., yesterday) by entering the following keywords in a search field: "AUTHOR:Mike Spatula DATE:yesterday.”
  • the search results in that case can include a document version (or portions thereof) that was created or edited yesterday by Mike Spatula.
  • Additional keywords can be used to specify document portions (e.g., "PAGE:2," or "PARAGRAPH:73"), such that search results can include one or more prior versions of those document portions.
  • Document versions can be filtered according to the search and displayed (e.g., in the activity feed) for user selection.
  • the searching abilities of the systems and methods allow users to find specific elements in a document that may have changed substantially in the past.
  • a user can find, for example, previous versions of a prior paragraph or other specific portion of the document.
  • the user can filter the search to find prior versions of document portions prepared or edited by other users. This improves collaboration among users and allows earlier portions to be identified and retrieved, as needed.
  • searching can capture tags and other forms of settings and user communication. Users can perform author-specific searches in an attempt to understand or determine the changes made by specific authors.
  • document searching with prior word processing tools is limited to searching through a current version.
  • Such prior tools are also unable to perform author-specific searches, for example, to identify changes made by a specific author, in the current version or previous versions (e.g., on a certain date).
  • the search capabilities of prior tools do not include or consider concepts that live in settings (e.g., background styling for regions of text and/or buttons provided to readers) or how such concepts have changed.
  • the systems and methods described herein provide an improved ability to search the history of a document. This gives authors and other users a powerful but intuitive way to search for and think about how the document has changed over time.
  • FIG. 12 is a schematic diagram illustrating an example method 1200 in which document edits can be grouped together, searched, and examined.
  • a group of edits can be referred to as a "session.”
  • the edits can be grouped together into a session, which can be created automatically and/or manually and given a name (e.g., "Chapter 5 rewrite").
  • a user can search for and review the edits from the session at a later time, for example, by requesting a listing of previous sessions (step 1202), which can cause the listing to be displayed for the user (e.g., at or near the navigation bar 216 or the snippets bar 218) (step 1204).
  • the user can select a session to review the state of the document before, during, or after the session occurred (step 1206).
  • the user can select a set of sessions to review the edits that occurred during the set of sessions (step 1208).
  • Such session information can be recorded in the log, as part of an entire history of the document.
  • this gives authors and other users an ability to determine the state of the document before, during, or after previous editing sessions.
  • FIG. 13 includes a screenshot illustrating an example method 1300 of adding a tag to a document using a mobile device, such as the smart phone 136.
  • a user can highlight a selection of text (step 1302) in the document and make a selection (step 1304) indicating that the user wants to edit the document.
  • the user can select an edit button 1306 from an edit bar 1308.
  • the user can insert one or more tags (e.g., a hashtag or an at-mention tag) and/or directly edit the document using a virtual keyboard.
  • tags e.g., a hashtag or an at-mention tag
  • a reaction menu 1310 is displayed that includes options for possible hashtag insertions (step 1312).
  • the user can select one of these options to insert a desired hashtag 210 (e.g., "#typo") near the selected text.
  • a desired hashtag 210 e.g., "#typo"
  • multiple users are able to view and/or edit a document simultaneously, from different client devices. For example, when the hashtag 210 is inserted as shown in FIG. 13, another user of a different client device (e.g., the personal computer 134) can see the inserted hashtag 210 in the document region 204, as shown in FIG. 14. Additionally or alternatively, when one user is editing a portion of text using one client device, another user of a different client device can see the edits, for example, in real-time.
  • the systems and methods support complete simultaneous editing, partial locking (e.g., one author blocking access to a paragraph, chapter, or other range of content), and/or one author completely locking the entire document (e.g., to prevent other users from making any changes).
  • partial locking e.g., one author blocking access to a paragraph, chapter, or other range of content
  • one author completely locking the entire document e.g., to prevent other users from making any changes.
  • Such features can be implemented, for example, using the server system 112.
  • a user is able to work in a private mode, which allows the user to edit a document without the edits being viewable by other users who have access to the document.
  • the user can exit the private mode, and the edits can be merged into the document and revealed to other users.
  • a user can edit a document and share the edits with other users in a safe mode. The user can then decide to abandon the edits, such that the edits are not incorporated into the document. Alternatively, the user can decide to accept the edits, for example, by exiting the safe mode and allowing the edits to be incorporated into the document.
  • the systems and methods described herein allow users (e.g., authors) to solicit feedback from other users (e.g., readers or editors).
  • users e.g., authors
  • an author can insert into the document a survey 1502 or set of one or more questions for a reader.
  • the reader can then respond to the survey 1502 by selecting one of the response options and/or by inserting a free-form text response.
  • the author can have control over the feedback options that are available to the reader (e.g., free-form, multiple choice, etc.).
  • the systems and methods described herein can allow users to insert feedback as they read the document.
  • the feedback can provide an indication of user sentiment (e.g., happy or sad) and/or can include one or more written comments (e.g., "this part is confusing” or "you should consider saying it this way . . . ").
  • a reader can select a happy button 1504 from a feedback selection menu 1506 to indicate that a portion of text makes the reader feel happy.
  • the feedback selection menu 1506 can include additional buttons representing other thoughts or emotions (e.g., sad or confused).
  • a user can select a note button 1508 from the feedback selection menu 1506, which preferably causes a virtual keyboard 1602 to be presented, as shown in FIG. 16.
  • an icon 1510 representing the submission may be presented, preferably near or within a corresponding portion of text.
  • One or more other users e.g., the author
  • the feedback selection menu 1506 is presented when a user selects the icon 1510 and/or selects (e.g., by tapping) a left-hand margin of the document region 204.
  • user feedback can correspond to a broad area of text (e.g., a page or chapter) or to a specific word or phrase.
  • the systems and methods described herein can collect and/or record (e.g., in the log) passive and active data associated with users and their interactions with documents.
  • Passive data can include, for example, an identification of reading speed, locations where readers paused (e.g., stopped and started), abandonment points (e.g., where a reader stopped a reading session), portions that were re-read and/or skipped, total time spent reading, time of day when reading occurred, and the like.
  • passive data can provide valuable feedback to authors regarding the content and quality of documents. For example, portions of a document that readers read quickly may be considered to be well written or interesting, while portions that readers read slowly may be considered to be poorly written and/or not interesting.
  • Reading speed can be measured by tracking a rate at which a user scrolls or advances through the document. Portions that were read slowly can be flagged (e.g., with a specific color or tag), such that an author can search for or readily identify those portions and attempt to make any desired changes. Likewise, when a reader stops reading the document (e.g., closes the word processing system 202), the location in the document where the reader stopped reading can be flagged as an abandonment point. Such locations may correspond to places where readers became bored or frustrated. An author can search for or otherwise identify such abandonment points and attempt to fix any possible issues at those locations.
  • a user's time spent reading can provide an indication of how carefully the user read the document and/or whether the user was interested or uninterested in the document or specific portions thereof.
  • the time of day when a user read the document can provide an indication of how focused the user was. For example, if a user read a document in the middle of the night, the user may have been less focused and/or done a poor quality job of editing or commenting on the document.
  • the active data can include, for example, purchased content, shared content (e.g., user edits), shared comments on specific portions of text (e.g., user comments related to the quality of the document), responses to surveys, comment text (e.g., text in a comment tag), sentiment in comment text, sections users clicked on, and/or structured user feedback (e.g., love, hate, etc.).
  • Active data generally is or includes data collected from specific user feedback or user decisions. Examples of active data include tags (e.g., hashtags and at-mention tags) and other user submitted feedback (e.g., notes, written comments, or icons providing an indication of user thoughts or sentiment).
  • Active data can include, for example, an edit distance (e.g., a number of edits required to make a change), an addition of text, a deletion of text, a change in topic, a factual change, a sentiment change, a spelling change, a grammatical change, and the like.
  • an edit distance e.g., a number of edits required to make a change
  • an addition of text e.g., a number of edits required to make a change
  • a deletion of text e.g., a number of edits required to make a change
  • a change in topic e.g., a change in topic
  • a factual change e.g., a sentiment change, a spelling change, a grammatical change, and the like.
  • the types of actions or feedback available to a user depends on whether the user is an author, an editor, or a reader.
  • Some user interfaces allow users to provide feedback as authors, such that tags can be converted into specific actions performed by the authors. For example, a "#cut" hashtag introduced by one user can introduce or become a cut button that the author can use to delete the text associated with the hashtag. Any changes made from the user interface (e.g., a mobile interface) can be inserted into the history of changes for the document (e.g., in the log).
  • Preferred implementations of the systems and methods can include various tools for authors to analyze passive and/or active data. For example, user feedback data can be automatically summarized and/or visually mapped to the document.
  • portions that users found confusing or boring are given a first color (e.g., red) and/or portions that users found clear and interesting are given a second color (e.g., green).
  • the document can be colored according to user sentiment (e.g., happy or sad).
  • users are able to provide an indication of sentiment directly, for example, by selecting a button from the feedback selection menu 1506.
  • Sentiment can also be determined automatically from any written user comments, for example, by performing a sentiment analysis or a polarity analysis on the written user comments.
  • the sentiment analysis may use one or more classifiers and/or natural language processing.
  • a classifier can be trained using a corpus of training data that includes example words and phrases and a corresponding sentiment associated with each word and phrase. Words associated with user sentiment (e.g., "happy,” “sad,” or “scary") in a document can be automatically identified and used by the systems and methods to determine user sentiment (e.g., using the trained classifier).
  • the systems and methods described herein compare a reader's feedback to any corresponding changes that are made by the author. For example, the systems and methods can automatically send notifications or messages to a reader when the reader's feedback is used or addressed by the author.
  • the systems and methods can look for any feedback tags (e.g., hashtags or at-mention tags) in the vicinity of edits made be author. For example, if the author changes a portion of the text near a feedback tag, the systems and methods may determine that the changes were made to address the feedback tag. In some implementations, the author can delete a feedback tag or otherwise mark a feedback tag as having been addressed. In response, a notification can be sent to the user who inserted or created the feedback tag, for example, to inform the user that the author addressed the feedback tag. In general, when feedback is synopsized and delivered to the author, a flag can be set on the appropriate reader comment to mark the comment as having been addressed and/or delivered. In other words, the author can mark the feedback (e.g., by removing the flag) to indicate that the feedback has been addressed.
  • feedback tags e.g., hashtags or at-mention tags
  • the systems and methods can use the collected data to evaluate the quality or abilities or users.
  • Users having a specific skillset e.g., good ability to find factual errors, grammatical errors, or narrative issues
  • users can be rated by other users according to ability and/or quality of feedback. Users having specific skills can be identified and
  • highly rated users can be classified based on a specific type of feedback the users are good at providing.
  • the systems and methods can create tables or charts (e.g., hash tables) that identify the skillsets of various users. Such users can be automatically identified and recommended to other users, as needed, according to the skillsets.
  • the systems and methods can allow users collaborating on a document to remain anonymous. Such anonymity can make it easier for users to exchange feedback or ideas freely, without worrying about being personally identified or recognized as the specific user who provided the feedback or ideas.
  • the systems and methods described herein automatically save a document periodically, over time, to create multiple versions of the document.
  • the new versions can be created, for example, after specified intervals of time (e.g., after 1, 5, 10, or 20 minutes of user activity) or after a threshold number of changes have been made to the document (e.g., after changes to more than 100, 200, or 1000 characters and/or after one or more tags have been inserted).
  • the systems and methods preferably track and record each change made by users so that previous versions of the document can be retrieved or reconstructed, as needed.
  • the systems and methods can automatically summarize any or all activity since the last saved version.
  • any changes made to the new version can be saved as a summary for the new version.
  • the summary of stored changes can include, for example, an identification of any users who made changes, an identification of any new users who accessed the document, an identification of specific changes (e.g., keystrokes) made by each user, and/or an identification of any tags or comments inserted by each user.
  • two or more versions of a document are saved as a single file, for example, in a database or other storage device. For example, all previous versions and the latest version of the document can be saved or stored as a single file.
  • the systems and methods are able to generate a far more accurate picture of user engagement with a document.
  • Such data can fill in any data collection gaps, for example, due to a reader not providing active feedback and/or any ambiguities in passive data.
  • Aggregating user feedback provides clearer advice and/or directional data for the author, preferably while preserving the anonymity of individual users.
  • FIG. 18 is a flowchart of an example method 1800 of aggregating and visualizing data for a document.
  • Feedback items are received (step 1802) for a document (e.g., from a plurality of client devices), wherein each feedback item is of a certain respective type and is associated with a user and a portion of the document.
  • the feedback item type can be, for example, a user comment, a user edit, a user response to a question, a feedback tag, a reading behavior, and the like.
  • modifications to a first portion of the document are received (step 1804) and, based thereon, a modified first portion of the document is generated (step 1806).
  • One or more feedback items are identified (step 1808) that are associated with the modifications to the first portion.
  • a notification is sent (step 1810) to the client device of the user associated with the at least one identified feedback item.
  • FIG. 19 is a flowchart of an example method 1900 of searching through previous versions of a document.
  • a query is obtained (step 1902) for a document having a plurality of versions, wherein each version represents a state of the document at a different point in time.
  • One or more search results are identified (step 1904) in a plurality of the document versions, wherein each search result is associated with a location in a respective document version that satisfies the query.
  • a view of the search results is provided (step 1906).
  • the method 1900 allows a user to search for previous versions of a document to, for example, understand the document history, retrieve content from previous versions, and/or undo changes made to a prior version.
  • the user can search the prior versions for user comments, edits, feedback tags, reading behavior, and the like.
  • the search can be used to identify changes made by specific authors, to specific portions of the document, and/or during a specific time range.
  • FIG. 20 is a flowchart of an example method 2000 of providing and using user feedback items for a document.
  • a document having a plurality of different versions is provided (step 2002), wherein each version represents a state of the document at a different point in time.
  • a plurality of feedback items provided by one or more users in the document versions is identified (step 2004), wherein each feedback item is associated with one or more occurrences in the document versions.
  • a view of the identified feedback items is provided (step 2006).
  • User selection of one or more of the identified feedback items is received (step 2008). Based on the user selection, a view of occurrences is provided (step 2010) of the selected feedback items organized according to the document versions.
  • the method 2000 allows a user to insert feedback tags (e.g., a hashtag or an at-mention tag) or other feedback items into a document.
  • the various feedback tags can be displayed (e.g., in the navigation bar 216) and, when a user selects a feedback tag (e.g., from the navigation bar 216), excerpts from the document associated with the feedback tag can be displayed for the user (e.g., in the snippets bar 218).
  • the excerpts can come from a current version of the document and/or from one or more previous versions of the document.
  • Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
  • Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.
  • the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus.
  • a computer storage medium can be, or be included in, a computer- readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). [0093] The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
  • the term "data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing.
  • the apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • the apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database
  • the apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
  • a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative, procedural, or functional languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment.
  • a computer program may, but need not, correspond to a file in a file system.
  • a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
  • a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output.
  • the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • the essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data.
  • a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic disks, magneto-optical disks, optical disks, or solid state drives.
  • mass storage devices for storing data, e.g., magnetic disks, magneto-optical disks, optical disks, or solid state drives.
  • a computer need not have such devices.
  • a computer can be embedded in another device, e.g., a smart phone, a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.
  • Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including, by way of example, semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
  • embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse, a trackball, a touchpad, or a stylus, by which the user can provide input to the computer.
  • a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and a pointing device e.g., a mouse, a trackball, a touchpad, or a stylus
  • a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
  • Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.
  • the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN”) and a wide area network (“WAN”), an internetwork (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
  • LAN local area network
  • WAN wide area network
  • Internet internetwork
  • peer-to-peer networks
  • the computing system can include clients and servers.
  • a client and server are generally remote from each other and typically interact through a communication network.
  • the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
  • a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device).
  • data e.g., an HTML page
  • client device e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device.
  • Data generated at the client device e.g., a result of the user interaction
  • a system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions.
  • One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • User Interface Of Digital Computer (AREA)
  • Document Processing Apparatus (AREA)

Abstract

Des modes de réalisation de l'invention concernent un procédé, un système et un article permettant de préparer et d'éditer des documents électroniques. Un exemple de procédé mis en oeuvre par ordinateur consiste : à obtenir un document comprenant une pluralité de versions différentes, chaque version représentant un état du document à un moment différent ; à identifier une pluralité d'éléments de rétroaction fournis par au moins un utilisateur dans les versions du document, chaque élément de rétroaction étant associé à au moins une occurrence dans les versions du document ; à obtenir une vue des éléments de rétroaction identifiés ; à recevoir une sélection utilisateur d'au moins un des éléments de rétroaction identifiés ; et à obtenir, en fonction de la sélection utilisateur, une vue d'occurrences des éléments de rétroaction sélectionnés organisés en fonction des versions du document.
PCT/US2018/020897 2017-03-13 2018-03-05 Systèmes et procédés de traitement de texte multi-utilisateur WO2018169711A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762470551P 2017-03-13 2017-03-13
US62/470,551 2017-03-13

Publications (1)

Publication Number Publication Date
WO2018169711A1 true WO2018169711A1 (fr) 2018-09-20

Family

ID=61873893

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/020897 WO2018169711A1 (fr) 2017-03-13 2018-03-05 Systèmes et procédés de traitement de texte multi-utilisateur

Country Status (1)

Country Link
WO (1) WO2018169711A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109460545A (zh) * 2018-10-26 2019-03-12 上海连尚网络科技有限公司 一种基于文本内容的用户匹配方法及其终端、服务器
US11336703B1 (en) * 2021-04-15 2022-05-17 Microsoft Technology Licensing, Llc Automated notification of content update providing live representation of content inline through host service endpoint(s)
WO2022221052A1 (fr) * 2021-04-15 2022-10-20 Microsoft Technology Licensing, Llc Notification automatisée d'une mise à jour de contenu fournissant une représentation en direct d'un contenu en ligne par l'intermédiaire d'un ou de plusieurs points d'extrémité de service hôte

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070055926A1 (en) * 2005-09-02 2007-03-08 Fourteen40, Inc. Systems and methods for collaboratively annotating electronic documents
EP2141614A1 (fr) * 2008-07-03 2010-01-06 Philipp v. Hilgers Procédé et dispositif d'enregistrement d'événements de navigateur liés au comportement se produisant pendant une lecture
WO2010124302A2 (fr) * 2009-04-24 2010-10-28 Globalenglish Corporation Outil d'annotation collaboratif accessible par réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070055926A1 (en) * 2005-09-02 2007-03-08 Fourteen40, Inc. Systems and methods for collaboratively annotating electronic documents
EP2141614A1 (fr) * 2008-07-03 2010-01-06 Philipp v. Hilgers Procédé et dispositif d'enregistrement d'événements de navigateur liés au comportement se produisant pendant une lecture
WO2010124302A2 (fr) * 2009-04-24 2010-10-28 Globalenglish Corporation Outil d'annotation collaboratif accessible par réseau

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109460545A (zh) * 2018-10-26 2019-03-12 上海连尚网络科技有限公司 一种基于文本内容的用户匹配方法及其终端、服务器
CN109460545B (zh) * 2018-10-26 2023-05-30 上海连尚网络科技有限公司 一种基于文本内容的用户匹配方法及其终端、服务器
US11336703B1 (en) * 2021-04-15 2022-05-17 Microsoft Technology Licensing, Llc Automated notification of content update providing live representation of content inline through host service endpoint(s)
WO2022221052A1 (fr) * 2021-04-15 2022-10-20 Microsoft Technology Licensing, Llc Notification automatisée d'une mise à jour de contenu fournissant une représentation en direct d'un contenu en ligne par l'intermédiaire d'un ou de plusieurs points d'extrémité de service hôte
WO2022220952A1 (fr) * 2021-04-15 2022-10-20 Microsoft Technology Licensing, Llc Notification automatisée d'une mise à jour de contenu fournissant une représentation en direct d'un contenu en ligne par l'intermédiaire d'un ou de plusieurs points d'extrémité de service hôte
US11546278B2 (en) 2021-04-15 2023-01-03 Microsoft Technology Licensing, Llc Automated notification of content update providing live representation of content inline through host service endpoint(s)

Similar Documents

Publication Publication Date Title
Moylan et al. Increasingly mobile: How new technologies can enhance qualitative research
Heer et al. Voyagers and voyeurs: supporting asynchronous collaborative information visualization
Zhi et al. Linking and layout: Exploring the integration of text and visualization in storytelling
US9092173B1 (en) Reviewing and editing word processing documents
Xie Users’ evaluation of digital libraries (DLs): Their uses, their criteria, and their assessment
US11860954B1 (en) Collaboratively finding, organizing and/or accessing information
Morris et al. Collaborative web search: Who, what, where, when, and why
CN102460413A (zh) 网络可访问的协作注解工具
US20230316186A1 (en) Multi-service business platform system having entity resolution systems and methods
WO2018169711A1 (fr) Systèmes et procédés de traitement de texte multi-utilisateur
Kim et al. Winder: linking speech and visual objects to support communication in asynchronous collaboration
US8418051B1 (en) Reviewing and editing word processing documents
Lount et al. Characterizing web-based tutorials: Exploring quality, community, and showcasing strategies
Ince et al. A qualitative study of social sciences faculty research workflows
US8296647B1 (en) Reviewing and editing word processing documents
McKinley Design principles for crowdsourcing cultural heritage
Price et al. Aligning Web-based Tools to the Research Process Cycle: A Resource for Collaborative Research Projects.
KR101810905B1 (ko) 소셜 플랫폼을 이용한 협업기록 동적 생성 방법 및 컴퓨터 프로그램
Battut et al. OneTrace: Improving Event Recall and Coordination With Cross-Application Interaction Histories
Tsatsou The Role of Digital Technologies in Social Research in the UK
Funk et al. The sensei overview of newspaper readers’ comments
Al-Thani Understanding and Supporting Cross-modal Collaborative Information Seeking
Lee et al. Uncovering CHI Reviewers Needs and Barriers
Lucassen Understanding user stories: computational linguistics in agile requirements engineering
de Bibliotecas REBIUN REBIUN, Science 2.0: The Use of Social Networking in Research

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18715294

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04.12.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 18715294

Country of ref document: EP

Kind code of ref document: A1