WO2001098940A1 - Multiple document creation method and system - Google Patents

Multiple document creation method and system Download PDF

Info

Publication number
WO2001098940A1
WO2001098940A1 PCT/GB2001/002765 GB0102765W WO0198940A1 WO 2001098940 A1 WO2001098940 A1 WO 2001098940A1 GB 0102765 W GB0102765 W GB 0102765W WO 0198940 A1 WO0198940 A1 WO 0198940A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
document
document creation
information
Prior art date
Application number
PCT/GB2001/002765
Other languages
French (fr)
Inventor
Michael Anthony Foy
Paul Bowden
Quentin Solt
Original Assignee
Knowhow Systems Group Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Knowhow Systems Group Limited filed Critical Knowhow Systems Group Limited
Priority to AU2001266149A priority Critical patent/AU2001266149A1/en
Publication of WO2001098940A1 publication Critical patent/WO2001098940A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/166Editing, e.g. inserting or deleting
    • G06F40/174Form filling; Merging

Definitions

  • This invention relates to a method and apparatus for document creation and particularly to electronic document creation using persistent data.
  • the term "persistent data" refers to data used in a document creation process which is retained by the document creation system for use in a subsequent document creation process.
  • the persistent data may comprise user specific data used in the selection of content for inclusion in the document and/or user specific data for populating the selected content. For example, a response or a sequence of responses made by a user to determine which content is included may be captured by the document creation system and retained for use in a subsequent process .
  • responses of a user may provide particulars relating specifically to a variable such as the name of a legal person mentioned in a clause of a document. Such information may be of use in a subsequent document creation process performed by the same user or requiring the same variable and so it is retained by the document creation system. Accordingly, responses providing that information need not be input again.
  • a method of operating a computer system to create a sequence of documents according to an automated document creation process comprising a host server and at least one client terminal, the process comprising: identifying a user at the client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining document creation information; receiving at the host server in electronic form responses to said prompts which include current data and persistent specific to the user for populating the documents; storing said persistent user specific data at the host server for use in the current and subsequent document creation processes; executing a first document creation process to generate a complete document including said user specific data; and subsequently, executing a second document creation process using different current data generated by the user and the persistent data received during the first document creation process.
  • said responses include user specific information for identifying clauses to be included in a document, said user specific information being stored with said persistent data for use in a subsequent document creation process.
  • Preferred methods comprise the step of updating the persistent data from a data source separate from the client terminal.
  • the data source is located remote-ly- -from the host server used ' in the document creation process.
  • Such a data source is operated and controlled independently of the document creation process.
  • the host server is connected to the data source by one of the internet and a dedicated communication path.
  • fresh data is transmitted to • said host server from said data source responsive to a query therefrom. This type of query is triggered by recognition of a user.
  • Other embodiments of the method comprise periodically updating the persistent data from the data source at intervals according to a predetermined schedule.
  • Persistent user specific data can be entered into two or more documents which are generated simultaneously in a document creation process.
  • a method of operating a computer system to create documents according to an automated document creation process comprising a host server and at least one client terminal, the process comprising: identifying a user at a client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining initial document creation information; receiving at the host server said initial document creation information responsive to said prompts; obtaining further document creation information from a plurality of remote data servers, said further document creation information including data specific to the user for inclusion in the document; and executing a first document creation process to generate a document including "said initial and further document creation information.
  • an internet based document creation system for creating documents according to an automated document creation process performed at a host server connected to at least one remote client terminal, the host server comprising: storage means holding a plurality of document templates and a set of clauses associated with said templates; a persistent data store holding persistent user specific data for inclusion in said clauses in the current and subsequent document creation processes; a current data store for holding user specific data for use in the current document creation process only; a processor for executing a document creation program to generate at least one complete document based on user inputs including document creation information identifying at least one document template, clauses for inclusion therein and current user specific data, said document creation process also using said persistent data; and document delivery means for delivering the complete document in electronic form to the client terminal.
  • a method of creating a document in a computer system comprising a host server and at least one remote client terminal connected by a data transmission path in which method: the host server and client terminal exchange messages to enable automatic creation of a plurality of documents at the host server; document content and variables for populating said content being selected responsive to inputs made by a user at the client terminal, wherein a single electronic template is used to generate said plurality of documents .
  • the document creation system comprises a computer program product comprising code means stored on a computer readable medium, the program code means being adapted to perform the steps in the document creation process, when run on a computer .
  • Figure 1 illustrates an embodiment of a document creation system
  • Figure 2 illustrates a client terminal for use in the system of Figure 1;
  • FIG 3 illustrates an internet content management system for use in the system of Figure 1;
  • Figure 4 illustrates schematically how the internet content management system of Figure 3 creates and delivers a document
  • Figure 5 illustrates schematically how documents are created by the internet content management system of Figure 3;
  • Figure 6 illustrates schematically method steps in the process of document creation and delivery by the system of Figure 1;
  • FIG 7 illustrates schematically the exchange of information occurring in document creation and delivery systems according to Figure 1;
  • Figure 8 illustrates a second embodiment of a document creation system.
  • FIG. 1 illustrates schematically an electronic document creation system generally designated by reference numeral 5.
  • the document creation system 5 includes an internet content management system 50 implemented at a host server which is connected via a gateway 41 to the internet 40.
  • a plurality of client terminals 10 are connected to the internet 40 remote from the internet content management system 50 by respective modems 24.
  • a data server 200 is also connected to the internet 40 by means of a gateway 201.
  • a broken line designated by reference numeral 11 schematically illustrates the boundary between the "system side" on which the internet content management system 50 is located and the "network side" on which the internet 40, the data server 200 and the client terminals 10 are located.
  • the embodiment illustrated in Figure 1 receives from a client terminal 10 via the internet 40 information necessary to create electronic documents on the server side of the electronic environment and thereafter delivers completed electronic documents to users on the network side via the internet 40.
  • the document creation system 5 includes a persistent data store containing specific data useful over a number of document creation processes and a current data store for holding data for the current document creation process only.
  • the persistent data store can be updated using data from sources connected to the document creation system 5, such as data server 200.
  • FIG 2 illustrates a preferred client terminal 10 for the document creation system of Figure 1.
  • the client terminal 10 is a personal computer which includes a processor 12, a clock generation circuit 14 connected to the processor, a read only memory 18 and a random access memory 16. Both of the read only memory 18 and the random access memory 16 can be accessed by the CPU 12.
  • the client terminal 10 also has a communication port 22 connected to an external modem 24.
  • the modem 24 is connected to the internet 40 as illustrated in Figure 1.
  • the client terminal 10 has externally connected display and input devices 28,32.
  • the display 28 and input 32 devices are supported by driver software 26,30, respectively.
  • the client terminal 10 is also provided with browser software 25.
  • the client terminal 10 thus has browser capability and enables the user to interface from a remote location with the system side of the document creation system 5.
  • FIG 3 illustrates components of the internet content management system 50 shown in the document creation system 5 of Figure 1.
  • the internet content management system 50 includes elements for receiving and deconstructing source documents, storing document content and for extracting previously stored content to be included in documents being created.
  • the internet content management system 50 comprises an input converter 53 and a host server 70.
  • the input converter 53 receives source documents 52 and converts the content of the source documents 52 into extensible markup language (XML) format.
  • the host server 70 has processor functionality.
  • the server 70 comprises a content management engine 72 which functions as a contract creation module (CCM) and a data repository 60 in which the content of source documents 52 and persistent data for use in the document creation process are stored.
  • the data repository 60 ' thus comprises a persistent data store 202 which contains user specific data of use in- the current document creation process which is desired to be retained for use in a subsequent document creation process.
  • CCM contract creation module
  • the data repository 60 includes a file system database 56 and a relational database 58.
  • the file system database 56' stores XML content extracted from the source documents 52.
  • the relational database 58 stores information about that content and comprises the persistent data store 202.
  • the relational database 58 may store information on who created the content, when it was created, when it was last modified, labels identifying specific portions of content, cross references between related portions of content and data relating specifically to persons who have previously used the document creation and delivery service.
  • the content management engine 72 of the server 70 can write to and extract information from the data repository 60.
  • An external data server 200 and an internal data server 300 are connected to the relational database 58 of the data repository 60 and can supply information to the persistent data store 202 contained therein.
  • Subject matter in XML format may also be stored in the relational database 58 and, although not shown, this database can also be connected to an external data server.
  • the host server 70 also comprises a current data store 210 for storing data required only in respect of the current document creation process.
  • the content management engine 72 is provided with software 74 for compiling documents created for the user as will be explained below.”
  • the host server 70 also comprises an output converter 55 which can convert a newly created document from XML format into a format acceptable to the intended recipient, i.e. a user at a client terminal 10.
  • source documents 52 are supplied to the input converter 53.
  • the input converter 53 is implemented in software on a server other than the internet content management server 70 and can accept source documents in a plurality of different electronic formats.
  • the input converter 53 ' could of course be implemented on the host server 70.
  • the converter 53 can accept documents in commercially available word processing and other recognised formats.
  • the converter 53 comprises software filters which are used to convert the received document from its original format into XML format.
  • the content in XML format is then transferred to the content management engine 72 of the host server 70.
  • the content management engine 72 deconstructs each source document 52 and stores content objects and information about those content objects in the data repository 60.
  • Information held in the data repository 60 includes a content library 57, labels and cross references 59 relating to the content objects in the content library, document templates 81 having various predefined structures and a persistent data store 202.
  • the content management engine 72 of the host server 70 can communicate with the user over the internet by means of . the browser enabled client terminal 10.
  • the user provides the document creation information 93,95 and data 97 necessary to construct the document as will be explained below.
  • the content management engine 72 sends prompts 78 to the user at the client terminal 10 to guide the user through the document creation process being performed at the host server 70.
  • the user is prompted to enter information 93 regarding the nature of the required documentation which is used to identify a relevant template or set of templates.
  • the user is further prompted to provide information 95 to enable the selection of content (clauses) for the document.
  • the user can also provide specific data 97 for populating any clauses of the document requiring such data.
  • Information and data 93,95,97 which is entered for use in the current document creation process is temporarily buffered at the host server in the current data store 210.
  • Information and data likely to be of use in a subsequent document creation process 93,95,97 is stored in the persistent data store 202.
  • the persistent data store 202 contains a first type of user specific information 204 relating to the selection of clauses for inclusion in the document as well as a second type of user specific data 206 for inclusion in the clauses of the document being created.
  • the persistent data store is connected to an external data server 200 and an internal data server 300.
  • the external data server 200 is located on the network side of the electronic environment and is maintained independently of the document creation system 5 by a third party.
  • the external data server 200 includes a database 250 containing data relevant for document creation and useful for updating the data held in the persistent data store 202.
  • the external data server 200 may include data on legal persons such as limited companies .
  • the data server 300 is located on the system side of the electronic environment and. is maintained under the control of the operator of the document creation system 5.
  • the internal data server 300 also includes a database 350 containing data relevant to document creation and useful for updating the data held in the persistent data store 202.
  • the internal data server 300 may comprise a database containing particulars of a company's clients.
  • the current data store 210 is used to (temporarily) buffer user responses providing document creation information and data for populating clauses in the document currently being created.
  • the information and data stored in the current data store 210 of Figure 4 relates to the present selection of a template 93, the selection of document content 95 and the population of clauses 97 comprised in the selected content.
  • the content library 57 held in the data repository 60 includes the content of source documents 52.
  • the content is stored in the form of a plurality of content objects 63 each of which corresponds to a document component.
  • the document components are clauses for example of a legal document.
  • the content objects 63 are labelled according to the type of document to which they relate.
  • this may be achieved by regarding the content objects 63 as belonging to a plurality of collections 65 A, B, C ... X, Y based on their subject matter.
  • the content objects 63 of each collection 65 are also labelled with structural identifiers 67 indicating to which section of a document template 81 they relate.
  • Different structural identifiers 67 may relate to, for example, heading sections, overview sections, detail sections and appendices .
  • Related collections 65 are cross-referenced 69. For example, collections of content about a general clause may have relevance only to certain other collections of content previously selected by the user.
  • Each document template 81 comprises a number of documents 71 each having a predetermined structure defined by a plurality of sections 67 for receiving content objects 63.
  • the templates 81 have various structures which depend upon the type of documentation intended to be created therefrom.
  • the template 81 indicated includes a plurality of separate sections 67 comprising a mixture of text such as heading, overview, detail, appendix and personal, and place holders, as required.
  • the place holders 73-80 act as insertion points for the content appropriate to that section.
  • groups 65 of logically associated content objects 63 are selected from the content library 57 simultaneously.
  • These groups 65 ' of logically associated content objects 63 correspond to the "collections" 65 of the content library 57. Some content objects 63 from a collection 65 may be used in multiple documents 71 and/or templates 81 in processes where two or more resultant documents are being created simultaneously.
  • the content management engine 72 uses data from the persistent data store 202 in the document creation process. If the user has used the document creation server before a considerable amount of the relevant document creation information and data for populating clauses may be available within the persistent data store. Referring to Figure 5, previously inserted data 204 relating to the selection of clauses can be used to extract appropriate document content 63 or collections 65 from the content library 57. Additionally, or alternatively, previously inserted data 206 for populating the clauses can be included in the group 65 of logically associated content objects before it is applied to the template 81. It is possible for data from the persistent data store 202 to be inserted into one or more different documents 71 or sections 67 thereof simultaneously. Thus, data provided by users during previous uses of the document creation system 5 is included in the document being created without the user inputting the data again .
  • the persistent data store' 202 can be updated using data from the external data server 200.
  • the content management engine 72 sends a query message 220 to the database 250 of the external data server 200.
  • a response message 222 responding to the query message 220 contains the data required to update the contents of the persistent data store 202.
  • This updating process can be triggered when a specific user initiates communication with the host server 70 and the system recognises the user as having used the system before.
  • a similar access procedure applies in respect of queries to and responses from 320,322 the database 350 of the internal data server 300.
  • the persistent data store 202 will contain all of the data required to select and populate the clauses desired to be included. In such cases the user need not be prompted to provide any new current data for inclusion in the clauses .
  • the adequacy of the data contained in the persistent data store 202 will depend on the extent of previous use, particularly by the current user and the content management engine 72 checks what data is available in the persistent data store during the document creation process. In the case of first time use, the persistent data store 202 will not contain any relevant data on the current user and so the user will need to be prompted 78 to enter all such data 93,95,97. In other cases, the persistent data store 202 will contain some but not all of the data relevant to the clauses selected and so only a limited number of further prompts 78 to the user will need to be generated to get new current data.
  • the content management engine 72 Based on the document creation information provided by the user, the content management engine 72 identifies at least one relevant template 81 and selects content objects 63 and/or collections 65 for insertion at appropriate place holders 73-80. In this way decision information and the data required to create the document is transferred from the user end terminal to the content management engine 72 for use in the document creation process. The user is not required to input data which has already been input during previous visits to the document creation server.
  • the content management engine 72 of the host server 70 runs the compiler software 74 to create the completed document.
  • the compiler software 74 governs the process of populating the templates 81 with clauses and the process of populating clauses with relevant data. Namely, the compiler software 74 controls the insertion of groups 65 of content objects 63 corresponding to the content collections 65 of the content library 57 into respective place holders 79 to 80 of the electronic template 81.
  • the compiler software 74 controls, where appropriate, the insertion of data from the persistent data store 202 as well as the insertion of any new data required by the current process .
  • the compiler software 74 also removes any unwanted place holders and any sections of text around them that are dependent on the place holders.
  • the content management engine 72 stores at the host server the completed document in association with a client identifier 85 indicating who generated the document.
  • the client identifier may comprise a client profile which embodies security applications.
  • the client identifier 85 may include a name that the user specifies, which means something in the context of the document creation process they have gone through (e.g. "NDA for XXX company 02032000") . This is accepted so a user can, at a later date, review the names, dates, versions of documents already created and select one to review or re-process.
  • the content management engine 72 also generates and stores a version identifier 87 and a time stamp 89 in association with the completed document.
  • the version identifier 87 indicates whether or not previous versions of the document have been created and if so, where they are stored.
  • the time stamp • 89 associated with a given document indicates when it was first generated and if applicable, when it was last modified. It will be appreciated that the preferred method can be used to create and deliver a suite of related documents simultaneously. In this case, tags 91 identifying the various documents belonging to the suite are stored in association with the completed documents.
  • the required documentation is constructed by the host server 70 on the system side of the electronic environment according to current data and information provided remotely by a user on the network side of the environment in combination with persistent data and information derived from previous uses stored within the document creation system 5.
  • the persistent data held within the document creation system 5 may be updated by means of remote external and/or internal data servers .
  • the completed document or document suite including clauses populated with data from the persistent data area and any newly provided current data, is converted by converter 55 into a format acceptable to the client terminal 10 and is delivered to the end user terminal via the internet 40. In certain circumstances, for example, when the client terminal 10 accepts XML format, it. is not necessary to employ the converter 55.
  • the user can initiate the document creation process 102 having established a connection to the document creation and delivery website from the client terminal 10.
  • the user may contact the document creation website directly or may establish a connection via another internet node, such as a link from another website.
  • the browser enabled client terminal 10 allows the user to view a document creation screen 104 generated at the host server 70. If the user has used the document creation system 5 before, this fact is recognised by the content management engine 72. In such cases the content management engine 72 knows which persistent data is relevant to the user and where to locate it in the persistent data store. The user is then guided through the document creation process occurring at the host server 70 by the screen on the user end terminal 10.
  • the first thing that the ICM system 50 does in a user session is determine whether the browser 25 in use is capable of supporting XML. This is achieved by means of a simple detection 103 of the browser type in use. Depending upon this, the content management engine 72 will determine whether XML is supported or not and will deliver either XML or say HTML. This is true of all communications between the browser 25 and the ICM system 50, not just the document creation process.
  • the user is led through the process of determining which document types they need and may not necessarily be given a choice in list form from which to select. It is of course possible for the user to select the type of document desired by clicking through options on the display 28 of the client terminal 10.
  • the user may require a single document or a suite of documents comprising a plurality of related documents and this is determined by the content management engine 72 based on the information extracted from the user.
  • the content management engine 72 selects one or more document templates 81 accordingly, see 106. Responsive to the selection of specific templates 81 in step 106, the content management engine 72 presents a series of on-screen prompts to the user. These on-screen prompts typically include a succession of questions to which the user responds by inputting information at the client terminal 10.
  • the questions are generated by the content management engine 72 according to a first set of rules 108 and, where appropriate, a second set of rules 115.
  • the first set of rules 108 comprises a logic tree for generating questions 110 for the user, the responses 111 to which questions identify content for inclusion in the template 71.
  • the number of questions 110 and the subjects to which they relate depend upon the clause selection data 204 available within the persistent data store 202.
  • the content management engine 72 checks whether or not the content selection process is complete. If the content (clauses) selected would not lead to a completed document when correctly populated, then further content selection data 95 is required and further content identification questions are generated according to the first set of rules 108.
  • document creation information may be obtained by the host server 70 directly from one or more servers remote from the host server 70. This will be explained further with reference to a second embodiment shown in Figure 8.
  • persistent data relevant to the population of the clauses selected in step 111 is identified in the persistent data store 202. Some or all of the persistent data may be viewed by the user to verify it is still applicable.
  • the user decides whether to re- enter the persistent data. If any data 97 required to populate a selected clause is not available within the persistent data store 202, a second set of rules 115 is used to generate further questions 116 to guide the user through the provision of the missing data.
  • the second set of rules 115 comprises a logic tree for generating further questions 116 for the user, the responses 117 to which • further questions provide the content management engine 72 with the new data required for inclusion in the current document.
  • This new current information is, where appropriate, added to the persistent data store 202 responsive to it being input by the user.
  • the content management engine 72 checks that all missing data required to complete the document has been extracted from the user. If certain information is still lacking, then the, second set of rules 115 are used to generate further questions for extracting the required data. However, assuming all of the data required to populate the selected clauses is now available the document is created 120 by the content management engine 72.
  • the content management engine 72 of the host server 70 runs the compiler software 74 to compile the document based on a third set of rules 121 which govern the creation process as explained with reference to Figures 4 and 5.
  • the user wishes to alter a document that is within the control of the server, they achieve this by re-running the creation process, which will already be pre-populated with the responses from the last time. These can then be amended on screen and the newly generated document will contain the required modifications. However, if the document is amended outside of the control of the server (i.e. not in the process, e.g. in a word processor after creation), then the server has no knowledge of the changes made and cannot maintain the document in any way afterwards. A document amended in this way, can however be stored back on the server.
  • the created documents are made available and/or delivered in a number of formats, including formats acceptable to a number of word processors (e.g. HTML, RTF) .
  • word processors e.g. HTML, RTF
  • the host server 70 offers the user a choice of alternative formats in which the document can be made available and the user selects a preferred format by clicking on-screen options.
  • the completed document 51 can also be downloaded to the user in the appropriate format.
  • the host server 70 communicates to tell the user the documentation is ready and the user can request the completed document 51 is downloaded. If such a request is received, the document is downloaded.
  • Figure 7 summarises in approximate chronological order the communication of information between the host server 70 and the client terminal 10 during the document creation and delivery process described herein.
  • the user establishes contact with the host server 70.
  • the host server 70 offers a choice of document types which may be created. The user is led through the process of determining which document types they need and may not necessarily be given a choice in list form from which to select.
  • the user inputs a selection of one or more document types.
  • the host server 70 prompts the user for document creation information.
  • the user' s responses are returned to the host server 70.
  • the completed document, including personal data is delivered to the user. Although not shown, the completion of the document process is communicated to the user who may then request a copy is downloaded (see 710) to the client terminal 10.
  • Figure 8 illustrates a second embodiment of the document creation system.
  • This embodiment includes many of the same features as that of Figure 1 and like reference numerals designate like features.
  • the second embodiment comprises a communication path to second 400 and third 800 external data servers.
  • These further external data servers 400,800 comprise databases 402,802 each contain data of a different type.
  • the data on servers 400 and 800 is also different from that of the first external data server 200 or the internal data server 300.
  • the various data servers are selected such that the data one provides is complementary to that of the others .
  • any or all of the first 200, second 400 and third 800 external data servers can be accessed as a source of document creation information, such as information relating to template selection 93, content selection 95 and the population of clauses 97. That is the host server 70 may use data from one or more of the first 200, second 400 and third 800 external data servers at any convenient stage in the document creation process. New data from one or more of the plurality of external data servers may be incorporated into the document creation process as current data 210. For example, data comprised in the document creation information may be obtained by query based access messages 220,420 sent by the host server 70 based on initial document creation information provided by a user. The first and second external data servers 200,400 respond to the messages 220,420 by providing data 222,422 for incorporation into the document creation process as current data 210. In this case the user may be given an opportunity to review the new data to check that it is correct.
  • data from one or more of the plurality of external data servers may be used to update data held in the persistent data store 202.
  • the first 200 and second 400 external data servers can be accessed by query messages 220, 420 sent by the host server 70 to which the first 200 and second 400 external data servers respond 222,422 by providing updated data to be stored in the persistent data store 202.
  • the number of external or internal data sources connected to the document creation system 5 is arbitrary and will depend, for example, upon the application.
  • the use of persistent data in electronic document creation processes makes the process more efficient by reducing the amount of input required from the user.
  • the use of persistent data reduces the probability of errors being carried through the process into the completed document.
  • the facility to source and update persistent data from external and/or internal information servers 200,300 ensures the persistent data is accurate and up-to-date.
  • the distribution of stored content and information about the content between the file system database 56 and the relational database 58 is such that time sliced documentation can be generated. That is, because the data repository 60 records information on when content was created, last modified etc., for each of the content objects 63 in the content library 57 and for the persistent data 204,206, versions of the documentation applicable at any given point in time can be accessed or regenerated.
  • versions of completed documents stored after the document creation process are labelled with a time stamp 89 and version identifier 87, these documents can be re-generated on demand.
  • the user identifier 85 and related document tags 91 enable a given user to access or regenerate documentation created by that user previously. Since any new information provided by the user is stored in the persistent data store 202, the persistent data information resource develops with time.
  • the content of the persistent data store 202 can be updated wherever appropriate with data from the external 200 and/or internal 300 information sources.
  • the system 50 can make comparisons between older versions of content and/or older versions of complete documents to ascertain where updating or checking by the user is likely to be useful. For example, such comparisons may indicate which types of persistent data require updating most frequently and where the relevant information was obtained last time.
  • Implementation of the invention should not be limited to the configuration of the described embodiment.
  • the described embodiment is an example of a configuration which may be used to implement a preferred method and is not intended to define the only type of configuration or order of apparatus features/method steps which can be used.
  • the persistent data store 202 may be independent or comprised in a larger data storage unit. It may have any structure suitable for the application. For example, it may or may not be divided into separate parts as illustrated in Figures 4, 5 and 6. Moreover, if it is divided into separate parts, the persistent data may be stored in a plurality o * f different data storage spaces located apart from one another. These data storage units can be distributed over several hardware components. In another modification the persistent data store is provided in a storage unit separate to and/or remote from the host server 70. Data in one server may replicate some or all of the data in another server as may be required by the application. In one modification, a communication route other than the internet path is provided between the internet content management system 50 and the external information server 200. This type of dedicated communication path can provide security advantages in some circumstances.
  • the persistent data store 202 By querying the remote information servers 200,300 at appropriate points in time messaging is kept to a minimum and storage space in the persistent data store is used effectively. It is possible for the persistent data store 202 to be updated at predetermined intervals, for example under the control of the host server 70. However, in another modification all or part of the information held in the databases of the remote servers 200,300 is replicated in the persistent data store 202 and updated as necessary.
  • the mechanism by which the host server 70 recognises a user who has used the document creation system before, may involve entry of a user name/password.
  • this recognition function may be implemented using "cookies" which are transparent to the user.
  • a substantially complete document can be downloaded to or otherwise accessed by one or more users at client terminals, whereby a user can alter at the client terminal text in the document.
  • the altered document can then be transmitted in electronic form to the host server maintained or re-stored at the host server. It is stored at the host server in association with a user identifier ' and profile which may embody security applications .
  • the delivery network can be a different type of network e.g., any type of fixed network such as PSTN, a mobile network such as PLMN, satellite, cable or intranet type networks. Typically however, it will be a TCP/IP based network comprising, for example, routers, ISP's, dial-up connections etc .
  • client terminals 10 have browser capability in line with http client technology.
  • client terminals 10 may include, for example a web T.V., a personal digital assistant or a WAP handset.
  • the configuration of the internet content management system 50 namely the arrangement and inter-dependence of the various functional elements including the converters 53 and 55, the content management engine 72, and the databases 56 and 58, may be varied within the scope of the invention as defined in the claims and will inevitably depend upon the application.
  • a host server 70 this term should be construed to include any network element or group of network elements with appropriate functionality.
  • a method of operating a computer system to create a sequence of documents according to an automated document creation process comprising: identifying a user at the client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining document creation information; receiving at the host server in electronic form responses to said prompts which include current data and persistent data specific to the user for populating the documents; storing said persistent user specific data at the host server for use in the current and subsequent document creation processes ; executing a first document creation process to generate a complete document including said user specific data; and subsequently, executing a second document creation process using different current data generated by the user and the persistent data received during the first document creation process .
  • responses include user specific information for identifying clauses to be included in a document, said user specific information being stored with said persistent data for use in a subsequent document creation process .
  • a method as in any preceding claim which comprises the step of updating the persistent data from a data source separate from the client terminal.
  • a method of operating a computer system to create documents according to an automated document creation process comprising a host server and at least one client terminal, the process comprising: identifying a user at a client terminal; transmitting in electronic form from the host server to the client terminal prompts to ' the " user for obtaining initial document creation information; receiving at the host server said initial document creation information responsive to said prompts; obtaining further document creation information from a plurality of remote data servers, said further document creation information including data specific to the user for inclusion in the document; and executing a first document creation process to generate a document including said initial and further document creation information.
  • An internet based document creation system for creating documents according to an automated document creation process performed at a host server connected to at least one remote client terminal, the host server comprising: storage means holding a plurality of document templates and a set of clauses associated with said templates; a persistent data store holding persistent user specific data for inclusion in said clauses in the current and subsequent document creation processes; a current data store for holding user specific data for use in the current document creation process only; a process for executing a document creation program to generate at least one complete document based on user inputs including document creation information identifying at least one document template, clauses for inclusion therein and current user specific data, said document creation process also using said persistent data; and document delivery means for delivering the complete document in electronic form to the client terminal.
  • a computer program product comprising code means stored in a computer readable medium, the program code means being adapted to perform any of steps of claim 16, when run on a computer.

