+

WO2008001025A1 - Noyau de base de données client-serveur - Google Patents

Noyau de base de données client-serveur Download PDF

Info

Publication number
WO2008001025A1
WO2008001025A1 PCT/GB2006/002442 GB2006002442W WO2008001025A1 WO 2008001025 A1 WO2008001025 A1 WO 2008001025A1 GB 2006002442 W GB2006002442 W GB 2006002442W WO 2008001025 A1 WO2008001025 A1 WO 2008001025A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
data
files
email
database
Prior art date
Application number
PCT/GB2006/002442
Other languages
English (en)
Inventor
Nigel Howard Elliott
Matthew David Watson
Phillipa Jane Allison
Original Assignee
Opal Information Systems 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 Opal Information Systems Limited filed Critical Opal Information Systems Limited
Priority to PCT/GB2006/002442 priority Critical patent/WO2008001025A1/fr
Publication of WO2008001025A1 publication Critical patent/WO2008001025A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management

Definitions

  • This invention relates to a server application and a client application for entering and retrieving information from a database and to a method of entering and retrieving information from a database.
  • users may operate on a so-called 'thin client' model in which a relatively simple application such as a web browser is used to render information provided from a centralised server and which takes small amounts of user input to control what is rendered.
  • a relatively simple application such as a web browser
  • This allows economies of scale since typically server costs do not scale linearly with user capacity so that costs per user headcount tend to reduce as servers support greater numbers of users.
  • This type of arrangement works well in a 'broadcast' type environment. For example, in a situation in which all users are expecting to use the same data and view the same information and when data input is minimal so that the system is used largely only for viewing.
  • the invention provides a method of remotely interacting with a database comprising receiving a first file by email, automatically parsing the file to extract data and control information, the control information including instructions to act on the data, and creating a second file containing the parsed data and control information.
  • the invention provides a method of transmitting data from a database comprising reading data parameters and instructions from a first file, inserting the parameters into a file template to create a second file, extracting a recipient address from the first file and initiating sending of the second file to the recipient address via email.
  • the invention provides a method of controlling data transmission and reception between a client application and a database server application comprising providing a plurality of workflow queues representative of predetermined operating system file storage areas, providing a user interface allowing files to be moved between the said workflow queues, acting on the files in different ways depending on the workflow queues in which they are located and transmitting and receiving files automatically via email to populate and empty at least some of the workflows queues without user intervention.
  • the invention provides data structure comprising a plurality of files including a word-processor document of a predetermined structure and having predetermined form fields, and a text document including information at least about a destination email address for the word-processor document.
  • Figure 1 is a schematic view of a user desktop
  • Figure 2 is a schematic diagram showing data flow between a database, an end user and a third party
  • Figure 3 is a schematic block diagram of a database shell, email interface and user desktop in accordance with the invention.
  • an end user is provided with a desktop system which provides a screen based user interface and sits on top of an email client.
  • Data flow between a centralised database 2 and the end user 4 is handled automatically and transparently using email messages automatically sent and received by the email client under control of the desktop system.
  • the invention is described below in connection with a flow of electronic documents but it will be appreciated that the system may be used to send and receive any type of electronic data.
  • a user-base concerns the need to process General Practitioners' (GPs) Reports for an underwriting department.
  • the department has a need to maintain a body of records that GPs provide concerning their patients, together with details of payments for these services.
  • an agent the end user 4
  • the GP third party 14
  • the system aids the end user in monitoring and assisting a plurality of end users 14.
  • the system keep track of what is required and when and also maintains a centralised record of a particular third party's 14 special requirements. It also allows centralised updating of legislative and regulatory requirements so that the end user 4 is always on top of those matters in his or her particular area of expertise.
  • the desktop system is designed to allow the user to process offline information which may be received and/or sent,
  • the system creates four areas 6 to 12 on the desktop, one for working on documents, one for printing documents, one for sending documents and one for document templates. These areas represent different parts of a workflow and contain lists of file names.
  • the desktop system 26 opens all emails received from the centralised database 2 and checks attachments to decide which area of the desktop 6 to 12 to download them to (as described in more detail below). This approach provides an extra layer of security because the application 26 is able to examine the attachment before it is released to the desktop. There are several optional aspects to this.
  • the system 26 may implement rules using naming conventions that allow it to place the attachments in specifically designated areas of the desktop. If necessary, potentially sensitive information could automatically be placed in a secure folder.
  • the system may check for passwords or other flags to ensure that the documents are safe to download onto the desktop.
  • the emails and/or commands may be passed between the desktop system and the database through an encrypted tunnel such as that provided by an SSH connection in order further to improve security and privacy.
  • the system periodically checks emails in the email client inbox and extracts the required attachments from specially constructed emails.
  • the emails are created automatically by the database system which is described in more detail below.
  • the attachments are automatically placed either in the work area 6 or the print area 8 (depending on whether the document will be worked on or just printed and then forwarded to a third party 14).
  • the system periodically checks the contents of the send area 10 and automatically sends any documents in that area as attachments in an email. It then deletes the oldest items from the mail client's sent items folder in order to prevent a build-up of files.
  • the sending of materials from the send area can be manually initiated using a dedicated button 20.
  • the user can work on the documents in the work area, for example, by entering information or reviewing what is required and then can drag and drop the document into the send area for email transmission back to the centralised system.
  • the user can print all the documents in the print area by pressing a print button 16. Documents that have been printed are automatically sent to an archive area before they are deleted from the print area thus keeping an audit trail of work completed. Printed documents may then be sent to the third party 14. The operation of the desktop client will now be described in detail.
  • the application When the application is started, it reads initialization data, calculates the size of the screen and works out sizes of the controls. It then sets up the file paths for the filelist controls 6 to 12.
  • a Word processor application (typically Word) is opened and maximised.
  • the document that was selected with the double-click operation is then opened in the word processor application.
  • email is retrieved from the email client.
  • This process may be initiated manually.
  • the process checks through the inbox folder for messages intended for the desktop system (typically identified by email header information such as a combination of attachment name and subject line text) and extracts all the attachments from the relevant emails. It copies the attachments into predetermined file paths and lists them in either the print area or the work area according to the name of the attachment. It then deletes the email message from the inbox and refreshes the filelists.
  • the user 4 typically completes a job when it enters the print area.
  • the documents received for printing typically will have been pre-populated with all the necessary standard paragraphs (which can be kept up-to-date centrally) and the specific information appropriate for the third party 14. Once printed, it may be sent to the third party 14 by post, for example. Documents in the work area are incomplete and require further input and sending off back to the centralised database system.
  • the user 4 presses a print button 16 on the desktop and for each document in the print filelist, the system opens an instance of Word, opens the document in Word, prints the document, releases Word and moves the document from the print area to an archive area.
  • the archive area may be viewed by pressing another button 18 which causes the archive area (a predetermined operating system folder ) to open for viewing.
  • the user 4 may place a file in the send area by using a drag-drop operation on the file name. This has the effect of moving the files between pre-designated operating system folders.
  • the word documents are typed in with fields denoting areas of the text which will be completed later. Each field is given a name which is used to uniquely match up with information from the dbase system.
  • Fields can be set to be fill-in enabled which allows the user 4 to enter information into the field, or not fill-in enabled which means that the user 4 cannot change the information in the field. This allows the system to have some fields that it populates and only displays, and some fields that it populates that can later be overwritten.
  • New documents are initiated by populating a template file chosen form the templates area 12. Once populated it is dragged to the send area to be sent back to the database system as described below.
  • Sending is initiated by clicking a send button 20. This causes the system to check through the send mail folder and for each attachment, to create an email (using standard parameters and a standard format described below) for the attachment. The system then deletes the attachment and sends the attachment using the email client. The system then refreshes the filelists
  • an email interface 22 sends and receives emails using a mail client and interfaces with a database shell 24.
  • the interface 22 is used to convert the information transmitted by the desktop client 26 into a format that can be used by both senders and recipients.
  • the email interface 22 carries out the following processes:
  • the interface 22 picks up a data file containing the content data and an email address from the database shell 24. It then merges data with a template (for example using a Word mailmerge operation) and then sends the populated template by email to the user(s) 4 as an attachment.
  • a template for example using a Word mailmerge operation
  • the user can open the attachment in a user-friendly format (e.g. Word or another file format) as described above, which can then be saved or worked on before being returned.
  • the interface 22 extracts the merged data, creates a new data file and sends it to the database shell 24 with a function type telling the database what actions to carry out on the data.
  • the system works by looking for form fields in a Word document received from the user 4 via the desktop system 26.
  • Each form field has a unique name that is matched with the name of a data field used by the database system 24.
  • the field contents are extracted from the Word document and sent through to the database system via the shell 24.
  • the email comes into an email inbox 28.
  • the email is automatically moved to a predetermined folder based on an email header such as the subject header.
  • the Word document attachment is moved to a predetermined folder (inreq) 30.
  • a process (readword.exe) 31 then reads the Word document attachment from inreq 30 and converts it to a text file format and places it in predetermined folder inrep 32 in the database shell.
  • a polling process 34 picks up the file from folder inrep 32 and processes it; placing it in predetermined folder outreq 36.
  • the processing includes any database reading and writing operations which are required.
  • a process (writeword.exe) 38 reads the processed text file from outreq 36 and converts it to a Word document and creates an .ini instruction file in a predetermined folder 'out' 40 in the email interface 22.
  • the process may reads a template from a predetermined 'originals' folder.
  • the .ini instruction file contains at least the name of the attachment file to send (the newly created Word document - in a predetermined location) and the email address to send it to. It may also include predetermined subject text for the email which aids automated filtering and sorting within the desktop system 26.
  • the .ini file is then processed to provide instructions for creating a complete email in the outbox 42 for onward transmission by email to the desktop client 26.
  • the .ini text file read by writeword.exe from outreq 36 may contain the following parameters:
  • Readword.exe reads a Word document and extracts data from bookmarks which delineate different section of the automatically generated document. It sends through three items of information to the database process 24 for each parameter. These include a variable name and a value as above, and a repeating flag to show repeating data.
  • the process sends through a function type as noted above, which allows the process 24 to decide what to do with the information extracted from the Word file.
  • Each file processed by readword.exe 31 and writeword.exe 38 has an associated .ini file which provides additional information on processing. Typically these have the same name as the file to which they relate except for the different filename extension. The contents of the .ini files are described below.
  • This process opens a file (presently a known filename with a .ini extension) containing key information that controls the creation of an attachment for an email.
  • the program reads information from the file, which it uses to customize the document, which is finally emailed to the recipient.
  • the process uses the following functional modules.
  • Timer for mail merge (beginjpollingZ) • Checks to see if there are any files called temp2.txt in the temp area and deletes them
  • Process the mail merge ⁇ processjob2) • Creates the files for the merge and reads information from the data file
  • the process uses the following functional modules.
  • Extracts the bookmarks extracts the bookmarks (extract_bookmarks)
  • Documents are named according to a convention so that they can be treated correctly by the desktop system 26 on the user's pc.
  • Documents that are for a specific customer are named according to the customer's name and account number. Subsequent repeated documents for the same customer are differentiated using a sequence number. e.g. gpr10let_607107#8_Posiak.doc would be the 8 th gpriOlet for customer Posiak, with account number 607107.
  • the .ini file follows the same convention apart from the extension which is .ini instead of .doc e.g. gpr10let_607107S8__Posiak.ini

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Cette invention concerne un procédé d'interaction à distance avec une base de données en recevant un premier fichier par courrier électronique, en analysant automatiquement le fichier pour extraire des données et des informations de commande, les informations de commande incluant des instructions destinées à agir sur les données, et en créant un deuxième fichier contenant les données et les informations de commande analysées. Les données peuvent être transmises par la base de données en lisant des paramètres de données et des instructions à partir d'un premier fichier, en insérant les paramètres dans un modèle de fichier pour créer un deuxième fichier, en extrayant une adresse de destinataire à partir du premier fichier et en lançant l'envoi du deuxième fichier à l'adresse du destinataire par l'intermédiaire du courrier électronique. La transmission et la réception des données peuvent être commandées en fournissant une pluralité de files d'attente de déroulement des opérations de bureau représentatives de zones de stockage prédéterminées de fichiers du système d'exploitation, en fournissant une interface utilisateur de bureau qui permet de déplacer les dossiers entre lesdites files d'attente de déroulement des opérations de bureau, en agissant sur les fichiers de différentes manières selon les files d'attente de déroulement des opérations dans lesquelles ils se situent et en transmettant et en recevant les fichiers automatiquement par l'intermédiaire d'un courrier électronique ou d'une liaison sécurisée afin de peupler et de vider au moins certaines des files d'attente de déroulement des opérations sans l'intervention d'un utilisateur.
PCT/GB2006/002442 2006-06-30 2006-06-30 Noyau de base de données client-serveur WO2008001025A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/GB2006/002442 WO2008001025A1 (fr) 2006-06-30 2006-06-30 Noyau de base de données client-serveur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/GB2006/002442 WO2008001025A1 (fr) 2006-06-30 2006-06-30 Noyau de base de données client-serveur

Publications (1)

Publication Number Publication Date
WO2008001025A1 true WO2008001025A1 (fr) 2008-01-03

Family

ID=37696453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2006/002442 WO2008001025A1 (fr) 2006-06-30 2006-06-30 Noyau de base de données client-serveur

Country Status (1)

Country Link
WO (1) WO2008001025A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5613108A (en) * 1993-02-24 1997-03-18 Minolta Camera Kabushiki Kaisha Electronic mail processing system and electronic mail processing method
US5870711A (en) * 1995-12-11 1999-02-09 Sabre Properties, Inc. Method and system for management of cargo claims
WO2001026004A2 (fr) * 1999-10-04 2001-04-12 Kana Communications, Inc. Procede et appareil pour messagerie interprocessus et leur utilisation pour la production automatique de courrier electronique transactionnel
WO2002010919A2 (fr) * 2000-07-28 2002-02-07 Axeda Systems Operating Company, Inc. Rapport de l'etat d'un appareil a un ordinateur distant
US20020046248A1 (en) * 2000-10-13 2002-04-18 Honeywell International Inc. Email to database import utility
US20050091600A1 (en) * 2003-08-26 2005-04-28 Kensaku Yamamoto Workflow management apparatus and method
US20060004720A1 (en) * 2004-07-01 2006-01-05 Tobias Haug Integrated e-mail system

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5613108A (en) * 1993-02-24 1997-03-18 Minolta Camera Kabushiki Kaisha Electronic mail processing system and electronic mail processing method
US5870711A (en) * 1995-12-11 1999-02-09 Sabre Properties, Inc. Method and system for management of cargo claims
WO2001026004A2 (fr) * 1999-10-04 2001-04-12 Kana Communications, Inc. Procede et appareil pour messagerie interprocessus et leur utilisation pour la production automatique de courrier electronique transactionnel
WO2002010919A2 (fr) * 2000-07-28 2002-02-07 Axeda Systems Operating Company, Inc. Rapport de l'etat d'un appareil a un ordinateur distant
US20020046248A1 (en) * 2000-10-13 2002-04-18 Honeywell International Inc. Email to database import utility
US20050091600A1 (en) * 2003-08-26 2005-04-28 Kensaku Yamamoto Workflow management apparatus and method
US20060004720A1 (en) * 2004-07-01 2006-01-05 Tobias Haug Integrated e-mail system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"JetForm Filler Pro for Windows", INTERNET CITATION, 1996, XP002202786, Retrieved from the Internet <URL:http://www.futureforms.com/Fillpro.pdf> [retrieved on 20020618] *
POPYACK J L ET AL: "Mail merge as a first programming language", March 1993, SIGCSE BULLETIN, ACM, NEW YORK, NY, US, PAGE(S) 136-140, ISSN: 0097-8418, XP002359875 *

Similar Documents

Publication Publication Date Title
US11343214B2 (en) Mechanism for associating emails with filter labels
JP5209124B2 (ja) 電子ビジネスカードの送信および受信
US7774408B2 (en) Methods, systems, and emails to link emails to matters and organizations
US7788218B2 (en) Handling digital documents in a networked system using an e-mail server
US20040158607A1 (en) System and method for associating an email attachment file with a storage location
US20070038702A1 (en) Communications data management
US20060293905A1 (en) Exchanging electronic business cards over digital media
US7424676B1 (en) System and method for improved electronic mail processing with introductory text
WO2007001638A2 (fr) Procede de production et de rendu de cartes de visite electroniques
US7818456B2 (en) Method and system for processing a file attached to an electronic document
JP5705804B2 (ja) 移動端末でファイルを操作するための方法、システム、コンピュータプログラム、及びコンピュータ読取り可能な記憶媒体
US20070112854A1 (en) Apparatus and method for automatic generation and distribution of documents
WO2008085654A2 (fr) Mécanisme de génération de courrier électronique composite
WO2008001025A1 (fr) Noyau de base de données client-serveur
US20250104171A1 (en) Data interchange system
JP2000151581A (ja) ドキュメント管理方法、ドキュメント管理システムおよびそのための記録媒体
JP2005293120A (ja) 連携インタフェース
Desmond Microsoft Office 2003 in 10 simple steps or less
JP2009217520A (ja) 関連メール削除システム及び関連メール削除プログラム
CA2538603A1 (fr) Systeme et methode de preparation et d&#39;envoi de documents electroniques

Legal Events

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

Ref document number: 06755688

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06755688

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载