User interface and systems for document creation

Description

FIELD

Embodiments herein relate to user interfaces, systems, and methods for creating a document based on previous document creation data.

SUMMARY

Various embodiments provide a method for document creation based on previous document creations. The method can include presenting a frame to a user, i. wherein the frame includes a first field, a second field, a third field, and a fourth field, ii. wherein a first group includes the first field and the second field, iii. wherein a second group includes the third field and the fourth field. The method can include presenting a first portion of a first collection of data, i. wherein the first collection of data includes data that was previously entered into the fields of the frame, ii. wherein the first portion of the first collection of data aligns with the first group and the first portion includes a first field data entry displayed in the first field and a second field data entry displayed in the second field. The method can include receiving a confirmation or a denial of the first portion of the first collection for the first group from the user. The method can include upon receiving a denial, presenting a first portion of a second collection of data for the first group, i. wherein the second collection of data includes data that was previously entered into the fields of the frame, ii. wherein the first portion of the second collection of data aligns with the first group and the first portion includes a first field data entry displayed in the first field and a second field data entry displayed in the second field. The method can include, after receiving a denial of the first portion of the first collection, receiving a confirmation of the second collection for the first group from the user. The method can include presenting a second portion of the first collection of data, i. wherein the second portion of the first collection of data aligns with the second group and the second portion includes a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field. The method can include receiving a confirmation or a denial of the second portion of the first collection for the second group from the user. The method can include upon receiving a denial, presenting a second portion of the second collection of data for the second group, i. wherein the second portion from the second collection of data aligns with the second group and the second portion includes a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field. The method can include after receiving a denial of the second portion of the first collection, receiving a confirmation of the second portion of the second collection for the second group from the user. The method can include compiling confirmed portions of data into a prose output, and presenting the prose output to the user through a user interface.

In various embodiments, the method can further include receiving edits to the prose output from the user.

In various embodiments, the method can further include saving confirmed portions of data as a third collection.

In various embodiments, the method can further include receiving a request to present the first portion of the first collection for the first group after previously receiving a denial of the first portion of the first collection for the first group.

In various embodiments, the method can further include presenting the first portion of the first collection after receiving the request to present the first portion of the first collection for the first group.

In various embodiments, the data for the first collection was previously entered at a different time than the data for the second collection.

In various embodiments, receiving a confirmation or a denial of the first portion of the first collection for the first group from the user includes receiving a confirmation of the first field of the first portion of the first collection and a denial of the second field of the first portion of the first collection.

In various embodiments, the method can further include presenting the second field data entry of the first portion of the second collection in the second field.

In various embodiments, the method can further include receiving a confirmation of the second field of the first portion of the second collection.

In various embodiments, presenting a first portion of a first collection of data includes presenting time data associated with the first collection of data, wherein the time data is associated with when the first collection of data was created.

In various embodiments, the method can further include, upon receiving a confirmation of the first portion of the first collection of data, removing the second portion of the second collection of data from consideration.

In various embodiments, the method can further include recording a non-presentation indicator on a fourth collection in response to receiving the confirmation of the first portion of the first collection for the first group.

Various embodiments provide a method for data entry. The method can include presenting a frame to a user, i. wherein the frame includes a first field, a second field, a third field, and a fourth field, ii. wherein a first group of fields includes the first field and the second field, iii. wherein a second group of fields includes the third field and the fourth field. The method can include retrieving a first portion of a first collection of data from a collection database, wherein the collection database includes a plurality of collections of data, each collection of data is divided into portions, each collection of data includes entries that were previously entered in completing the frame. The method can include presenting the first portion of the first collection of data, i. wherein the first portion of the first collection of data aligns with the first group and the first portion includes a first field data entry displayed in the first field and a second field data entry displayed in the second field. The method can include receiving a confirmation of the first field data entry of the first portion of the first collection for the first field of the first group from the user. The method can include in response to receiving confirmation of the first field data entry, recording a non-presentation indicator on a second collection from the collection database that inhibits the presentation of any of a first portion of the second collection of data, and presenting a second field data entry of a first portion of a third collection of data.

In various embodiments, the method can further include presenting a second portion of the first collection, i. wherein the second portion of the first collection of data aligns with the second group and the second portion includes a third field data entry display in the third field and a fourth field data entry display in the fourth field, receiving a confirmation or a denial of the second portion of the first collection for the second group from the user, upon receiving a denial, presenting a second portion of the third collection of data, i. wherein the second portion from the third collection of data aligns with the second group and the second portion includes a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field, after receiving a denial of the second portion of the first collection, receiving a confirmation of the second portion of the third collection for the second group from the user, compiling confirmed portions of data into a prose output, and presenting the prose output to the user through a user interface.

In various embodiment, the method can include presenting a second portion of the first collection, i. wherein the second portion of the first collection of data aligns with the second group and the second portion includes a third field data entry display in the third field and a fourth field data entry display in the fourth field, receiving a confirmation or a denial of the second portion of the first collection for the second group from the user, upon receiving a denial, presenting a second portion of the second collection of data, a. wherein the second portion from the second collection of data aligns with the second group and the second portion includes a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field, after receiving a denial of the second portion of the first collection, receiving a confirmation of the second portion of the second collection for the second group from the user, compiling confirmed portions of data into a prose output, and presenting the prose output to the user through a user interface.

Various embodiments provide a method for presenting an improved user interface for data entry based on prior entries. The method can include identifying a frame can include a plurality of data fields, wherein: i. the data fields in the frame are grouped into a first data group and a second data group, ii. the first group includes a first plurality of data fields, and iii. the second group includes a second plurality of data fields. The method can include receiving a plurality of data collections for the frame, wherein each data collection includes: i. a first portion of data entries for the first group, ii. a second portion of data entries for the second group. The method can include identifying a unique set of the first portions of the data entries, wherein: i. each first portion relates to a single data collection, ii. identical first portions from different data collections are scrubbed from the unique set of the first portions to remove duplicates so that the unique set of the first portions includes the first portions of a first subset of all the plurality of data collections. The method can include identifying a first unique set of the second portions of the data entries, wherein: i. each second portion relates to a single data collection, ii. identical second portions from different data collections are scrubbed from the first unique set of the second portions to remove duplicates so that the first unique set of the second portions includes the second portions of a second subset of all the plurality of data collections that is different than the first subset of all the plurality of data collections. The method can include presenting the frame for data input in the improved user interface to a user, the improved user interface is included, the method i. the first group of the frame having a first interface element to select from among the unique set of first portions of the data entries, and ii. the second group of the frame having a second interface element to select from among the first unique set of second portions of the data entries.

In various embodiments, the selection of a particular value in a particular field in the first group presented in the improved user interface causes the creation of a second unique set of the second portions, wherein only second portions from data collections having the particular value in the particular field are included in the second unique set of second portions, further wherein the second unique set of second portions are scrubbed to remove duplicates, still further wherein the second interface elements then selects from second unique set of second portions of the data entries.

In various embodiments, the unique set of first portions of the data entries is sorted in a first sort order, and is presented in the improved user interface in the first sorted order.

In various embodiments, the unique set of second portions of the data entries is sorted in a second sort order that differs from the first sort order, and is presented in the improved user interface in the second sort order.

This summary is an overview of some of the teachings of the present application and is not intended to be an exclusive or exhaustive treatment of the present subject matter. Further details are found in the detailed description and appended claims. Other aspects will be apparent to persons skilled in the art upon reading and understanding the following detailed description and viewing the drawings that form a part thereof, each of which is not to be taken in a limiting sense. The scope herein is defined by the appended claims and their legal equivalents.

BRIEF DESCRIPTION OF THE FIGURES

Aspects may be more completely understood in connection with the following figures (FIGS.), in which:

FIG. 1 is a schematic view of document creation system in accordance with various embodiments herein.

FIG. 2 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 3 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 4 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 5 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 6 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 7 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 8 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 9 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 10 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 11 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 12 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 13 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 14 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 15 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 16 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 17 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 18 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 19 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 20 is a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

FIG. 21 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein.

FIG. 22 is a schematic view of a portion of a document creation system requesting user input in accordance with various embodiments herein.

FIG. 23 is a schematic view of a document created by the document creation system in accordance with various embodiments herein.

FIG. 24 is a schematic view of various collections in accordance with various embodiments herein.

FIG. 25 is a schematic view of filtered data in accordance with various embodiments herein.

FIG. 26 is a schematic view of filtered data in accordance with various embodiments herein.

FIG. 27 is a schematic view of filtered data in accordance with various embodiments herein.

FIG. 28 is a schematic of a document creation system in accordance with various embodiments herein.

FIG. 29 is a schematic of a document creation system in accordance with various embodiments herein.

FIG. 30 is a schematic of a document creation system in accordance with various embodiments herein.

FIG. 31 is a schematic of a collection of data in accordance with various embodiments herein.

FIG. 32 is a flowchart depicting a method in accordance with various embodiments herein.

FIG. 33 is a flowchart depicting a method in accordance with various embodiments herein.

FIG. 34 is a flowchart depicting a method in accordance with various embodiments herein.

FIG. 35 is a flowchart depicting a method in accordance with various embodiments herein.

While embodiments are susceptible to various modifications and alternative forms, specifics thereof have been shown by way of example and drawings, and will be described in detail. It should be understood, however, that the scope herein is not limited to the particular aspects described. On the contrary, the intention is to cover modifications, equivalents, and alternatives falling within the spirit and scope herein.

DETAILED DESCRIPTION

Creating documents can be time consuming, repetitive, and frustrating for users. This can be especially true when the user has previously created similar documents. The interfaces, systems, and methods described herein can provide more efficient processes to create new documents based on previous inputs to create similar documents. When a user has previously created a document similar to a new document that he/she is creating, it can be helpful to make use of the previous inputs and data such that a user does not have to recreate existing data.

In some situations, documents can be automatically created or generated after a user has entered information into a frame or template. Various embodiments disclosed herein can make use of previously entered data to efficiently create a new document. Therefore, the user does not need to start from scratch. While filling out a frame of prompts requesting data from a user, a user can be presented with data that has previously been entered into the frame during a previous document creation process.

The user interfaces, systems, and methods described herein can present previously entered data to a user. The interfaces, systems, and methods allow a user to combine portions of data from different data sets or collections to create a new document. The data from a previous data set can be separated into various groups, such that a user can be shown a group of data from different data sets. The user is able to select or choose a group of data or a subset of a group (e.g., a single field of data within a group). The user's selections can be combined into a new collection of data for creating a new document. The available data sets yet to be presented to the user can be reduced based on selections made by a user. As a result, the available options shown to the user can be reduced, which can result in increased efficiency in creating the document.

In reference now to the figures, FIG. 1 shows a schematic view of a document creation system in accordance with various embodiments herein. The subject matter shown in FIG. 1 can represent a user interface 100. The user interface 100 can display a frame 102. The frame 102 can be an outline or template that can be used for the system to display existing data to the user. The frame 102 can be used to obtain the necessary data to create the desired document through user inputs, such as confirmation or denial of presented data.

The frame 102 can include various prompts 104. The prompts 104 can be requests of specific types of data, which can vary depending on the type of document that is being created.

Each prompt 104 can be accompanied with a data field 106. The user can enter data into each of the data fields 106 in response to each or the prompts 104, such as if previous data does not appropriately respond to the prompt. In various embodiments, as will be discussed below, the data fields 106 can be populated with data from previous document creations. The system can receive a user input, such as in the form of a confirmation/acceptance or a denial/rejection of the displayed data.

The prompts 104 and the associated data fields 106 can be separated into groups. As an example, FIG. 1 show shows a first group 108, a second group 110, and a third group 112. In some embodiments, data fields 106 can be divided into at least two groups, at least three groups, at least four groups, at least five groups, at least six groups, at least seven groups, at least eight groups, at least nine groups, or at least ten groups. Additional numbers of groups are also possible.

In the embodiments shown in FIG. 1, each of the group 108, 110, 112 includes three data fields. The first group 108 includes a first field 114, a second field 116, and a third field 118. The second group 110 includes a fourth field 120, a fifth field 122, and a sixth field 124. The third group 112 includes a seventh field 126, an eighth field 128, and a ninth field 130.