Abstract

A method of operating a computer system to create a sequence of documents involves the steps of identifying a user at a client terminal and transmitting prompts to the user to obtain document creation information. The responses from a user are used to populate documents along with persistent user data.

Description

MULTIPLE DOCUMENT CREATION METHOD AND SYSTEM
This invention relates to a method and apparatus for document creation and particularly to electronic document creation using persistent data.
It is an object of the present invention to provide an improved document creation system.
In the context of the present invention the term "persistent data" refers to data used in a document creation process which is retained by the document creation system for use in a subsequent document creation process. The persistent data may comprise user specific data used in the selection of content for inclusion in the document and/or user specific data for populating the selected content. For example, a response or a sequence of responses made by a user to determine which content is included may be captured by the document creation system and retained for use in a subsequent process . Alternatively, or additionally, responses of a user may provide particulars relating specifically to a variable such as the name of a legal person mentioned in a clause of a document. Such information may be of use in a subsequent document creation process performed by the same user or requiring the same variable and so it is retained by the document creation system. Accordingly, responses providing that information need not be input again.
According to a first aspect of the present invention, there is provided a method of operating a computer system to create a sequence of documents according to an automated document creation process, the computer system comprising a host server and at least one client terminal, the process comprising: identifying a user at the client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining document creation information; receiving at the host server in electronic form responses to said prompts which include current data and persistent specific to the user for populating the documents; storing said persistent user specific data at the host server for use in the current and subsequent document creation processes; executing a first document creation process to generate a complete document including said user specific data; and subsequently, executing a second document creation process using different current data generated by the user and the persistent data received during the first document creation process.
Preferably, said responses include user specific information for identifying clauses to be included in a document, said user specific information being stored with said persistent data for use in a subsequent document creation process.
Preferred methods comprise the step of updating the persistent data from a data source separate from the client terminal.
Preferably, the data source is located remote-ly- -from the host server used' in the document creation process. Such a data source is operated and controlled independently of the document creation process.
Preferably, the host server is connected to the data source by one of the internet and a dedicated communication path.
In preferred embodiments fresh data is transmitted to said host server from said data source responsive to a query therefrom. This type of query is triggered by recognition of a user. Other embodiments of the method comprise periodically updating the persistent data from the data source at intervals according to a predetermined schedule.
Persistent user specific data can be entered into two or more documents which are generated simultaneously in a document creation process.
According to another aspect of the invention, there is provided a method of operating a computer system to create documents according to an automated document creation process, the computer system comprising a host server and at least one client terminal, the process comprising: identifying a user at a client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining initial document creation information; receiving at the host server said initial document creation information responsive to said prompts; obtaining further document creation information from a plurality of remote data servers, said further document creation information including data specific to the user for inclusion in the document; and executing a first document creation process to generate a document including "said initial and further document creation information.
According to another aspect of the invention, there is provided an internet based document creation system for creating documents according to an automated document creation process performed at a host server connected to at least one remote client terminal, the host server comprising: storage means holding a plurality of document templates and a set of clauses associated with said templates; a persistent data store holding persistent user specific data for inclusion in said clauses in the current and subsequent document creation processes; a current data store for holding user specific data for use in the current document creation process only; a processor for executing a document creation program to generate at least one complete document based on user inputs including document creation information identifying at least one document template, clauses for inclusion therein and current user specific data, said document creation process also using said persistent data; and document delivery means for delivering the complete document in electronic form to the client terminal.
According to another aspect of the present invention there is provided a method of creating a document in a computer system comprising a host server and at least one remote client terminal connected by a data transmission path in which method: the host server and client terminal exchange messages to enable automatic creation of a plurality of documents at the host server; document content and variables for populating said content being selected responsive to inputs made by a user at the client terminal, wherein a single electronic template is used to generate said plurality of documents .
Preferably, the document creation system comprises a computer program product comprising code means stored on a computer readable medium, the program code means being adapted to perform the steps in the document creation process, when run on a computer .
According to another aspect of the present invention, there is provided a document creation process capable of generating a suite of documents from a single multi-document template. For a better understanding of the present invention and as to how the same may be carried into effect, reference will now be made by way of example to the accompanying drawings, in which:
Figure 1 illustrates an embodiment of a document creation system;
Figure 2 illustrates a client terminal for use in the system of Figure 1;
Figure 3 illustrates an internet content management system for use in the system of Figure 1;
Figure 4 illustrates schematically how the internet content management system of Figure 3 creates and delivers a document;
Figure 5 illustrates schematically how documents are created by the internet content management system of Figure 3;
Figure 6 illustrates schematically method steps in the process of document creation and delivery by the system of Figure 1;
Figure 7 illustrates schematically the exchange of information occurring in document creation and delivery systems according to Figure 1; and
Figure 8 illustrates a second embodiment of a document creation system.
Figure 1 illustrates schematically an electronic document creation system generally designated by reference numeral 5. The document creation system 5 includes an internet content management system 50 implemented at a host server which is connected via a gateway 41 to the internet 40. A plurality of client terminals 10 are connected to the internet 40 remote from the internet content management system 50 by respective modems 24. A data server 200 is also connected to the internet 40 by means of a gateway 201. A broken line designated by reference numeral 11 schematically illustrates the boundary between the "system side" on which the internet content management system 50 is located and the "network side" on which the internet 40, the data server 200 and the client terminals 10 are located.
The embodiment illustrated in Figure 1 receives from a client terminal 10 via the internet 40 information necessary to create electronic documents on the server side of the electronic environment and thereafter delivers completed electronic documents to users on the network side via the internet 40. As will be explained below, the document creation system 5 includes a persistent data store containing specific data useful over a number of document creation processes and a current data store for holding data for the current document creation process only. The persistent data store can be updated using data from sources connected to the document creation system 5, such as data server 200.
Figure 2 illustrates a preferred client terminal 10 for the document creation system of Figure 1. The client terminal 10 is a personal computer which includes a processor 12, a clock generation circuit 14 connected to the processor, a read only memory 18 and a random access memory 16. Both of the read only memory 18 and the random access memory 16 can be accessed by the CPU 12. The client terminal 10 also has a communication port 22 connected to an external modem 24. The modem 24 is connected to the internet 40 as illustrated in Figure 1. The client terminal 10 has externally connected display and input devices 28,32. The display 28 and input 32 devices are supported by driver software 26,30, respectively. The client terminal 10 is also provided with browser software 25. The client terminal 10 thus has browser capability and enables the user to interface from a remote location with the system side of the document creation system 5.
Figure 3 illustrates components of the internet content management system 50 shown in the document creation system 5 of Figure 1. The internet content management system 50 includes elements for receiving and deconstructing source documents, storing document content and for extracting previously stored content to be included in documents being created. The internet content management system 50 comprises an input converter 53 and a host server 70. The input converter 53 receives source documents 52 and converts the content of the source documents 52 into extensible markup language (XML) format. The host server 70 has processor functionality. The server 70 comprises a content management engine 72 which functions as a contract creation module (CCM) and a data repository 60 in which the content of source documents 52 and persistent data for use in the document creation process are stored. The data repository 60 ' thus comprises a persistent data store 202 which contains user specific data of use in- the current document creation process which is desired to be retained for use in a subsequent document creation process.
The data repository 60 includes a file system database 56 and a relational database 58. The file system database 56' stores XML content extracted from the source documents 52. The relational database 58 stores information about that content and comprises the persistent data store 202. For example the relational database 58 may store information on who created the content, when it was created, when it was last modified, labels identifying specific portions of content, cross references between related portions of content and data relating specifically to persons who have previously used the document creation and delivery service. The content management engine 72 of the server 70 can write to and extract information from the data repository 60. An external data server 200 and an internal data server 300 are connected to the relational database 58 of the data repository 60 and can supply information to the persistent data store 202 contained therein. Subject matter in XML format may also be stored in the relational database 58 and, although not shown, this database can also be connected to an external data server.
The host server 70 also comprises a current data store 210 for storing data required only in respect of the current document creation process. The content management engine 72 is provided with software 74 for compiling documents created for the user as will be explained below." The host server 70 also comprises an output converter 55 which can convert a newly created document from XML format into a format acceptable to the intended recipient, i.e. a user at a client terminal 10.
A document creation process of the system 5 shown in Figure 1 will now be explained with reference to Figures 3 to 1 . , Referring to Figure 4, source documents 52 are supplied to the input converter 53. The input converter 53 is implemented in software on a server other than the internet content management server 70 and can accept source documents in a plurality of different electronic formats. The input converter 53' could of course be implemented on the host server 70. For example, the converter 53 can accept documents in commercially available word processing and other recognised formats. The converter 53 comprises software filters which are used to convert the received document from its original format into XML format. The content in XML format is then transferred to the content management engine 72 of the host server 70.
The content management engine 72 deconstructs each source document 52 and stores content objects and information about those content objects in the data repository 60. Information held in the data repository 60 includes a content library 57, labels and cross references 59 relating to the content objects in the content library, document templates 81 having various predefined structures and a persistent data store 202.
The content management engine 72 of the host server 70 can communicate with the user over the internet by means of . the browser enabled client terminal 10. The user provides the document creation information 93,95 and data 97 necessary to construct the document as will be explained below. The content management engine 72 sends prompts 78 to the user at the client terminal 10 to guide the user through the document creation process being performed at the host server 70. The user is prompted to enter information 93 regarding the nature of the required documentation which is used to identify a relevant template or set of templates. The user is further prompted to provide information 95 to enable the selection of content (clauses) for the document. Where appropriate, the user can also provide specific data 97 for populating any clauses of the document requiring such data. Information and data 93,95,97 which is entered for use in the current document creation process is temporarily buffered at the host server in the current data store 210. Information and data likely to be of use in a subsequent document creation process 93,95,97 is stored in the persistent data store 202. The persistent data store 202 contains a first type of user specific information 204 relating to the selection of clauses for inclusion in the document as well as a second type of user specific data 206 for inclusion in the clauses of the document being created. The persistent data store is connected to an external data server 200 and an internal data server 300.
The external data server 200 is located on the network side of the electronic environment and is maintained independently of the document creation system 5 by a third party. The external data server 200 includes a database 250 containing data relevant for document creation and useful for updating the data held in the persistent data store 202. For example, the external data server 200 may include data on legal persons such as limited companies .
The data server 300 is located on the system side of the electronic environment and. is maintained under the control of the operator of the document creation system 5. The internal data server 300 also includes a database 350 containing data relevant to document creation and useful for updating the data held in the persistent data store 202. For example, the internal data server 300 may comprise a database containing particulars of a company's clients.
The current data store 210 is used to (temporarily) buffer user responses providing document creation information and data for populating clauses in the document currently being created. The information and data stored in the current data store 210 of Figure 4 relates to the present selection of a template 93, the selection of document content 95 and the population of clauses 97 comprised in the selected content. Referring now to Figure 5, the content library 57 held in the data repository 60 includes the content of source documents 52. The content is stored in the form of a plurality of content objects 63 each of which corresponds to a document component. In the described embodiment, the document components are clauses for example of a legal document. The content objects 63 are labelled according to the type of document to which they relate. For example, this may be achieved by regarding the content objects 63 as belonging to a plurality of collections 65 A, B, C ... X, Y based on their subject matter. The content objects 63 of each collection 65 are also labelled with structural identifiers 67 indicating to which section of a document template 81 they relate. Different structural identifiers 67 may relate to, for example, heading sections, overview sections, detail sections and appendices .
Related collections 65 are cross-referenced 69. For example, collections of content about a general clause may have relevance only to certain other collections of content previously selected by the user.
An electronic document template such as that indicated by reference numeral 81 of Figure 5 is provided for each different suite of documents. Each document template 81 comprises a number of documents 71 each having a predetermined structure defined by a plurality of sections 67 for receiving content objects 63. The templates 81 have various structures which depend upon the type of documentation intended to be created therefrom. The template 81 indicated includes a plurality of separate sections 67 comprising a mixture of text such as heading, overview, detail, appendix and personal, and place holders, as required. The place holders 73-80 act as insertion points for the content appropriate to that section. In preferred embodiments, groups 65 of logically associated content objects 63 are selected from the content library 57 simultaneously. These groups 65' of logically associated content objects 63 correspond to the "collections" 65 of the content library 57. Some content objects 63 from a collection 65 may be used in multiple documents 71 and/or templates 81 in processes where two or more resultant documents are being created simultaneously.
Whenever available, the content management engine 72 uses data from the persistent data store 202 in the document creation process. If the user has used the document creation server before a considerable amount of the relevant document creation information and data for populating clauses may be available within the persistent data store. Referring to Figure 5, previously inserted data 204 relating to the selection of clauses can be used to extract appropriate document content 63 or collections 65 from the content library 57. Additionally, or alternatively, previously inserted data 206 for populating the clauses can be included in the group 65 of logically associated content objects before it is applied to the template 81. It is possible for data from the persistent data store 202 to be inserted into one or more different documents 71 or sections 67 thereof simultaneously. Thus, data provided by users during previous uses of the document creation system 5 is included in the document being created without the user inputting the data again .
Referring back to Figure 4, the persistent data store' 202 can be updated using data from the external data server 200. The content management engine 72 sends a query message 220 to the database 250 of the external data server 200. A response message 222 responding to the query message 220 contains the data required to update the contents of the persistent data store 202. This updating process can be triggered when a specific user initiates communication with the host server 70 and the system recognises the user as having used the system before. A similar access procedure applies in respect of queries to and responses from 320,322 the database 350 of the internal data server 300.
In some circumstances, the persistent data store 202 will contain all of the data required to select and populate the clauses desired to be included. In such cases the user need not be prompted to provide any new current data for inclusion in the clauses . The adequacy of the data contained in the persistent data store 202 will depend on the extent of previous use, particularly by the current user and the content management engine 72 checks what data is available in the persistent data store during the document creation process. In the case of first time use, the persistent data store 202 will not contain any relevant data on the current user and so the user will need to be prompted 78 to enter all such data 93,95,97. In other cases, the persistent data store 202 will contain some but not all of the data relevant to the clauses selected and so only a limited number of further prompts 78 to the user will need to be generated to get new current data.
Based on the document creation information provided by the user, the content management engine 72 identifies at least one relevant template 81 and selects content objects 63 and/or collections 65 for insertion at appropriate place holders 73-80. In this way decision information and the data required to create the document is transferred from the user end terminal to the content management engine 72 for use in the document creation process. The user is not required to input data which has already been input during previous visits to the document creation server.
The content management engine 72 of the host server 70 runs the compiler software 74 to create the completed document. The compiler software 74 governs the process of populating the templates 81 with clauses and the process of populating clauses with relevant data. Namely, the compiler software 74 controls the insertion of groups 65 of content objects 63 corresponding to the content collections 65 of the content library 57 into respective place holders 79 to 80 of the electronic template 81. The compiler software 74 controls, where appropriate, the insertion of data from the persistent data store 202 as well as the insertion of any new data required by the current process . The compiler software 74 also removes any unwanted place holders and any sections of text around them that are dependent on the place holders.
When the document creation process is concluded, the content management engine 72 stores at the host server the completed document in association with a client identifier 85 indicating who generated the document. The client identifier may comprise a client profile which embodies security applications. The client identifier 85 may include a name that the user specifies, which means something in the context of the document creation process they have gone through (e.g. "NDA for XXX company 02032000") . This is accepted so a user can, at a later date, review the names, dates, versions of documents already created and select one to review or re-process. The content management engine 72 also generates and stores a version identifier 87 and a time stamp 89 in association with the completed document. The version identifier 87 indicates whether or not previous versions of the document have been created and if so, where they are stored. The time stamp 89 associated with a given document indicates when it was first generated and if applicable, when it was last modified. It will be appreciated that the preferred method can be used to create and deliver a suite of related documents simultaneously. In this case, tags 91 identifying the various documents belonging to the suite are stored in association with the completed documents.
Thus the required documentation is constructed by the host server 70 on the system side of the electronic environment according to current data and information provided remotely by a user on the network side of the environment in combination with persistent data and information derived from previous uses stored within the document creation system 5. The persistent data held within the document creation system 5 may be updated by means of remote external and/or internal data servers . The completed document or document suite, including clauses populated with data from the persistent data area and any newly provided current data, is converted by converter 55 into a format acceptable to the client terminal 10 and is delivered to the end user terminal via the internet 40. In certain circumstances, for example, when the client terminal 10 accepts XML format, it. is not necessary to employ the converter 55.
Referring to Figure 6, the user can initiate the document creation process 102 having established a connection to the document creation and delivery website from the client terminal 10. The user may contact the document creation website directly or may establish a connection via another internet node, such as a link from another website. While the connection is established, the browser enabled client terminal 10 allows the user to view a document creation screen 104 generated at the host server 70. If the user has used the document creation system 5 before, this fact is recognised by the content management engine 72. In such cases the content management engine 72 knows which persistent data is relevant to the user and where to locate it in the persistent data store. The user is then guided through the document creation process occurring at the host server 70 by the screen on the user end terminal 10.
The first thing that the ICM system 50 does in a user session is determine whether the browser 25 in use is capable of supporting XML. This is achieved by means of a simple detection 103 of the browser type in use. Depending upon this, the content management engine 72 will determine whether XML is supported or not and will deliver either XML or say HTML. This is true of all communications between the browser 25 and the ICM system 50, not just the document creation process.
The user is led through the process of determining which document types they need and may not necessarily be given a choice in list form from which to select. It is of course possible for the user to select the type of document desired by clicking through options on the display 28 of the client terminal 10. The user may require a single document or a suite of documents comprising a plurality of related documents and this is determined by the content management engine 72 based on the information extracted from the user. The content management engine 72 selects one or more document templates 81 accordingly, see 106. Responsive to the selection of specific templates 81 in step 106, the content management engine 72 presents a series of on-screen prompts to the user. These on-screen prompts typically include a succession of questions to which the user responds by inputting information at the client terminal 10. The questions are generated by the content management engine 72 according to a first set of rules 108 and, where appropriate, a second set of rules 115. The first set of rules 108 comprises a logic tree for generating questions 110 for the user, the responses 111 to which questions identify content for inclusion in the template 71. The number of questions 110 and the subjects to which they relate depend upon the clause selection data 204 available within the persistent data store 202. At step 112, the content management engine 72 checks whether or not the content selection process is complete. If the content (clauses) selected would not lead to a completed document when correctly populated, then further content selection data 95 is required and further content identification questions are generated according to the first set of rules 108. Alternatively, or in addition, document creation information may be obtained by the host server 70 directly from one or more servers remote from the host server 70. This will be explained further with reference to a second embodiment shown in Figure 8.
If the content selection process is complete then persistent data relevant to the population of the clauses selected in step 111 is identified in the persistent data store 202. Some or all of the persistent data may be viewed by the user to verify it is still applicable. At step 114, the user decides whether to re- enter the persistent data. If any data 97 required to populate a selected clause is not available within the persistent data store 202, a second set of rules 115 is used to generate further questions 116 to guide the user through the provision of the missing data. The second set of rules 115 comprises a logic tree for generating further questions 116 for the user, the responses 117 to which further questions provide the content management engine 72 with the new data required for inclusion in the current document. This new current information is, where appropriate, added to the persistent data store 202 responsive to it being input by the user. At step 118, the content management engine 72 checks that all missing data required to complete the document has been extracted from the user. If certain information is still lacking, then the, second set of rules 115 are used to generate further questions for extracting the required data. However, assuming all of the data required to populate the selected clauses is now available the document is created 120 by the content management engine 72. The content management engine 72 of the host server 70 runs the compiler software 74 to compile the document based on a third set of rules 121 which govern the creation process as explained with reference to Figures 4 and 5.
If the user wishes to alter a document that is within the control of the server, they achieve this by re-running the creation process, which will already be pre-populated with the responses from the last time. These can then be amended on screen and the newly generated document will contain the required modifications. However, if the document is amended outside of the control of the server (i.e. not in the process, e.g. in a word processor after creation), then the server has no knowledge of the changes made and cannot maintain the document in any way afterwards. A document amended in this way, can however be stored back on the server.
In the document creation process, the created documents are made available and/or delivered in a number of formats, including formats acceptable to a number of word processors (e.g. HTML, RTF) . These are not native word processing formats, but are formats that are supported and can be read by commercially available word processors.
The host server 70 offers the user a choice of alternative formats in which the document can be made available and the user selects a preferred format by clicking on-screen options. The completed document 51 can also be downloaded to the user in the appropriate format.
The host server 70 communicates to tell the user the documentation is ready and the user can request the completed document 51 is downloaded. If such a request is received, the document is downloaded.
Figure 7 summarises in approximate chronological order the communication of information between the host server 70 and the client terminal 10 during the document creation and delivery process described herein. At step 700 the user establishes contact with the host server 70. At step 702 the host server 70 offers a choice of document types which may be created. The user is led through the process of determining which document types they need and may not necessarily be given a choice in list form from which to select. At step 704 the user inputs a selection of one or more document types. At step 706 the host server 70 prompts the user for document creation information. At step 708 the user' s responses are returned to the host server 70. At step 709 the completed document, including personal data, is delivered to the user. Although not shown, the completion of the document process is communicated to the user who may then request a copy is downloaded (see 710) to the client terminal 10.
Figure 8 illustrates a second embodiment of the document creation system. This embodiment includes many of the same features as that of Figure 1 and like reference numerals designate like features. The second embodiment comprises a communication path to second 400 and third 800 external data servers. These further external data servers 400,800 comprise databases 402,802 each contain data of a different type. The data on servers 400 and 800 is also different from that of the first external data server 200 or the internal data server 300. The various data servers are selected such that the data one provides is complementary to that of the others .
Any or all of the first 200, second 400 and third 800 external data servers can be accessed as a source of document creation information, such as information relating to template selection 93, content selection 95 and the population of clauses 97. That is the host server 70 may use data from one or more of the first 200, second 400 and third 800 external data servers at any convenient stage in the document creation process. New data from one or more of the plurality of external data servers may be incorporated into the document creation process as current data 210. For example, data comprised in the document creation information may be obtained by query based access messages 220,420 sent by the host server 70 based on initial document creation information provided by a user. The first and second external data servers 200,400 respond to the messages 220,420 by providing data 222,422 for incorporation into the document creation process as current data 210. In this case the user may be given an opportunity to review the new data to check that it is correct.
Alternatively, or in addition, data from one or more of the plurality of external data servers may be used to update data held in the persistent data store 202.
For example, the first 200 and second 400 external data servers can be accessed by query messages 220, 420 sent by the host server 70 to which the first 200 and second 400 external data servers respond 222,422 by providing updated data to be stored in the persistent data store 202.
The number of external or internal data sources connected to the document creation system 5 is arbitrary and will depend, for example, upon the application.
The use of persistent data in electronic document creation processes makes the process more efficient by reducing the amount of input required from the user. In addition, the use of persistent data reduces the probability of errors being carried through the process into the completed document. The facility to source and update persistent data from external and/or internal information servers 200,300 ensures the persistent data is accurate and up-to-date.
The distribution of stored content and information about the content between the file system database 56 and the relational database 58 is such that time sliced documentation can be generated. That is, because the data repository 60 records information on when content was created, last modified etc., for each of the content objects 63 in the content library 57 and for the persistent data 204,206, versions of the documentation applicable at any given point in time can be accessed or regenerated.
In addition, since versions of completed documents stored after the document creation process are labelled with a time stamp 89 and version identifier 87, these documents can be re-generated on demand. The user identifier 85 and related document tags 91 enable a given user to access or regenerate documentation created by that user previously. Since any new information provided by the user is stored in the persistent data store 202, the persistent data information resource develops with time. The content of the persistent data store 202 can be updated wherever appropriate with data from the external 200 and/or internal 300 information sources.
The system 50 can make comparisons between older versions of content and/or older versions of complete documents to ascertain where updating or checking by the user is likely to be useful. For example, such comparisons may indicate which types of persistent data require updating most frequently and where the relevant information was obtained last time.
Implementation of the invention should not be limited to the configuration of the described embodiment. Specifically, the described embodiment is an example of a configuration which may be used to implement a preferred method and is not intended to define the only type of configuration or order of apparatus features/method steps which can be used.
The persistent data store 202 may be independent or comprised in a larger data storage unit. It may have any structure suitable for the application. For example, it may or may not be divided into separate parts as illustrated in Figures 4, 5 and 6. Moreover, if it is divided into separate parts, the persistent data may be stored in a plurality o *f different data storage spaces located apart from one another. These data storage units can be distributed over several hardware components. In another modification the persistent data store is provided in a storage unit separate to and/or remote from the host server 70. Data in one server may replicate some or all of the data in another server as may be required by the application. In one modification, a communication route other than the internet path is provided between the internet content management system 50 and the external information server 200. This type of dedicated communication path can provide security advantages in some circumstances.
By querying the remote information servers 200,300 at appropriate points in time messaging is kept to a minimum and storage space in the persistent data store is used effectively. It is possible for the persistent data store 202 to be updated at predetermined intervals, for example under the control of the host server 70. However, in another modification all or part of the information held in the databases of the remote servers 200,300 is replicated in the persistent data store 202 and updated as necessary.
The mechanism by which the host server 70 recognises a user who has used the document creation system before, may involve entry of a user name/password. Alternatively, this recognition function may be implemented using "cookies" which are transparent to the user.
Thus a substantially complete document can be downloaded to or otherwise accessed by one or more users at client terminals, whereby a user can alter at the client terminal text in the document. The altered document can then be transmitted in electronic form to the host server maintained or re-stored at the host server. It is stored at the host server in association with a user identifier ' and profile which may embody security applications .
Completed documents may be transmitted to or otherwise made available to users in formats selected bv the users. Although in the described embodiment, the document is delivered via the internet, the delivery network can be a different type of network e.g., any type of fixed network such as PSTN, a mobile network such as PLMN, satellite, cable or intranet type networks. Typically however, it will be a TCP/IP based network comprising, for example, routers, ISP's, dial-up connections etc .
The client terminals 10 have browser capability in line with http client technology. In other embodiments, client terminals 10 may include, for example a web T.V., a personal digital assistant or a WAP handset.
The configuration of the internet content management system 50, namely the arrangement and inter-dependence of the various functional elements including the converters 53 and 55, the content management engine 72, and the databases 56 and 58, may be varied within the scope of the invention as defined in the claims and will inevitably depend upon the application. Although the specific description of preferred embodiments refers to a "host server 70", this term should be construed to include any network element or group of network elements with appropriate functionality.
CLAIMS :
1. A method of operating a computer system to create a sequence of documents according to an automated document creation process, the computer system comprising a host server and at least one client terminal, the process comprising: identifying a user at the client terminal; transmitting in electronic form from the host server to the client terminal prompts to the user for obtaining document creation information; receiving at the host server in electronic form responses to said prompts which include current data and persistent data specific to the user for populating the documents; storing said persistent user specific data at the host server for use in the current and subsequent document creation processes ; executing a first document creation process to generate a complete document including said user specific data; and subsequently, executing a second document creation process using different current data generated by the user and the persistent data received during the first document creation process .
2. A method as in claim 1, wherein said responses include user specific information for identifying clauses to be included in a document, said user specific information being stored with said persistent data for use in a subsequent document creation process .
3. A method as in claim 1 or 2, wherein the computer system includes a data repository which holds document creation information and version information relating to the document creation information such that documents can be regenerated subsequently as at a given point in time.
4. A method as in any preceding claim, wherein said persistent user specific data is entered into two or more documents which are generated simultaneously by a document creation process.
5. A method as in any preceding claim, which comprises the step of updating the persistent data from a data source separate from the client terminal.
6. A method as in claim 5, wherein the data source is located remotely from the host server used in the document creation process .
7. A method as in claim 5 or 6, wherein the data source is operated and controlled independently of the document creation process .
8. A method as in any of claims 5 to 7, wherein the host server is connected to the data source by one of the internet and a dedicated communication path.
9. A method as in any of claims 5 to 8, wherein fresh data is transmitted to said host server from said data source responsive to a query therefrom.
10. A method as in claim 9, wherein said query is triggered by a recognised user.
11. A method as in any of claims 5 to 9, which comprises periodically updating the persistent data from the data source at intervals according to a predetermined schedule. 12. A method as in any of claims 5 to 11, wherein document creation information is obtained from a plurality of remote data sources .
13. A method of operating a computer system to create documents according to an automated document creation process, the computer system comprising a host server and at least one client terminal, the process comprising: identifying a user at a client terminal; transmitting in electronic form from the host server to the client terminal prompts to ' the" user for obtaining initial document creation information; receiving at the host server said initial document creation information responsive to said prompts; obtaining further document creation information from a plurality of remote data servers, said further document creation information including data specific to the user for inclusion in the document; and executing a first document creation process to generate a document including said initial and further document creation information.
14. A method as in any of claims 5 to 13, wherein the user verifies the accuracy of document creation information obtained from a remote server.
15. A method as in any of claims 5 to 14, wherein document creation information obtained from a plurality of remote data sources is used to update a persistent data store.
16. An internet based document creation system for creating documents according to an automated document creation process performed at a host server connected to at least one remote client terminal, the host server comprising: storage means holding a plurality of document templates and a set of clauses associated with said templates; a persistent data store holding persistent user specific data for inclusion in said clauses in the current and subsequent document creation processes; a current data store for holding user specific data for use in the current document creation process only; a process for executing a document creation program to generate at least one complete document based on user inputs including document creation information identifying at least one document template, clauses for inclusion therein and current user specific data, said document creation process also using said persistent data; and document delivery means for delivering the complete document in electronic form to the client terminal.
17. A computer program product comprising code means stored in a computer readable medium, the program code means being adapted to perform any of steps of claim 16, when run on a computer.
PCT/GB2001/002765 2000-06-22 2001-06-22 Multiple document creation method and system WO2001098940A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001266149A AU2001266149A1 (en) 2000-06-22 2001-06-22 Multiple document creation method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0015363.5 2000-06-22
GB0015363A GB2368949A (en) 2000-06-22 2000-06-22 Document creation

