[go: up one dir, main page]

WO1999066433A1 - Systeme de gestion de documents en temps reel - Google Patents

Systeme de gestion de documents en temps reel Download PDF

Info

Publication number
WO1999066433A1
WO1999066433A1 PCT/AU1999/000480 AU9900480W WO9966433A1 WO 1999066433 A1 WO1999066433 A1 WO 1999066433A1 AU 9900480 W AU9900480 W AU 9900480W WO 9966433 A1 WO9966433 A1 WO 9966433A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
real
management system
document management
Prior art date
Application number
PCT/AU1999/000480
Other languages
English (en)
Inventor
Philip Hirschberg
Original Assignee
Easysite Australia Pty Ltd
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 Easysite Australia Pty Ltd filed Critical Easysite Australia Pty Ltd
Priority to AU45898/99A priority Critical patent/AU4589899A/en
Publication of WO1999066433A1 publication Critical patent/WO1999066433A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting

Definitions

  • the data storage means including a public area from which the documents can be accessed and a private area including data relating to the documents, the processor means being responsive to said data to produce the documents according to a predetermined format, whereby said documents reflect the current data in the private area.
  • Figure 29 shows an add new service form
  • Figure 30 shows an edit/remove services form
  • Figure 31 shows an edit service form
  • Figure 32 is a flow chart of the news administration zone shown in figure 9;
  • Figure 42 is a flow chart of the contact details administration zone shown in figure 9;
  • Figure 44 is a flow chart showing the operation of the "add" function
  • each user may have a domain name or delegated domain name pointing to their documents in the public area 10.
  • the document management system operates as follows. A user accesses the private area 12 using a Internet web browser. After user name and password authentication has occurred, the user gains access to the website administration area 16 in which they can add, modify or remove various components of their website.
  • the website administration area 16 is presented to the user has HTML web page documents, with information being submitted and edited using forms. As such, a user is not required to familiarise himself with any HTML authoring tools. Any changes to the information on any of the user's documents are submitted to the website administration area 16 by the user clicking the submit button (or equivalent) on the appropriate form.
  • the system administrator is taken to an edit user account form 26, otherwise the system administrator is presented with an alphabetical list of user names at 28 which are closest to that entered by the system administrator. The system administrator can then select a user name to edit from the list and proceed to the edit user account form 26.
  • the edit user account form 26 is generated using a perl script which accesses the user data file in creating the form 26.
  • the form 26 is similar in nature to the add new account form 22, except that the user's existing details are already entered, as shown in figure 6.
  • the system administrator can then modify any of the details for the user and effect the modifications by clicking the "modify user” button.
  • the "modify user” button is pressed, the amended details in the edit user account form 26 are written back to the user data file and the system administrator is presented with a modification confirmation page 30 shown at figure 7. This page will automatically forward to the user account administration page 20 after 5 seconds in a similar manner to the user account created page 24 described above.
  • the system administrator can also suspend and terminate a user account from the user account administration page 20.
  • the system administrator types the desired user name into the appropriate space and clicks the submit button.
  • the action proceeds, otherwise a list of users appear from which a selection may be made.
  • Account suspension retains the users files on the computer but prevents access to the files to all persons, including the user until the account has been reactivated.
  • Account termination involves removing the user account from the computer, including the deletion of any stored files. ln the embodiment, a single predetermined format is presented for all users.
  • each user's public website consists of a main page 32, with links to the following pages: about page 34, products page 36, services page 38, news page 40, feedback page 42, links page 44, contact page 46 and copyright page 48.
  • the about page 34 consists of a description about the company and its objectives and contains an index of links to staff pages 50 having details of staff members.
  • the products page 36 is an index of products offered by the user, consisting of a list of links. Each link is to a separate products page 52 containing details of that product.
  • the news page 40 contains an index of news items, with links to individual news pages 56 containing single news items.
  • the contact page 46 contains contact details of the user, such as address, phone and fax details.
  • the copyright page 48 contains a copyright notice.
  • Figure 9 shows a website administration main page 60, which can be accessed by each user of the system
  • each user in order to access the website administration main page 60, each user must enter their user name and password using a secured transaction, and each of the website administration pages to be described uses secure communications
  • the website administration main page 60 contains links to the following pages, referred to as zones: account administration zone, global settings administration zone, mailing list administration zone, enable/disable pages zone, about administration zone, staff administration zone, products administration zone, services administration zone, news administration zone, feedback administration zone, links administration zone and contact administration zone.
  • zones referred to as zones: account administration zone, global settings administration zone, mailing list administration zone, enable/disable pages zone, about administration zone, staff administration zone, products administration zone, services administration zone, news administration zone, feedback administration zone, links administration zone and contact administration zone.
  • the global settings administration zone consists of a global settings administration form 70 which is shown in detail in figure 12.
  • the global settings administration form 70 allows the user to select the colour of the background and text from a predetermined list, the font size of the default text, the font of the default text, the graphics and icons used in the website from a predefined list, a short description of the user or the user's organisation, and a list of key words describing the user or organisation.
  • the description and key words are used to build a site database which is searchable by users on the Internet wishing the find a particular home page but without knowing the address thereof.
  • a flow chart of the mailing list administration zone is shown in figure 14, including a mailing list administration main page 72. From the main page 72, the user can choose to add a subscriber to the mailing list via form 74, edit and remove subscribers from the mailing list via form 76 and send a message to the mailing list via form 78.
  • the user's quota of subscribers is checked. If the user's quota is currently full, an error page 80 is displayed instead of the add subscriber form 74. From the error page 80, the user can either return to the mailing list administration main page 72 or go to the edit/remove subscriber page 76 to remove some subscribers.
  • the edit/remove subscriber page 76 contains a list of current subscribers each of which has a check box adjacent thereto. By clicking on any of these subscribers, the user is taken to the edit subscriber page 82. Alternatively, checking one or more of the check boxes next to any of the subscribers and then clicking a "remove subscriber" button will remove the selected subscribers. Before removing the subscribers, the user is presented with a confirmation page 84 requesting confirmation of the removal action Confirmation is then sent to the user of their action with the mailing list and the appropriate changes made to the user s mailing list data file
  • Figure 15 is a flow chart of the enable/disable pages zone, consisting of a pages administration form 86 shown in detail in figure 16.
  • the form 86 consists of a first check box 86A which can be used to enable or disable the entire website.
  • the form 86 also includes a second section 86B which includes a check box for each of the about page 34, products page 36, services page 38, news page 40, feedback page 42, links page 44 and contact page 46.
  • a tick in the check box corresponding to any of the proceeding pages corresponds with that page being enabled, and therefore accessible from the user's main page 32.
  • the user can enable and disable individual pages by checking or unchecking the appropriate check boxes and can make the changes by clicking the "make changes to site" button When this button is pressed, control data is written to a file indicating which pages are enabled and disabled.
  • disabling a page results in the link to that page not appearing in the main page 32.
  • disabling the services page 38 results in the services link 38A being removed from the main webpage 32. Accordingly, a person visiting the user's main webpage 32 will not see a link to a services page.
  • Pages may be enabled or disabled for a number of reasons, including that the user or the user's organisation provide products only or services only, or the user may wish to disable a specific area until revisions or fresh data has been entered.
  • Disabling the entire site using the check box at 86A prevents access to the main page 32, thereby preventing access to any of the subsidiary pages.
  • Figure 17 is a flow chart of the about administration zone, consisting of an about administration form 88, which is shown in detail in figure 18.
  • the form 88 is created by a perl script, which reads from the data files 14 and inserts the current information into the form 88 ready for editing.
  • the form 88 consists of four sections: mission statement section 88A, philosophy section 88B, profile section 88C and history section 88D. Each section includes a check box to enable or disable that section in the about page 34 and a text box which can be used to enter and edit text described in the mission statement, philosophy, profile or history as appropriate.
  • the form 88 further includes a "reset form” button, which resets the information in the form 88 to that in the currently stored data file.
  • FIG 19 which is a flow chart of the staff administration zone which can be used to add and remove staff members profiles.
  • the staff administration zone includes a staff administration main page 90 from which the user can select to add a new staff member or to edit/remove an existing staff member.
  • the form 96 includes text boxes for entry of the following details regarding the staff member: name, position, phone number, mobile phone number, e-mail address and profile. Of these, check boxes are provided adjacent to the phone number, mobile phone number, e-mail address and profile sections so that the user can enable or disable each of these sections.
  • the status of each check box is stored as control data and is used in creating the staff member page 50 and the about page 34. The relevant details are entered by the user, and the "add to staff list" button is used to save the data.
  • the edit/remove staff member form 94 is presented, shown in figure 21.
  • the form 94 is generated by a perl script by reading the data file of current staff members.
  • the form includes two sections, a "remove profile” section 94A containing a check box for each staff member stored in the data file, and a "edit profile” section 94B containing a list of names of each staff member.
  • Figure 24 shows a flow chart of the products administration zone, which is functionally similar to the staff member administration zone shown in figure 18.
  • the products administration zone includes a products administration main page 102, from which a user can choose to add a new product, or edit/remove an existing product.
  • the add product function operates in a similar manner to the add staff member function described above, with a check of the user's quota of products being performed prior to an add product form 104 being displayed to the user. If the user's quota of products is fully, an error page 106 is presented, from which the user can return to the products administration main page 102 or move to the edit/remove product form 108.
  • the edit product page 110 is shown in figure 27 and is of the same general layout as the add products form shown in figure 25.
  • the edit product form 110 is presented to the user with the current information regarding the product already entered therein for editing by the user. If the user clicks the save changes button, the computer performs the same actions as described above in relation to the add product form 104, however instead of saving new information regarding a product, the computer updates the existing information regarding the product and the product page 52.
  • Figure 28 shows a flow chart of the services administration zone which operates in an identical manner to the products administration zone shown in figure 24. However, the services administration zone is used to manipulate the services data and updates the services page 38 and the individual service pages 54.
  • Figure 29 shows the add new service form 112 which operates in a similar manner to the add new product form 104 shown in figure 25.
  • Figure 30 shows the edit/remove service form 114 which operates in analogous manner to the edit/remove products form 108 shown in figure 26.
  • the edit service form 1 16 is shown in figure 31 , and is of the same general form as the add new service form 1 12 shown in figure 29.
  • the operation of the add new service form 112, the edit/remove service form 114 and the edit service 116 are identical to the corresponding product forms described above.
  • the add news item form 124 includes text boxes for the title and the story, and a check box to enable or disable the storage.
  • the add news item form 124 further includes an expiry section, where the user can elect that the news item either never expires or expires no predetermined period of time.
  • the add news form 124 is processed in a similar manner to that described above in relation to an add new staff member, in that the new news story is stored in the data files, and the news page 40 is updated to reflect a link to the new news story, and a individual news item page 56 is created for the new story.
  • the edit/remove news item form 122 is shown in figure 34 and operates in an identical manner to the edit/remove staff members form described above.
  • the edit/remove news item form 122 includes a further column titled "category" in which an indication of whether each news item is current or has expired is indicated. This provides a convenient mechanism for the user to remove expired news items.
  • Figure 36 is a flow chart of the feedback administration zone, consisting of a feedback administration form 128, which is shown in detail in figure 37.
  • the feedback administration form 128 includes two predefined options for an auto- response message, and an option to provide a customised message.
  • the selected message is used by the computer in auto-replying to any person that submits feedback via the feedback page 42.
  • Changes made to the feedback administration form 128 can be effected by pressing the "save changes" button, whereupon the information in the feedback administration form 128 is stored as data for future reference by the computer when auto-replying to a person submitting feedback.
  • the edit link form 138 is shown in figure 41 , which operates in a similar manner to the edit staff member form 100 described above.
  • the edit link form 138 is presented to the user precompleted with information stored in the data regarding the selected link.
  • the general layout of the edit link form 138 is similar to that of
  • Figure 42 shows a flow chart of the operation of the contact administration zone, consisting of a contact administration form 140.
  • the contact administration form 140 is shown in detail in figure 43 and contains text boxes for the following information: organisation name, trading name, company number or business registration number, building/suite, street address, suburb, state/county, postcode/zip code, country, phone number, fax number, e-mail address number 1 , e-mail address number 2 and e-mail address number 3. Further, check boxes are provided for each of the above items, with the exception of organisation name, to enable/disable the corresponding item.
  • the contact administration form 140 is precompleted with existing details when presented to the user. Clicking "change contact details" button saves the current information in the contact administration form 140 as data, and updates the contact page 46.
  • the operation of the contact administration zone is functionally similar to the about administration zone described above.
  • the perl script 142 reads the user's product quota from the data files and then reads the users current products data file and counts the number of products contained therein. The perl script 142 then compares whether the user's quota would be exceeded if a new product were added and if so generates the error page 106. The error page 106 will auto-forward to the edit/remove product form 108 after 5 seconds.
  • the information on the form is submitted to a seventh perl script 154, which firstly reads the current products index page 36 to obtain the name of the edited product therefrom. This is necessary since the user may have edited the name of the product on the form 110. However, the product will be identified by a product number passed to the perl script 154.
  • the current information is then written to the data files 14 regarding this product.
  • the products index page 36 is then written, as is the individual product page 52 for the current product.
  • An e- mail message is then sent to the user confirming the changes have been effected, and finally a confirmation message is displayed to the user. The confirmation message forwards the user to the products administration main page 102 after 5 seconds.
  • the link in the products administration main page 102 to edit/remove a product is a reference to the perl script 150.
  • the perl script 150 generates a list 108 from which the user can either select to edit a product or remove one or more products. If the user check marks one or more of the check boxes and clicks the remove product button, the information on the form 108 is forwarded to an eighth perl script 156.
  • the perl script 156 reads from the data files 14 the names of the products selected and produces a confirmation page 1 11.
  • each user's data can be stored in a number of different ways, either in a single file, in a number of separate files, or as part of a database.
  • the embodiment has been described with reference to perl scripts, it should be appreciated that a number of other languages and systems may be used.
  • the flow charts in the embodiment are not the only way of achieving the invention, but are the preferred embodiment of the applicant.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système de gestion de documents en temps réel permettant d'assister les utilisateurs du point de vue de la gestion et de la création de documents dans des langages tels que HTML. Ledit système comprend un ordinateur comportant une zone (10) de données publique permettant l'accès aux documents et une zone (14) de données privée comprenant des données relatives aux documents. L'ordinateur lit les données pour produire les documents dans un format prédéterminé en temps réel, les documents reflétant ainsi les données (14) privées courantes. Les modifications apportées aux données privées (14) peuvent être effectuées sur le réseau.