In some embodiments, each group can include the same number of data fields. In some embodiments, different groups can include different numbers of data fields. In various embodiments, each group can include at least two data fields, at least three data fields, at least four data fields, at least five data fields, at least six data fields, at least seven data fields, at least eight data fields, at least nine data fields, or at least ten data fields. Additional numbers of fields within a group are also possible.

In various embodiments, the user interface can display a selector 134 for each group. The selector 134 can allow the user to switch between collections of data that are shown in the fields 106 within a group. The user can select an arrow to move the selector icon 136 between different collection icons 138. Each of the collection icons 138 can represent a previously entered collection of data that is available to the user for populating the fields within the group. In various embodiments, the collection icons 138 can each represent a collection and the collections can be arranged in chronological order in the selector 134. Other orders are possible, such as alphabetical order for one of the fields 106 in the group 108, 110, 112. As a user selects the arrows in the group selector 134, the selector icon 136 can proceed through the collection icons 138. A user can go forward or backwards through the collections using the arrows of the selector 134.

Each group can also include date selection element 140 or a calendar icon. The date selection element 140 can be selected by the user to display a calendar showing the dates of when collections of data that are available were created. As an example, a user might remember that they created a relevant collection of data on a specific date. The date selection element 140 can allow the user to jump directly to the desired collection of data based on the date. In contrast, use of the group selector arrows can switch between collections sequentially. The date selection element 140 can provide time and/or date data associated with the collections of data, such as when each collection of data was created. In some embodiments, selecting a date with the date selection element 140 returns only that subset of the collections of data that were created on that date.

FIG. 2 shows a schematic view of document creation system 100 with a collection of data in accordance with various embodiments herein. In various embodiments, the frame 102 can be populated with a first collection of data, such as shown in FIG. 2. A collection of data can refer to a collection of previously entered data that completed, responded to, or filled in the data fields of a frame. A combination of data entries that were previously used to complete the frame can be saved as a collection. As an example, FIG. 2 shows a first collection, or “Col. 1.” Collection 1 includes data entries for the nine fields within the frame. The format of the data within a collection can be maintained, such that each collection can include portions of data that aligns with the prompts the data responds to. The format of the data field entry data can be saved with data that related to the prompt it is associated with or responds to. As an example, the first collection can include a first data field entry that aligns with and is displayed in the first field. The first collection can include a second data field entry that aligns with and is displayed in the second field. The first collection can include data field entries that align with and are displayed in each of the fields.

The prompts can be specific depending on the type of document being created. In some embodiments, different types of documents can have different frames that can include at least some of the same prompts. Frames can also include prompts that can be specific to the type of document being generated. The frame can also include generic prompts that can be universally used between different frames, such as the name of the user creating the document or prompt requesting the title of the document being created.

FIGS. 3-5 show a master grouping option provided in the interface 100. Various embodiments of the system or user interface 100 can include a master grouping selection 132. The master grouping selection 132, upon being selected, can require the system or user interface 100 to display collections in their entirety.

When a user wants to view a different collection, all of the fields of the different collection are displayed. The master grouping selection 132 when activated prevents data from different collections from being presented and/or selected together in a new combination of data. When the master grouping selection 132 is activated, the user is restricted to switching between complete collections and, if desired, selecting a complete collection for creating a document.

As an example, FIG. 3 shows the master grouping selection 132 turned ON or as selected. FIG. 3 shows the frame 102 completed with collection 1, similar to FIG. 2. The group selectors also show the selector icons on the same collection icons representing collection 1. If a user, in response to example of FIG. 3, wishes to display a different collection, he/she can switch to a different collection, such as by using the arrows on the group selector 134. Advancing to a different collection of data can be referred to as declining or a denial of the first collection of data. A user can go back or return to a previously shown collection of data by selecting an arrow in the opposite direction.

Upon advancing the selector icon 136 to the next collection icon 138, the next collection of data can be populated into the fields and presented to the user. FIG. 4 shows the frame populated with a second collection or collection 2 in response to receiving a denial from the user in response to collection 1 shown in FIG. 3. Similarly, FIG. 5 shows the frame populated with a third collection or collection 3 in response to receiving a denial from the user in response to collection 2 shown in FIG. 4.

FIG. 4 shows the selector icon 136 advanced to the second collection icon 138. FIG. 5 shows the selector icon advanced to the third collection icon 138. As the user switches between different collections of data, the selector icon 136 can switch between the collection icons 138 to visually provide the user information about which collection is being shown. In various embodiments, the collections and the collection icons can be ordered chronologically according to the creation dates and times of the collections. In some embodiments, when the master grouping selection 132 is on, only a single group selector 134 is displayed and active, such as that shown with the first group 108. In these embodiments, the selectors for the second group 110 and the third group 112 are not functional, so they can be greyed-out or removed from the interface 100.

FIGS. 6-12 show the system combining groups of data from different collections to complete the frame 102. FIG. 2 can represent a starting point for filling out or completing the frame 102. FIG. 2 shows a first collection or collection 1 completing the frame. In various embodiments, a user may wish to include some data from collection 1 and some data from collection 2 or a different collection. As shown in FIG. 6, in response to the display of FIG. 2, a user has declined the data from collection 1 for the first group 108. The fields 114, 116, 118 of the first group 108 are now populated with the data for the first group 108 from collection 2. When the master group selection 132 is not activated, data in the frame can be presented on a group-by-group basis. The group selector 134 further shows the selector icon 136 advanced to the second collection icon 138 to represent collection 2 being presented and displayed in the first group 108.

The second group 110 and the third group 112 are still populated with the data from collection 1, as the user has not advanced the selector icons for those groups 110, 112 to a different collection for those groups, and the master grouping selection 132 is not activated/selected.

FIG. 7 shows a schematic view of document creation system with a combination of data in accordance with various embodiments herein. In various embodiments, each field can be provided with a field entry element 742. In some embodiments, a user can select the field entry element 742 to lock in or choose the data that is currently being displayed for a field as the data that the user wants to use for the document being created. In various embodiments, each field can include a field entry element 742, such that a user can individually lock in or select a data field.

In various embodiments, each group can be provided with a group entry element 744. In some embodiments, a user can select the group entry element 744 to lock in, confirm, or choose the data that is currently being displayed in the fields for an entire group as the data that the user wants to use for the document that is currently being created. In various embodiments, each group can include a group entry element 744, such that a user can lock in or select the currently displayed data for one of the groups. It is also possible for the group entry element to appear locked or selected upon selecting each of the field entry elements 742 for a given group. Once each of the fields has the data selected for a given group, the group itself can be confirmed, locked in, or selected.

FIG. 7 shows the first group 108 with data from collection 2 confirmed or selected for use in the current document creation process. The remaining groups 110, 112 are still able to be modified and/or changed until the desired data is displayed in the given fields and confirmed by the user.

FIG. 8 is a schematic view of document creation system following FIG. 7 in accordance with various embodiments herein. In FIG. 8, the second group 110 is populated with data from collection 2. It is further shown that the selector icon 136 is on the second collection icon 138.

In some embodiments, the options available to a user can be reduced based on a previous selection or confirmation of data. As an example, confirming the data for the first group 108 in the step shown in FIG. 7 has reduced the available options for the second group in FIG. 8.

As shown in the FIG. 8, the third collection is unavailable for the user as shown by the collection icon 846 being greyed out or otherwise noted as unavailable. In some embodiments, a previous selection of data can create future options irrelevant, improper, or even impossible, as such those options can be removed from consideration for the user. As an example, if the document creation system is being used to prepare a job posting, and a previous data field require the user to select one of the company's locations, the future options can be reduced or restricted to only jobs that are performed at the selected/confirmed location. If the location selected was Washington, but assembly positions are located in Oregon, collections or data relevant to assembly positions can be automatically removed from consideration in response to the selection of Washington as the location.

As the user rejects or denies the data from collection 2 for the second group 110, the data from collection 4 can be presented for the second group 110 as shown in FIG. 9. The data displayed for the second group can go from collection 2 in FIG. 8 to collection 4 in FIG. 9 because of collection 3 being removed from consideration due to a confirmation of at least some of the data in the first group 108.

FIG. 10 shows the data from collection 4 has been confirmed or selected for the second group 110. FIG. 11 shows the user has denied or rejected the data from collection 1 for the third group 112 and now displays the data from collection 2 in the third group 112.

FIG. 12 shows the user has denied or rejected the data from collection 2 for the third group 112 and now displays the data from collection 3 in the third group 112. FIG. 12 further shows the user has confirmed or selected the data from collection 3 for the third group 112.

In various embodiments, a selection or confirmation of one portion of data can result in data from a collection not being available or removed from consideration from a subsequent group or data field, such as was shown in FIG. 8 with collection 3 being removed from consideration for the second group 110 based on a confirmation of at least a portion of the data for the first group 108. In various embodiments, the removal of consideration can be limited to a specific group or field. As shown in FIG. 12, the data of collection 3 was available and displayed in the third group 112 even though collection 3 was not available for the second group 110. The removal of consideration can have a limited scope, such as for a specific group or field.

In addition to being able to select or confirm data on a group-by-group basis, the user interfaces, systems, and method described herein can also provide the ability to select or confirm data individually, such as by confirming a single data field. FIG. 13 shows a schematic view of document creation system with a collection of data in accordance with various embodiments herein.

In various embodiments, the user interface can allow a user to select or confirm data for a single data field 106 (sometimes referred to as “locking” that field). The user interface 100 can provide a field entry element 742. Selecting the field entry element can select or confirm the data that is currently displayed in the data field. FIG. 13 shows a confirmation of the first field 114 of the first group 108.

In various embodiments, the user interface can allow data from a different collection to be displayed in the other data fields within the group after at least one of the fields has had data selected or confirmed for a data field within the group. As an example, FIG. 13 shows confirmation of the data from collection 1 in the first field 114. The confirmation of the data from collection 1 in the first field can occur before the denial of the data for the remaining data fields within the group. The user can deny the data in the second field 116 and the third field 118, such as by advancing the selector icon 136 to an alternate collection icon 138.

Upon receiving a denial of remaining unlocked or unselected data fields 106, the user interface 100 can display data from a different collection within those data fields 106, such as shown in FIG. 14. FIG. 14 shows the data from collection 2 being displayed or presented in the second field 116 and the third field 118.

After displaying an additional collection in fields 116, 118 (collection 2 in FIG. 14), the user can provide confirmation or denial of some or all of the remaining unconfirmed data fields with the group. As an example, FIG. 14 shows collection 2 being presented in the second field 116 and the third field 118. The user denies collection 2 by moving to the next collection using group selector 134. As a result, the interface presents or displays collection 3 in the second field 116 and the third field 118 as shown in FIG. 15. FIG. 15 further shows that the data from collection 3 has been confirmed or selected for the second field 116 and the third field 118. The data fields 114, 116, 118 within the first group 108 have been fulfilled with confirmed data from collection 1 and collection 3 in FIG. 15.

FIG. 16 is a schematic view of document creation system with a combination of data in accordance with various embodiments herein. After the example shown in FIG. 15, the user can eventually provide selections or confirm data for the entire frame 102. FIG. 16 shows a completed frame 102 that includes a combination of data from collection 1, collection 3 and collection 4.

FIG. 17 shows a schematic view of document creation system with a collection of data in accordance with various embodiments herein. In some embodiments, a collection or a portion of a collection can be removed from consideration from the entire frame or from a sub-part of the frame (e.g. removed from consideration for a group). As discussed above, in some embodiments, a collection or a portion of a collection can be removed from consideration based on the confirmation of a previous portion of data. In some embodiments, duplicate data can be removed from consideration, such that data can be removed from consideration without the confirmation of data.

In various embodiments, if two or more collections include the same data for a group, the repetitive data can be removed from consideration (i.e. the repetitive data will not be presented to the user). In the embodiment shown in FIG. 17, collection 2 has been removed from consideration for the first group 108. Similarly, collections 3 and 4 have been removed from consideration for second group 110, such as a result of collection 3 and collection 4 having the same data as collection 1 or collection 2 for the second group 110.