Publications (1)

Publication Number Publication Date
WO2001098940A1 true WO2001098940A1 (en) 2001-12-27

Family

ID=9894220

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2001/002765 WO2001098940A1 (en) 2000-06-22 2001-06-22 Multiple document creation method and system

Country Status (3)

Country Link
AU (1) AU2001266149A1 (en)
GB (1) GB2368949A (en)
WO (1) WO2001098940A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024018184A1 (en) * 2022-07-18 2024-01-25 Gamiet Khaled Document generation and editing system

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2374964A (en) * 2001-01-31 2002-10-30 Epoch Software Holdings Plc Editing and formatting of assembled documents

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5272623A (en) * 1990-11-07 1993-12-21 The United States Of America As Represented By The Secretary Of The Navy Software programming method for forming Government contracting documents
US5563998A (en) * 1990-10-19 1996-10-08 Moore Business Forms, Inc. Forms automation system implementation
US5729751A (en) * 1995-03-15 1998-03-17 Automated Legal Systems, Inc. Document assembly system with assembly logic

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5987480A (en) * 1996-07-25 1999-11-16 Donohue; Michael Method and system for delivering documents customized for a particular user over the internet using imbedded dynamic content
WO2001031488A2 (en) * 1999-10-28 2001-05-03 B4Bpartner, Inc. Electronic document/form generator
US20030188261A1 (en) * 2000-03-17 2003-10-02 Smith Peter Thomas Form production system
AU2001245744A1 (en) * 2000-04-14 2001-10-30 Yodlee.Com, Inc. Method and apparatus for providing auto-registration and service access to internet sites for internet portal subscribers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5563998A (en) * 1990-10-19 1996-10-08 Moore Business Forms, Inc. Forms automation system implementation
US5272623A (en) * 1990-11-07 1993-12-21 The United States Of America As Represented By The Secretary Of The Navy Software programming method for forming Government contracting documents
US5729751A (en) * 1995-03-15 1998-03-17 Automated Legal Systems, Inc. Document assembly system with assembly logic

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
N.N.: "ELECTRONIC FORMS, DocNet, Visioneer's PaperPort(R), OmniForm 4.01", INTERCON, 1998, XP002146925 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024018184A1 (en) * 2022-07-18 2024-01-25 Gamiet Khaled Document generation and editing system

