JP2000215123A - Document registration / update method in shared document management device - Google Patents

Abstract

(57) [Summary] [Problem] A document (attached file) can be easily registered at a registration position designated for each user or an arbitrary registration position of a user. Provides a means to register after converting to. A client creates a document and sends the created document as an attached file of an e-mail to a destination address dedicated to registration. The transmitted e-mail is taken in, a source address of header information, and a server. The server determines a registration position in the server based on user information including a mail address, registration position information, a personal certificate, and the like prepared in advance, and registers an attached file in the server. 【effect】

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for registering and updating a document in a sharing device when sharing a document using a network, and more particularly to an information sharing server (WWW server, FTP server) on the Internet or an intranet.
Related to registration technology.

[0002]

2. Description of the Related Art In recent years, the number of Internet and intranet WWW (World Wide Web) applications has exploded as a medium for easy information transmission and information sharing.
This WWW is used for characters, images,
Multimedia information combining sounds and the like can be easily transmitted. Data for that purpose is created in several description languages (mainly HTML) or a programming language, and is associated with attached data such as images and sounds.

In order to transmit document information on the current WWW, a file group (HTML) constituting a page on the WWW is required.
Generally, it is necessary to create a file, image / sound data, and the like on a client and copy it to a WWW server that is a shared document management device. At that time, FTP (Fi
le Transfer Protocol), and requires knowledge of FTP.

[0004] As another registration method for a shared document temporary device, it is possible to collect and transmit information from an unspecified number of people by using the CGI (Common Gateway Interface) of the WWW. When using a dial-up connection, there is a demerit that the connection fee increases because the user must always be connected while writing a document. Also, it is difficult to handle multimedia information such as images and sounds, mainly in characters. In order to improve these problems, the following techniques have been invented.

In Japanese Patent Application Laid-Open No. Hei 10-63592, a bulletin board system is constructed by using an electronic mail, automatically converting the text of the mail to HTML on a server side, and automatically creating a table of contents. A system that manages a bulletin board system by writing a command in a mail body is disclosed.

[0006]

The prior art has the following problems.

[0007] In the registration procedure for the server, the designation of the registration position (directory) is limited to the bulletin board system and below, and the registration cannot be made to the position for each user.

[0008] The user cannot specify an arbitrary position in registration with the server.

[0009] The attached file cannot be converted into an arbitrary format.

[0010] A first object of the present invention is to register a document (attached file) at a registration position designated for each user or at an arbitrary registration position of the user in order to solve these problems.

It is a second object of the present invention to provide a means for converting a document (attached file) into a user-arbitrary format and then registering it.

[0012]

In order to achieve the above object, there is a system comprising a shared document server used on a network and a client for creating / viewing a document to be shared. Send the document created as an e-mail attachment to the destination address dedicated to registration, fetch the transmitted e-mail, and send the source address of the header information, the e-mail address prepared in advance on the server, and the registration The registration position in the storage device read by the document sharing server is determined based on the user information including the position information and the personal certificate, and the attached file is registered.

In addition to the above, by describing a conversion command in the body of an electronic mail transmitted from the client, the attached file of the mail is converted and registered in the shared document server.

[0014] In addition to the above, by changing the registration position information when the user wants to register at a place other than the registration position defined in the user information by describing the user's arbitrary registration position information in the e-mail text transmitted from the client. It is.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows a case where an e-mail created by a mail client is transmitted, sent to a document registration / update system via a mail server, stored as a shared document in a storage device, and linked by a document viewing client. 1 is an overall configuration diagram when the system of the present invention is used. FIG. 2 corresponds to 104 in FIG. 1, and is a configuration diagram of the document registration / update system according to the embodiment of the present invention.

Hereinafter, the first embodiment will be described.

A document to be shared by the client 101 shown in FIG. 1 is created in advance, a dedicated mail address for registration in the shared document management apparatus 102 is set as a destination address of the mail header 202, and the previously created document is attached. And send it by email. Up to this point, it is the same as an ordinary e-mail with an attached file. The e-mail that arrives at the registration-only e-mail address is a document registration / update system using the present invention.
The processing is passed to 104 and the processing in FIG. 2 is started.

The mail information analysis unit 207 in FIG. 2 is described in detail with reference to FIG. 3, and the server registration unit 209 is described in detail with reference to FIG. In FIG. 2, the sent e-mail is taken into a mail information analysis unit 207, and a mail header 202, a mail body 203, an attached file 204, an attached file 205, and an electronic signature are respectively provided.
Separated into 206 and held. There are two attached files (204, 205) of the e-mail 201, but it is sufficient if at least one.

As processing when an electronic mail arrives, the mail information analysis unit 207 determines in step 302 the personal certificate (email address is stored in the server) based on the source address included in the mail header 202 in advance. The corresponding certificate and the registered position information are extracted from the user information 208 which is a table in which the registered position information and the registered position information are paired. If there is no such request, it is reported by e-mail to the source address that the user cannot be registered and cannot be registered in 306.

Next, in step 303, the mail and user information 208
, A digest is generated from the public key of the individual, and the digest attached in step 304 is compared for authentication. If the result of the authentication is the same, the registered location information and the attached files 204 and 205 taken in are registered in the server registration unit 209 (= step
401). At this time, the number of attached files may be one or more (two or more).

If they are different, it is determined that the message has been altered or spoofed, and the message is processed in an authentication error process 306. In the next server registration unit 209, the storage device
Attachment files 204 and 205 are placed at 105 registration positions. Thereafter, the registered document is read out by the shared document server and displayed on the document viewing client.

Next, a second embodiment will be described.

The invention of the second embodiment is an invention of a method corresponding to various shared document management apparatuses by adding a document conversion function to the invention of the first embodiment. The system configuration in FIG. 2 is the same as that in the first embodiment, but the insides of the mail information analysis unit 207 and the server registration unit 209 are changed to be as shown in FIG. 5 and FIG.

As processing when an electronic mail arrives in the second embodiment, the mail information analysis unit 207 determines in step 502 the personal certificate prepared in the server in advance based on the source address included in the mail header 202. The corresponding certificate and the registered position information are extracted from the user information 208, which is a table in which the mail address is included, and the registered position information, and the process proceeds to step 503.

If there is no corresponding information, it is determined that the user cannot be registered because the user cannot be authenticated, and a report is sent by e-mail to the source address. Next, in step 503, a digest is generated from the e-mail and the individual's public key in the user information 208.
Authentication is performed by comparing the digests attached in the above.

If the result of the authentication is the same, the registration position information and the acquired attached files 204 and 205 are passed to step 505. At this time, the number of attached files may be one or more (two or more). If they are different, it is determined that the message has been altered or spoofed, and is processed in the authentication error process 506.

Next, in the second embodiment, a conversion command name (for example, a command such as doc2html for converting a Microsoft Word [Microsoft Word is a product name of Microsoft Corp. USA]) into an Html document is described in the mail body 203. In step 505, the process proceeds from the presence / absence of a command (the presence / absence of a mail text) to step 507, and confirms the presence / absence of the command from the command definition information prepared in advance (corresponding to the command name and the position of the actual conversion command). If not, error processing is performed in step 510. If there is, the position of the conversion command (for example, / usr / bin / doc2html) is returned, and the process proceeds to step 509 together with the registered position information and the attached file, which are the information so far. .

Next, the process proceeds to step 602 as the server registration unit 209, and if the presence or absence of the conversion command has not been checked, the first embodiment
The process proceeds to step 606 in the same processing as in. If there is, the process proceeds to step 603. If the conversion executed by passing the conversion command and the attached file as an option is successful, the process directly proceeds to step 606 with the conversion result and the registered position information. When the conversion fails, error processing (for example, transmitting a message indicating the conversion failure to the sender) is performed. In step 606, an attached file or a converted file is arranged based on the registered position information. Here, various conversion commands exist on the Internet, and are given as examples.
More information about doc2html is available at http://www.emacsys.com/.

Next, a third embodiment will be described.

In the first embodiment, the registration position of the attached file of the e-mail is determined according to the registration position defined in advance in the user information 208. However, the user information 208 is changed to change the registration position. rather than,
The registration position can be easily changed by registering it in the mail text.

The system configuration diagram is the same as that of the first embodiment in FIG. 2, but the inside of the mail analyzer 207 is as shown in FIG.
In the third embodiment, when an e-mail is received, the mail information
Based on the sender address included in 2 above, the corresponding certificate is obtained from the user information 208 which is a table in which a personal certificate (including the email address) prepared in advance on the server and the registered location information are paired. The certificate and the registered position information are extracted, and the process proceeds to step 705.

If there is no corresponding information, it is determined that the user cannot be registered because the user cannot be authenticated, and a report is sent by e-mail to the source address. Next, in step 703, a digest is generated from the mail and the individual's public key in the user information 208.
Authentication is performed by comparing the digests attached in the above.

If the result of the authentication is the same, the registration position information and the acquired attached files 204 and 205 are passed to step 705. At this time, the number of attached files may be one or more (two or more). If they are different, it is determined that the message has been altered or spoofed, and processing is performed in an authentication error process 706.

In step 705, if the presence or absence of the contents of the mail text has not been checked, the flow proceeds to step 708, where the registration position information and the attached files 204 and 205 that were included in the user information 208 are passed to the server registration unit 209. 4 is processed in the same manner. If there is an e-mail text, it is checked whether it is a directory, and if it is a directory, the process proceeds to step 708 as registered position information. If it is not a directory, it is processed as an error in step 709.

[0035]

The effect of the present invention is that the document can be automatically arranged at a fixed registration position for each user of the shared document device, so that the registered user can easily locate the personal location without being conscious of the directory. Can be registered at Further, since an automatic conversion part as in the prior art is not essential, it is easy to put to practical use.

Furthermore, by describing the conversion command in the body of the mail, the attached file can be converted after conversion into an arbitrary format (preparation of a conversion program and registration for using the conversion program are required separately) and then registration. However, there is no need to have a conversion program on the local machine.

In addition, since it is possible to write a place other than the standard place for personal registration in the body of the mail, the convenience of file registration and the convenience that the user can place a file at an arbitrary position are expanded.

[Brief description of the drawings]

FIG. 1 is a diagram showing an example of a system configuration when the present invention is used.

FIG. 2 is a block diagram showing a document update registration system of the present invention.

FIG. 3 is a flowchart illustrating a procedure of an information analysis unit 207 when updating and registering a document.

FIG. 4 is a flowchart when a document is registered.

FIG. 5 is a mail analysis unit 20 at the time of conversion processing by a command.
7 is an internal flowchart of FIG.

FIG. 6 is a diagram illustrating a server registration unit 20 during a conversion process using a command;
9 is an internal flowchart of FIG.

FIG. 7 is a mail analysis unit 2 when a user specifies an arbitrary registration position.
07 is an internal flowchart.

[Explanation of symbols]

101: mail client, 102: electronic mail, 1
03: mail server, 104: document registration / update system, 105: storage device, 106: shared document device, 107
... Document browsing client, 201 ... E-mail data,
202: mail header, 203: mail body, 204 ...
Attachment file 1, 205: Attachment file 2, 206: Electronic signature, 207: Mail information analysis unit, 208: User information, 209: Server registration unit, 301: Data acquisition, 3
02: user information acquisition, 303: message digest generation, 304: digest comparison, 305: registration position information, attached file output, 306: authentication error processing,
401: # 305 data acquisition, 402: attached file arrangement processing, 510: command invalid error processing, 601: data acquisition, 707: registration position information check.

Claims (3)

[Claims] 1. A system comprising a client for creating / viewing a document to be shared with a shared document server used on a network. The user creates the document and attaches the created document to an e-mail attached file. And send the e-mail to the source address of the header information, and the user information consisting of the e-mail address, registration location information, personal certificate, etc. prepared in the server in advance A document registration / update method for a shared document management device, characterized in that a registration position in a storage device read out by a document sharing server is determined based on the information, and an attached file is registered. 2. A shared document according to claim 1, wherein a conversion command is described in the body of the e-mail transmitted from the client, whereby the attached file of the e-mail is converted and registered in the shared document server. Document registration / update method to the management device. 3. Registered position information when the user wants to register at a location other than the registered position defined in the user information by describing the user's arbitrary registered position information in the body of the e-mail sent from the client according to claim 1. A document registration / update method in a shared document management device, characterized by changing