As discussed above, in various embodiments, the interface 100 can include a field entry element 742 for each data field 106. Other options for confirming or selecting data for a data field 106 are also possible. As an example, FIG. 18 shows a schematic view of a sub-part of the document creation system in accordance with various embodiments herein. In the example of FIG. 18, the user can select or click on the data field to confirm the data for that specific data field 106. FIG. 18 shows the first field 114, the second field 116, and the third field 118 as having data confirmed. In some embodiments, the user interface 100 can provide a visual indication that the data has been confirmed for the data field 106. In some embodiments, such as shown in FIG. 18, the data field 106 can be bolded. In other embodiments, the data field 106 can change color, such as being greyed out or highlighted. It will be appreciated that other ways to confirm or deny data are also possible and included in the scope of the disclosure.

FIGS. 19-21 show an example of the user interface for creating a document. The user interfaces, systems, and methods disclosed herein can be used in a wide variety of contexts. As an example, the creation of a job positing is depicted in the example shown in FIGS. 19-23. Other potential implementations for the embodiments disclosed herein include creating legal documents, such as a will or a contract, or creating a summary of an event, such as an article for a newspaper.

The example shown in FIGS. 19-23 relates to the creation of a job description for a job posting. Recruiters, hiring managers, or human resource personnel can create job descriptions for open positions that they are hiring for. In many instances, similar job postings have previously been created. The person creating the new job posting can make user of the previously entered data to create a new job posting in a more efficient manner. The person creating the new job posting does not need to retype or reenter all of the data that he/she (or another user) has previously entered. This can result in great time savings and a more enjoyable experience for the user.

FIG. 19 shows a first collection of data populating the data fields. FIG. 20 shows a second collection of data populating the data fields. FIG. 21 shows a second collection populating the first group and a third collection populating the second group 110 and the third group 112, such as because the user confirmed the data for the second collection for the first group 108.

After confirming data for all of the data fields 106 of the frame 102, the user can be presented with a preview of the finalized document, such as shown in FIG. 22. The user can be provided with the opportunity to provide any additional user inputs in the form of edits, changes, or additions to the document prior to creating or publishing the document. FIG. 23 shows an example of a final created document. After the document is created, the document can be published to the intended audience, such as printed or uploaded onto a website. In various embodiments, the final document or output can include content or data that was not part of the confirmed data in response to the frame prompts, such as additional text to provide context to the confirmed data. In some embodiments, the created document can omit some of the confirmed data, such as data that is related to responses to the created document. In the example shown in FIGS. 22 and 23, the hiring manager's information is not displayed with the job posting. However, responses to the job posting can be forwarded to the manager making confirmation of the manager's information important background data (or metadata) for the created document.

While only two complete collections are shown in FIGS. 19-20, it should be understood that additional complete collections can also be available. In addition to various number of collections, it is also possible for each collection and frame to include various number of portions or groups. While the figures show three groups 108, 110, 112, other numbers of groups are also possible and considered. Similarly, there can be various number of data fields 106 within each group.

As discussed above, in some embodiments, some portions of some collections can be removed from consideration, such as when the confirmation of a portion of the data makes a subsequent portion of data inappropriate, impossible, or otherwise not desirable. Some portions of some collections can be removed from consideration for other reasons too.

In various embodiments, some portions of data for some collections can also be removed from consideration when the portion of data is the same as other data that is in consideration. FIGS. 24-27 show schematics of how data can be removed from consideration in accordance with various embodiments.

FIG. 24 shows a plurality of collections 2446, 2448, 2450, 2452, 2454, 2456, 2458 with data entries for the fields of the first group 108, the second group 110, and the third group 112. FIG. 24 can represent a complete database of collections in consideration for a frame, such as collections of data that have previously been used to complete the frame.

In various embodiments, the system can remove duplicate entries from the complete database or the database of data that is in consideration. As shown in FIG. 25 when compared to FIG. 24, the data available for consideration and for being displayed to the user is reduced. The duplicate data has been removed from the database, such that only distinct entries remain in the database of available options. The determination of duplications is generally done based on all fields 106 in a group 108, 110, 112. The system can then remove any collection that is a duplicate for that group from consideration. As a result, there can be different numbers of available data for each of the groups 108, 110, 112. For example, the first group 108 shows that data from four collections remain. Data from collection 2452 is duplicative of collection 2445 within the first group 108, and is therefore removed. Similarly, data from collections 2456 and 2458 is duplicative of collection 2450. Note that the first two collections for the first group 108 in FIG. 25 both are for the same Job Category “Nurse,” while the second two collections are for the Job Category “Custodian.” This type of repetition is acceptable in many embodiments, which is why duplicates in these embodiments are determined by examining all fields 106 in the group 108. In some embodiments, however, the removal of duplicate data can be performed on a field-by-field basis, such that the removal is not dependent on other fields within the group or within the collection.

In various embodiments, confirmation of a first portion of data, such as a confirmation of data for the first group 108, can reduce the available data for the subsequent groups. In some embodiments, the confirmation of a portion of the data can reduce the available data for all of the subsequent groups to collections that have the same data as the confirmed portion of data. As shown in FIG. 26, the confirmation of “custodian,” “entry custodian,” and “basic janitorial” for the first group 108 reduces the data available for the second group 110 and the third group 112. In FIG. 26, the available options for the second group 110 and the third group 112 are reduced to collections that had the same data for the first group 108. In particular, the available options are selected from collections 2450, 2456, and 2458, which are those collections that contain the confirmed data “custodian,” “entry custodian,” and “basic janitorial” in the first group 108.

In some embodiments, the confirmation of a portion of the data can reduce the available data for less than all of the remaining groups. As show in FIG. 27, the confirmation of “custodian,” “entry custodian,” and “basic janitorial” for the first group 108 reduces the data available for the third group 112 (which relates to job skills), but not for the second group 110 (which relates to the location and hiring manager for the job).

The data shown in FIG. 27 can be presented through an interface 102 similar to that shown in FIGS. 1-21. A user that confirmed the “Custodian,” “Entry Custodian,” and “Basic Janitorial” data in the first group (such as by selecting group entry element 744) would be given five choices for the second group 110 (reflected in five collection icons 138 for that group selector 134) and three choices for the third group 112 (reflected in three collection icons 138 for that group selector 134). In other words, the number of collection icons 138 for each group selector 134 will depend on the result of the duplicate-removal process. Furthermore, the position of the selector icon 136 would directly no longer directly relate to a particular selected collection. The selector icon 136 being on the first collection icon 138 for the second group 110 would result in showing data “Minnesota,” “Joan,” and “100 Main Street” (which originated in collection 2446—the first collection on FIG. 24). In contrast, the selector icon 136 being on the first collection icon 138 for the third group 110 would result in showing data “Clean,” and “Fun” (which originated in collection 2450—the third collection on FIG. 24).

In this context, it is frequently useful to sort (or otherwise reorganize) the non-duplicative data within each group 108, 110, 112 to make selecting data through interface 102 more intuitive. Although this sorting will reorganize the order of the data, the collections within the group remain together even after this sorting. This is because data entered into a particular collection 2446-2458 for a group will frequently have a logical connection to each other. Returning to FIG. 25, the data for the first group 108 might have a primary sort on the Job Category field (with the “Custodian” data being sorted before the “Nurse” data) with a secondary sort on the Job Title field (with “Entry Custodian” being sorted before “Lead Custodian”). This results in the first set of data being “Custodian,” “Entry Custodian,” and “Basic Janitorial”; and the last set of data being “Nurse,” “Lead Nurse,” “Manage Nurses.” The sorting of each group 108, 110, 112 is independent from the other groups. For example, the group 110 might have a primary sort on the Location field 106 and a secondary sort on Hiring Manager field 106. In this way, the number of data entries, and the sorting of those entries, will differ between the groups 108, 110, 112. With this process, the first set of data presented for group one 108 is unlikely to be part of the same collection 2446-2458 as the first set of data for the second group 110 or the third group 112.

FIG. 28 shows a schematic of the data flow for the document creation system in accordance with various embodiments herein.

The system 2800 can include a complete database 2860. The complete database 2860 can include frames that have been used for the system and a plurality of collections or inputs used previously to complete the frames. In various embodiments, the data within the complete database 2860 can be grouped such that the collections are linked to the frame they are used to fulfill. The collections can be grouped with the frames, such that a collection is not presented to a frame in which it was not used to complete.

The complete database 2860 can include all of the potential collections or data. The current database 2862 can be a reduced subset of the data included in the complete database 2860. The current database 2862 can include the collections (or portions of collections) that are in consideration for completing at least part of the frame. In various embodiments, the current database 2862 can include a plurality of collections that are available for completing the frame. In some embodiments, the current database 2862 can include the collections or portions of collections that can be presented to a user for completing a current frame. In some embodiments, the complete database 2860 can be reduced by removing duplicate entries, such as with a scrub distinct command 2864, to establish an initial current database 2862. The determination of distinction can be based on all fields within a group, as described above. The current database 2862 can be further reduced by removing other collections or portions of collections, such as in response to a user confirming a portion of data.

The collections 2868, 2870, 2872, 2874 can be separated, such that each collection 2868, 2870, 2872, 2874 or a portion of each collection 2868, 2870, 2872, 2874 can be individually presented to the user through the user interface as completing a portion of the frame 2866. In some embodiments, grouped portions of the collections are separately sorted. In other embodiments, the association between grouped portions and the original collection are maintained between the groups. The user provides inputs 2876 to confirm or deny displayed data as the desired data entry for each group or field of the frame 2866. In various embodiments, the user input 2876 can include adding new or additional data that was not previously included as an input to a frame. In such an embodiment, the user interface can allow the user to type or otherwise input new data into one or more of the data fields.

Upon completing the frame 2866, such as by entering or confirming data for each of the data fields of the frame, the user can be presented with the option to provide additional input as editing or changing parts of the output, such as discussed in connection with FIG. 22. In various embodiments, the system 2800 can produce an output, such as a prose output containing words and/or sentences based on the frame 2866, collection 2868, 2870, 2872, 2874, and the user inputs 2876. The pose output 2878 can be published 2880, such as printed for signing or uploaded to a website for public viewing.

In various embodiments, the system 2800 can include adding the newly created collection to complete the frame 2866 as a previous input 2882, which can be saved into the complete database 2860 for use in completing a future frame.

FIG. 29 shows a schematic of data flow for the document creation system in accordance with various embodiments herein. In various embodiments, the system 2900 can change how data is presented or flows based on user inputs. As discussed above, a user input 2976, such as confirming a portion of data, can affect future options that will or will not be presented to the user through the user interface. User inputs 2976 can also determine which portions of data will be confirmed and which portions of data will be denied for completing the frame 2966. In various embodiments, user inputs 2976 can also be applied to the created document or prose output 2978, such as by editing the document prior to publishing or creating the document.

The current database 2962 can include collections or portions of collections that are in consideration for completing the frame 2966. The current database 2962 can include collections or portions of collection that can be presented to the user through the user interface. In some embodiments, a user input 2976 can reduce the potential collections or a portion of the potential collections available for completing the frame 2966. As shown in FIG. 29, a plurality of collections 2968, 2970, 2972, 2974 can be used for completing the frame 2966. However, based on a user input 2976, collection 3 2972 can be removed from the current database 2962 or simply not presented to the user as indicated by the discontinuity in the dataflow shown in FIG. 29. Upon completing the frame 2966, the prose output 2978 can be created and published 2980.

FIG. 30 is a schematic of various components in or supporting the document creation system 3000 in accordance with various embodiments herein. The system 3000 can include a user computer system 3060, a system server 3070, and a database 3080. These components 3060, 3070, 3080 can be connected or linked together by network 3050.

The user computer system 3060 is a computing device that includes a processor for processing computer programming instructions. In most cases, the processor is a CPU, such as the CPU devices created by Intel Corporation (Santa Clara, CA), Advanced Micro Devices, Inc. (Santa Clara, CA), or a RISC processer produced according to the designs of Arm Holdings PLC (Cambridge, England). Furthermore, computer system 3060 has memory 3064, which generally takes the form of both temporary, random access memory (RAM) and more permanent storage such a magnetic disk storage, FLASH memory, or another non-transitory (also referred to as permanent) storage medium. The memory and storage (referred to collectively as “memory”) contain both programming instructions and data. In practice, both programming and data can be stored permanently on non-transitory storage devices and transferred into RAM when needed for processing or analysis. In some embodiments, the computer system 3060 may include a graphics processing unit (or GPU) for enhanced processing of visual input and outputs, such as to display the user interface, or an audio processing board, a single chip audio processor, or a digital signal processor (or DSP) that accelerates the processing of audio inputs and outputs.

It should be understood that the receiving, processing, analyzing, and storage of data can take place at the computer system 3060 or at a remote server, such as system server 3070. Discussion of the steps taken with data can be understood to apply to both the computer system 3060 and the server 3070.

The computer system 3060 or the system server 3070 can also tasked with making sure that data is safely stored. The data can be stored locally, or it can be stored remotely. In FIG. 1, the data is stored in database (also referred to as data) 3080. This database 3080 can include defined database entities that may constitute database tables in a relational database. In other embodiments, these entities constitute database objects or any other type of database entity usable with a computerized database. In the present embodiment, the phrase database entity refers to data records in a database whether comprising a row in a database table, an instantiation of a database object, or any other populated database entity. Data within this database 3080 can be “associated” with other data. This association can be implemented in a variety of techniques depending on the technology used to store and manage the database, such as through formal relationships in a relational database or through established relationships between objects in an object-oriented database.

Although this database 3080 is shown as being connected to the user computer system 3060 over network 3050, the data 3082 can be stored locally to the user computer system 3060 or the system server 3070. FIG. 30 shows the database 3080 comprising collection data 3082. Each collection data profile can include frame data, data field entry data, creation data and additional data related to the systems and methods disclosed herein.

The computer system 3060 can be generally responsible for coordinating the various elements of the systems and method disclosed herein. For instance, the computer system 3060 can be configured to display the disclosed user interfaces to a user and to determine which data will be presented and when the data will be presented to the user.

The computing systems 3060, 3070 can each include a processor 3062, 3072, memory and/or storage 3064, 3074, and a network interface 3068, 3078 to allow communications over network 3050. The memory 3064, 3074 is shown in FIG. 30 as containing computer programming 3066, 3076 that controls the processor 3062, 3072.

In FIG. 30, the system server 3070 is represented as a single computing device. Nonetheless, it is expected that some embodiments will implement the system server 3070 over multiple computing devices all operating together through common programming as a single system server 3070.

In some embodiments, the user can refer to the decision maker. The user can be presented with a frame and various collections or portions of collections for completing the frame. The user computer system 3060 can take the form of a mobile device such as a smartphone or tablet computer. If the user computer system 3060 is a standard computer system, it can operate custom application software or browser software 3066 that allows it to communicate over the network 3050 as part of the system 3000. In particular, the programming 3066 can at least allow communication with the system server 3070 over the network 3050.

Note that even though FIG. 30 shows that collection data 3080 is found in the database 3080, there is no need for all the data to be physically or logically stored in a single structure. FIG. 30 merely schematically groups data into a single element for ease in understanding the system. Nonetheless, relationships between certain types of data will drive the systems and methods described below, so it will be necessary to analyze and compare much of the data shown with other data.

FIG. 31 is a schematic of collection data 3082 in accordance with various embodiments herein. The collection data 3082 can include creation data 3184 and frame data 3186. In various embodiments, creation data 3184 can include data that is not part of the prose output. In some embodiments, the creation data can include user data 3188, time data 3190, date data 3192, relevancy data 3194, private data 3196, and any additional data 3198.

User data 3188 can include data regarding which user created the collection and the save data. Time data 3190 can include data regarding the time at which the collection was created. Date data 3192 can include data about when the collection was created. Relevancy data 3194 can include data about what the current collection data is relevant to, such as the subject matter included or for which frame the collection fulfills. Relevancy data 3194 can also include data about which portions of the frame data 3186 should exclude or remove frame data from other collections upon the confirmation of a portion of the collection data. Private data 3196 can include data regarding whether or not the collection data should be provided to other users for access when completing a frame. In some embodiments, the collection data can be restricted to the user that created the data, such as to keep data private. The additional data 3198 can include other types of data that can be saved for each collection.

The frame data 3186 can include data field entry data 3102, 3104, 3106, 3108, 3110, 3112. The data field entry data can include data for responding to a prompt of a frame, such as the data that is displayed to the user through the user interface. The data field entry data can further include relationship data for removing data from consideration upon confirmation of other data for responding to a prompt.

FIG. 32 is a flowchart depicting a method in accordance with various embodiments herein. The method can include presenting a frame to a user 3202. In various embodiments, the method can include presenting a first portion (i.e., first group) of a first collection of data 3204. The method can include receiving a confirmation or a denial of the first portion of the first collection for the first group from the user, with step 3206 being the receipt of a confirmation. The method can include, upon receiving a denial, presenting a first portion of a second collection of data for the first group 3208. The method can include, if a denial of the first portion of the first collection was received, receiving a confirmation of the second collection for the first group from the user 3210. The method can include, after receiving a confirmation of either (1) the first portion of the first collection or (2) the first portion of the second collection, presenting or continuing to present a second portion of the first collection of data 3212. The method can include receiving a confirmation 3214 or a denial 3216 of the second portion of the first collection for the second group from the user. The method can include, upon receiving a denial, presenting a second portion of the second collection of data for the second group 3216. The method can include, if a denial of the second portion of the first collection was received, receiving a confirmation of the second portion of the second collection for the second group from the user 3218. Although FIG. 32 shows receiving a confirmations or denials related to a first portion, the process of confirmations and denials can relate to any of the portions of the frame. The method can include compiling confirmed portions of data into a prose output 3220. The method can include presenting the prose output to the user through a user interface 3222.

The method can further include receiving edits to the prose output from the user, such as edits or additions to the prose output. The method can further include saving confirmed portions of data as a new collection, such as a collection that can be used in a future document creation process. In various embodiments, the method can further include receiving a request to present the first portion of the first collection for the first group after previously receiving a denial of the first portion of the first collection for the first group, such as the user requesting a previously displayed portion of data to be redisplayed.

FIG. 33 is a flowchart depicting a method in accordance with various embodiments herein. The method can include presenting a frame to a user 3302. In various embodiments, the method can include retrieving a first portion (i.e., first group) of a first collection of data from a collection database (i.e., current database) 3304. The collection database can include a plurality of collections of data. Each collection of data can be divided into portions or groups. Each collection of data can include entries that were previously entered in completing a similar frame. In various embodiments, the method can include presenting the first portion of the first collection of data 3306, such as within the frame. In various embodiments, the method can include receiving a confirmation of the first field data entry of the first portion of the first collection for the first field of the first group from the user 3308. In various embodiments, the method can include, in response to receiving confirmation of the first field data entry, recording a non-presentation indicator on a second collection from the collection database 3310. In some embodiments a non-presentation indicator causes the removal of data from the second collection from the collection database for consideration in completing the first group of the frame. In various embodiments, the method can include presenting a second field data entry of a first portion of a third collection of data 3312.

In various embodiments, the method can further include presenting a second portion (i.e., second group) of the first collection. In various embodiments, the method can further include receiving a confirmation or a denial of the second portion of the first collection for the second group from the user. In various embodiments, the method can further include, upon receiving a denial, presenting a second portion of the third collection of data for the second group. In various embodiments, the method can further include, if a denial of the second portion of the first collection was received, receiving a confirmation of the second portion of the third collection for the second group from the user. In various embodiments, the method can further include, compiling confirmed portions of data into a prose output. In various embodiments, the method can further include presenting the prose output to the user through a user interface.

FIG. 34 is a flowchart depicting a method in accordance with various embodiments herein. In various embodiments, a method for presenting an improved user interface can be provided. In various embodiments, the method can include identifying a frame comprising a plurality of data fields 3402. In various embodiments, the first and second data groups each include plurality of fields.

In various embodiments, the method can include receiving data collections for the frame 3404. Each of the data collections can include a first portion that aligns with the first group and a second portion that aligns with the second group. In various embodiments, the method can include identifying a unique set of the first portions 3406, such as by removing duplicate portions or sections of data from consideration. In various embodiments, the method can include identifying a unique set of the second portions 3408, such as by removing duplicate portions or section of data from consideration. In various embodiments, the unique sets relate to different subsets of data collections, such that each unique set can be from a different collection. In some embodiments, the unique set of first portions and the unique set of second portions can be sorted. In various embodiments, the method can include presenting the frame for data input in the user interface 3410. In various embodiments, the user interface can include a first interface element to select from among the unique set of first portions. The user interface can further include an element to receive a confirmation of a unique set of the first portion for using in creating the current document. The user interface can further include a second interface element to select from among the unique set of second portions. The user interface can further include an element to receive a confirmation of a unique set of the second portion for using in creating the current document.

FIG. 35 is a flowchart depicting a method in accordance with various embodiments herein. Various embodiments can provide a method for presenting an improved user interface for data entry based on prior entries. In various embodiments, the method can include identifying a frame comprising a plurality of data fields 3502. In various embodiments, the data fields in the frame are grouped into a first data group and a data second group. The first group can include a first plurality of data fields. The second group can include a second plurality of data fields.

In various embodiments, the method can include receiving a plurality of data collections for the frame 3504. Each data collection can include a first portion of data entries for the first group and a second portion of data entries for the second group.

In various embodiments, the method can include identifying a unique set of the first portions of the data entries 3506. In various embodiments, each first portion relates to a single data collection, such as the first portion has a collection as its original origin. In various embodiments, identical first portions from different data collections are scrubbed from the unique set of the first portions to remove duplicates, such that the unique set of the first portions includes the first portions of a first subset of all the plurality of data collections.

In various embodiments, the method can include identifying a first unique set of the second portions of the data entries 3508. In various embodiments, each second portion relates to a single data collection. In various embodiments, identical second portions from different data collections are scrubbed from the first unique set of the second portions to remove duplicates so that the first unique set of the second portions includes the second portions of a second subset of all the plurality of data collections that is different than the first subset of all the plurality of data collections. The first unique set of first portions and the first unique set of second portions can be separately sorted into different presentation orders.

In various embodiments, the method can include presenting the frame for data input in the improved user interface to a user 3510. The user interface can include the first group of the frame having a first interface element to select from among the unique set of first portions of the data entries in a first presentation order, and the second group of the frame having a second interface element to select from among the first unique set of second portions of the data entries in a second presentation order.

In various embodiments, the selection of a particular value in a particular field in the first group presented in the user interface causes the creation of a second unique set of the second portions, wherein only second portions from data collections having the particular value in the particular field are included in the second unique set of second portions, further wherein the second unique set of second portions are scrubbed to remove duplicates, still further wherein the second interface elements then selects from second unique set of second portions of the data entries.

It should be noted that, as used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the content clearly dictates otherwise. It should also be noted that the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.

It should also be noted that, as used in this specification and the appended claims, the phrase “configured” describes a system, apparatus, or other structure that is constructed or configured to perform a particular task or adopt a particular configuration. The phrase “configured” can be used interchangeably with other similar phrases such as arranged and configured, constructed and arranged, constructed, manufactured and arranged, and the like.

All publications and patent applications in this specification are indicative of the level of ordinary skill in the art to which this invention pertains. All publications and patent applications are herein incorporated by reference to the same extent as if each individual publication or patent application was specifically and individually indicated by reference.

As used herein, the recitation of numerical ranges by endpoints shall include all numbers subsumed within that range (e.g., 2 to 8 includes 2.1, 2.8, 5.3, 7, etc.).

The headings used herein are provided for consistency with suggestions under 37 CFR 1.77 or otherwise to provide organizational cues. These headings shall not be viewed to limit or characterize the invention(s) set out in any claims that may issue from this disclosure. As an example, although the headings refer to a “Field,” such claims should not be limited by the language chosen under this heading to describe the so-called technical field. Further, a description of a technology in the “Background” is not an admission that technology is prior art to any invention(s) in this disclosure. Neither is the “Summary” to be considered as a characterization of the invention(s) set forth in issued claims.

The embodiments described herein are not intended to be exhaustive or to limit the invention to the precise forms disclosed in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art can appreciate and understand the principles and practices. As such, aspects have been described with reference to various specific and preferred embodiments and techniques. However, it should be understood that many variations and modifications may be made while remaining within the spirit and scope herein.