Also Published As

Publication number Publication date
GB0015363D0 (en) 2000-08-16
GB2368949A (en) 2002-05-15
AU2001266149A1 (en) 2002-01-02

Similar Documents

Publication Publication Date Title
US20020046235A1 (en) Document creation and delivery
US7058857B2 (en) Method and system for testing a software product
US7904595B2 (en) Globalization management system and method therefor
JP4437918B2 (en) Apparatus and method for selectively retrieving information and subsequently displaying the information
US20020129059A1 (en) XML auto map generator
US20050034065A1 (en) Method and apparatus for processing content
KR100750962B1 (en) Parsing structured data
JP2006172444A (en) Actionable email document
US11842231B2 (en) Cloud-based API metadata management method and system for integrated API management
CN111767704B (en) Excel form template generation method and device
WO2001057652A2 (en) Method and system for building internet-based applications
US20060089940A1 (en) Instantaneous integrated system and method of heterogeneous databases
US20030167262A1 (en) Cross-search method and cross-search program
CN111240681B (en) Conversion method and device for different programming languages
JP2006065467A (en) Device for creating data extraction definition information and method for creating data extraction definition information
WO2001098940A1 (en) Multiple document creation method and system
CN111708542B (en) Test case generation method, system, equipment and storage medium
CN111711605B (en) Data protocol active analysis method for Internet of things platform
CN114238024A (en) Timing diagram generation method and system
Le Zou et al. On synchronizing with web service evolution
CN114647688A (en) Service data sharing method and device and computer storage medium
US20050086262A1 (en) Method and apparatus for WAP and XHTML site management
WO2002050691A1 (en) Software architecture for interaction with dynamic data sources and role based access control
CN113505143A (en) Statement type conversion method and device, storage medium and electronic device
CN114205276B (en) Performance test method and device for product management system and electronic equipment

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP