JPH10334086A - Information disclosure system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information disclosure system to freely generate a document according to various requests of a user and to simultaneously and automatically embed link information in the document. SOLUTION: A template file 22 to hold a template, in which specification of information to be disclosed for every type of the information is prepared, the template corresponding to a document request from a client device 90 is called, and the document is generated and transmitted to a request source by a CPU 10. In addition, a table 25, in which a pair of a keyword and the link information is registered, is prepared, and the link information is automatically embedded in a place of the keyword in the document. Furthermore, a table 26 to manage an address of the user, form of sending a mail, etc., is prepared, a new arrival information guiding mail is generated and transmitted to the preliminarily registered user in the case of update of the document, etc.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a system for publishing information to users through a network such as the Internet.

[0002]

2. Description of the Related Art Conventionally, an information disclosure system via a network as shown in FIG. 9 is known. That is, the user makes a document transmission request to the host computer 920 via the network 910 from the terminal device 900 equipped with a WWW (World Wide Web) browser, and the host computer 920 stores the specified document in an external storage such as a hard disk. The data is read from the device 930 and transmitted to the terminal device 900.

[0003] Documents are generally written in HTML (Hyper Text Mar).
(k-UP Language) format. In this format, information such as the location of another document can be embedded in an arbitrary portion of the document (generally, "tag" is embedded). When such a document is displayed on a WWW browser, clicking on that portion with a mouse causes the specified document to be displayed. This mechanism is generally called a “link”, and various information can be organically linked by using the “link”, thereby improving the convenience of information disclosure. For example, if a document contains technical terms,
Prepare the explanatory document at the link destination in advance so that it can be referred to. If the document includes the name of the organization that has a homepage, the homepage can be referenced.

However, conventionally, embedding of a tag is performed manually, and embedding a tag for a technical term or an organization name frequently appearing in a document has been troublesome.

[0005] Further, when such an information disclosure system is made public to users, it is necessary to prepare a document called "What's New"(What's New) which collects links to the latest information. Is indispensable as a service for the elderly. However, documents that are frequently updated in the documents are monitored from time to time, and the latest "news information"
Preparing the document was time-consuming.

Conventionally, a CG for automatically editing a document in such an information disclosure system has been used.
A mechanism called L (Computer Guided Interface) is also provided. That is, a mechanism for executing an external program for executing a necessary procedure when a predetermined control code is designated in a called document. However, the necessary procedures vary for each document, and creating a separate external program for each existing document is rather time-consuming.

[0007]

SUMMARY OF THE INVENTION It is an object of the present invention to solve the above-mentioned conventional problems, freely create various documents corresponding to the needs of the user, and to set an arbitrary part in the document. An object of the present invention is to provide a highly scalable information disclosure system that automatically embeds link information into a URL.

[0008]

In an information disclosure system according to the present invention, a host computer holds, for each type of information to be disclosed, a template document (template) in which specifications are described, and requests a document from a client device. The main feature is that a template document corresponding to the template document is called, a document is generated according to the specification of the template document, and transmitted to a request source.

In the information disclosure system of the present invention, the host computer holds a first table for registering a plurality of correspondences between keywords and link information, and calls the table when generating a document according to the specification of the template document. If a keyword registered in the table exists in a document, link information paired with the keyword is embedded at the corresponding location in the document.

In the information disclosure system of the present invention, the host computer holds a second table for managing at least the destination of the user who uses the system and the mail sending form, and updates the document according to the specification of the template document. (Including registration, deletion) call the table,
It is characterized in that an e-mail is generated and sent back to the update data to the user registered with the immediate notification.

Further, in the information disclosure system of the present invention, the host computer holds a journal file for managing the update history of the document, and generates a mail at a predetermined date and time based on the update history of the journal file. Is sent to the user registered in the second table.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below in detail with reference to the drawings. FIG. 1 is an overall block diagram of a hardware configuration of the information disclosure system of the present invention. In the figure, a central processing unit (CPU) 10, an external storage device 20, an input / output control unit 30, an input device 40, a display device 50, an output device 60, a communication control unit 70, and the like constitute a host (server) system. . A client device (user terminal device) 90 is connected to this host system via a network 80. The external storage device 20 includes an HTML file 21, an HTML template file 22, a data pool file 23, a journal file 24, a replacement table 25, and a user management table 26.
Are prepared.

[0013] Of the above file table group, HTML
The file 21 is the same as the conventional one (prepared as an option if necessary), and the files 22 and below relate to the present invention. Here, the HTML template file 22 is a description of a template of the HTML document in the form of a command statement. The template (template) is, for example, a presentation board template or a registration / correction index template.
It is prepared for each type of document, and defines the document structure, display items, and other various necessary items. The data pool file 23 is a so-called database, and stores information (text) to be presented to the user. The journal file 24 is a file that stores the update history of the data pool file 23, and is used when guiding the user to new arrival information and the like. As shown in FIG. 3, the replacement table 25 is a table storing correspondences between keywords, their replacement character strings, and URLs of link destinations. A tag describing a link to another document or a related organization in an HTML document is stored in the replacement table 25. Used when embedding. The user management table 26 is a table for managing a destination, a communication mode, and the like of the user, and is used when transmitting a mail such as new arrival information to a registered user.

The outline of the operation of the system shown in FIG. 1 is as follows. The user is a client device (WWW browser) 9
0, the server system is accessed to request document search, new registration, update, and deletion. The request is made in a so-called URL description sentence. Hereinafter, search, registration, update, and deletion are collectively referred to as document requests. The CPU (WWW server) 10 receives a document request (URL) from the user through the communication control unit 70 and the input / output control unit 30, and if the document request is a search for an HTML document as in the related art, the HTML
The document is read from the L file 21 and sent to the user,
Otherwise, it operates as follows. When the document request from the user is a search, first, a predetermined template is read from the HTML template file 22, the data pool file 23 is accessed according to the description of the template, the processing result is edited, and the HTML document is generated. Then, it transmits to the request source 90. At this time, the replacement table 25
And embed the link information in the document as necessary. When the request is a search for new arrival information, the journal file 24 is accessed in place of the data pool file 23 to generate a new arrival information guide document, and similarly transmitted to the request source 90.

When a document request from a user is new registration, update / deletion, or the like, a predetermined template is similarly read from the HTML template file 22 and the data pool file 23 is accessed, and a predetermined template is accessed in accordance with the description of the template. HTML document of the request source 9
Send to 0. The user inputs data according to the document format displayed by the WWW browser and sends the data back to the server. The CPU 10 reads a predetermined template from the HTML template file 22 again, writes input data from the user into the data pool file 23 according to the description, and simultaneously reads the journal file 24.
Register to Further, the CPU 10 sends a mail of new arrival information to the user registered in advance according to the user management table 24.

FIG. 2 shows the CPU (WWW server) 1 shown in FIG.
FIG. 2 is a diagram showing a hierarchical structure of programs (processes and modules) operating on the H.0 and a relationship of transfer of control between programs. The function of each program is as follows.

The HTTP daemon 110 sends a document request (UR) from the WWW browser 100 on the client device 90.
L), the document request is passed to the web interfacer (Web Interface) 120 as it is, the edited HTML document is received from the web interfacer 120, and the HTML document is sent to the requesting WWW browser 1
Send to 00. Also, the HTTP daemon 110
Depending on the format of the document request, the HTML file 21
The HTML document is also read from the URL and transmitted to the WWW browser 100. FIG. 4 shows a processing flow of the HTML daemon 110.

The web interface 120 is an HTT
When a document request (URL) is received from the P daemon 110, the document request is analyzed, a predetermined template is read from the HTML template file 22, and the data pool daemon 130 is searched, registered, updated, Instruct specific processing contents such as deletion. Then, when the processing result is sent from the data pool daemon 130, the processing result is edited according to the specification of the template, an HTML document is generated, and the generated HTML document is transferred to the HTTP daemon 110. FIG. 5 shows the web interfacer 12.
0 shows a processing flow.

When receiving a processing request from the web interfacer 120, the data pool daemon 130 reads (searches) or writes (registers, updates, and deletes) the data pool file 23, and stores the processing result in the web interface. Hand over to server 120. At the same time, the data pool daemon 130 activates the filter (1) 131 or the filter (2) 132 if the processing request from the web interface 120 directs the activation of the filter, and transmits the processing result to the web server. Notify the interfacer 120. In addition, the data pool daemon 130 executes the data pool file 2
3 is changed, the journal file 2
4, journal information such as the change data and the change date and time is registered. FIG. 6 shows a processing flow of the data pool daemon 130.

Filter (1) (Filter with automatic link)
When activated by the data pool daemon 130, the 131 receives the search data read from the data pool file 23 from the data pool daemon 130, refers to the replacement table 25 (FIG. 3), and refers to the replacement table 25.
If the term (keyword) registered in 5 exists in the search data, the corresponding link information (description, URL) is notified to the data pool daemon 130. FIG. 7 shows a processing flow of the filter (1) 131.

When activated by the data pool daemon 130, the filter (2) (new arrival notification mail filter) 132 receives registration / update data from the data pool daemon 130 and refers to the user management table 26 to If the user who wants the new arrival notification immediately is registered, an e-mail is created using the registered / updated data and the like, and sent to the user. Then, the filter (2) 132
Notifies the data pool daemon 130 of the processing result. FIG. 8 shows a processing flow of the filter (2) 132.

Data Pool Watch Agent 14
0 is the user management table 26 in units of days, weeks, months, etc.
, A new arrival information list is created using the contents of the journal file 24 for a user who desires a new arrival notification, and sent to the relevant user.

Next, the flow of processing in the case of search, registration, update and deletion will be described in detail with reference to FIG.

<Search> The HTTP daemon 110 checks the WW
When a search request (URL) is received from the W browser 100, the search request (URL) is analyzed, and the received search request is passed to the web interface 120 as it is, except for reading an HTML document directly from the HTML file 21 as in the related art.

The web interface 120 is an HTT
The search request (URL) passed from the P daemon 110 is analyzed, and a predetermined template is read from the HTML template file 22. For example, if the search request is a top page, the template of the top page is read. If an item is also specified in the search request, the template of the corresponding item is read. Then, according to the specification of the template, the web interfacer 120 executes the data pool daemon 130
Is instructed for the specific processing contents of the search. In the case of this search, the filter of the filter function with automatic link (1)
131 is also instructed.

The data pool daemon 130 is a web server.
In accordance with an instruction from the interfacer 120, data is read from the data pool file 23 and passed to the web interfacer 120. At the same time, data pool daemon 1
30 activates the filter (1) 131, and also passes the data (search data) read from the data pool file 23 to the filter (1) 131. Filter (1) 131
Reads the substitution table 25 (FIG. 3), checks whether the term (keyword) registered in the substitution table 25 exists in the search data, and if it exists, the corresponding link information (description, link destination URL) To the data pool daemon 130. The data pool daemon 130 passes the link information notified from the filter (1) 131 to the web interfacer 120.

The web interfacer 120 edits the search data passed from the data pool daemon 130 in accordance with the specification of the template to generate an HTML document. At this time, when the link information is also passed from the data pool daemon 130, the link information is embedded in the corresponding portion of the HTML document. And Web Interfacer 1
20 passes the generated HTML document to the HTTP daemon 110.

The HTTP daemon 110 transmits the HTML document passed from the web interfacer 120 to the requesting WWW browser 100.

When a search request for new information is made from the WWW browser 100, the data pool daemon 13
The processing sequence is basically the same as described above, except that 0 executes reading of the contents of the journal file 24 in place of the contents of the data pool file 23. The new arrival information is transmitted to the WWW browser 100 as a part of the top page, for example.

<Registration, Update, and Deletion> The flow of the registration, update, and deletion processes is basically the same, and the case of registration will be described here.

When the HTTP daemon 110 receives a registration request (URL) from the WWW browser 100, it passes the registration request to the web interface 120 as it is.
The web interfacer 120 reads a predetermined template from the HTML template file 22, and requests the data pool daemon 130 for desired data. The data pool daemon 130 is the data pool file 23
The data such as the target item and its contents is read out from the server and passed to the web interfacer 120. The web interfacer 120 generates an HTML document (registration / modification index page) according to the specification of the template, and transmits the generated HTML document to the requesting WWW browser 100 via the HTTP daemon 110.

The user instructs new information registration according to the displayed registration / correction index page. In the case of updating / deleting, the corresponding item is designated to instruct the updating / deleting.

When the HTTP daemon 110 receives the new information registration (URL) from the WWW browser 100, it passes it to the web interfacer 120. The web interface 120 reads a predetermined template from the HTML template file 22 and requests desired data from the data pool daemon 130. The data pool daemon 130 reads data from the data pool file 23 and returns it to the web interface 120. . The web interfacer 120 uses H according to the specification of the template.
A TML document (registration work page) is generated and transmitted to the requesting WWW browser 100 via the HTTP daemon 110.

The user inputs data (new registration information) on the displayed registration work page and instructs registration completion.

The HTTP daemon 110 passes registration data (URL) from the WWW browser 100 and passes input data to the web interface 120. The web interface 120 re-enters the HTML template file 22
A specific template is read out of the data pool daemon 130 in accordance with the specification of the template, and the input processing is passed at the same time. In addition, in the case of this registration (same in the case of update and deletion)
, Filter (2) 132 of the instant arrival notification mail function
Is also instructed.

The data pool daemon 130 is a web server.
In accordance with an instruction from the interfacer 120, input data is written to the data pool file 23, journal information is generated and registered in the journal file 24. At the same time, the data pool daemon 130 activates the file (2) 132 and converts the input data to the filter (2).
Hand over to 132. The filter (2) 132 reads the user management table 26, and if there is a user who wants an immediate notification of new arrival, creates a mail (new arrival information guide) using the data passed from the data pool daemon 130, and Send to the user and notify the data pool daemon 130 of the end of sending. Note that the filter (2) 132 may notify the data pool daemon 130 of the destination information. The data pool daemon 130 receives the notification of the end of the mail transmission from the filter (2) 132 and notifies the web interfacer 120 of the completion of the registration process. At this time, the data pool daemon 130
When notified of the destination information from the filter (2) 132, the filter information may be passed to the web interfacer 120.

When the web interface 120 receives the completion of the registration process from the data pool daemon 130, the web interface 120
An HTML document (registered page) is generated according to the specification of the template, and passed to the HTTP daemon 110. In addition,
Immediate notification destination information may be added to this HTML document.

[0038] The HTTP daemon 110 transmits the HTML document passed from the web interfacer 120 to the WWW browser 100 that has issued the registration request.

In the above description of the registration processing, the user of the registration request requests the registration / correction index page prior to the registration work page. However, the URL of the target registration work page is known on the user side. In this case, the registration / correction index page request may be omitted.

The embodiment of the present invention has been described above in detail.
It goes without saying that the information disclosure system of the present invention is not limited to the configurations shown in FIGS.

[0041]

According to the first aspect of the present invention, for each type of information to be disclosed, a template document (template) in which specifications are described is held, and a document is generated by calling a template corresponding to the document request. Accordingly, there is no need to prepare and prepare a document to be disclosed in advance, the document creation operation is reduced, and a highly extensible information disclosure system that automatically performs the operation of creating a typical document or the like can be provided.

According to the second aspect of the present invention, link information is automatically embedded at an arbitrary position in a document by using a table in which pairs of keywords and link information are registered.
It is free from complicated correction work such as when a term that needs to be linked frequently appears in a document.

According to the third aspect of the present invention, a new information guide mail is automatically generated based on the registration / update data of the document, and a table for managing the destination of the user, the mail sending form, and the like is used.
It becomes possible to provide a service that immediately sends the new arrival information guide to the user who wants it immediately.

According to the fourth aspect of the present invention, a new arrival information guide list is created for each predetermined date and time (day, week, month, etc.) using a journal file for managing the update history of a document.
A service for sending to a pre-registered user is also possible.

[Brief description of the drawings]

FIG. 1 is an overall block diagram of an information disclosure system according to an embodiment of the present invention.

FIG. 2 is a diagram showing an embodiment of a program, a file, and a group of tables operated by a host computer of the information disclosure system of the present invention.

FIG. 3 is a diagram illustrating a configuration example of a replacement table.

FIG. 4 is a processing flowchart of an HTTP daemon.

FIG. 5 is a processing flowchart of a web interfacer.

FIG. 6 is a processing flowchart of a data pool daemon.

FIG. 7 is a processing flowchart of an automatic link filter.

FIG. 8 is a processing flowchart of a new arrival notification mail filter.

FIG. 9 is a schematic block diagram of a conventional information disclosure system.

[Explanation of symbols]

 10 Host Computer 20 External Storage Device 21 HTML File 22 HTML Template File 23 Data Pool File 24 Journal File 25 Replacement Table 26 User Management File 80 Network 90 Client Device 100 WWW Browser 110 HTTP Daemon 120 Web Interfaceer 130 Data Pool Daemon 131 Filter (1) 132 Filter (2) 140 Datapool Watch Agent

 ────────────────────────────────────────────────── ─── Continued on the front page (72) Inventor Keishin Matsushita 4-1-1, Shinjuku, Shinjuku-ku, Tokyo

Claims (4)

[Claims] 1. An information disclosure system in which a client device sends a document request to a host computer via a network, and the host computer sends a designated document to the client device. The host computer, for each type of information to be disclosed, Holds a model document (template) that describes the specifications,
An information disclosure system characterized by calling a template document corresponding to a document request from a client device, generating a document according to the specifications of the template document, and sending the generated document to a request source. 2. The information disclosure system according to claim 1, wherein the host computer holds a first table for registering a plurality of correspondences between the keyword and the link information, and generates the first table when generating the document according to the specification of the template document. An information disclosure system, wherein a table is called, and if a keyword registered in the first table exists in a document, link information paired with the keyword is embedded in the corresponding location in the document. 3. The information disclosure system according to claim 1, wherein the host computer holds a second table for managing at least a destination and a mail sending form of a user who uses the system, and a specification of the template document. When the document is updated (including registration and deletion) in accordance with the above, the second table is called, and an email is generated and sent back to the user who has registered the immediate notification with the updated data. Information disclosure system. 4. The information disclosure system according to claim 3, wherein the host computer further holds a journal file for managing an update history of the document, and sends a mail every predetermined date and time based on the update history of the journal file. An information disclosure system, which is generated and sent to a user registered in the second table.