Claims

1. A method for document creation based on previous document creations, comprising: (a) presenting a frame to a user, i. wherein the frame comprises a first field, a second field, a third field, and a fourth field,ii. wherein a first group comprises the first field and the second field,iii. wherein a second group comprises the third field and the fourth field;(b) presenting a first portion of a first collection of data, i. wherein the first collection of data comprises data that was previously entered into the fields of the frame,ii. wherein the first portion of the first collection of data aligns with the first group and the first portion comprises a first field data entry displayed in the first field and a second field data entry displayed in the second field;(c) receiving a denial of the first portion of the first collection for the first group from the user;(d) upon receiving a denial, presenting a first portion of a second collection of data for the first group, i. wherein the second collection of data comprises data that was previously entered into the fields of the frame,ii. wherein the first portion of the second collection of data aligns with the first group and the first portion comprises a first field data entry displayed in the first field and a second field data entry displayed in the second field;(e) after receiving a denial of the first portion of the first collection, receiving a confirmation of the second collection for the first group from the user;(f) after receiving the confirmation of the second collection for the first group, presenting a second portion of the first collection of data, i. wherein the second portion of the first collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(g) receiving a confirmation of the second portion of the first collection for the second group from the user;(h) compiling the confirmed portions of data into a prose output; and(i) presenting the prose output to the user through a user interface.
2. The method of claim 1, further comprising: receiving edits to the prose output from the user.
3. The method of claim 1, further comprising: saving confirmed portions of data as a third collection.
4. The method of claim 1, further comprising: receiving a request to present the first portion of the first collection for the first group after previously receiving a denial of the first portion of the first collection for the first group.
5. The method of claim 4, further comprising presenting the first portion of the first collection after receiving the request to present the first portion of the first collection for the first group.
6. The method of claim 1, wherein the data for the first collection was previously entered at a different time than the data for the second collection.
7. The method of claim 1, wherein receiving a denial of the first portion of the first collection for the first group from the user comprises receiving a confirmation of the first field of the first portion of the first collection and a denial of the second field of the first portion of the first collection.
8. The method of claim 7, further comprising: presenting the second field data entry of the first portion of the second collection in the second field.
9. The method of claim 8, further comprising: receiving a confirmation of the second field of the first portion of the second collection.
10. The method of claim 1, wherein presenting a first portion of a first collection of data comprises presenting time data associated with the first collection of data, wherein the time data is associated with when the first collection of data was created.
11. The method of claim 1, further comprising: upon receiving a confirmation of the first portion of the second collection of data, removing a second portion of a third collection of data from consideration.
12. The method of claim 1, further comprising recording a non-presentation indicator on a third collection in response to receiving the confirmation of the first portion of the second collection for the first group.
13. A method for data entry, comprising: (a) presenting a frame to a user, i. wherein the frame comprises a first field, a second field, a third field, and a fourth field,ii. wherein a first group of fields comprises the first field and the second field,iii. wherein a second group of fields comprises the third field and the fourth field;(b) retrieving a first portion of a first collection of data from a collection database, wherein the collection database comprises a plurality of collections of data, each collection of data is divided into portions, each collection of data comprises entries that were previously entered in completing the frame;(c) presenting the first portion of the first collection of data, i. wherein the first portion of the first collection of data aligns with the first group and the first portion comprises a first field data entry displayed in the first field and a second field data entry displayed in the second field;(d) receiving a confirmation of the first field data entry of the first portion of the first collection for the first field of the first group from the user;(e) in response to receiving confirmation of the first field data entry, recording a non-presentation indicator on a second collection from the collection database that inhibits the presentation of any of a first portion of the second collection of data; and(f) presenting a second field data entry of a first portion of a third collection of data.
14. The method of claim 13, further comprising: (g) presenting a second portion of the first collection, i. wherein the second portion of the first collection of data aligns with the second group and the second portion comprises a third field data entry display in the third field and a fourth field data entry display in the fourth field;(h) receiving a confirmation or a denial of the second portion of the first collection for the second group from the user;(i) upon receiving a denial, presenting a second portion of the third collection of data, i. wherein the second portion from the third collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(j) after receiving a denial of the second portion of the first collection, receiving a confirmation of the second portion of the third collection for the second group from the user;(k) compiling confirmed portions of data into a prose output; and(l) presenting the prose output to the user through a user interface.
15. The method of claim 13, further comprising: (g) presenting a second portion of the first collection, i. wherein the second portion of the first collection of data aligns with the second group and the second portion comprises a third field data entry display in the third field and a fourth field data entry display in the fourth field;(h) receiving a confirmation or a denial of the second portion of the first collection for the second group from the user;(i) upon receiving a denial, presenting a second portion of the second collection of data, a. wherein the second portion from the second collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(j) after receiving a denial of the second portion of the first collection, receiving a confirmation of the second portion of the second collection for the second group from the user;(k) compiling confirmed portions of data into a prose output; and(l) presenting the prose output to the user through a user interface.
16. A method for document creation based on previous document creations, comprising: (a) presenting a frame to a user, i. wherein the frame comprises a first field, a second field, a third field, and a fourth field,ii. wherein a first group comprises the first field and the second field,iii. wherein a second group comprises the third field and the fourth field;(b) presenting a first portion of a first collection of data, i. wherein the first collection of data comprises data that was previously entered into the fields of the frame,ii. wherein the first portion of the first collection of data aligns with the first group and the first portion comprises a first field data entry displayed in the first field and a second field data entry displayed in the second field;(c) receiving a denial of the first portion of the first collection for the first group from the user;(d) upon receiving a denial, presenting a first portion of a second collection of data for the first group, i. wherein the second collection of data comprises data that was previously entered into the fields of the frame,ii. wherein the first portion of the second collection of data aligns with the first group and the first portion comprises a first field data entry displayed in the first field and a second field data entry displayed in the second field;(e) after receiving a denial of the first portion of the first collection, receiving a confirmation of the second collection for the first group from the user;(f) after receiving the confirmation of the second collection, presenting a second portion of the first collection of data, i. wherein the second portion of the first collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(g) receiving a denial of the second portion of the first collection for the second group from the user;(h) upon receiving the denial of the second portion of the first collection, presenting a second portion of the second collection of data for the second group, i. wherein the second portion from the second collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(i) receiving a denial of the second portion of the second collection for the second group from the user;(j) upon receiving the denial of the second portion of the second collection, presenting a third portion of a third collection of data; i. wherein the third collection of data comprises data that was previously entered into the fields of the frame,ii. wherein the second portion of the third collection of data aligns with the second group and the second portion comprises a third field data entry displayed in the third field and a fourth field data entry displayed in the fourth field;(k) receiving a confirmation of the second portion of the third collection for the second group from the user.
17. The method of claim 16, further comprising: receiving edits to the prose output from the user.
18. The method of claim 16, further comprising: saving confirmed portions of data as a fourth collection.
19. The method of claim 16, further comprising: receiving a request to present the first portion of the first collection for the first group after previously receiving a denial of the first portion of the first collection for the first group.
20. The method of claim 19, further comprising presenting the first portion of the first collection after receiving the request to present the first portion of the first collection for the first group.

US Referenced Citations (519)

Number	Name	Date	Kind
1173785	Deagan	Feb 1916	A
1686351	Spitzglass	Oct 1928	A
3152622	Rothermel	Oct 1964	A
3764135	Madison	Oct 1973	A
5109281	Kobori et al.	Apr 1992	A
5410344	Graves et al.	Apr 1995	A
5495565	Millard	Feb 1996	A
5544360	Lewak et al.	Aug 1996	A
5675788	Husick et al.	Oct 1997	A
5732221	Feldon	Mar 1998	A
5835667	Wactlar et al.	Nov 1998	A
5867209	Irie et al.	Feb 1999	A
5884004	Sato et al.	Mar 1999	A
5886967	Aramaki	Mar 1999	A
5897220	Huang et al.	Apr 1999	A
5906372	Recard	May 1999	A
5937138	Fukuda et al.	Aug 1999	A
5949792	Yasuda et al.	Sep 1999	A
6128414	Liu	Oct 2000	A
6229904	Huang et al.	May 2001	B1
6289165	Abecassis	Sep 2001	B1
6484266	Kashiwagi et al.	Nov 2002	B2
6502199	Kashiwagi et al.	Dec 2002	B2
6504990	Abecassis	Jan 2003	B1
RE37994	Fukuda et al.	Feb 2003	E
6598059	Vasudevan	Jul 2003	B1
6600874	Fujita et al.	Jul 2003	B1
6618723	Smith	Sep 2003	B1
6651217	Kennedy	Nov 2003	B1
6928623	Sibert	Aug 2005	B1
6981000	Park et al.	Dec 2005	B2
7095329	Saubolle	Aug 2006	B2
7146627	Ismail et al.	Dec 2006	B1
7216292	Snapper	May 2007	B1
7293275	Krieger et al.	Nov 2007	B1
7313539	Pappas et al.	Dec 2007	B1
7336890	Lu et al.	Feb 2008	B2
7343551	Bourdev	Mar 2008	B1
7499918	Ogikubo	Mar 2009	B2
7606444	Erol et al.	Oct 2009	B1
7650286	Obeid	Jan 2010	B1
7702542	Aslanian	Apr 2010	B2
7725812	Balkus et al.	May 2010	B1
7797402	Roos	Sep 2010	B2
7810117	Karnalkar et al.	Oct 2010	B2
7865424	Pappas et al.	Jan 2011	B2
7895620	Haberman et al.	Feb 2011	B2
7904490	Ogikubo	Mar 2011	B2
7908287	Katragadda	Mar 2011	B1
7962375	Pappas et al.	Jun 2011	B2
7974443	Kipman et al.	Jul 2011	B2
7991635	Hartmann	Aug 2011	B2
7996292	Pappas et al.	Aug 2011	B2
8032447	Pappas et al.	Oct 2011	B2
8046814	Badenell	Oct 2011	B1
8069411	Titemore et al.	Nov 2011	B2
8099415	Luo et al.	Jan 2012	B2
8111326	Talwar	Feb 2012	B1
8112365	Foster	Feb 2012	B2
8169548	Ryckman	May 2012	B2
8185543	Choudhry et al.	May 2012	B1
8225204	Cheng	Jul 2012	B2
8229841	Pappas et al.	Jul 2012	B2
8238718	Toyama et al.	Aug 2012	B2
8241628	Diefenbach-Streiber et al.	Aug 2012	B2
8266068	Foss et al.	Sep 2012	B1
8290958	Boone et al.	Oct 2012	B2
8300785	White	Oct 2012	B2
8301550	Pappas et al.	Oct 2012	B2
8301790	Morrison et al.	Oct 2012	B2
8326133	Lemmers	Dec 2012	B2
8326853	Richard et al.	Dec 2012	B2
8331457	Mizuno et al.	Dec 2012	B2
8331760	Butcher	Dec 2012	B2
8339500	Hattori et al.	Dec 2012	B2
8352850	Creed	Jan 2013	B1
8358346	Hikita et al.	Jan 2013	B2
8387094	Ho et al.	Feb 2013	B1
8505054	Kirley	Aug 2013	B1
8508572	Ryckman et al.	Aug 2013	B2
8543450	Pappas et al.	Sep 2013	B2
8560482	Miranda et al.	Oct 2013	B2
8566698	Zubizarreta	Oct 2013	B1
8566880	Dunker et al.	Oct 2013	B2
8600211	Nagano et al.	Dec 2013	B2
8611422	Yagnik et al.	Dec 2013	B1
8620771	Pappas et al.	Dec 2013	B2
8633964	Zhu	Jan 2014	B1
8650114	Pappas et al.	Feb 2014	B2
8751231	Larsen et al.	Jun 2014	B1
8774604	Torii et al.	Jul 2014	B2
8792780	Hattori	Jul 2014	B2
8824863	Kitamura et al.	Sep 2014	B2
8854457	De Vleeschouwer et al.	Oct 2014	B2
8856000	Larsen et al.	Oct 2014	B1
8902282	Zhu	Dec 2014	B1
8909542	Montero et al.	Dec 2014	B2
8913103	Sargin et al.	Dec 2014	B1
8918532	Lueth et al.	Dec 2014	B2
8930260	Pappas et al.	Jan 2015	B2
8988528	Hikita	Mar 2015	B2
9009045	Larsen et al.	Apr 2015	B1
9015746	Holmdahl et al.	Apr 2015	B2
9026471	Pappas et al.	May 2015	B2
9026472	Pappas et al.	May 2015	B2
9047634	Pappas et al.	Jun 2015	B2
9064258	Pappas et al.	Jun 2015	B2
9070150	Pappas et al.	Jun 2015	B2
9092813	Pappas et al.	Jul 2015	B2
9106804	Roberts et al.	Aug 2015	B2
9111579	Meaney et al.	Aug 2015	B2
9117201	Kennell et al.	Aug 2015	B2
9129640	Hamer	Sep 2015	B2
9135674	Yagnik et al.	Sep 2015	B1
9223781	Pearson et al.	Dec 2015	B2
9224156	Moorer	Dec 2015	B2
9305286	Larsen et al.	Apr 2016	B2
9305287	Krishnamoorthy et al.	Apr 2016	B2
9355151	Cranfill et al.	May 2016	B1
9378486	Taylor et al.	Jun 2016	B2
9398315	Oks et al.	Jul 2016	B2
9402050	Recchia et al.	Jul 2016	B1
9437247	Pendergast et al.	Sep 2016	B2
9438934	Zhu	Sep 2016	B1
9443556	Cordell et al.	Sep 2016	B2
9456174	Boyle et al.	Sep 2016	B2
9462301	Paśko	Oct 2016	B2
9501663	Hopkins et al.	Nov 2016	B1
9501944	Boneta et al.	Nov 2016	B2
9542452	Ross et al.	Jan 2017	B1
9544380	Deng et al.	Jan 2017	B2
9554160	Han et al.	Jan 2017	B2
9570107	Boiman et al.	Feb 2017	B2
9583144	Ricciardi	Feb 2017	B2
9600723	Pantofaru et al.	Mar 2017	B1
9607655	Bloch et al.	Mar 2017	B2
9652745	Taylor et al.	May 2017	B2
9653115	Bloch et al.	May 2017	B2
9666194	Ondeck et al.	May 2017	B2
9684435	Carr et al.	Jun 2017	B2
9693019	Fluhr et al.	Jun 2017	B1
9696904	Mohapatra	Jul 2017	B1
9710790	Taylor et al.	Jul 2017	B2
9723223	Banta et al.	Aug 2017	B1
9747573	Shaburov et al.	Aug 2017	B2
9792955	Fleischhauer et al.	Oct 2017	B2
9805767	Strickland	Oct 2017	B1
9823809	Roos	Nov 2017	B2
9876963	Nakamura et al.	Jan 2018	B2
9881647	McCauley et al.	Jan 2018	B2
9883144	Marlow et al.	Jan 2018	B2
9928230	Jain	Mar 2018	B1
9936185	Delvaux et al.	Apr 2018	B2
9940508	Kaps et al.	Apr 2018	B2
9940973	Roberts et al.	Apr 2018	B2
9979921	Holmes	May 2018	B2
10008239	Eris	Jun 2018	B2
10019136	Ozog	Jul 2018	B1
10019653	Wilf et al.	Jul 2018	B2
10021377	Newton et al.	Jul 2018	B2
10108932	Sung et al.	Oct 2018	B2
10115038	Hazur et al.	Oct 2018	B2
10147460	Ullrich	Dec 2018	B2
10152695	Chiu et al.	Dec 2018	B1
10152696	Thankappan et al.	Dec 2018	B2
10168866	Wakeen et al.	Jan 2019	B2
10178427	Huang	Jan 2019	B2
10235008	Lee et al.	Mar 2019	B2
10242345	Taylor et al.	Mar 2019	B2
10268736	Balasia et al.	Apr 2019	B1
10296873	Balasia et al.	May 2019	B1
10310361	Featherstone	Jun 2019	B1
10318927	Champaneria	Jun 2019	B2
10325243	Ross et al.	Jun 2019	B1
10325517	Nielson et al.	Jun 2019	B2
10331764	Rao et al.	Jun 2019	B2
10346805	Taylor et al.	Jul 2019	B2
10346928	Li et al.	Jul 2019	B2
10353720	Wich-Vila	Jul 2019	B1
10433030	Packard et al.	Oct 2019	B2
10438135	Larsen et al.	Oct 2019	B2
10445417	Dhanawat	Oct 2019	B2
10489439	Calapodescu et al.	Nov 2019	B2
10607188	Kyllonen et al.	Mar 2020	B2
10657498	Dey et al.	May 2020	B2
10664803	Obeid	May 2020	B2
10694097	Shirakyan	Jun 2020	B1
10728443	Olshansky	Jul 2020	B1
10735396	Krstic et al.	Aug 2020	B2
10740349	Kohlmeier et al.	Aug 2020	B2
10748118	Fang	Aug 2020	B2
10796217	Wu	Oct 2020	B2
10963841	Olshansky	Mar 2021	B2
10997560	Chen et al.	May 2021	B2
11017335	Ponce De Leon	May 2021	B1
11023735	Olshansky	Jun 2021	B1
11055667	Pande	Jul 2021	B2
11107040	Sawarkar et al.	Aug 2021	B2
11115486	Jimenez Salgado et al.	Sep 2021	B2
11127232	Olshansky	Sep 2021	B2
11144882	Olshansky	Oct 2021	B1
11184578	Olshansky	Nov 2021	B2
11423071	Olshansky	Aug 2022	B1
20010001160	Shoff et al.	May 2001	A1
20010038746	Hughes et al.	Nov 2001	A1
20020040866	Tuneld	Apr 2002	A1
20020097984	Abecassis	Jul 2002	A1
20020103826	Kriho et al.	Aug 2002	A1
20020113879	Battle et al.	Aug 2002	A1
20020122659	McGrath et al.	Sep 2002	A1
20020191071	Rui et al.	Dec 2002	A1
20030005429	Colsey	Jan 2003	A1
20030027611	Recard	Feb 2003	A1
20030028792	Plow	Feb 2003	A1
20030189589	LeBlanc et al.	Oct 2003	A1
20030194211	Abecassis	Oct 2003	A1
20030233345	Perisic et al.	Dec 2003	A1
20040033061	Hughes et al.	Feb 2004	A1
20040122809	Clark	Jun 2004	A1
20040186743	Cordero	Sep 2004	A1
20040243551	Boone et al.	Dec 2004	A1
20040264919	Taylor et al.	Dec 2004	A1
20050060175	Farber et al.	Mar 2005	A1
20050095569	Franklin	May 2005	A1
20050137896	Pentecost et al.	Jun 2005	A1
20050187765	Kim et al.	Aug 2005	A1
20050198563	Kristjansson	Sep 2005	A1
20050232462	Vallone et al.	Oct 2005	A1
20050235033	Doherty	Oct 2005	A1
20050257148	Goodman	Nov 2005	A1
20050271251	Russell et al.	Dec 2005	A1
20060042483	Work et al.	Mar 2006	A1
20060045179	Mizuno et al.	Mar 2006	A1
20060059434	Boss	Mar 2006	A1
20060075337	Jones et al.	Apr 2006	A1
20060097987	Hughes	May 2006	A1
20060100919	Levine	May 2006	A1
20060107197	Friend	May 2006	A1
20060116555	Pavlidis et al.	Jun 2006	A1
20060229896	Rosen et al.	Oct 2006	A1
20070088601	Money et al.	Apr 2007	A1
20070094199	Deshpande	Apr 2007	A1
20070124161	Mueller et al.	May 2007	A1
20070237502	Ryckman et al.	Oct 2007	A1
20070245308	Hill	Oct 2007	A1
20070276858	Cushman, II	Nov 2007	A1
20070288245	Benjamin	Dec 2007	A1
20080086504	Sanders et al.	Apr 2008	A1
20080115193	Prax	May 2008	A1
20090083103	Basser	Mar 2009	A1
20090083670	Roos	Mar 2009	A1
20090087161	Roberts et al.	Apr 2009	A1
20090094179	Jager	Apr 2009	A1
20090144785	Walker et al.	Jun 2009	A1
20090171899	Chittoor et al.	Jul 2009	A1
20090192884	Lo	Jul 2009	A1
20090204881	Murthy	Aug 2009	A1
20090248685	Pasqualoni et al.	Oct 2009	A1
20090258334	Pyne	Oct 2009	A1
20100086283	Ramachandran et al.	Apr 2010	A1
20100143329	Larsen	Jun 2010	A1
20100183280	Beauregard et al.	Jul 2010	A1
20100191561	Jeng et al.	Jul 2010	A1
20100199228	Latta et al.	Aug 2010	A1
20100217757	Fujioka	Aug 2010	A1
20100223109	Hawn et al.	Sep 2010	A1
20100306645	Roulland	Dec 2010	A1
20100325307	Roos	Dec 2010	A1
20110055098	Stewart	Mar 2011	A1
20110055930	Flake et al.	Mar 2011	A1
20110060671	Erbey et al.	Mar 2011	A1
20110076656	Scott et al.	Mar 2011	A1
20110088081	Folkesson et al.	Apr 2011	A1
20110119230	Zuber	May 2011	A1
20110119264	Hu et al.	May 2011	A1
20110135279	Leonard	Jun 2011	A1
20110271173	Ait-Mokhtar	Nov 2011	A1
20120036127	Work et al.	Feb 2012	A1
20120053996	Galbavy	Mar 2012	A1
20120084096	Wang	Apr 2012	A1
20120084649	Dowdell et al.	Apr 2012	A1
20120114246	Weitzman	May 2012	A1
20120130771	Kannan et al.	May 2012	A1
20120257875	Sharpe et al.	Oct 2012	A1
20120271774	Clegg	Oct 2012	A1
20130007670	Roos	Jan 2013	A1
20130016815	Odinak et al.	Jan 2013	A1
20130016816	Odinak et al.	Jan 2013	A1
20130016823	Odinak et al.	Jan 2013	A1
20130024105	Thomas	Jan 2013	A1
20130111401	Newman et al.	May 2013	A1
20130117383	Hymel	May 2013	A1
20130121668	Meaney et al.	May 2013	A1
20130124998	Pendergast et al.	May 2013	A1
20130124999	Agnoli et al.	May 2013	A1
20130125000	Fleischhauer et al.	May 2013	A1
20130177296	Geisner et al.	Jul 2013	A1
20130212033	Work et al.	Aug 2013	A1
20130212180	Work et al.	Aug 2013	A1
20130216206	Dubin et al.	Aug 2013	A1
20130216982	Bennett	Aug 2013	A1
20130218688	Roos	Aug 2013	A1
20130222601	Engstroem et al.	Aug 2013	A1
20130226578	Bolton et al.	Aug 2013	A1
20130226674	Field et al.	Aug 2013	A1
20130226910	Work et al.	Aug 2013	A1
20130254192	Work et al.	Sep 2013	A1
20130259447	Sathish et al.	Oct 2013	A1
20130262241	Nelson	Oct 2013	A1
20130266925	Nunamaker et al.	Oct 2013	A1
20130268452	MacEwen et al.	Oct 2013	A1
20130283378	Costigan et al.	Oct 2013	A1
20130290210	Cline et al.	Oct 2013	A1
20130290325	Work et al.	Oct 2013	A1
20130290420	Work et al.	Oct 2013	A1
20130290448	Work et al.	Oct 2013	A1
20130297589	Work et al.	Nov 2013	A1
20130332381	Clark et al.	Dec 2013	A1
20130332382	LaPasta et al.	Dec 2013	A1
20140012586	Rubin et al.	Jan 2014	A1
20140032594	Bayliss	Jan 2014	A1
20140036023	Croen et al.	Feb 2014	A1
20140089217	McGovern et al.	Mar 2014	A1
20140092254	Mughal et al.	Apr 2014	A1
20140123177	Kim et al.	May 2014	A1
20140125703	Roveta et al.	May 2014	A1
20140143165	Posse et al.	May 2014	A1
20140153902	Pearson et al.	Jun 2014	A1
20140157390	Lurey	Jun 2014	A1
20140173407	Kruglick	Jun 2014	A1
20140186004	Hamer	Jul 2014	A1
20140191939	Penn et al.	Jul 2014	A1
20140192200	Zagron	Jul 2014	A1
20140198196	Howard et al.	Jul 2014	A1
20140214709	Greaney	Jul 2014	A1
20140236615	Ragusky	Aug 2014	A1
20140245146	Roos	Aug 2014	A1
20140258288	Work et al.	Sep 2014	A1
20140258828	Lymer	Sep 2014	A1
20140270706	Pasko	Sep 2014	A1
20140278506	Rogers et al.	Sep 2014	A1
20140278683	Kennell et al.	Sep 2014	A1
20140279634	Seeker	Sep 2014	A1
20140282709	Hardy et al.	Sep 2014	A1
20140317009	Bilodeau et al.	Oct 2014	A1
20140317126	Work et al.	Oct 2014	A1
20140325359	Vehovsky et al.	Oct 2014	A1
20140325373	Kramer et al.	Oct 2014	A1
20140327779	Eronen et al.	Nov 2014	A1
20140330734	Sung et al.	Nov 2014	A1
20140330773	Brillhart et al.	Nov 2014	A1
20140336942	Pe'er et al.	Nov 2014	A1
20140337900	Hurley	Nov 2014	A1
20140356822	Hoque et al.	Dec 2014	A1
20140358810	Hardtke et al.	Dec 2014	A1
20140359439	Lyren	Dec 2014	A1
20140372857	Otero	Dec 2014	A1
20150003603	Odinak et al.	Jan 2015	A1
20150003605	Odinak et al.	Jan 2015	A1
20150006422	Carter et al.	Jan 2015	A1
20150012453	Odinak et al.	Jan 2015	A1
20150039989	Dhanawat	Feb 2015	A1
20150046357	Danson et al.	Feb 2015	A1
20150063775	Nakamura et al.	Mar 2015	A1
20150066535	Dobrean	Mar 2015	A1
20150067723	Bloch et al.	Mar 2015	A1
20150099255	Aslan et al.	Apr 2015	A1
20150100702	Krishna et al.	Apr 2015	A1
20150127565	Chevalier et al.	May 2015	A1
20150139601	Mate et al.	May 2015	A1
20150154564	Moon et al.	Jun 2015	A1
20150155001	Kikugawa et al.	Jun 2015	A1
20150170303	Geritz et al.	Jun 2015	A1
20150201134	Carr et al.	Jul 2015	A1
20150205800	Work et al.	Jul 2015	A1
20150205872	Work et al.	Jul 2015	A1
20150206102	Cama et al.	Jul 2015	A1
20150222815	Wang et al.	Aug 2015	A1
20150228306	Roberts et al.	Aug 2015	A1
20150242707	Wilf et al.	Aug 2015	A1
20150269165	Work et al.	Sep 2015	A1
20150269529	Kyllonen et al.	Sep 2015	A1
20150269530	Work et al.	Sep 2015	A1
20150271289	Work et al.	Sep 2015	A1
20150278223	Work et al.	Oct 2015	A1
20150278290	Work et al.	Oct 2015	A1
20150278964	Work et al.	Oct 2015	A1
20150286988	Ogrinz	Oct 2015	A1
20150324698	Karaoguz et al.	Nov 2015	A1
20150339939	Gustafson et al.	Nov 2015	A1
20150356512	Bradley	Dec 2015	A1
20150380052	Hamer	Dec 2015	A1
20160005029	Ivey et al.	Jan 2016	A1
20160036976	Odinak et al.	Feb 2016	A1
20160062972	Ramakrishnan	Mar 2016	A1
20160104096	Ovick et al.	Apr 2016	A1
20160116827	Tarres Bolos	Apr 2016	A1
20160117942	Marino et al.	Apr 2016	A1
20160139562	Crowder et al.	May 2016	A1
20160154883	Boerner	Jun 2016	A1
20160155475	Hamer	Jun 2016	A1
20160180234	Siebach et al.	Jun 2016	A1
20160180883	Hamer	Jun 2016	A1
20160219264	Delvaux et al.	Jul 2016	A1
20160225409	Eris	Aug 2016	A1
20160225410	Lee et al.	Aug 2016	A1
20160247537	Ricciardi	Aug 2016	A1
20160267436	Silber et al.	Sep 2016	A1
20160313892	Roos	Oct 2016	A1
20160323608	Bloch et al.	Nov 2016	A1
20160330398	Recchia et al.	Nov 2016	A1
20160364692	Bhaskaran et al.	Dec 2016	A1
20170024614	Sanil et al.	Jan 2017	A1
20170026667	Pasko	Jan 2017	A1
20170039525	Seidle et al.	Feb 2017	A1
20170068404	Jobs	Mar 2017	A1
20170076751	Hamer	Mar 2017	A9
20170134776	Ranjeet et al.	May 2017	A1
20170148488	Li et al.	May 2017	A1
20170164013	Abramov et al.	Jun 2017	A1
20170164014	Abramov et al.	Jun 2017	A1
20170164015	Abramov et al.	Jun 2017	A1
20170171602	Qu	Jun 2017	A1
20170178688	Ricciardi	Jun 2017	A1
20170195491	Odinak et al.	Jul 2017	A1
20170206504	Taylor et al.	Jul 2017	A1
20170213190	Hazan	Jul 2017	A1
20170213573	Takeshita et al.	Jul 2017	A1
20170227353	Brunner	Aug 2017	A1
20170236073	Borisyuk et al.	Aug 2017	A1
20170244894	Aggarwal et al.	Aug 2017	A1
20170244984	Aggarwal et al.	Aug 2017	A1
20170244991	Aggarwal et al.	Aug 2017	A1
20170262706	Sun et al.	Sep 2017	A1
20170264958	Hutten	Sep 2017	A1
20170293413	Matsushita et al.	Oct 2017	A1
20170316806	Warren et al.	Nov 2017	A1
20170332044	Marlow et al.	Nov 2017	A1
20170353769	Husain et al.	Dec 2017	A1
20170357627	Peterson	Dec 2017	A1
20170372748	McCauley et al.	Dec 2017	A1
20180011621	Roos	Jan 2018	A1
20180025303	Janz	Jan 2018	A1
20180054641	Hall et al.	Feb 2018	A1
20180070045	Holmes	Mar 2018	A1
20180074681	Roos	Mar 2018	A1
20180082238	Shani	Mar 2018	A1
20180082680	Pereg et al.	Mar 2018	A1
20180096307	Fortier et al.	Apr 2018	A1
20180109737	Nakamura et al.	Apr 2018	A1
20180109826	McCoy et al.	Apr 2018	A1
20180110460	Danson et al.	Apr 2018	A1
20180114154	Bae	Apr 2018	A1
20180130497	McCauley et al.	May 2018	A1
20180132014	Khazanov et al.	May 2018	A1
20180150604	Arena et al.	May 2018	A1
20180158027	Venigalla	Jun 2018	A1
20180182436	Ullrich	Jun 2018	A1
20180191955	Aoki et al.	Jul 2018	A1
20180211258	Buis	Jul 2018	A1
20180218238	Viirre et al.	Aug 2018	A1
20180226102	Roberts et al.	Aug 2018	A1
20180227501	King	Aug 2018	A1
20180232751	Terhark et al.	Aug 2018	A1
20180247271	Van Hoang et al.	Aug 2018	A1
20180253697	Sung et al.	Sep 2018	A1
20180260085	Whitelaw	Sep 2018	A1
20180260086	Leme	Sep 2018	A1
20180268868	Salokannel et al.	Sep 2018	A1
20180270613	Park	Sep 2018	A1
20180302680	Cormican	Oct 2018	A1
20180308521	Iwamoto	Oct 2018	A1
20180316947	Todd	Nov 2018	A1
20180336528	Carpenter et al.	Nov 2018	A1
20180336930	Takahashi	Nov 2018	A1
20180350405	Marco et al.	Dec 2018	A1
20180353769	Smith et al.	Dec 2018	A1
20180374251	Mitchell et al.	Dec 2018	A1
20180376225	Jones et al.	Dec 2018	A1
20190005373	Nims et al.	Jan 2019	A1
20190019157	Saha et al.	Jan 2019	A1
20190057356	Larsen et al.	Feb 2019	A1
20190087455	He et al.	Mar 2019	A1
20190087558	Mercury et al.	Mar 2019	A1
20190096307	Liang et al.	Mar 2019	A1
20190141033	Kaafar et al.	May 2019	A1
20190155894	Gandhi	May 2019	A1
20190156292	Wehrle	May 2019	A1
20190197102	Lerner	Jun 2019	A1
20190213242	Pathak	Jul 2019	A1
20190220824	Liu	Jul 2019	A1
20190244176	Chuang et al.	Aug 2019	A1
20190259002	Balasia et al.	Aug 2019	A1
20190295040	Clines	Sep 2019	A1
20190311488	Sareen	Oct 2019	A1
20190325064	Mathiesen et al.	Oct 2019	A1
20200012350	Tay	Jan 2020	A1
20200073924	Sokol	Mar 2020	A1
20200110786	Kim	Apr 2020	A1
20200126545	Kakkar et al.	Apr 2020	A1
20200143329	Gamaliel	May 2020	A1
20200175961	Thomson et al.	Jun 2020	A1
20200311163	Ma et al.	Oct 2020	A1
20200311682	Olshansky	Oct 2020	A1
20200311953	Olshansky	Oct 2020	A1
20200396376	Olshansky	Dec 2020	A1
20210035047	Mossoba et al.	Feb 2021	A1
20210110104	Leme	Apr 2021	A1
20210124751	Jennings	Apr 2021	A1
20210158663	Buchholz et al.	May 2021	A1
20210174308	Olshansky	Jun 2021	A1
20210233262	Olshansky	Jul 2021	A1
20210312184	Olshansky	Oct 2021	A1
20210314521	Olshansky	Oct 2021	A1
20210342525	Leme	Nov 2021	A1
20220005295	Olshansky	Jan 2022	A1
20220019806	Olshansky	Jan 2022	A1
20220092548	Olshansky	Mar 2022	A1
20220391927	Jain	Dec 2022	A1

