Presents an overview of the components in the file
By recording and evaluating user actions on file components, identifying and presenting an overview of important components, the problem that users in the prior art cannot view only the components of interest is solved, and the user experience and efficiency are improved.
Patent Information
- Application Number
- CN201980024313.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-04-06
- Filing Date
- 2019-03-27
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-03-27
AI Technical Summary
Existing software applications cannot allow users to view only the components of interest without providing users with all the components in the file, resulting in limited user experience, especially when viewing files of large numbers of components.
By recording the user's actions on multiple components of the file, evaluating these actions to identify important components, and presenting only an overview of these components in the user interface, including continuous viewing, hovering, clicking and other actions of components, combined with User identity, location, and subject information are weighted for evaluation.
Improves user experience, saves users time to search for file components, ensures that users do not ignore components that other users consider important, and improves file viewing efficiency.
Smart Images

Figure CN111954873B_ABST
Abstract
Description
Technical Field
[0001] Some aspects of this disclosure relate to computing hardware and software techniques, and in particular, some aspects of this disclosure relate to presenting an overview of components in a file. Background Art
[0002] Many software applications provide users with the function of distributing files between a large number of users. These software applications include various components (e.g., presentation slides, some parts of text, spreadsheet tabs, audio clips, video clips, etc.) compiled into files (e.g., presentation slides, text documents, electronic spreadsheet books, audio files, video files, etc.), which can be shared and viewed by any user accessing the files in the software application, such as in a cloud computing environment. These files can include any number of components and may become very large. Although some components in the file may be interesting to some users, other components may not be. However, current software applications cannot enable users to only view components of interest without providing users with all components distributed between users in the file. When viewing the components in the file with a large number of components, this limits the ability of the application to enhance the user experience. Summary of the invention
[0003] Disclosed herein is an enhanced system, method, and software application for improving the provision of an overview of components in a file to a user. A record of actions taken by a user on a plurality of components in a file is saved. The record is evaluated to identify one or more identified components of a plurality of components based on the actions taken by the user on the plurality of components in the file. In response to identifying the one or more components in the file, an overview of the plurality of components in the file is presented in a user interface including the one or more identified components of the plurality of components.
[0004] This summary is provided to introduce a set of design concepts that are further described below in the detailed description in a simplified form. This summary is not intended to identify key features or important features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Additional aspects, features, and / or advantages of the examples will be set forth in part in the description below, and in part will be apparent from the description, or may be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Many aspects of the present disclosure may be better understood with reference to the following drawings. Although several embodiments are described in conjunction with these drawings, the present disclosure is not limited to the embodiments disclosed herein. On the contrary, it is intended to cover all alternatives, modifications and equivalents.
[0006] Figure 1An operational architecture for implementing an enhanced application for providing a user with an overview of components in a file is shown.
[0007] Figure 2 A summarization process employed in an embodiment of an enhanced application for providing a user with a summary of components in a file is shown.
[0008] Figure 3 An exemplary data table in an embodiment of an enhanced application for providing a user with an overview of components in a file is shown.
[0009] Figure 4 An operational architecture in an embodiment of an enhanced application for providing a user with an overview of components in a file is shown.
[0010] Figure 5 An alternative operating architecture in an embodiment of an enhanced application for providing a user with an overview of components in a file is shown.
[0011] Figure 6 An alternative operating architecture in an embodiment of an enhanced application for providing a user with an overview of components in a file is shown.
[0012] Figure 7 A computing system suitable for implementing the techniques disclosed herein is shown, including any of the architectures, processes, operating scenarios, and operating sequences shown in the figures and discussed below in the detailed description. DETAILED DESCRIPTION
[0013] Examples of the present disclosure describe an application for providing a user with an overview of components in a file. A record of actions taken by the user on multiple components in the file is saved. The record is evaluated to identify one or more components in the multiple components based on the actions taken by the user on the multiple components in the file. In response to identifying the one or more components in the file, an overview of the multiple components in the file is presented in a user interface including the one or more identified components in the multiple components.
[0014] The technical effect that can be appreciated from this discussion is that efficiency is improved when identifying components that may be relevant to a given user based on prior interactions between other users and components (e.g., other users viewing certain slides in a presentation more than others indicating that these slides may be more important), and providing the user with an overview of only those slides. The application described herein also improves efficiency by showing only the most important components to the user, which saves the user time searching for components of a file and ensures that the user does not overlook components that other users who have viewed components of the file consider important.
[0015] In addition, the examples herein describe that the actions taken by the user on the multiple components in the file include at least one of the following on the multiple components in the file: screen viewing, hovering, tapping, touching, clicking, or screenshots for a timed duration. In other examples, the actions taken by the user on the multiple components in the file may also include at least one of the following on the multiple components in the file: adding, editing, inserting, copying and pasting, repeating, rearranging, or typographical changes. The actions taken by the user on the multiple components in the file may also include rewinding, fast forwarding, replaying, pausing, or slow motion.
[0016] In some embodiments, the record of the action taken by the user also includes: the user identity, user group, position, or theme associated with each action. In this embodiment, the record is evaluated to identify one or more components based on the indicated user identity, user group, position, or theme associated with each action taken on multiple components in the file. In some examples, the record is evaluated to identify one or more components based on the weighted average of the indicated user identity, user group, position, or theme associated with each action taken on multiple components in the file. In other scenarios, the record also includes the action taken by the user to some parts of the multiple components in the file. In this example, the overview also includes one or more identified parts of the multiple components in the file.
[0017] In yet another example, the overview of multiple components in a file includes presenting an option to view additional components in the file associated with each of the one or more identified components in the file. The components in the file may include at least a presentation slide, a portion of text, a spreadsheet tab, a data entity card, a photo, a table, a reference, a graphic, an audio clip, or a video clip. The file may include at least a set of presentation slides, a text document, a spreadsheet book, an audio file, or a video file.
[0018] With reference to the accompanying drawings, Figure 1 An exemplary operational architecture 100 related to processing operations for managing an exemplary enhanced system that can be used to practice aspects of the present disclosure is shown. The operational architecture 100 includes an application service 101. The application service 101 employs an overview process 200 in the context of generating a view in a user interface 110 in a computing environment. The user interface 110 displays components in a shared file generated by the application service 101 to a user.
[0019] Application service 101 represents any device capable of running an application locally or in the context of a web browser, streaming an application, or executing an application in any other manner. Examples of application service 101 include, but are not limited to, a personal computer, a mobile phone, a tablet computer, a desktop computer, a laptop computer, a wearable computing device, or any other form factor, including any combination or variation of a computer. Application service 101 may include various hardware and software elements in a supporting architecture suitable for performing overview process 200. Figure 7 One such representative architecture is shown in .
[0020] Application service 101 also includes software applications or application components that can selectively indicate actions on components in a shared file according to the processes described herein. Examples of software applications include, but are not limited to: presentation applications, drawing applications, computer-aided design applications, productivity applications (such as word processors or spreadsheet applications), audio and video applications, and any other type of combination or variation thereof. Software applications can be implemented as applications that are installed and executed locally, web applications hosted in the context of a browser, streaming or streaming applications, mobile applications, or any variation or combination thereof.
[0021] although Figure 1 The dynamics shown for user interface 110 in FIG. 1 may be applied to any other suitable application, but user interfaces 110-113 include representative views that may be generated by a file sharing application that may be opened and viewed by multiple users, such as from Email to multiple users or in Shared on The user interfaces 110-113 may display components, such as presentation slides, portions of text, tabs in a spreadsheet, photos, tables, graphics, quotes, audio clips, or video clips, to name a few. The end user may interface with the application service 101 to view / hover over components, screenshot / screen share components, add / edit components, copy and paste components, insert components, point a laser at components, or write on components by using user interface tools or any other type of component actions in the file 120 presented in the user interfaces 111-113. The actions taken by the user on the multiple components 130-134 in the file 120 may also include rewinding, fast forwarding, replaying, pausing, or slow motion. It should be noted that user interactions with the components 130-134 of the file 120 are tracked and a record (i.e., record 140) is saved.
[0022] The user may interface with the application service 101 through the user interface 110-113 using an input tool, such as a stylus, a mouse device, a keyboard, touch gestures, and any other suitable input device. The user may initiate commands for introducing components 130-134 into the file 120, such as typing, copying and pasting, inserting, dragging and dropping, importing / exporting, etc. The user may also interface with the components 130-134 of the file 120 by viewing the components for a period of time, hovering over, tapping, touching, clicking, screenshotting, screen sharing, zooming, laser pointing, or writing on the components using a digital ink pen.
[0023] More specifically, Figure 2 The summary process 200 is shown, which, as previously described, can be used by the application service 101 to provide a summary of components in a document as described herein. Some or all of the steps of the summary process 200 can be implemented as program instructions in the context of one or more components of an application for performing the summary feature. The program instructions direct the application service 101 to operate as follows, Figure 1 To quote parenthetically in the context of Figure 2 Steps in .
[0024] In operation, the application service 101 saves a record of actions taken by a user on the user interface 111-113 on a plurality of components 130-134 in the file 120 (step 201). The file 120 may be a presentation, a canvas or chart, a productivity document (e.g., a word document or a spreadsheet), an audio file, a video file, and any other type of combination or variation thereof. The file 120 may be generated in the application service 101 by one or more users and distributed among the users. For example, a user may create a file 120 by uploading a template or generating a presentation to be distributed among all users in a company. Some exemplary applications are also configured to enable a user to pull a previously generated file locally (e.g., from a storage device of a particular computing device) or to obtain the file via a network connection (e.g., from a distributed storage device, a website, etc.). The user may then share the file 120 with other users for viewing using the application service 101.
[0025] Although not in Figure 1130-134 in a software application. The application service 101 may be used to store the components 130-134 in a local application, a web browser, a streaming application, a cloud application, or any other application. The different records may be used to track the actions taken on the components 130-134 between users in the software application. The record database (i.e., record 140) may be found in a variety of applications (including text-based applications, spreadsheet applications, presentation applications, mobile applications, web applications, database applications, audio / video editing and playback applications, and graphic design applications) and may be particularly useful in the context of document sharing and viewing. The application service 101 may insert the components into the file 120. Some exemplary applications are also configured to enable users to pull components locally (e.g., from the storage of a particular computing device) or obtain components via a network connection (e.g., from a distributed storage device, a website, etc.).
[0026] The application service 101 can receive user input indicating a command for performing an action on the components 130, 134 by receiving the user input in the user interfaces 111-113. The application service 101 can then store the action taken on the component in a record 140 in the software application based on the received user input. The application service 101 can use an input tool (e.g., a stylus, a mouse device, a keyboard, a touch gesture, and any other suitable input device) to receive the user input. The components 130-134 can be presentation slides, portions of text, tabs in a spreadsheet book, data entity cards, images, tables, graphics, data ranges, references, audio clips, video clips, and the like. For example, a component 130 can be introduced into the file 120 by typing a portion of text (e.g., "ABC") in the file 120.
[0027] The user of user interface 111-113 can then interact with each of components 130-134 using various actions tracked and stored by application service 101. For example, user interface 111-113 can determine extended viewing time on component 130 and component 134. In addition, user interface 112 can also receive actions on component 131, such as touch, zoom, screenshot, etc. However, neither component 132 nor component 133 has any action taken by the user of user interface 111-113 indicating that these components may not be important in file 120. Although component 131 has an action performed via user interface 112, it may not be determined that the component is important because only one user is interested in the component. On the other hand, since all (or at least most) users of user interface 111-113 perform actions on each of components 130 and 134, it can be determined that components 130 and 134 are important. Application service 101 can record these actions in record 140 together with the identity of the user of user interface 111-113. In some embodiments, the actions taken by the user on the plurality of components in the file include at least one of the following: screen viewing, hovering, tapping, touching, clicking, or screenshots of the plurality of components 130-134 in the file 120 for a timed period of time. Other actions that the user can take include editing, copying, typographical changes, rewinding, fast forwarding, replaying, or slow motion of the plurality of components 130-134 in the file 120.
[0028] In a next operation, the application service 101 then evaluates the record 140 to identify one or more components 130 and 134 of the plurality of components 130-134 based on the actions taken by the user of the user interface 111-113 on the plurality of components 130-134 in the file 120 (step 202). The application service 101 may query the record 140 for any actions taken on the components 130-134 of the file 120 by periodically identifying the actions taken on the components 130-134 of the file 120 in a recent time period. The application service 101 also queries the record 140 when the user 109 interfaces with the file 120 (e.g., when the file 120 is saved, reopened, shared, sent via email, relocated in a storage system, etc.). When directed by the user 109, the record 140 may also be queried for actions taken by other users on the components 130 and 134, such as by prompting the user 109 with a summary option. It should also be noted that in some embodiments, the record 140 also tracks and saves actions taken on some parts of the components 130-134. For example, in addition to tracking the actions taken by the user on the presentation slide, the record 140 can also track the specific parts of the presentation slide that the user is taking actions on.
[0029] In some embodiments, the record of actions taken by the user also includes: a user identity, user group, location, or subject associated with each action. In this embodiment, the record 140 is evaluated to identify one or more components based on the indicated user identity, user group, location, or subject associated with the actions taken by the user on multiple components 130-134 in the file 120. For example, the user can indicate the following user preference profile: user 109 is interested in actions taken by users of the user interface 111, users associated with a name group, or actions on components of a specified subject. In some examples, the record 140 is evaluated to identify one or more components based on a weighted average of the indicated user identity, user group, location, or subject associated with the actions taken by the user on multiple components 130-134 in the file 120.
[0030] Application service 101 can also distribute components as real-time or static. If component is distributed as real-time, then in file 120, can be for the action that other users take, for the action to track this component. If this component is distributed as static, then in file 120, will not be for the action that other users take to track this component. For example, the catalogue in the document can be distributed as static, this is because many users can view the catalogue, but the catalogue need not be included in the overview of the component of highlighting. It should be noted that application service 101 can also distribute components as real-time for some actions that users take, and then distribute as static for other actions that other users take. For example, the action that is carried out by department manager can be distributed as the activity action that is carried out to component. However, the action that is taken by the employee of another department can be distributed as static, therefore when record 140 is evaluated to determine component 130-134, it will not be considered.
[0031] In a final operation, the application service 101 presents an overview 150 of the plurality of components 130-134 in the file 120 in the user interface 110, which includes one or more of the identified components in the plurality of components (step 203). The overview 150 of the plurality of components 130-134 in the file 120 includes presenting an option for viewing additional components 131-133 in the file 120 associated with each of the one or more identified components 130 and 134. The application service 101 may also present the overview 150 to the user 109 by displaying icons, toolbar indicators, typographical changes (e.g., highlighting, shading, bolding, underlining, size enlargement or reduction), animation, or any other technique to indicate important portions of the components 130 and 134 in the file 120. The overview 150 may also be displayed in the form of an overview card or activity log associated with the file 120. The overview card or activity log may additionally display an explanation or preview of actions taken by the user of the user interface 111-113 on the components 130 and 134. In some implementations, the summary 150 may also display only a portion of the components 130 and 134 based on a user action taken on that portion of the components. For example, the application service 101 may display only a portion of a presentation slide in the summary 150 instead of displaying the entire presentation slide.
[0032] Figure 3 The data table 300 is shown in more detail, with exemplary actions tracked for each component in the file, as well as exemplary user identities and user types for each column. The file types in column 341 of the table 300 represent, at least in part, specific presentations shared between users in the company. For the components in column 342, each component indicates a different slide in a slide set for the presentation, but other component types are possible and are considered within the scope of the present disclosure.
[0033] The user in column 344 is the user who is recorded as performing the action indicated in column 343 to the component of column 342. The action of column 343 can be a command initiated by any user to the component, such as the viewing of the component for a period of time, the highlighting of the component, the screen shot of the component, etc. The user type of column 345 represents the user group of the user who takes the action of column 343, and can be used to determine whether the action should be included in a specific overview. It should be noted that other exemplary columns can be included in the data table, and these columns are tracked together with the action taken by the user to the component. These other columns can include position, theme, time range, format type, etc.
[0034] As shown on the right side of table 300, different overviews can be generated for each department group and for the entire company. For example, when 97% of all users view slide 1, the slide will likely be included in the overview for the entire company. Similarly, if the CEO adds slide 22, the slide may be important to all employees in the company. On the other hand, if 70% of users in the Research and Development (R&D) department view slide 12, but only a few users in the company as a whole view slide 12. Therefore, slide 12 will likely only be included in the overview for the R&D department. In addition, if the manager of the marketing department takes a screenshot of slide 23, the marketing department can include slide 23 in the marketing department overview.
[0035] It should also be noted that actions taken by other employees outside of a given department may be "active" for the overview of that given department. For example, if a controller in the accounting department shares the screen with other employees in the marketing department, then that slide (i.e., slide 24) may also be determined to be important to the marketing department. On the other hand, slides that have not had any actions performed on them (i.e., have only been viewed for a short period of time) may not be included in any type of overview, such as slides 2-9 and 13-20. Furthermore, slides that have had actions performed on them but not by a majority of users (in the company or in the department), or by interested users (e.g., managers or executives), will not be added to any overview, such as slide 21 that was edited by only one user.
[0036] Figure 4 An exemplary operational architecture for providing an overview of slides in a presentation that can be used in one or more scenarios of the present technology is shown. Figure 4 An operational scenario 400 is shown relating to what happens when a person of interest, such as a manager, takes action on a slide. The operational scenario 400 includes an application service 401, a user interface 410 in a user environment 409, and other users using user interfaces 411-413. The user interfaces 411-413 display a presentation 420 to the manager via user interface 411, and display the presentation 420 to two employees via user interfaces 412-413. The user 409 views a presentation overview 450 in the user interface 410. The operational scenario 400 also includes a record 440 to track and save actions taken by users of the user interfaces 411-413 on slides 430-435 in the presentation 420. In this example, the record 440 is saved in a cloud-based environment.
[0037] In a first operation, at time 1, each user of user interfaces 411-413 views presentation 420. The users also perform various actions on slides 430-435. For example, the manager takes a screenshot of slide 431 and highlights slide 433. In addition, employee #1 views slide 430 during an extended period of time, and employee #2 references the content of slide 432. Application service 401 tracks each of these actions and saves record 440 indicating slides 430-435, the action or actions taken on each of slides 430-435, and the user or users who took the action.
[0038] In addition, each action performed by each user on the slide indicates an assignment type. The assignment type identifies which user actions should be assigned as important. For example, the actions taken by the manager on slides 431 and 433 are assigned as active, indicating that the actions taken by the manager should be used to determine that the slides are important. On the other hand, the actions taken by employee #1 and employee #2 are assigned as static and are not determined for the generation of the overview.
[0039] In the next operation, at time 2, user 409 requests presentation summary 450. In response to the request, application service 401 evaluates record 440 to determine that slides 431 and 433 are important. On the other hand, slides 430, 432, and 434-435 are determined to be unimportant and are not included in presentation summary 450. After presentation summary 450 has been generated, application service 401 displays presentation summary 450 to user 409 in user interface 410.
[0040] Figure 5 An alternative operational architecture for providing an overview of audio clips in an audio file that may be used in one or more scenarios of the present technology is shown. Figure 5 An operational scenario 500 is shown relating to what happens when an action is taken on one or more audio clips in an audio file. The operational scenario 500 includes an application service 501, a user interface 510 in a user environment 509, and other users using user interfaces 511-513. The user interfaces 511-513 present an audio file 520 via the user interfaces 511-513. The application service 501 presents the audio file 520 and an audio summary 550 in the user interface 510. The operational scenario 500 also includes a record 540 to track and save the actions taken by the users of the user interfaces 511-513 on the audio clips 530-532 in the audio file 520. In this example, the record 540 is saved in a cloud-based environment.
[0041] In a first operation, at time 1, each user of user interfaces 511-513 views presentation 520. The users also perform various actions on audio clips 530-532. For example, user #1 rewinds and replays clip 531. Additionally, user #2 rewinds and replays audio clips 530-531, and user #3 fast-forwards on audio clip 530 and plays audio clips 531-532. Application service 501 tracks each of these actions and saves record 540 indicating the users of user interfaces 511-513 and the actions taken on audio clips 530-532 by each of user interfaces 511-513.
[0042] In the next operation, at time 2, user 509 requests to open audio file 520 and audio overview 550. In response to the request, application service 501 evaluates record 540 to determine that audio clip 531 has been rewound and replayed by most users, or fast-forwarded and played. Therefore, audio clip 531 is determined to be an important audio clip of audio file 520. After audio overview 550 has been generated, application service 501 transmits both audio file 520 and audio overview 550 to user 509. At this point, user 509 opens audio file 520. In the last operation, at time 3, user 509 requests audio overview 550, and user interface 510 presents audio clip 531 in audio overview 550.
[0043] Figure 6 An alternative operational architecture for providing an overview of related components (ie, references) of an identified component in a text document is shown that may be used in one or more scenarios of the present technology. Figure 6 An operational scenario 600 is shown relating to what occurs when an action is taken on one or more portions of text in a document and a user requests to view an overview of references to the identified portions of text. The operational scenario 600 includes an application service 601, a user interface 610 in a user environment 609, and another user using a user interface 611. The user interface 611 presents a document 620 via the user interface 611. The user interface 610 presents an overview 650 and an overview of references to the user. The operational scenario 600 also includes a log 640 to track and save actions taken on the text 630 and associated components 631-632.
[0044] In the first operation, at time 1, the user of user interface 611 views document 620. The user of user interface 611 also performs editing on a portion of text 630. Application service 601 tracks the action and saves record 640, which indicates the user of user interface 611, the action taken on a portion of text 630, and the references 631-632 associated with the portion of text 630. In the next operation, at time 2, the user requests to view an overview 650 of document 620. In response to the request, application service 601 evaluates record 640 to determine that the portion of text 630 is determined to be an important section of text 630 because the text has been edited by another user. After the overview 650 has been generated, application service 601 transmits the overview 650 to the user. At this point, the user views the overview 650 including a portion of text 630 and requests to view the associated references to a portion of text 630. In the final operation, at time 3, the user receives a reference overview 660, which is displayed in user interface 610.
[0045] Figure 7 A computing system 701 is shown, which represents any system or visual representation of a system in which the various applications, services, scenarios, and processes disclosed herein may be implemented. Examples of computing system 701 include, but are not limited to: server computers, rack servers, web servers, cloud computing platforms, and data center equipment, as well as any other type of physical or virtual server machines, containers, and any variations or combinations thereof. Other examples may include smart phones, laptops, tablet computers, desktop computers, hybrid computers, gaming consoles, virtual reality devices, smart televisions, smart watches and other wearable devices, and any variations or combinations thereof.
[0046] The computing system 701 may also be implemented as a single device, system or apparatus, or may be implemented as multiple devices, systems or apparatuses in a distributed manner. The computing system 701 includes, but is not limited to, a processing system 702, a storage system 703, software 705, a communication interface system 707, and a user interface system 709. The processing system 702 is operatively coupled to the storage system 703, the communication interface system 707, and the user interface system 709.
[0047] Processing system 702 loads and executes software 705 from storage system 703. Software 705 includes processes 706, which represent the Figure 1-Figure 6 The processes discussed herein include the overview process 200. When executed by the processing system 702 to implement the application, the software 705 directs the processing system 702 to operate as described herein at least for the various processes, operating scenarios and sequences discussed in the foregoing embodiments. The computing system 701 may optionally include additional devices, features or functions that are not discussed for the sake of simplicity.
[0048] Still refer to Figure 7 , the processing system 702 may include a microprocessor and other circuits to retrieve and execute software 705 from a storage system 703. The processing system 702 may be implemented within a single processing device, but may also be distributed among multiple processing devices or subsystems that cooperate to execute program instructions. Examples of the processing system 702 include: a general-purpose central processing unit, a graphics processing unit, a special-purpose processor and logic device, and any other type of processing device, combination, or variation.
[0049] The storage system 703 may include any computer-readable storage medium that is readable by the processing system 702 and capable of storing the software 705. The storage system 703 may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Examples of storage media include random access memory, read-only memory, magnetic disks, optical disks, flash memory, virtual and non-virtual memory, magnetic cassettes, tapes, disk storage devices or other magnetic storage devices, or other suitable storage media other than propagating signals. The storage system 703 may be implemented as a single storage device, but may also be implemented between multiple storage devices or subsystems that are co-located or distributed relative to each other. The storage system 703 may include additional elements, such as a controller that can communicate with the processing system 702 or possibly other systems.
[0050] The software 705 may be implemented in program instructions and, when executed by the processing system 702, direct the processing system 702 to operate as described for the various operational scenarios, sequences, and processes described herein, as well as to perform other functions. The software 705 may include program instructions for implementing the overview process 200.
[0051] Specifically, program instructions may include various components or modules that collaborate or otherwise interact to perform various processes and operation scenarios described herein. Various components or modules may be embodied as compiled or interpreted instructions or some other variation or combination of instructions. Various components or modules may be executed in a synchronous or asynchronous manner, serially or in parallel, in a single-threaded or multi-threaded environment, or according to any other suitable execution paradigm, variation or combination thereof. In addition to or including process 706, software 705 may also include additional processes, programs or components, such as operating system software, virtual machine software or other application software. Software 705 may also include firmware or some other form of machine-readable processing instructions that may be executed by processing system 702.
[0052] In summary, when loaded into processing system 702 and executed, software 705 can transform a suitable device, system or apparatus (represented by computing system 701) generally from a general purpose computing system into a special purpose computing system for enhancing services for notifying a user of another user's actions on a component of a collaborative document. Indeed, the encoded software 705 on storage system 703 can transform the physical structure of storage system 703. The specific transformation of the physical structure can depend on various factors in different embodiments of the present specification. These factors can include, but are not limited to: the technology of the storage medium used to implement storage system 703, and whether the computer storage medium is characterized as a primary storage device or a secondary storage device, as well as other factors.
[0053] If the computer-readable storage medium is implemented as a semiconductor-based memory, when the program instructions are encoded in the software 705, the software 805 can transform the physical state of the semiconductor memory, for example, by transforming the state of transistors, capacitors, or other discrete circuit elements that make up the semiconductor memory. Similar transformations can occur for magnetic or optical media. Other transformations of the physical medium are possible without departing from the scope of this specification, and the foregoing examples are provided only to facilitate this discussion.
[0054] The communication interface system 707 may include communication connections and devices that allow communication with other computing systems (not shown) through a communication network (not shown). Examples of connections and devices that together allow communication between systems may include: network interface cards, antennas, power amplifiers, RF circuits, transceivers, and other communication circuits. The connections and devices may communicate over a communication medium to exchange communications with other computing systems or systems network, such as metal, glass, air, or any other suitable communication medium. The above-mentioned media, connections, and devices are well known and need not be discussed in detail herein.
[0055] The user interface system 709 may include a keyboard, a mouse, a voice input device, a touch input device for receiving touch gestures from a user, a motion input device for detecting non-touch gestures and other movements of a user, and other similar input devices and associated processing units capable of receiving user input from a user. Output devices such as displays, speakers, tactile devices, and other types of output devices may also be included in the user interface system 709. In some cases, input devices and output devices may be combined in a single device, such as a display capable of displaying images and receiving touch gestures. The above-mentioned user input and output devices are well known in the art and need not be discussed in detail herein. The user interface system 709 may also include: associated user interface software that can be executed by the processing system 702 to support the various user input and output devices discussed above.
[0056] The communication between computing system 701 and other computing systems (not shown) can occur through one or more communication networks and according to various communication protocols, combinations of protocols, or variations thereof. Examples include an intranet, the Internet, a local area network, a wide area network, a wireless network, a wired network, a virtual network, a software-defined network, a data center bus, a computing backplane, or any other type of network, combination of networks, or variations thereof. The above communication networks and protocols are well known and need not be discussed in detail herein.
[0057] In any of the above examples in which data, content, or any other type of information is exchanged, the exchange of information may occur according to any of a variety of protocols including FTP (File Transfer Protocol), HTTP (Hypertext Transfer Protocol), HTTPS, REST (Representational State Transfer), web sockets, DOM (Document Object Model), HTML (Hypertext Markup Language), CSS (Cascading Style Sheets), HTML5, XML (Extensible Markup Language), JavaScript, JSON (JavaScript Object Notation), and AJAX (Asynchronous JavaScript and XML), as well as any other suitable protocols, variations, or combinations thereof.
[0058] From the foregoing disclosure, certain inventive aspects can be appreciated, and the following are various examples.
[0059] The functional block diagrams, operation scenarios and sequences, and flow charts provided in the accompanying drawings represent exemplary systems, environments, and methods for executing novel aspects of the present disclosure. Although, in order to simplify the description, the methods included herein may be in the form of functional diagrams, operation scenarios or sequences, or flow charts, and may be described as a series of actions, it should be understood and appreciated that these methods are not limited to the order of the actions, because, accordingly, some actions may occur in different orders and / or occur simultaneously with other actions shown and described herein. Those skilled in the art will understand and appreciate that the methods may alternatively be represented as a series of interrelated states or events, such as in a state diagram. In addition, not all actions described in the method are necessary for novel implementations.
[0060] Example 1. A computer device comprising: one or more computer-readable storage media; one or more processors operatively coupled to the one or more computer-readable storage media; and a media application comprising program instructions stored on the one or more computer-readable storage media, wherein the program instructions, when read and executed by the one or more processors, direct the one or more processors to perform at least the following operations: save a record of actions taken by a user on multiple components in a file; evaluate the record to identify one or more of the multiple components based on the actions taken by the user on the multiple components in the file; and present an overview of the multiple components in the file in a user interface of the application, the overview including one or more identified components of the multiple components.
[0061] Example 2. A computer device according to Example 1, wherein the action taken by the user on the multiple components in the file includes at least one of the following on the multiple components in the file: screen viewing, hovering, tapping, touching, clicking, or screenshot for a timed duration.
[0062] Example 3. A computer device according to Examples 1-2, wherein the actions taken by the user on the multiple components in the file include at least one of: editing, copying, printing changes, rewinding, or fast forwarding the multiple components in the file.
[0063] Example 4. A computer device according to Examples 1-3, wherein: the record of actions taken by the user also includes at least one of the following associated with each of the actions: a user identity, a user group, a location, or a subject; and the program instructions also instruct the one or more processors to evaluate the record to identify the one or more components based on at least one of the user identity, the user group, the location, or the subject associated with each of the actions.
[0064] Example 5. A computer device according to Examples 1-4, wherein, in order to evaluate the record to identify the one or more components, the program instructions direct the one or more processors to evaluate the record to identify the one or more components based on a weighted average of at least one of the user identity, the user group, the location, or the subject associated with each of the actions.
[0065] Example 6. A computer device according to Examples 1-5, wherein: the record also includes actions taken by the user on some parts of the multiple components in the file; and the overview also includes one or more identified parts of the multiple components in the file.
[0066] Example 7. A computer device according to Examples 1-6, wherein, in order to present the overview of the multiple components in the file, the program instructions also instruct the one or more processors to present options for viewing additional components in the file associated with each of the one or more identified components in the file.
[0067] Example 8. A computer device according to Examples 1-7, wherein the components in the file include at least a presentation slide, a portion of text, a spreadsheet tab, a data entity card, a photo, a table, a quote, a graphic, an audio clip, or a video clip.
[0068] Example 9. A computer device according to Examples 1-8, wherein the files include at least a set of presentation slides, a text document, a spreadsheet, an audio file, or a video file.
[0069] Example 10. A method comprising: saving a record of actions taken by a user on multiple components in a file; evaluating the record to identify one or more of the multiple components based on the actions taken by the user on the multiple components in the file; and presenting an overview of the multiple components in the file in a user interface of an application, the overview including one or more identified components of the multiple components.
[0070] Example 11. A method according to Example 10, wherein the action taken by the user on the multiple components in the file includes at least one of the following on the multiple components in the file: screen viewing, hovering, tapping, touching, clicking, or screenshot for a timed duration.
[0071] Example 12. A method according to Examples 10-11, wherein the action taken by the user on the multiple components in the file includes at least one of the following on the multiple components in the file: editing, copying, printing changes, rewinding, or fast forwarding.
[0072] Example 13. A method according to Examples 10-12, wherein: the record of actions taken by the user also includes at least one of the following associated with each of the actions: a user identity, a user group, a location, or a subject; and evaluating the record to identify the one or more components includes: evaluating the record to identify the one or more components based on at least one of the user identity, the user group, the location, or the subject associated with each of the actions.
[0073] Example 14. A method according to Examples 10-13, wherein evaluating the record to identify the one or more components includes: evaluating the record to identify the one or more components based on a weighted average of at least one of the user identity, the user group, the location, or the subject associated with each of the actions.
[0074] Example 15. A method according to example requirements 10-14, wherein: the record also includes actions taken by the user on some parts of the multiple components in the file; and the overview also includes one or more identified parts of the multiple components in the file.
[0075] Example 16. A method according to example requirements 10-15, wherein presenting the overview of the multiple components in the file also includes: presenting an option for viewing additional components in the file associated with each of the one or more identified components in the file.
[0076] Example 17. A method according to Examples 10-16, wherein the components in the file include at least a presentation slide, a portion of text, a spreadsheet tab, a data entity card, a photo, a table, a graphic, an audio clip, or a video clip.
[0077] Example 18. The method according to Examples 10 to 17, wherein the file includes at least a set of presentation slides, a text document, a spreadsheet, an audio file, or a video file.
[0078] Example 19. One or more computer-readable storage media having program instructions stored thereon, wherein the program instructions, when executed by a processing system, direct the processing system to perform at least the following operations: save a record of actions taken by a user on some portions of multiple components in a file; evaluate the record to identify one or more portions of the multiple components based on the actions taken by the user on the portions of the multiple components in the file; and present an overview of one or more identified portions of the multiple components in a user interface of the application.
[0079] Example 20. One or more computer-readable storage media according to Example 19, wherein: the record of actions taken by the user also includes at least one of the following associated with each of the actions: a user identity, a user group, a location, or a subject; and the program instructions also instruct the one or more processors to evaluate the record to identify one or more parts of the component based on at least one of the user identity, the user group, the location, or the subject associated with each of the actions.
Claims
1. A computer device, comprising: one or more computer-readable storage media; one or more processors operatively coupled to the one or more computer-readable storage media; as well as A medium application comprising program instructions stored on the one or more computer-readable storage media, the program instructions, when read and executed by the one or more processors, directing the one or more processors to perform at least the following operations: receiving user input from a plurality of users interacting with a shared document via a plurality of computing devices remote from the computer apparatus, wherein the user input comprises commands for performing actions with respect to a plurality of components of the shared document; tracking the actions taken by the plurality of users with respect to the plurality of components in the shared document; for each of the actions, recording information about the action in a database, wherein the information includes an indication of a component associated with the action, an identity of a corresponding user performing the action, a group to which the corresponding user belongs, a status of the action, and a status of the component; receiving, from a productivity application on a computing device associated with one of the plurality of users, a request for an overview of the shared document; In response to the request, querying the information in the database to identify at least one component of the plurality of components to present in the summary of the shared document based at least on a weighted average evaluated for each of the actions; and The summary is sent to the productivity application on the computing device, wherein the summary includes a card displaying the at least one component and an indication of one or more actions associated with the at least one component.
2. The computer device according to claim 1, wherein: The action includes at least one of the following actions on the multiple components in the shared document: screen viewing for a timed duration, hovering, tapping, touching, clicking, or screenshotting.
3. The computer device according to any one of claims 1 to 2, wherein: The action includes at least one of the following actions on the plurality of components in the shared document: editing, copying, printing changes, rewinding, or fast forwarding.
4. The computer device according to any one of claims 1 to 2, wherein: The information also includes at least one of the following associated with each of the actions: a user identity, a user group, a location, or a subject; and To identify the at least one component, the program instructions further direct the one or more processors to evaluate a weighted average for each of the actions based on at least one of the user identity, the user group, the location, and the topic associated with each of the actions.
5. The computer device according to any one of claims 1 to 2, wherein: To identify the at least one component, the program instructions direct the one or more processors to select the at least one component based on a weighted average evaluated for each of the actions.
6. The computer device according to claim 1, wherein: The summary includes an option for viewing additional components associated with the at least one component in the shared document.
7. The computer device according to claim 1, wherein: The at least one component includes at least a presentation slide, a portion of text, a spreadsheet tab, a data entity card, a photograph, a table, a quote, a graphic, an audio clip, or a video clip.
8. The computer device according to claim 1, wherein: The shared document at least includes a set of presentation slides, a text document, an electronic spreadsheet, an audio file, or a video file.
9. A method implemented at a server computer, comprising: receiving user input from a plurality of users interacting with a shared document via a plurality of computing devices remote from the server computer, wherein the user input includes commands for performing actions with respect to a plurality of components of the shared document; for each of the actions, recording information about the action in a database, wherein the information includes an indication of a component associated with the action, an identity of a corresponding user performing the action, a group to which the corresponding user belongs, a status of the action, and a status of the component; receiving, from a productivity application on a computing device associated with one of the plurality of users, a request for an overview of the shared document; In response to the request, querying the information in the database to identify at least one component of the plurality of components to present in the summary of the shared document based at least on a weighted average evaluated for each of the actions; and The summary is sent to the productivity application on the computing device, wherein the summary includes a card displaying the at least one component and an indication of one or more actions associated with the at least one component.
10. The method according to claim 9, wherein: The action includes at least one of the following for the multiple components in the shared document: screen viewing, hovering, tapping, touching, clicking, screenshotting for a timed duration, editing, copying, printing changes, rewinding, or fast-forwarding the multiple components in the shared document.
11. The method according to claim 9 or 10, wherein: The information also includes at least one of the following associated with each of the actions: a user identity, a user group, a location, or a subject; and Identifying the at least one component includes evaluating a weighted average for each of the actions based on at least one of the user identity, the user group, the location, and the topic associated with each of the actions.
12. The method according to claim 9 or 10, wherein: The summary includes an option for viewing additional components associated with the at least one component in the shared document.
13. One or more computer-readable storage media having program instructions stored thereon, wherein: When executed by a processing system in a server computer, the program instructions direct the processing system to perform at least the following operations: receiving user input from a plurality of users interacting with a shared document via a plurality of computing devices remote from the server computer, wherein the user input includes commands for performing actions with respect to a plurality of components of the shared document; for each of the actions, recording information about the action in a database, wherein the information includes an indication of a component associated with the action, an identity of a corresponding user performing the action, a group to which the corresponding user belongs, a status of the action, and a status of the component; receiving, from a productivity application on a computing device associated with one of the plurality of users, a request for an overview of the shared document; In response to the request, querying the information in the database to identify at least one component of the plurality of components to present in the summary of the shared document based at least on a weighted average evaluated for each of the actions; and The summary is sent to the productivity application on the computing device, wherein the summary includes a card displaying the at least one component and an indication of one or more actions associated with the at least one component.
