Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/197—Version control
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/12—Use of codes for handling textual entities
  • G06F40/131—Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/166—Editing, e.g. inserting or deleting
  • G06F40/169—Annotation, e.g. comment data or footnotes
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/20—Natural language analysis
  • G06F40/205—Parsing
  • G06F40/216—Parsing using statistical methods
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/20—Natural language analysis
  • G06F40/263—Language identification
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/20—Natural language analysis
  • G06F40/279—Recognition of textual entities
  • G06F40/289—Phrasal analysis, e.g. finite state techniques or chunking
  • G06F40/295—Named entity recognition

Definitions

• the present invention is generally directed to systems and methods of identifying, tagging, modifying, incorporating, associating and reconciling information contained in legal, commercial and business-related documents.
• the system provides a user with a visual representation of the document throughout the negotiation process, or otherwise presents the user with a graphical representation of the status of the document to better monitor various manipulations occurring over the course of the document lifecycle.
• the system and method provides a user with the ability to efficiently identify text or other information in the document and associate the user selection with source data, by way of example, a Salesforce object and/or field.
• the user may the ability to create metadata tags and/or inject certain metadata with text or other information contained within the document.
• the system and method provide alerts and/or notifications when information associated with source data has been added, modified or removed.
• the system and method also comprises the step of converting the document to a recognizable format and/or creating new categories/criteria based on the identification of a new term, clause, etc.
• the general process of identifying and extracting text from a document involves performing optical character recognition (OCR) on the document.
• OCR optical character recognition
• the identifying and extracting steps may involve a natural language engine.
• the method may further comprise a learning engine.
• a computer readable storage medium comprising processor executable instructions operable to utilize the system or perform the methods is provided.
• each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C", “one or more of A, B, or C" and "A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
• the term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms“comprising”,“including”, and“having” can be used interchangeably.
• the term“automatic” and variations thereof, as used herein, refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be“material”.
• machine-readable media refers to any tangible storage that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
• Non-volatile media includes, for example, NVRAM, or magnetic or optical disks.
• Volatile media includes dynamic memory, such as main memory.
• Computer- readable media include, for example, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, magneto-optical medium, a CD-ROM, any other optical medium, a RAM, a PROM, an EPROM, a FLASH-EPROM, a solid state medium like a memory card, any other memory chip or cartridge, or any other medium from which a computer or like machine can read.
• the computer-readable media is configured as a database
• the database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Accordingly, the invention is considered to include a tangible storage medium and prior art-recognized equivalents and successor media, in which the software implementations of the present invention are stored.
• module refers to any known or later developed hardware, software, firmware, machine engine, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Also, while the invention is described in terms of exemplary embodiments, it should be appreciated that individual aspects of the invention may be separately claimed. BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 2 illustrates another view of the embodiment illustrated in FIG. 1;
• FIG. 3 illustrates a pop-over user interface according to the embodiment illustrated in FIG. 1;
• FIG. 4 illustrates yet another view of the embodiment illustrated in FIG. 1;
• FIG. 5 illustrates yet another view of the embodiment illustrated in FIG. 1;
• FIG. 6 illustrates a display for information associated with a particular document in accordance with embodiments of the present disclosure
• FIG. 8 illustrates another display for presenting a document for modification in accordance with embodiments of the present disclosure
• FIG. 12 depicts a clause identification module display in accordance with embodiments of the present disclosure
• FIG. 13 depicts yet another clause identification module display in accordance with embodiments of the present disclosure
• FIG. 14 depicts a suggestion service module display in accordance with embodiments of the present disclosure
• FIG. 15 depicts yet another suggestion service module display in accordance with embodiments of the present disclosure
• FIG. 16 depicts a merge module display in accordance with embodiments of the present disclosure
• FIG. 17 depicts a visualization display in accordance with embodiments of the present disclosure
• FIG. 19 depicts yet another visualization display in accordance with embodiments of the present disclosure.
• clauses, terms and conditions within a particular document and companion documents may be revised and the document dynamically altered by one or more individuals without loss of associated data, objects or fields.
• the system and method provides a user with the ability to create and manage templates based on clauses, terms and conditions (and subsequent revisions), which may be accessed by the user or a different user for incorporation with similar or related documents.
• the templates may be contained in a library or similar repository, and may be easily managed, searched and retrieved by a user.
• embodiments of the present disclosure will be described in connection with various examples of documents, it should be appreciated that embodiments of the present disclosure are not so limited. In particular, embodiments of the present disclosure may be applied to any document and any data source. For instance, while embodiments of the present invention may be described with respect to Salesforce or equivalent CRM, the inventions described herein are not so limited. More particularly, the aspects of the invention described herein may apply to a wide range of documents, including contracts, invoices, purchase orders, terms of sale, memoranda of understanding, warranty documents, license agreements, assignments, settlement agreements, and other legal, commercial and business documents, regardless of the repository where those document types are stored. It should be understood the reference to one particular document, such as a contract, is for illustrative purposes only and should not be construed as limiting the claimed invention.
• the user may be presented with a listing of options 102 for mapping data corresponding to a“Contract Field” as well as the ability to search for a particular Contract Field 104.
• the user may be presented with a listing of options 106 for mapping data corresponding to a particular“Clause” in the contract, and the ability to “Search Clauses” 108 stored by the system.
• the user may select the appropriate data source to associate with the captured text.
• the user may select multiple data types to associate with a particular text string, clause or provision in the contract, etc.
• the user may select the option“Contract Start Date” 116 using any of the three options described above.
• the pop-over user interface 118 allows the user to save the selection, and may further display the document value and corresponding source data value (the “Document Value” 120 and “Salesforce Value” 122 fields shown in Figure 5).
• a user may select any tagged text string, clause or provision in the contract and quickly retrieve and modify, if necessary, the document value or the data source value.
• the user may extract the source data, perform reconciliation, or one of the other functions described herein using this user interface, several of which are described in further detail below.
• the system provides a user with the ability to quickly view and/or extract data linked to the selected text in a document. Furthermore, the system according to this embodiment allows a user to update source data information automatically, including in the event any one document (regardless of whether the document is the one containing the originally selected text or a companion document associated with the same) implicated by the source data is subsequently modified. This prevents errors and omissions when negotiating and finalizing the document.
• the user may be presented with an interface to update or reconcile source data associated with a document, particularly if the source data information has been changed within the source data repository.
• the user may update the objects and/or fields associated with the document, including by adding, removing or altering a previous selection. This may be helpful when a particular text string has more than one consequence (i.e., contract term and warranty term) or when the text string represents more than a single object and/or field within Salesforce or equivalent CRM.
• the system provides a user with the ability to efficiently identify text or other information in the document and associate the user selection with source data, such as Salesforce objects and/or fields.
• a system and method for dynamically modifying a document and tracking modifications made during the course of the document life cycle, including to data contained within the document.
• a user may desire to modify a document created by, for example, Microsoft Word.
• the user may have further associated data from a CRM, such as Salesforce, by using a composer tool such as Conga Composer.
• the user may extract data from Salesforce and embed that data in the Word document using Conga Composer.
• the system may advantageously mark or tag data elements that tell the user the data source.
• the tags are a hidden element, and not immediately visible to the user or a subsequent user of the system. In other embodiments, the tags are selectively visible by the user.
• the tags applied to data thereby permit selected text in the Word document to be associated with the data source(s), which allows the data to be updated in, for example, Salesforce or an equivalent CRM, even though the user may make modifications to the document independently from Salesforce. This feature will be described in more detail below as it relates to reconciliation of modified documents, and tagged data within those modified portions of a document.
• a user may begin the process using an application known as Conga Contracts.
• Conga Contracts One exemplary user interface is shown in Fig. 6, which comprises an overview of various capabilities and tools of the system described herein.
• the user has the ability to input activities 124 associated with a document, including adding a new event 126, a new task 128, inputting future steps 130 or comment on past activity 132, etc.
• the user interface of Fig. 6 further comprises the ability to send a selected document 134 to other parties for negotiation, or to view modifications made to a document by one or more parties.
• an original user of the document may communicate with other users, by email correspondence, with the document provided as an attachment.
• the system applies a tracking identifier.
• This identifier may be viewed as a service, running in the background of the system and independently of the user, for monitoring the evolution of the document and tagged data within the document as it is modified.
• the identifier service is programmed to listen for subsequent usage of the document by tracking the original email and subsequent emails in the thread.
• the service is specifically configured to watch for attachments to the email thread, as users respond and reply to the original email, and extract a subsequent version of the attached document. Once identified and extracted, the subsequent version of the document may be uploaded to, for example, Salesforce or equivalent CRM.
• the modified document attached to an email may be uploaded to a document repository in Salesforce called Content.
• Salesforce a document repository in Salesforce called Content.
• the system automatically watches for, extracts and uploads subsequent versions of the document, and in a preferred embodiment creates a new Content version of that particular document in the repository.
• each version of the modified document is automatically preserved and stored by the system.
• One aspect of the system then permits a user to compare any one version of the document with any subsequent version of the document.
• the system also permits individual or group users to incorporate comments, proposed terms or clauses, or other annotations to facilitate the completion of a final, negotiated document.
• a user interface 136 is shown according to one embodiment for a user to view dynamic modifications made to a document. Modifications may be made directly by another party, or may be merged into the document as a result of changes to the source data.
• the modifications are preferably highlighted 138 or called out to the user through the user interface 136, and may comprise changes to specific terms 140, as shown in Fig. 7, or to clauses 142 or other language appearing in the document, as shown in Fig. 8.
• the user may take on or more actions relative to their review of the modified document, as described in greater detail below.
• Figs. 9-11 another aspect of the system and method of the present disclosure is illustrated. After potentially numerous iterations to the document, a final negotiated document may be created through the system and methods described above. However, the document may still contain modifications, comments, annotations, etc. from several users, which require reconciliation before a true final document can be circulated.
• reconciliation may occur by providing the user with the ability to compare and automatically identify or call out certain differences to be reconciled, including between different versions of a document, differences between the language or terms in a document and one or more data sources, or between documents of a related or similar nature.
• a particular term may have been modified by a user during a portion of the negotiation, but in other parts of the document that same term is not modified.
• the system therefore allows a user to compare changes made between any versions of the document, while being alerted to discrepancies that have emerged during the modification process.
• the reconciliation process is a critical process for generating a final, clean document.
• this reconciliation process is provided by a module known as True- up, and is shown in relation to Figs. 9-11.
• the reconciliation module recognizes the presence of tags (hidden or otherwise) that have been applied to certain data in the document, and flags each for reconciliation by the user.
• the module may also make updates to source data from which the tagged text has been extracted.
• the module may search for and identify potential issues for further reconciliation by the user.
• the module may automatically reconcile issues created during the merging of modifications in a document, including modifications involving adding new content to a document.
• the module is configured to identify and store new content added to a document.
• the new content may be stored in the CRM or equivalent repository.
• a user may initiate the True-up module for a particular document and, as reflected in Figures 9-11, step through each term or clause in the document that requires some degree of reconciliation.
• the True-up module will prompt the user to reconcile that term with the source data (in Salesforce or otherwise).
• This reconciliation module provides an important service to the user, once the negotiation is completed, such that a document owner, or in some instances a Salesforce contract administrator, may reconcile modified data and ensure the data in the document matches the data in Salesforce or other repository system.
• the data to be reconciled consists of the data that was merged into the document when it was created, such as by Conga Composer, and appropriately tagged. In other embodiments, additional data may be tagged and tracked for future reconciliation, either by the original user or a subsequent user of the system.
• the present disclosure comprises a system of “bookmarks” or equivalent tags associated with the merged data to track the source of the data that was merged.
• the system employs document variables to track the source of the data that was merged. As the information associated with the source data is modified, the corresponding source data may be updated automatically and seamlessly.
• each field that is merged into a document may be“bookmarked” by one or more invisible (or alternatively, visible) fields that contain pertinent source information needed to return updated data to the original source files. Whenever data is merged into a document, that data may be surrounded by the bookmarks in order for subsequent revisions to be interrogated for changes.
• the field type for the word field may be ADDIN, and is preferably not displayed to the user.
• the format of the fields will start with the following character sequence:
• CCFIELD comprises a string used to identify the ADDIN field as one to be parsed, and also indicates that other values should be ignored.
• VERSION represents the current version of the field specification, and in a preferred embodiment is set to 1.
• END comprise the two fields associated with the beginning and ending of each discrete merged piece of data, the beginning marked with a START and the ending marked with an END.
• OBJECTED represents the unique identifier of the object in the system the source data originated from.
• FIELDNAME represents the name associated with the given object that the data originated from.
• CHECKSUM A CRC32 comprises a checksum operation of the following fields, preferably concatenated together: CongaSystemldentifier + CongaObjectldentifier + OBJECTED + FIELDNAME.
• CHECKSUM A CRC32 is encoded.
• document variables are used in lieu of bookmarking to store origination data to validate returning data.
• These variables will include: A system identifier that uniquely identifies the system that generated the data. For example, in the example of a Salesforce application, this identifier may be set to the Organization ID, and may be used to validate data coming back in was created by the system in question. Variable may also include an object identifier, or unique ID of the object that generated the particular document. In the example of the Salesforce application, if a user generated a document off of a quote it would contain the ID of the Quote object that it was created from. In another embodiment, both bookmarking and document variables are employed with a document.
• the user may select from a listing of data source types contained within the pop-over user interface, or may conduct a search for the appropriate data source to associate with the text string.
• the pop-over user interface allows the user to save the selection(s), and then the user repeats these steps for all remaining text strings and clauses that the user desires to associate with source data.
• the system permits a user to inject text or other information contained within a dynamically created document with metadata. For instance, if a document was created and later undergoes revision that includes additional clause language in the document, a user may select to inject metadata corresponding to the newly added content and save time and/or resources otherwise required to individually select and map out data sources for text strings located within the additional clauses. Thus, injecting metadata may be accomplished to only a portion of a document, according to the user’s preference.
• a system for identifying and classifying text contained within a document is described.
• terms, clauses or other information contained in the document may be parsed directly within the document, or alternatively converted by performing optical character recognition (OCR) on the document.
• OCR optical character recognition
• the document is analyzed to identify different portions or sections of the document.
• the different parts of the document are extracted and classified based on matching or pattern recognition performed on each part. Whether the part is correctly classified by the system or not, the next step is to compare each part with templates stored in the system (i.e., the library described in further detail below) to identify any logical matches based on the content associated with each part. Any identified and matched parts of the document are then returned to the user for processing and mapping to any desired data sources, including by way of metadata injection described above.
• Specific user interfaces depicting the steps of identification and classification are appended hereto as Figures 12-13.
• the identifying and categorizing steps may involve a natural language module.
• the natural language module may be configured to recognize natural language appearing in a clause or section of a document.
• the natural language module may also be configured to determine a template correlating to the recognized language and either call up the template or provide the user with a selection of the closest matching templates. If the natural language engine determines that the recognized clause or section is not associated with a current template, the user may be provided with the option to create and name a new template.
• the system and method may comprise a deep neural net learning engine or equivalent computer machine learning engine, configured to model high-level abstractions in data appearing in a document.
• the system and method may further employ artificial neural networks comprising learned representations of data, and may further employ features such as automatic speech recognition, foreign language processing, and adaptive learning.
• the system may therefore comprise separate modules for employing each of the foregoing.
• the system and method also comprises the step of converting the document to a recognizable format, such that the document may be parsed and categorized according to the system and method described above.
• the user is provided with one or more interfaces for establishing new categories or criteria for a template or class of templates, based in part on the newly identified term, clause, section, etc.
• a system and method for managing terms and clauses used in legal, commercial and business-related documents is disclosed.
• This system and method permits a user to search, identify, select and efficiently merge such terms and clauses into a document, and then manage the work product (i.e., the subsequent versions of the term or clause) in future document creation and/or negotiation.
• the system automatically creates a repository for storing versions of a document, clause or term with saved versions reflecting modifications from an original.
• a user may tag, name or otherwise label and/or categorize subsequent modifications to a document, clause or term, which may be viewed by other users during the negotiation and finalization of the document.
• these labels and categorizations may be used either by a subsequent user or the adaptive learning module described above.
• User interfaces provided by the system allow a user to quickly and efficiently identify, categorize and store commonly used terms and clauses for future searching and selection by the user or another user of the system.
• the system further comprises a resource library or repository, where previously created or modified terms, clauses or complete documents, which may be configured for a specific user or user organization, have been automatically or manually categorized and managed.
• This library may be further subdivided to contain finally negotiated documents for managing by the user, or templates to be used in future document negotiation.
• the interface 150 preferably includes a portion 152 for displaying or previewing the document.
• the interface 150 may further comprise a list 154 to select a document type or category, and in certain embodiments may include the titles or names associated with the particular documents.
• the interface includes an option for the user to input and search for key words associated with the desired document.
• the user interface also provides the user with the ability to modify and store new versions of documents in the library, with the ability to categorize and name custom made documents for future ease in locating.
• a library or equivalent repository may be provided to a large population of users to retrieve clauses or other content for a particular document type.
• a user interface 156 may be included with the system for allowing a user to scan various clauses and/or sort clauses based on a number of different criteria including, by way of example but not limitation, the clause name 158, clause revision 160, clause type 162, document name 164, document type 166, document revision 168, creation date 170, last updated date 172, last updated by 174, and created by, which may be listed in the interface for ease of review. Variations on the search and sort capabilities of the user interface shown in Fig. 13 are contemplated and considered within the scope of the present disclosure.
• the system consumes objects and fields within the source data and creates a schema of the source data, along with associated metadata.
• the system compares the discrete entities extracted from the text strings to the metadata and identifies potential relationships between the same (and presents the user with a suggestion).
• the system may optionally present the user with an interface 176 to further investigate each suggestion, as shown in Figs. 14-15, by highlighting 178 or otherwise calling out the entities with which the system has at least one suggestion.
• a pop-over display 180 preferably appears with the option of either selecting the suggestions identified by the system or, if preferred, searching all source data tags for making a new association between the particular entity and an object and/or field.
• the system and method according to this embodiment may comprise a recommendation module.
• This module may be activated by the user, or alternatively running in the background while the user is engaged in any of the foregoing activities.
• this recommendation engine may comprise a search of a particular document, identifying the type of document (or a clause within the document) and suggest further action by the user. For instance, the suggestion may contain a certain term based on either a particular clause incorporated by the user or, for example, the appearance of a data source merged into the negotiated document.
• the recommendation engine searches the library or other repository for similar documents, and then identifies particular clauses or terms that are contained within those similar documents but are not incorporated into the working document.
• the recommendation engine may suggest alternative clauses or terms from those contained in the working document.
• the step of merging stored clauses into a document may be repeated as many times as necessary until the document has the content the user prefers, and is ready for sharing with other users.
• the user may identify a clause that is more preferred than one in the library and decide to save that clause to the library.
• the system provides the user with this capability, thereby allowing the user to select the saved clause in future documents using the merge feature.
• the system preferably includes a tool for visualizing the process of negotiation that occurs from inception until document completion.
• this allow a user to create a visual representation of the document lifecycle, implement rules at different points in that lifecycle, and apply restrictions as necessary for different stages of the document negotiation.
• a certain task or activity or event may be represented in the system by a block 186, bubble or other icon. Additional tasks, activities and events may be subsequently built, with relationships interrelating the different icons.
• the visual representation may comprise multiple paths 188, 190, depending on a certain event occurring (or not occurring) or a different event occurring (or not occurring).
• the visual representation may include a different path and set of tasks, activities or events.
• a different user interface may be provided to some or all users after the diagrams shown in figs. 17-18 have been configured.
• the user is presented only with the tasks, activities or events that are current or immediate, and guides the user from one task, activity or event to the next.
• This interface may include task bars 192, 194, as shown in Fig. 19, and include different colors or other indicia to indicate to the user the status of those tasks.
• the interface may also provide a user with a quick visualization 196 of the document negotiation process, immediately alerting the user of tasks, activities or events that have yet to occur and the user(s) responsible for those remaining steps.
• a user may be alerted once the process flow advances to a task, activity or event that user is responsible for. Variations on the interfaces described in this section are contemplated.
• the user is provided with a system for identifying and extracting text from a native document.
• the system may include one or more processors, memory, an identifier module and an extractor module, which receives the document, identifies text and other fields in the document, recognizes data to be associated within the document and marks that data.
• the method of using the system in this manner comprises several steps, described below, which permit the user to make and review modifications to a native document and then reconcile the document, as described above. In this manner, any document type may employ the systems and methods described herein.
• a method whereby data is automatically identified and retrieved from a document.
• Text from most electronically kept documents can be identified and categorized, regardless of the type of document.
• an OCR process may be applied to a document to first identify, and later mark, text representing data to be merged during the course of negotiating the document.
• a search algorithm may be employed to assist with identifying and locating all text to be tagged.
• the text identifier and extractor module may perform an OCR or equivalent native language search process on the document to retrieve one or more text tokens.
• the text identifier and extractor module may apply one or more rules to the sequences of text tokens received from the OCR process, using an existing or new rules set. For example, knowledge of a particular document type may determine or influence one or more rules that are applied and thereby tags that are assigned to data identified in the document. The application of the rules continues in this step until it is determined if there are no further rules to apply to the document or the text tokens created during the preceding steps.
• the method may then move to the next step, where it is determined whether there are additional pages in the document in which to search for additional text tokens. If there are more pages to be searched, the method retrieves the next page and continues with the extraction steps described above. Otherwise, the method proceeds to the next step, where it is determined if the retrieved text token(s) match recognized pattern elements. These pattern elements may be closely tied to rules described above, and further assist in the method of associating the natively captured text with the type of information to be tagged in the document. If a match is found, the method then proceeds to identify the text to be tagged respective to that matched pattern, and continues for each pattern recognized from the native document. This process is completed until there are no more patterns recognized and no more rules to apply.
• the method may then create an original source document for use by the various systems and methods described above. Processes described above with respect to modifying and reconciling modifications to the document may commence.
• the OCR process referenced above may produce a sequence of text tokens, which represent lines of text on a page of the document. For example, for each line of text on a page, a separate token representing text desired for tagging may be generated. In some instances, multiple tokens may be generated for a single line of text in the document. In other instances, a single token may be generated for multiple lines of a document.
• a text verification module may be utilized. In this embodiment, the text tokens recovered by the OCR process may be compared to text characters in the native document or in a separate document of the same type, such as one of the documents located in the library or other repository described above. If any discrepancy between the tokens identified in the OCR process and the text are found, a separate discrepancy process may be initiated to resolve such a discrepancy.
• the text identifier and extractor module may utilize rules according to one or more document classifications. As one example, if the text identifier and extractor module is utilized to identify data from a business- related document, such as a warranty, the text identifier and extractor module may utilize rules previously established for warranty-related documents. The text identifier and extractor module may utilize a group or subgroup of rules applying to the document type, may utilize a group or subgroup of rules for a warranty with a specific vendor, or may utilize a group or subgroup of rules for a specific client.
• native documents are processed according to the systems and methods described above, those documents may be added to the library or other repository.
• the information may be sent to or otherwise associated with a user profile, such that a user associated with the user profile may access and/or send the document to another user or business entity.
• the systems and methods described above may further comprise an application, or be provided via one or several modules.
• the application/modules are designed to operate on a mobile device or mobile computer, and assist a user with managing organizational documents and associated data organization.
• the application/modules may comprise one or more data sets, tables or databases, including one or more relational databases.
• the application includes time and/or content-specific notifications.
• the application/modules further permit a user to sort, search and modify documents and manipulate data associated therewith, in many instances automatically.
• the application preferably is configured to run on a computer server or similar computational machinery.
• the application is also preferable configured to provide alerts.
• Alerts may be provided via the application (e.g., notification upon login, push notification), email, messaging, or any other suitable method of communication to the user.
• Alerts may be defined for certain conditions, for example, modification occurring to one or more clauses or data types in a document.
• alerts may be provided for continued modification or approval of a modified document.
• alerts may be provided based on all users completing the modification of a document.
• an alert may indicate a recommended course of action.
• the alert may recommend that content not already contained within a document be incorporated, or that specific data be modified to comply with predetermined rules established by one or more users.
• the application comprises one or more user interfaces and displays, such as the displays depicted in the drawing Figures appended hereto.
• the application may be stored or operated on a computing environment, wherein the systems, devices, servers, modules, etc. may execute.
• the computing environment described according to this embodiment preferably includes at least one network.
• the network can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation SIP, TCP/IP, SNA, IPX, AppleTalk, and the like.
• the system in varying embodiments may also include one or more server computers.
• One server may be a web server, which may be used to process requests for web pages or other electronic documents from user computers.
• the web server can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems.
• the web server can also run a variety of server applications, including SIP servers, HTTP servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some instances, the web server may publish operations available operations as one or more web services.
• the computing environment may also include one or more file and or/application servers, which can, in addition to an operating system, include one or more applications accessible by a client running on one or more of the user computers.
• the server(s) may be one or more general purpose computers capable of executing programs or scripts in response to the user computers.
• the server may execute one or more web applications.
• the web application may be implemented as one or more scripts or programs written in any programming language, such as JavaTM, C, C# , or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages.
• the application server(s) may also include database servers, including without limitation those commercially available from Oracle, Microsoft, SybaseTM, IBMTM and the like, which can process requests from database clients running on a user computer.
• the web pages created by the application server may be forwarded to a user computer via a web server.
• the web server may be able to receive web page requests, web services invocations, and/or input data from a user computer and can forward the web page requests and/or input data to the web application server.
• the server may function as a file server.
• machine-executable instructions may be stored on one or more machine-readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions.
• machine-readable mediums such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions.
• the methods may be performed by a combination of hardware and software.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• Health & Medical Sciences (AREA)
• Artificial Intelligence (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Computational Linguistics (AREA)
• General Health & Medical Sciences (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Probability & Statistics with Applications (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Applications Claiming Priority (4)

Publications (2)

Family

ID=66665954

Family Applications (1)

Country Status (2)

Families Citing this family (1)

Family Cites Families (5)

• 2018
  • 2018-11-16 EP EP18882534.3A patent/EP3676731A4/de not_active Withdrawn
  • 2018-11-16 WO PCT/US2018/061513 patent/WO2019108413A1/en not_active Ceased

Also Published As

Similar Documents

Legal Events