Foreign Referenced Citations (84)

Number	Date	Country
2002310201	Mar 2003	AU
2007249205	Mar 2013	AU
2206105	Dec 2000	CA
2763634	Dec 2012	CA
105229633	Jan 2016	CN
109146430	Jan 2019	CN
1376584	Jan 2004	EP
1566748	Aug 2005	EP
1775949	Dec 2007	EP
1954041	Aug 2008	EP
2009258175	Nov 2009	JP
2019016192	Jan 2019	JP
9703366	Jan 1997	WO
9713366	Apr 1997	WO
9713367	Apr 1997	WO
9828908	Jul 1998	WO
9841978	Sep 1998	WO
9905865	Feb 1999	WO
0133421	May 2001	WO
0117250	Sep 2002	WO
03003725	Jan 2003	WO
2004062563	Jul 2004	WO
2005114377	Dec 2005	WO
2006103578	Oct 2006	WO
2006129496	Dec 2006	WO
2007039994	Apr 2007	WO
2007097218	Aug 2007	WO
2008029803	Mar 2008	WO
2008039407	Apr 2008	WO
2009042858	Apr 2009	WO
2009042900	Apr 2009	WO
2009075190	Jun 2009	WO
2009116955	Sep 2009	WO
2009157446	Dec 2009	WO
2010055624	May 2010	WO
2010116998	Oct 2010	WO
2011001180	Jan 2011	WO
2011007011	Jan 2011	WO
2011035419	Mar 2011	WO
2011129578	Oct 2011	WO
2011136571	Nov 2011	WO
2012002896	Jan 2012	WO
2012068433	May 2012	WO
2012039959	Jun 2012	WO
2012089855	Jul 2012	WO
2013026095	Feb 2013	WO
2013039351	Mar 2013	WO
2013074207	May 2013	WO
2013088208	Jun 2013	WO
2013093176	Jun 2013	WO
2013131134	Sep 2013	WO
2013165923	Nov 2013	WO
2014089362	Jun 2014	WO
2014093668	Jun 2014	WO
2014152021	Sep 2014	WO
2014163283	Oct 2014	WO
2014164549	Oct 2014	WO
2015031946	Apr 2015	WO
2015071490	May 2015	WO
2015109290	Jul 2015	WO
2016031431	Mar 2016	WO
2016053522	Apr 2016	WO
2016073206	May 2016	WO
2016123057	Aug 2016	WO
2016138121	Sep 2016	WO
2016138161	Sep 2016	WO
2016186798	Nov 2016	WO
2016189348	Dec 2016	WO
2017022641	Feb 2017	WO
2017042831	Mar 2017	WO
2017049612	Mar 2017	WO
2017051063	Mar 2017	WO
2017096271	Jun 2017	WO
2017130810	Aug 2017	WO
2017150772	Sep 2017	WO
2017192125	Nov 2017	WO
2018042175	Mar 2018	WO
2018094443	May 2018	WO
2020198230	Oct 2020	WO
2020198240	Oct 2020	WO
2020198363	Oct 2020	WO
2021108564	Jun 2021	WO
2021202293	Oct 2021	WO
2021202300	Oct 2021	WO