PCT/AU1999/000480 1998-06-16 1999-06-16 Systeme de gestion de documents en temps reel WO1999066433A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU45898/99A AU4589899A (en) 1998-06-16 1999-06-16 Real-time document management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AUPP4152 1998-06-16
AUPP4152A AUPP415298A0 (en) 1998-06-16 1998-06-16 Real-time document management system

Publications (1)

Publication Number Publication Date
WO1999066433A1 true WO1999066433A1 (fr) 1999-12-23

Family

ID=3808397

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU1999/000480 WO1999066433A1 (fr) 1998-06-16 1999-06-16 Systeme de gestion de documents en temps reel

Country Status (2)

Country Link
AU (1) AUPP415298A0 (fr)
WO (1) WO1999066433A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2812420A1 (fr) * 2000-07-28 2002-02-01 Baptiste Vermes Procede automatique de mise en forme de pages dynamiques sur un site internet

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998004983A1 (fr) * 1996-07-29 1998-02-05 Rae Technology, Inc. Editeur de structures hierarchisees pour sites du web
WO1998004978A1 (fr) * 1996-07-29 1998-02-05 Rae Technology, Inc. Editeur graphique pour pages web
US5742672A (en) * 1994-07-19 1998-04-21 Burk; Peter Installation of a multi-terminal network
WO1998018086A1 (fr) * 1996-10-23 1998-04-30 Family Systems Limited Systeme de livre web interactif

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5742672A (en) * 1994-07-19 1998-04-21 Burk; Peter Installation of a multi-terminal network
WO1998004983A1 (fr) * 1996-07-29 1998-02-05 Rae Technology, Inc. Editeur de structures hierarchisees pour sites du web
WO1998004978A1 (fr) * 1996-07-29 1998-02-05 Rae Technology, Inc. Editeur graphique pour pages web
WO1998018086A1 (fr) * 1996-10-23 1998-04-30 Family Systems Limited Systeme de livre web interactif

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ABOUT INTERNET CREATOR, http://www.internetcreator.com/about.html viewed on 6 August 1998 and Reviewed in PC Magazine Online 18 November 1997, No Longer Available on the Internet. *
PC MAGAZINE ONLINE: OPEN FOR BUSINESS WEB STOREFRONT CREATION SOFTWARE, http://www.zdnet.com/pcmag/features/e-comm_ prod/_open.htm. 18 November 1997, Vol. 16, No. 20. *
WEBSITE GENERATOR FROM PRONET, http://pronet.ca/website/toolbar.cgi?atsid= 77685318atsid_email=Bob(a)Apperson.Com International Copyright (c) 1996 Pronet Enterprises Limited. *
YAHOO] STORE, http://www.viaweb.com/viewed on 6 August 1998 and Reviewed in PC Magazine Online 18 November 1997. *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2812420A1 (fr) * 2000-07-28 2002-02-01 Baptiste Vermes Procede automatique de mise en forme de pages dynamiques sur un site internet
WO2002010972A1 (fr) * 2000-07-28 2002-02-07 Baptiste Vermes Procede automatique de mise en forme de pages dynamiques sur un site internet

Also Published As

Publication number Publication date
AUPP415298A0 (en) 1998-07-09

Similar Documents

Publication Publication Date Title
US6691158B1 (en) E-service to manage contact information and track contact location
US7930316B2 (en) Method, system, and computer program product for dynamic field-level access control in shared documents
US6341290B1 (en) Method and system for automating the communication of business information
US6598015B1 (en) Context based computer-assisted language translation
US7003528B2 (en) Method and system for web management
US7155491B1 (en) Indirect address rewriting
US6944817B1 (en) Method and apparatus for local generation of Web pages
US7240294B2 (en) Method of constructing a composite image
US20070239726A1 (en) Systems and methods of transforming data for web communities and web applications
US20040221231A1 (en) Editing a document within web-based production system
US20080072164A1 (en) Methods and the Program-Recording Medium for Creating, Editing and Trading Home Page Components to Assemble a Home Page and a Personal Portal Site Directly in Wysiwyg on Web Browser
US20040162895A1 (en) Web site management with electronic storefront and page categorization
US20050182644A1 (en) E-service to manage contact information with privacy levels
KR101525279B1 (ko) 구축 이후에 사용자 번역된 사이트
US5905979A (en) Abstract manager system and method for managing an abstract database
US20050044383A1 (en) Information providing system and a method for providing information
US20050177784A1 (en) Creating an html document from a source document
US6915299B1 (en) Web server document library
JP2003288143A (ja) ユーザインタフェースを自動的に生成する方法
JP2001273318A (ja) エクスポート機能を有する電子ビジネス・カードのアクセス方法
CN111045990A (zh) 文档管理系统
WO2002037939A9 (fr) Procede de construction d'une image composite
US20140245257A1 (en) Context-switching mechanism for facilitating content creation and software development
CA2356846A1 (fr) Systeme de gestion et de remise de contenu extensible a interfaces multiples generalise, et agenda en ligne
WO1999066433A1 (fr) Systeme de gestion de documents en temps reel

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK 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 MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT 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 SD SL SZ 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 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)
WWE Wipo information: entry into national phase

Ref document number: 45898/99

Country of ref document: AU

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: CA