Non-Patent Literature Citations (77)

Entry
“Air Canada Keeping Your Points Active Aeroplan,” https://www.aircanada.com/us/en/aco/home/aeroplan/your-aeroplan/inactivity-policy.html, 6 pages.
“American Express Frequently Asked Question: Why were Membership Rewards points forfeited and how can I reinstate them?,” https://www.americanexpress.com/us/customer-service/faq.membership-rewards-points-forfeiture.html, 2 pages.
“DaXtra Parser (CVX) Technical Specifications,” DaXtra Parser Spec. available at URL: <https://cvxdemo.daxtra.com/cvx/download/Parser%20Technical%20Specifications.pdf> at least as early as Feb. 25, 2021 (3 pages).
“Final Office Action,” for U.S. Appl. No. 16/366,703 dated Nov. 19, 2019 (25 pages).
“Final Office Action,” for U.S. Appl. No. 16/696,781 dated Oct. 8, 2020 (26 pages).
“Final Office Action,” for U.S. Appl. No. 16/828,578 dated Jan. 14, 2021 (27 pages).
“Final Office Action,” for U.S. Appl. No. 16/910,986 dated Jan. 25, 2022 (40 pages).
“Final Office Action,” for U.S. Appl. No. 17/500,687 dated Jun. 6, 2022 (22 pages).
“How We Calculate Sentiment Score,” AI AlphaSense Article published online at URL <https://www.alpha-sense.com/blog/sentiment-score/> on Sep. 10, 2020 (4 pages).
“International Preliminary Report on Patentability,” for PCT Application No. PCT/US2020/024470 dated Oct. 7, 2021 (9 pages).
“International Preliminary Report on Patentability,” for PCT Application No. PCT/US2020/024488 dated Oct. 7, 2021 (9 pages).
“International Preliminary Report on Patentability,” for PCT Application No. PCT/US2020/024722 dated Oct. 7, 2021 (8 pages).
“International Preliminary Report on Patentability,” for PCT Application No. PCT/US2020/062246 dated Jun. 9, 2022 (12 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2020/024470 dated Jul. 9, 2020 (13 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2020/024488 dated May 19, 2020 (14 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2020/024722 dated Jul. 10, 2020 (13 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2020/062246 dated Apr. 1, 2021 (18 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2021/024423 dated Jun. 16, 2021 (13 pages).
“International Search Report and Written Opinion,” for PCT Application No. PCT/US2021/024450 dated Jun. 4, 2021 (14 pages).
“Invitation to Pay Additional Fees,” for PCT Application No. PCT/US2020/062246 dated Feb. 11, 2021 (14 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/366,703 dated Jun. 10, 2019 (28 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/366,703 dated May 6, 2020 (65 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/366,746 dated Aug. 22, 2019 (53 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/696,781 dated Apr. 7, 2020 (43 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/696,781 dated Jan. 26, 2021 (28 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/828,578 dated Sep. 24, 2020 (39 pages).
“Non-Final Office Action,” for U.S. Appl. No. 16/910,986 dated Jun. 23, 2021 (70 pages).
“Non-Final Office Action,” for U.S. Appl. No. 17/025,902 dated Jan. 29, 2021 (59 pages).
“Non-Final Office Action,” for U.S. Appl. No. 17/230,692 dated Feb. 15, 2022 (58 pages).
“Non-Final Office Action,” for U.S. Appl. No. 17/396,294 dated Jul. 7, 2022 (57 pages).
“Non-Final Office Action,” for U.S. Appl. No. 17/500,687 dated Feb. 1, 2022 (51 pages).
“Notice of Allowance,” for U.S. Appl. No. 16/366,703 dated Nov. 18, 2020 (19 pages).
“Notice of Allowance,” for U.S. Appl. No. 16/366,746 dated Mar. 12, 2020 (40 pages).
“Notice of Allowance,” for U.S. Appl. No. 16/696,781 dated May 17, 2021 (20 pages).
“Notice of Allowance,” for U.S. Appl. No. 16/910,986 dated May 20, 2022 (17 pages).
“Notice of Allowance,” for U.S. Appl. No. 16/931,964 dated Feb. 2, 2021 (42 pages).
“Notice of Allowance,” for U.S. Appl. No. 17/025,902 dated May 11, 2021 (20 pages).
“Notice of Allowance,” for U.S. Appl. No. 17/212,688 dated Jun. 9, 2021 (39 pages).
“Notice of Allowance,” for U.S. Appl. No. 17/463,221 dated Apr. 18, 2022 (51 pages).
“Nurse Resumes,” Post Job Free Resume Search Results for “nurse” available at URL <https://www.postjobfree.com/resumes?q=nurse&l=&radius=25> at least as early as Jan. 26, 2021 (2 pages).
“Nurse,” LiveCareer Resume Search results available online at URL <https://www.livecareer.com/resume-search/search?jt=nurse> website published as early as Dec. 21, 2017 (4 pages).
“Response to Advisory Action,” for U.S. Appl. No. 16/696,781, filed Jan. 8, 2021 (22 pages).
“Response to Final Office Action,” for U.S. Appl. No. 16/366,703, filed Feb. 18, 2020 (19 pages).
“Response to Final Office Action,” for U.S. Appl. No. 16/696,781, filed Dec. 8, 2020 (18 pages).
“Response to Final Office Action,” for U.S. Appl. No. 16/910,986, filed Apr. 20, 2022 (13 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 16/366,746, filed Nov. 21, 2019 (12 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 16/696,781, filed Apr. 23, 2021 (16 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 16/696,781, filed Jul. 6, 2020 (14 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 16/828,578, filed Dec. 22, 2020 (17 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 16/910,986, filed Sep. 30, 2021 (18 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 17/025,902, filed Apr. 28, 2021 (16 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 17/230,692, filed Jun. 14, 2022 (15 pages).
“Response to Non Final Office Action,” for U.S. Appl. No. 17/500,687, filed May 2, 2022 (17 pages).
“Response to Non-Final Rejection,” dated May 6, 2020 for U.S. Appl. No. 16/366,703, submitted via EFS-Web on Sep. 8, 2020, 25 pages.
“Resume Database,” Mighty Recruiter Resume Database available online at URL <https://www.mightyrecruiter.com/features/resume-database> at least as early as Sep. 4, 2017 (6 pages).
“Resume Library,” Online job board available at Resume-library.com at least as early as Aug. 6, 2019 (6 pages).
“Television Studio,” Wikipedia, Published Mar. 8, 2019 and retrieved May 27, 2021 from URL <https://en.wikipedia.org/w/index/php?title=Television_studio&oldid=886710983> (3 pages).
“Understanding Multi-Dimensionality in Vector Space Modeling,” Pythonic Excursions article published Apr. 16, 2019, accessible at URL <https://aegis4048.github.io/understanding_multi-dimensionality_in_vector_space_modeling> (29 pages).
“What is CV/Resume Parsing?,” daXtra blog post published Oct. 18, 2016 at URL <https://info.daxtra.com/blog/2016/10/18/what-is-cvresume-parsing> (5 pages).
Advantage Video Systems “Jeffrey Stansfield of AVS interviews rep about Air-Hush products at the 2019 NAMM Expo,” YouTube video, available at https://www.youtube.com/watch?v=nWzrM99qk_o, accessed Jan. 17, 2021.
Alley, E. “Professional Autonomy in Video Relay Service Interpreting: Perceptions of American Sign Language-English Interpreters,” (Order No. 10304259). Available from ProQuest Dissertations and Theses Professional. (Year: 2016), 209 pages.
Bishop, Todd “Microsoft patents tech to score meetings using body language, facial expressions, other data,” Article published Nov. 28, 2020 at URL <https://www.geekwire.com/author/todd/> (7 pages).
Brocardo, Marcelo Luiz, et al. “Verifying Online User Identity using Stylometric Analysis for Short Messages,” Journal of Networks, vol. 9, No. 12, Dec. 2014, pp. 3347-3355.
Hughes, K. “Corporate Channels: How American Business and Industry Made Television Useful,” (Order No. 10186420). Available from ProQuest Dissertations and Theses Professional. (Year: 2015), 499 pages.
Jakubowski, Kelly, et al. “Extracting Coarse Body Movements from Video in Music Performance: A Comparison of Automated Computer Vision Techniques with Motion Capture Data,” Front. Digit. Humanit. 2017, 4:9 (8 pages).
Johnson, Stefanie K., et al. “Research: To Reduce Gender Bias, Anonymize Job Applications,” Harvard Business Review article published Mar. 5, 2020 available online at URL <https://hbr.org/2020/03/research-to-reduce-gender-bias-anonymize-job-applications> (7 pages).
Johnston, A. M, et al. “A Mediated Discourse Analysis of Immigration Gatekeeping Interviews,” (Order No. 3093235). Available from ProQuest Dissertations and Theses Professional (Year: 2003), 262 pages.
Krause, Annabelle, et al. “Anonymous job applications in Europe,” IZA Jounal of European Labor Studies 2012, 1:5 (20 pages).
Lai, Kenneth, et al. “Decision Support for Video-based Detection of Flu Symptoms,” Biometric Technologies Laboratory, Department of Electrical and Computer Engineering, University of Calgary, Canada, Aug. 24, 2020 available at URL <https://ucalgary.ca/labs/biometric-technologies/publications> (8 pages).
Liu, Weihua, et al. “RGBD Video Based Human Hand Trajectory Tracking and Gesture Recognition System,” Mathematical Problems in Engineering vol. 2015, article ID 863732 (16 pages).
Luenendonk, Martin “The Secrets to Interviewing for a Role That's Slightly Out of Reach,” Cleverism Article available at URL <https://www.cleverism.com/interviewing-for-a-role-thats-slightly-out-of-reach/> last updated Sep. 25, 2019 (13 pages).
Pentland, S. J. “Human-Analytics in Information Systems Research and Applications in Personnel Selection,” (Order No. 10829600). Available from ProQuest Dissertations and Theses Professional. (Year: 2018), 158 pages.
Ramanarayanan, Vikram, et al. “Evaluating Speech, Face, Emotion and Body Movement Time-series Features for Automated Multimodal Presentation Scoring,” In Proceedings of the 2015 ACM on (ICMI 2015). Association for Computing Machinery, New York, NY, USA, 23-30 (8 pages).
Randhavane, Tanmay, et al. “Identifying Emotions from Walking Using Affective and Deep Features,” Jan. 9, 2020 Article available at Cornell University website URL <https://arxiv.org/abs/1906.11884v4> (15 pages).
Swanepoel, De Wet, et al. “A Systematic Review of Telehealth Applications in Audiology,” Telemedicine and e-Health 16.2 (2010): 181-200 (20 pages).
Wang, Jenny “How to Build a Resume Recommender like the Applicant Tracking System (ATS),” Towards Data Science article published Jun. 25, 2020, accessible at URL <https://towardsdatascience.com/resume-screening-tool-resume-recommendation-engine-in-a-nutshell-53fcf6e6559b> (14 pages).
Yun, Jaeseok, et al. “Human Movement Detection and Identification Using Pyroelectric Infrared Sensors,” Sensors 2014, 14, 8057-8081 (25 pages).

Related Publications (1)

	Number	Date	Country
	20230394230 A1	Dec 2023	US

User interface and systems for document creation

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC