JP4926736B2 - Document management system - Google Patents

Description

  The present invention relates to a document management system that manages documents such as catalogs and manuals as a collection of various files such as document files, table files, and image files, and more particularly, a document that manages a file by sharing one file among a plurality of documents. Regarding the management system.

  Conventionally, in a file system in an OS (Operating System), a file is stored in a folder, and when the file is copied to another folder, the file entity is copied at that time. When the same file is to be handled in a plurality of folders, a shortcut to the file to be copied to the copy destination, that is, link information to the file is created.

  Also in the document management system, for example, when a catalog is revised, catalogs (documents) before and after revision may refer to the same image file, and the same file may be referred to among a plurality of documents.

  For this reason, as described in Patent Document 1, instead of creating an entity of a document element (a file referred to by a document) for each document, link information to the document element is created and held for each document. A technique is known in which changes made to document elements are reflected in all related documents.

  Also, as described in Patent Document 2, the correspondence relationship between a document and a document element is stored in a DB (Data Base), and when a document element referred to in a plurality of documents is changed, the user is notified. Notification techniques are also known.

According to the techniques described in Patent Document 1 and Patent Document 2, a file entity is not created for each document, and only information for identifying a file referred to by the document, such as link information to the file entity, is created. The Therefore, when a plurality of documents refer to the same file, the capacity of the storage device is not wasted by copying the file entity. When the file entity is changed, the contents of the document are changed without performing a special operation.
JP-A-6-96078 Japanese Patent Laid-Open No. 10-269071

  However, the techniques described in Patent Document 1 and Patent Document 2 have a problem that flexibility in use for file sharing may be lacking.

  Specifically, for example, when the same file is referred to among a plurality of documents, that is, when the same file is shared, there is a problem that it may not be possible to cancel the sharing state with the conventional technology. . This will be described using the initial product version and the improved product version of the product catalog as examples.

  For example, when the improved product version was created, the product overview of the initial product and the improved product was almost the same, so we shared a document file explaining the product overview (hereinafter referred to as “product overview description file”). Suppose you want to clarify the characteristics of a product. In this case, if the description content of the product overview description file is changed, the product overview of the initial product version also changes. Therefore, in this case, copy the product overview description file to create another file (copy destination file), change the contents of the copy destination file, and link to refer to the copy destination file for the improved product version. Information etc. need to be changed, but cannot be done using conventional techniques.

  Here, when there is an error in the contents of the product outline explanation file, it is desirable that the contents of the product outline explanation file can be changed while maintaining the shared state. Also, when creating another file of the referenced file, simply creating another file will increase the number of files with similar contents, for example, correcting typographical errors that existed from the beginning of the initial product version In such a case, there arises a problem that the file to be corrected has to be searched.

  As described above, when a plurality of documents share a file, it is not always necessary to change the contents of the file while maintaining the shared state. Taking the above product catalog as an example, regarding the sharing between the initial product version and the improved product version, if the file contents are changed, the sharing status is automatically canceled, but the file association is maintained. It is desirable to be able to easily know changes made to related files.

  On the other hand, when a revised catalog is created because the product is the same and accessories are added, it is desirable that the shared file continues to be shared even if the file content is changed. Furthermore, when creating a foreign language version of a product catalog, it is desirable to maintain the relevance of the file without sharing the product overview description file from the beginning.

  As mentioned above, document management technology not only allows sharing one file among multiple documents, but also releases the sharing state while maintaining the relevance of the file according to the creation purpose of the document, etc. Further flexibility in use is required.

  SUMMARY OF THE INVENTION In view of the above situation, an object of the present invention is to provide a document management system capable of improving the flexibility in use for file sharing.

In order to solve the above problems, the present invention provides the following configurations.
A document management system having a server that manages a document, which is a collection of one or more files, using information indicating which file the document refers to .
(A) When creating a document using an existing document as a diversion source document, correspondence is made between the document identification information, diversion method information in which one of a plurality of diversion methods from the diversion source document is set, and the diversion source document identification information Means for storing in the document management table,
(B) means for storing the document identification information, the file identification information of each of one or more files referred to by the document, and the file version of each file in association with each other in a file management table in the document;
(C) means for associating file identification information, a file version, and a storage location of a file entity in a file management table,
(D) When a first diversion method that is one of the plurality of diversion methods is set as the diversion method information, the server
(D1) At the time of creating a document, means for sharing all files referred to by the created document with the diversion source document;
(D2) When a file referred to by the created document is requested for updating, it is determined by referring to the file management table in the document whether or not the requested file is shared with other documents. Means,
(D3) When the requested file is in a shared state, the new file entity obtained by copying the file entity acquired based on the file management table is updated to obtain the file identification information and the new file version. Storing in the file management table in association with each other, and storing the document identification information, the file identification information, and the new file version in the document file management table in association with each other;
(D4) When the requested file is not in the shared state, the file management table is updated by updating the file entity acquired based on the file management table so that the file identification information and the new file version are associated with each other. And storing the document identification information, the file identification information, and the new file version in association with each other in the document file management table .
In the above system, when (e) a second diversion method that is one of the plurality of diversion methods is set as the diversion method information, the server
(E1) When creating a document, means for sharing all files referred to by the created document with the diversion source document;
(E2) When a file referred to by a document is requested for updating, the file entity acquired based on the file management table is updated to associate the file identification information with a new file version, and It is preferable to include means for storing the file identification information, the file identification information, and the new file version in association with each other in the file management table.

  According to the first aspect of the present invention, there is provided a document management system including document management information for managing a document that refers to predetermined information including a file, and the document management information includes at least information including a file for each document. Has identification information indicating whether or not to share the file with other documents, and sharing of information including the file is switched according to the identification information, so that the flexibility in use for file sharing can be improved. A possible document management system can be realized.

Hereinafter, embodiments of the present invention will be described with reference to the drawings showing examples.
First, some terms used below are explained.
A “document” is a collection of one or more files. For example, in the case of a document called “product catalog”, it is a collection of a document file explaining an outline of product functions, an image file capturing the appearance of the product, and the like.
“Document creation” means that a name and an identification code are assigned to a document, and information indicating which file the document refers to is paired with the identification code of the document.
“Document management” means adding a file to which a document refers.

FIG. 1 is a system configuration diagram of a document management system according to the present invention.
The document management system is configured such that the server 1 and the client 4 are communicably connected to each other via a communication line 6. Although FIG. 1 shows a configuration in which both the server 1 and the client 4 are provided, a plurality of clients 4 may be provided. In the following description, it is assumed that a plurality of clients 4 are provided. Further, for example, a plurality of servers 1 may be used in order to distribute the load. However, for the sake of understanding of the explanation, a single server 1 will be described.

  Each of the server 1 and the client 4 is composed of, for example, a general computer. The communication line 6 includes a communication line such as a wireless or wired LAN (Local Area Network) or the Internet. Although not shown, the server 1 and the client 4 are assigned identification codes such as IP addresses that can be uniquely identified at least within the communication line 6. You can send and receive communication messages to other parties.

  A storage device 2 and 3 are communicably connected to the server 1, and a screen display device 7 and an input device 8 are connected to the server 1. The storage devices 2 and 3 are storage devices that use, for example, a magnetic disk, and store files and the like required by the document management system. The screen display device 7 includes a CRT (Cathode Ray Tube), a liquid crystal screen, and the like, and displays necessary information for the user of the server 1. The input device 8 includes a keyboard, a mouse, and the like, and is operated by a user of the document management system so as to give necessary instructions to the server 1.

  The first storage device 2 stores a file folder entity 20, and the file folder entity 20 stores files that can be referred to by each document. For example, the first storage device 2 can be allocated as the C drive, and the “material” folder in the C drive can be used as the file folder entity 20.

  In the document management system according to the present invention, first, a file folder entity 20 is created. For example, when the “material” folder in the C drive is used as the file folder entity 20, first, the “material” folder is created in the C drive by using an OS (Operating System) operation command or the like. Move or copy files that the document may reference in.

  In general, each file needs to be uniquely identified. In the present embodiment, a file ID and a file version are assigned to the file, and each file can be uniquely identified by combining the file ID and the file version. Therefore, for example, each time a file is moved or copied into the “material” folder, a sequential file ID (for example, “0001”) and a file version (for example, “0001”) are assigned to the bottom of the file name. Specifically, for example, when a file named “ABC.txt” is moved or copied in a state where no file exists in the “material” folder, the file name in the “material” folder is changed to “ABC.txt — 00010001”. change. Further, when a file named “ABC.doc” is moved or copied again in this state, the maximum file ID in the “material” folder is incremented by 1, and the file name in the “material” folder is changed to “ABC”. .Doc_00020001 ". The file ID and file version given above are given by the user who moved or copied the file using the OS file name change command or the like. For example, the file is moved or copied into the “material” folder. A dedicated program may be created for this program. Further, instead of giving the file ID and file version to the end of the file name, the information stored in the file folder entity 20 has management information and can uniquely identify the file (for example, an absolute path) and the file ID. And file versions may be managed in pairs. In this case, when referring to the file ID or file version of the file stored in the file folder entity 20, the management information must be referred to and the processing becomes complicated. By moving or copying and setting and updating management information using a dedicated program, the file ID or file version assigned to the file name may be changed to an inappropriate value due to an erroneous operation by the user of the server 1. Can be prevented. In addition, when information other than the file ID and file version to be managed regarding the target file is generated, the storage contents of the management information may be added without changing the file name, which is excellent in extensibility. In the following, in order to avoid complicated explanations, a file ID and a file version that can be uniquely identified are combined and given to the end of the file name, and a file folder entity 20 for storing the file is created. As an example, the description will be given.

  In the document management system according to the present invention, files having the same file ID, that is, files having the same file ID but different file versions are referred to as related files, and related file groups (hereinafter simply referred to as “file groups”). Process. The files in the “material” folder may be placed directly under the “material” folder, or a subfolder may be created in the “material” folder and placed in the subfolder.

  The second storage device 3 stores a document management DB (Data Base) 30 for managing documents. The document management DB 30 includes a document management table 31, an in-document file management table 32, and a file management table 33. Hereinafter, the document management DB 30 will be described as being an RDB (Relational Data Base), but this is not always necessary. For example, a database having a tree structure may be used as long as it holds logically equivalent data items. Instead of a regular file.

  The server 1 realizes a document creation function, a document management function, a file transmission function to the client 4, and the like, a GUI (Graphical User Interface) processing control unit 11, a new document creation unit 12, a diverted translation document creation unit 13, and a file addition Section 14, file display section 15, data transmission processing section 16, and data reception processing section 17.

  For example, the client 4 can update a file referred to by a document managed by the server 1 in accordance with a user operation. Specifically, when it becomes necessary to change the contents of a file referred to by a document (for example, the description contents of a document file that explains the product function outline), the server 1 sends a file that needs to be changed to the client 4. Then, the client 4 updates the received file and returns it to the server 1. In this way, the file is updated by separating the server 1 having the function of managing the document and the client 4 having the function of updating the file referred to from the document (hereinafter, the file is updated). Is referred to as “file update”.) Users can be restricted from referring to files other than the update target file. If such a reference restriction is not required, the server 1 may also update the file.

  In order to realize the file update function, the client 4 is connected to the third storage device 5 so as to be communicable with the screen display device 9 and the input device A. The third storage device 5 is a storage device using, for example, a magnetic disk or the like, and is written in the file temporary storage folder 51 for temporarily storing the file sent from the server 1 and the file temporary storage folder 51. An update management table 52 for managing whether or not the file has been updated is stored. For example, the third storage device 5 can be assigned as the C drive, and a “temporary storage folder” can be created in the C drive and used as the file temporary storage folder 51.

  The screen display device 9 includes a CRT, a liquid crystal screen, and the like, and can display necessary information for the user of the client 4. The input device A includes a keyboard, a mouse, and the like, and the user of the document management system can give necessary instructions to the client 4 by operating the input device A.

FIG. 2 is a system configuration diagram showing the configuration of the server side of the document management system in more detail.
The server 1 includes a main storage device 10, a central control device 1A, a storage device control device 1B, an output device control device 1C, an input device control device 1D, an internal bus storage device 1E, and the like. In addition, a storage device B is connected.

  The storage device B stores a server function program B0 that is loaded into the main storage device 10 of the server 1 and implements various functions. For example, when the server 1 is powered on, the OS or the like of the server function program B0 is loaded from the storage device B to the main storage device 10 of the server 1. The central control unit 1A obtains and decodes an instruction code or the like in the OS or the like 18p via the internal bus 1E, and implements a predetermined function by executing this.

For example, when the user of the server 1 instructs to activate the document management system via the input device 8, the operation is executed as follows.
The central controller 1A receives the above instruction via the input device controller 1D and the internal bus 1E, and provides the storage device controller 1B with necessary functions such as a GUI processing control program in the server function program B0. An instruction is given to read a program for realization into a predetermined address of the main storage device 10.

  The storage device control device 1B reads a program such as a GUI processing control program from the storage device B in response to an instruction from the central control device 1A, transfers it to the main storage device 10 via the internal bus 1E, and sets it to a predetermined address. The information is stored, and the central controller 1A is notified that the operation instructed has been completed.

  When the central controller 1A receives a notification that the operation instructed from the storage controller 1B has been completed, the central controller 1A sequentially obtains the instruction code of the GUI processing control program 11p from a predetermined address in the main storage 10 and decodes it. And executing the GUI processing control function.

  As described above, the GUI processing control unit 11, the new document creation unit 12, the diverted translation document creation unit 13, the file addition unit 14, the file display unit 15, the data transmission processing unit 16, and the data reception processing unit 17 illustrated in FIG. , Each corresponding GUI processing control program 11p, new document creation program 12p, diverted translation document creation program 13p, file addition program 14p, file display program 15p, data transmission processing written in the main storage device 10 shown in FIG. This is a component that realizes individual functions according to the program 16p and the data reception processing program 17p. For each function of the server 1, the central control unit 1A obtains the instruction code of the program and decodes it, and if necessary, via the internal bus 1E, the storage device control unit 1B, the output device control unit 1C, and the input device This is realized by instructing any one or more of the control devices 1D to perform a predetermined operation, or receiving an operation completion notification from these devices and performing an operation corresponding thereto.

  In the present embodiment, for example, when “GUI processing control unit 11 displays an initial screen on screen display device 7” is described, the corresponding component unit operates as follows. That is, the central controller 1A acquires and decodes the corresponding instruction code of the GUI processing control program 11p via the internal bus 1E, and the initial value written to the output device controller 1C at a predetermined address of the main storage device 10 Instructing to display the screen display information, the output device control device 1C receiving this instruction transfers the initial screen display information written at a predetermined address of the main storage device 10 to a screen display storage device (not shown). To do.

  Hereinafter, in order to avoid the complexity of the description, the operation of the device described thereafter is represented by the simple description in the parentheses. The operation of such a computer is a well-known technique, and the present description is also adapted thereto. Accordingly, in the following description, the storage device B, the server function program B0, the main storage device 10, the central control device 1A, the storage device control device 1B, the output device control device 1C, and the input device control described in FIG. Details of the operation of the device 1D, the internal bus 1E, the OS, etc. 18p corresponding to the above description will not be mentioned. Further, since the client 4 side of the document management system has the same system configuration as that of the server 1 side shown in FIG. 2, the description thereof is omitted for the same reason as described above.

  In the present embodiment, the three storage devices of the first storage device 2, the second storage device 3, and the storage device B are connected to the server 1, but the present invention is not limited to the first storage device, for example. The same applies to a configuration in which the device 2 stores all the file folder entity 20, the document management DB 30, the server function program B0, etc., and is connected to the server 1, as well as other configurations.

FIG. 3 is a diagram showing a configuration of a table constituting the document management DB.
The document management table 31 is a table for managing each document to be managed by the document management system via one record (hereinafter simply referred to as “document management record”) 310. Therefore, in the document management table 31, one document management record 310 corresponds to one document.

  In the document management record 310, data whose data items are a document ID 311, a document name 312, a diversion method 313, and an ID of the original document to be diverted (hereinafter simply referred to as “diversion source document ID”) 314 is written. It is.

  As the document ID 311, data for uniquely identifying a document to be managed by the document management system is set. Specifically, for example, when the first document is created, a document management record 310 in which “0001” is set as the document ID 311 is created in the first record, and each time a new document is created thereafter. Then, the maximum value of the document ID 311 is retrieved from the created document management record 310, and a value obtained by adding 1 to this is set in the new document management record 310 as a new document ID 311.

  The document name 312 is a name set so that the user can identify the document, and is displayed on the screen display device 7 when displaying a list of documents. The document name 312 is set with the content input via the input device 8 at the time of document creation, and for example, data such as “document A / V1” is set.

  As the diversion method 313, data for determining a file management method by the document management system is set, such as whether or not the file referred to by the document is shared with the diversion source document. Here, as the diversion method 313, for example, any one of four types of identification characters “link diversion”, “branch diversion”, “new”, and “translation” is set when a document is created.

  “Link diversion” indicates that the target document should be managed so that the file sharing state is maintained when the file is shared with another document (original document) and the contents of the shared file are changed. ing. For example, in the product catalog, when the product is the same but a revised catalog is created because an accessory is added, this identification character is set.

  “Branch diversion” means that if the target document shares a file with another document (the diversion source document) at the time of document creation, the content of the shared file is changed during the process, This indicates that management should be performed so that the file sharing state is canceled while maintaining. For example, in the product catalog, when a document about a product improved by using the original product as the original product is created, this identification character is set.

  “New” is set when a new document is created, and indicates that there is no diversion source document and no shared file with other documents. For example, in the product catalog, when a new catalog is created, this identification character is set.

  “Translation” indicates that the diversion source document exists but does not share the file with the diversion source document. This point is the main difference from “new”, and will be described in detail in the description of the document creation processing described later. For example, when a foreign language version is created in a product catalog, this identification character is set.

  As the diversion source document ID 314, the document ID 311 of the diversion source document is set when the diversion source document is designated at the time of document creation. When a diversion source document is specified at the time of document creation, any one of “link diversion”, “branch diversion”, and “translation” is set as the diversion method 313.

  The in-document file management table 32 associates a document with a file referred to by the document. Records corresponding to the number of files to be referred to for each document (hereinafter simply referred to as “in-document file management record”) 320 are allocated to the in-document file management table 32. In the in-document file management record 320, data having a document ID 321, a file ID 322, a file version 323, and a file group last update date 324 as data items is written.

As the document ID 321, the data set as the document ID 311 in one of the document management records 310 is set.
As the file ID 322 and the file version 323, data is set so that the file referred to by the document among the files stored in the file folder entity 20 can be uniquely identified by combining these two data items. .

  As the file group last update date and time 324, the update date and time of the latest file among the files in the file folder entity 20 having the same file ID as the file ID 322 of this record and different file versions is set. Therefore, by referring to the file group last update date and time 324, the latest update date and time of the latest one of the related files can be known. Specifically, for example, when the latest update date and time of the latest file in the file group is 14:07:23 on December 26, 2006, data such as “20061226140723” is set. As the file group last update date and time 324, a value up to hour, minute and second may be set as in this example, or a value up to, for example, milliseconds may be set.

  The file management table 33 associates the file associated with the document by the in-document file management table 32 with the file entity. A record (hereinafter referred to as “file management record”) 330 is assigned to the file management table 33 for each file. In the file management record 330, data having a file ID 331, a file version 332, a file storage location 333, and a last update date and time 334 as data items is written.

  As the file ID 331 and the file version 332, data is set so that the file stored in the file folder entity 20 can be uniquely identified by combining these two data items.

  As the file storage location 333, the storage location of the file in the file folder entity 20 specified by the combination of the file ID 331 and the file version 332 is set. Specifically, as the file storage location 333, for example, if the file entity is an “ABC_00020002.txt” file directly under the “Material” folder of the C drive, “C ¥ Material ¥ ABC_00020002. txt "etc. are set. In addition to this, the file storage physical location (sector number, etc.) in the storage medium, the identification code for managing the file by the OS, etc. can be set as the file storage location 333. However, for the sake of explanation, an absolute path is added below. The description will be made assuming that the file name is set.

  As the last update date and time 334, the update date and time of the file specified by the combination of the file ID 331 and the file version 332 is set. Specifically, for example, “20061224121314” is set. Note that the last update date and time of the file can be obtained from the attribute information of the file entity using an API (Application Program Interface) provided by the OS.

FIG. 4 is an explanatory diagram of a document management method according to the present invention.
One or more document management records 310 are assigned to the document management table 31. In the document management record 310, data is written for a plurality of data items including the document ID 311 as described above. As the document ID 311, data for uniquely identifying a document is set for each document when the document is created. Therefore, there is no document management record 310 in which the same document ID 311 is set. FIG. 4 shows a state in which “0001”, “0002”, and “0003” are set as the document ID 311 in the three document management records 310, in other words, three documents have been created.

  One or more in-document file management records 320 are assigned to the in-document file management table 32. Here, even if a document is created, the file management table 32 in the document is not generated if no file to be referred to by the document is set. In the in-document file management record 320, data items such as a document ID 321, a file ID 322, and a file version 323 are set as data items. The document ID 321 indicates to which document management record 310 the in-document file management record 320 is related. A file is specified by a combination of the file ID 322 and the file version 323.

  For example, FIG. 4 includes two in-document file management records 320 in which “0001” is written as the document ID 321 and two in-document file management records 320 in which “0002” is written as the document ID 321. It is shown that each document to be referenced refers to two files. Here, a document whose document ID 321 is “0001” is a file whose file ID 322 is “0001” and whose file version 323 is “0001”, and whose file ID 322 is “0002” and whose file version 323 is “0001”. It is shown to refer to the file. In addition, a document whose document ID 321 is “0002” is a file whose file ID 322 is “0001” and whose file version 323 is “0001”, and whose file ID 322 is “0002” and whose file version 323 is “0002”. And to refer to.

  Even when a document is created, the file management table 33 is not generated when no file to which the document refers is set. In the file management record 330, data items such as a file ID 331, a file version 332, and a file storage location 333 are set as data items. A file is specified by a combination of the file ID 331 and the file version 332. Therefore, there is no file management record 330 in which the same file ID 331 and file version 332 are set. As the file storage location 333, the absolute path information of the file 200 in the file folder entity 20 is written.

  For example, in FIG. 4, there are three file management records 330 in which the combinations of the file ID 331 and the file version 332 are “0001, 0001”, “0002, 0001”, and “0002, 0002”, respectively, and corresponding file storage locations. 333 indicates that a storage location of a different file 200 is set.

FIG. 5 is a diagram illustrating a data configuration of the update management table.
The update management table 52 is a table for managing whether or not each file referred to by the document acquired from the server 1 has been updated on the client 4 side. A predetermined record (hereinafter referred to as “update management record”) 520 is assigned to the update management table 52. By referring to the update management table 52, it is easy to determine whether a file has been updated. When the file content is changed on the client 4 side and the file is updated, it is necessary to return the file to the server 1, but it is not necessary to return the file that has not been updated as a result, and the update management table 52 is referred to. This makes it easy to omit unnecessary processing such as return. Here, on the client 4 side, the corresponding file of the target document is written in the temporary file storage folder 51.

  In the update management record 520, data having a document ID 521, a document name 522, a file ID 523, a file version 524, a file storage location 525, and a file storage date 526 as data items is written.

  As the document ID 521, the file ID 523, and the file version 524, data is set so that the update management record 520 can be uniquely identified by combining them. Therefore, there is no update management record 520 having the same combination of these three data items.

  As the document name 522, the name of the document corresponding to the document ID 521, that is, the document name 312 in the document management record 310 having the same document ID 311 as the document ID 521 is set.

  As the file storage location 525, information including the storage location of the file in the temporary file storage folder 51 specified by a combination of the file ID 523 and the file version 524 is set. Specifically, for example, when the file entity is an “ABC_00020002.txt” file directly under the “temporary storage folder” folder of the C drive, “C \ temporary storage folder \ ABC_00020002.txt” with an absolute path added to the file. Etc. are set. As the file storage location 525, instead of an absolute path, a file storage physical location (sector number or the like) in the storage medium, an identification code for managing a file by the OS, or the like can be set. However, for convenience of explanation, In the following description, it is assumed that an absolute path is assigned and set.

  As the file storage date and time 526, the date and time when the file specified by the combination of the file ID 523 and the file version 524 is written in the temporary file storage folder 51 is set. Specifically, for example, data such as “20061224241314” is set. If the file storage date and time 526 and the last update date and time of the file do not match, it can be determined that the file has been updated on the client 4 side.

FIG. 6 is a diagram illustrating a data configuration of main communication messages transmitted and received between the server and the client.
The document transmission request message 61 is set as a transmission request when the client 4 requests the server 1 to transmit information regarding the document written in the document management table 31. The document transmission request message 61 includes a message ID 611 and a client identification 612 as data items.

As the message ID 611, data indicating that this message is a “document transmission request message” is set.
As the client identification 612, data such as an IP address that can uniquely identify the client 4 is set. The server 1 transmits the requested information to the client 4 set in the client identification 612.

  The document transmission message 62 is used when the server 1 transmits information regarding the corresponding document stored in the document management table 31 in response to the document transmission request message 61 from the client 4. The document transmission request message 62 includes a document ID 621 and a document name 622 as data items.

  As the document ID 621, the document ID 311 of the document requested to be transmitted is set by the number of records of the document management record 310 in which this ID is written (n examples are shown in FIG. 6). Similarly, as the document name 622, the document name 312 of the document requested to be transmitted is set for the number of records.

  The file transmission request message 63 is used when the client 4 requests the server 1 to transmit a file referred to by a specific document. The file transmission request message 63 includes a message ID 631, a client identification 632, and a document ID 633 as data items.

As the message ID 631, data indicating that this message is a “file transmission request message” is set.
As the document ID 633, an ID capable of uniquely identifying the document from which the client 4 is to acquire a file is set.

  As the client identification 632, data such as an IP address that can uniquely identify the client 4 is set. When the server 1 receives the file transmission request message 63, the server 1 searches for and acquires the in-document file management record 320 in which the same document ID 321 as the document ID 633 assigned to the in-document management table 32 is written, and the corresponding file entity etc. Is transmitted to the client 4 set in the client identification 632.

  The file transmission message 64 is used when the server 1 transmits a file entity or the like in response to the file transmission request message 63 from the client 4. The file transmission message 64 includes a document ID 641, a file ID 642, a file version 643, a file name 644, and a file entity 645 as data items.

  As the document ID 641, the set value of the document ID 633 set by the client 4 in the file transmission request message 63 is set. As the file ID 642, the file ID 322 of the in-document file management record 320 in which the same document ID 321 as the document ID 633 is written is set, and as the file version 643, the corresponding file version 323 is set.

  As the file entity 645, the storage location of the file entity 200 written in the file storage location 333 of the file management record 330 in which the same file ID 331 as the file ID 642 is written and the same file version 332 as the file version 643 is written. Is set. As the file name 644, the file name of the file entity 645 is set. The file ID 642, the file version 643, the file name 644, and the file entity 645 are set for the number of records (m) in the document file management record 320 corresponding to the above condition.

  The file return message 65 is used when the client 4 returns an updated file to the server 1. The file return message 65 includes a message ID 651, a client identification 652, a document ID 653, a file ID 654, a file version 655, and a file entity 656 as data items.

As the message ID 651, data indicating that this message is a “file return message” is set.
As the client identification 652, data such as an IP address that can uniquely identify the client 4 is set.

  As the document ID 653, an ID for identifying which document the file returned by the client 4 is referred to is set.

  As the file ID 654, the file version 655, and the file entity 656, the file ID 654, the file version 655, and the file entity 656 of the file updated on the client 4 side among the files referenced by the document identified by the document ID 653 are updated files. It is set for several minutes (p).

  In addition to the above messages, messages such as normal communication start and communication end are also transmitted and received between the server 1 and the client 4. Each message is added with necessary information such as a predetermined header and information indicating which message is a response to the message, and is subjected to necessary processing to be transmitted and received. Since these processes are performed according to the selected communication protocol and are well known, detailed description thereof will be omitted.

Next, the operation of the document management system according to the present invention will be described.
FIG. 7 is a flowchart illustrating GUI processing control performed by the server-side GUI processing control unit.
The GUI process control unit 11 is activated when the user activates the document management system via the input device 8 and performs GUI process control.

  First, the GUI processing control unit 11 displays an initial screen on the screen display device 7 (S701). FIG. 17 is a diagram showing an example of the initial screen. In FIG. 17, “new document creation” and the like are described as so-called buttons 1701 to 1706, and when these buttons 1701 to 1706 are clicked with a mouse or the like constituting the input device 8, GUI processing control is performed. The unit 11 detects which button is pressed.

  The GUI processing control unit 11 continues to wait for notification that the button has been pressed, and when the notification is received from a mouse or the like (S702), the pressed button (hereinafter simply referred to as “press button”) is “finished”. It is determined whether or not it is a button (S703).

  When it is determined that the pressed button is the “end” button, the GUI process control unit 11 deletes the initial screen (S704) and ends the process.

  When it is determined that the pressed button is not the “end” button, the GUI process control unit 11 executes processing corresponding to the pressed button (S705). Specifically, when the “Create new document” button 1701 is pressed, the new document creation unit 12 is selected. When the “Create diverted document” button 1702 or the “Create translated document” button 1703 is pressed, the diverted translation is performed. The document creation unit 13 is activated when the “add file” button 1704 is pressed, and when the “file display” button 1705 is pressed, the file display unit 15 is activated.

  Note that when the diverted translation document creation unit 13 is activated, the diverted translation document creation unit 13 is provided with information that can identify whether the pressed button is the “create diversion document” button or the “create translation document” button (hereinafter referred to as “create diversion document”) Simply called “Diversion / Translation Identification Information”).

  When the new document creation unit 12, the diverted translation document creation unit 13, the file addition unit 14, and the file display unit 15 finish the processing, the GUI processing control unit 11 receives a notification to that effect, returns to step S701, and displays the screen again. An initial screen is displayed on the display device 7.

FIG. 8 is a flowchart illustrating a new document creation process performed by a new document creation unit on the server side.
When started, the new document creation unit 12 displays a new document creation screen on the screen display device 7 (S801). FIG. 18 is a diagram showing an example of a new document creation screen. On the new document creation screen, a document name input field 1801, a “create” button 1802, and a “cancel” button 1803 are displayed.

  The new document creation unit 12 continues to wait for a notification that the button has been pressed. When the notification is received (S802), the new document creation unit 12 determines whether the pressed button is a “create” button (S803). If it is determined in step S803 that the push button is not the “create” button, the push button is a “cancel” button, and the new document creation unit 12 ends the process.

  If it is determined in step S803 that the pressed button is the “create” button, the new document creation unit 12 determines whether an appropriate document name is input in the document name input field (S804).

  The determination as to whether or not the input document name is appropriate is an error, for example, when the document name is not input or when only a blank character string is input. The determination may be made according to the type of document to be managed by the document management system. Further, if necessary, it may be determined that only a full-width character string is permitted. Further, a determination may be made that permits the input document name to match any of the document names 312 in the document management table. By configuring in this way, there is no document with the same name, and therefore it is possible to avoid an operation error such as a file being added to an unintended document by mistake. Hereinafter, in the present embodiment, description will be made assuming that determination including these exemplified determinations (hereinafter simply referred to as “document name appropriateness determination”) is performed.

  If it is determined in step S804 that an appropriate document name has not been input in the document name input field, the new document creation unit 12 displays an error message or the like on the new document creation screen, returns to step S802, and the button is pressed again. Wait for it.

  If it is determined in step S804 that an appropriate document name has been input, the new document creation unit 12 creates a document management record 310 (S805). Specifically, the maximum value of the document ID 311 is retrieved from the document management record 310 assigned to the document management table 31, and the result obtained by adding 1 is written as the document ID 311 in the created document management record 310. In the created document management record 310, the input document name is written as the document name 312, “new” is written as the diversion method 313, and the blank value is written as the diversion source document ID 314. The new document creation process is then terminated.

  Here, when the diversion method is “new”, a so-called empty document is created that does not refer to the file at all. In the present embodiment, a process for setting information about a file referred to by a document (hereinafter simply referred to as “file addition process”) will be described in the description of the file addition process described later. Note that another step may be provided after step S805 to perform file addition processing on the created document management record 310.

FIG. 9 is a flowchart for explaining a diversion translation document creation process performed by the diversion translation document creation unit on the server side.
First, the diverted translation document creation unit 13 displays a diversion source selection screen for selecting a diversion source document on the screen display device 7 when activated (S901). FIG. 19 is a diagram showing an example of the diversion source selection screen.

  On the diversion source selection screen, a document information display area 1901, a “select” button 1904, and a “cancel” button 1905 are displayed. At this time, the diverted translation document creation unit 13 searches all the document management records 310 assigned to the document management table 31 and temporarily sets the obtained document ID 311 and the document name 312 as a pair. The data is stored in a storage area (hereinafter simply referred to as “document information temporary storage area”). The diverted translation document creation unit 13 scrolls the document name 312 in the document name display field 1903 in the document information display area, and displays a document selection radio button 1902 corresponding to the document name display field.

  At this time, the arrangement order of the document name display fields may be determined from the viewpoint of the convenience of browsing, for example, the descending order of the document ID 311 and the ascending order of the document names 312 that are easy for the user to represent the newly created order. it can. It is assumed that information obtained by pairing the document ID 311 and the document name 312 in the document information temporary storage area is rearranged in accordance with the arrangement order of the document name display column for the later processing.

  Next, the diverted translation document creation unit 13 continues to wait for a notification that the button has been pressed. When the notification is received (S902), it is determined whether or not the pressed button is a “select” button (S903). . If it is determined in step S903 that the push button is not the “select” button, the push button is a “cancel” button, and the diverted translation document creation unit 13 ends the process.

  If it is determined in step S903 that the pressed button is the “select” button, the diverted translation document creation unit 13 determines whether the diversion source document is selected, that is, whether any of the document selection radio buttons is selected. Determination is made (S904). If it is determined in step S904 that no document selection radio button is selected, the diverted translation document creation unit 13 displays an error message or the like on the diversion source selection screen, returns to step S902, and the button is pressed again. Wait for The document selection radio button has a function as a so-called “radio button” and cannot select two or more buttons at the same time.

  When it is determined in step S904 that any one of the document selection radio buttons is selected, the diverted translation document creation unit 13 displays the diverted translation document creation screen on the screen display device 7 (S905). FIG. 20 is a diagram showing an example of the diverted translation document creation screen.

  On the diverted translation document creation screen, a document name input field 2001, a “create” button 2003, and a “cancel” button 2004 are displayed. When the diversion / translation identification information delivered from the GUI processing control unit indicates “diversion”, a diversion method selection radio button 2002 for selecting either “link diversion” or “branch diversion” is displayed. On the other hand, when the diversion / translation identification information indicates “translation”, the diversion method selection radio button 2002 is not displayed.

  The diverted translation document creation unit 13 continues to wait for a notification that the button has been pressed. When the notification is received (S906), the diversion translation document creation unit 13 determines whether the pressed button is a “create” button (S907). If it is determined in step S907 that the push button is not the “create” button, the diverted translation document creation unit 13 ends the process because the push button is a “cancel” button.

  If it is determined in step S907 that the pressed button is the “Create” button, the diversion translation document creation unit 13 determines whether the input content is appropriate (hereinafter simply referred to as “input appropriateness determination”) (S908). ).

  Here, the input appropriateness determination is performed in the same manner as the document name appropriateness determination as to whether or not an appropriate document name is input in the document name input field. For example, the document management system manages the document to be managed. This is based on the type. Next, when the diversion / translation identification information indicates “diversion”, it is a condition that one of the diversion method selection radio buttons is appropriately selected. In summary, when an appropriate document name is input and the diversion / translation identification information is “Diversion”, if any diversion method selection radio button is selected, it is determined that the input content is appropriate. The

  If it is determined in step S908 that the input content on the diversion translation document creation screen is not appropriate, the diversion translation document creation unit 13 displays an error message or the like on the diversion translation document creation screen, returns to step S906, and the button is pressed again. Wait for it.

  If it is determined in step S908 that the input content on the diversion translation document creation screen is appropriate, the diversion translation document creation unit 13 creates a document management record 310 (S909).

  Specifically, the maximum value of the document ID 311 is retrieved from the document management record 310 assigned to the document management table 31 as described above, and the result obtained by adding 1 to this is written as the document ID 311 and the corresponding document name 312 is obtained. The input document name is written. In addition, a document ID corresponding to the document name selected via the document selection radio button in the diversion source selection screen (hereinafter simply referred to as “selected document ID”) is written as the diversion source document ID 314. Specifically, for example, information indicating the number of the selected document selection radio button is acquired, and the document IDs in this order in the document information temporary storage area are written. Further, as the diversion method 313, when the diversion / translation identification information indicates “translation”, “translation” is written, and when the diversion / translation identification information is “diversion”, the diversion method selection radio button is selected. “Link diversion” or “Branch diversion” is written.

  Next, the diversion translation document creation unit 13 determines whether or not the diversion method is “translation” based on the diversion / translation identification information (S910). The file entity is copied to create a file management record 330 (S911).

  Here, copying of the file entity is performed as follows. First, the file ID 322 and the file version 323 are acquired for all records in which the document ID 321 is equal to the selected document ID among the in-document file management records 320 assigned to the in-document file management table 32. Next, a file management record (hereinafter simply referred to as “processing target file management record”) 330 having a file ID 331 and a file version 332 that match the acquired file ID 322 and file version 323 is searched. Next, the file entity is acquired based on the file storage location 333 of the processing target file management record 330. Finally, classify whether this file is a document file, table file, image file, etc. based on the obtained file entity, that is, the file name extension of the file, and copy according to the classification result Process. For example, since the image file does not require translation, the target file is simply copied in the file folder entity 20, and the document file has a format and content that can be decoded by the translation software. The changed file is created in the file folder entity 20. Here, the file version added to the file name of the duplicate file or the created file is changed to one added. In addition, the absolute path of the duplicate file and the date and time when the file was copied are read for later processing.

  In addition to the above method using an extension, for example, the file classification may be performed by searching the contents of the file and determining whether or not character information to be translated is included. In addition, the processing such as copying performed based on the classification result is not limited to the above, and is suitable for a program used for editing the target file, for example, changing the extension of the duplicate file or the created file. It may be a process to do so. Furthermore, it may be possible not to copy a specific file based on the classification result. However, in this case, it is necessary to exclude the target file from the processing for creating the file management record 330 and the processing for creating and updating the in-document file management record 320 described below.

  The file management record 330 is created as follows. As the file ID 331 of the newly created file management record 330, the file ID 331 of the processing target file management record is added to the file version 332 of the processing target file management record as the file version 332 (copied in the file folder entity 20) Is the same as the file version given to the file name of the equalized file), the absolute path of the file copied as the file storage location 333, and the date and time when the file was copied as the last update date and time 334, respectively. Is set. The setting values of these data items are written in the file management record 330, and form a file management table 33 as management information for a new file.

  Next, the diverted translation document creation unit 13 performs the “document file management record creation / update process” described below (S912). In the “document file management record creation / updating process”, the document file management record 320 is created and updated regardless of the diversion method.

  Here, the new in-document file management record 320 is created by copying all records in which the document ID 321 is equal to the selected document ID among the in-document file management records 320 assigned to the in-document file management table 32. Is done. At this time, the document ID 311 of the document management record 310 created in step S909 is set as the document ID 321 of the record obtained by copying (hereinafter simply referred to as “copy destination record”).

Next, the file ID 322, the file version 323, and the file group last update date and time 324 of the copy destination record are set as follows.
First, when the diversion / translation identification information indicates “diversion”, the corresponding information of the copy source record is set as the file ID 322, the file version 323, and the file group last update date 324.

Next, when the diversion / translation identification information indicates “translation”, the file ID 322 corresponding to the copy source record is added as the file version 323 to the file version 323 of the copy source record, respectively. Is set. Further, as the file group last update date and time 324, the latest value of the last update date and time 334 is acquired and set from all the records assigned to the file management table 33 and having the same file ID 331 as the file ID 322.
The set value of each data item corresponding to the diversion / translation identification information is written in the copy destination record, and forms the in-document file management table 32 as new management information.

Documents that share all reference files with the diversion source document by the above diversion translation document creation process (diversion method is “link diversion” or “diversion diversion”), or all files are copied from the diversion source document, etc. (The translation method is “translation”). Therefore, the file referred to by the created document completely matches or corresponds to the file referred to by the diversion source document.
The diverted translation document creation unit 13 then ends the process.

  Here, when the created document needs to refer to a file different from the diversion source document, for example, a file addition process described below is performed. On the other hand, in the present embodiment, no means for deleting a file referred to by a created document is described, but a file deletion unit for deleting unnecessary file management records 320 is added to the server 1 side. This can be realized.

FIG. 10 is a flowchart illustrating file addition processing performed by the file addition unit on the server side.
First, when activated, the file addition unit 14 displays a file addition screen on the screen display device 7 (S1001). FIG. 21 is a diagram illustrating an example of the file addition screen. On the file addition screen, a document name input field 2101, a file information display area 2102, a file selection check box 2103, a file name display field 2104, a “create” button 2105 and a “cancel” button 2106 are displayed.

  At this time, the file adding unit 14 searches all the files 200 stored in the file folder entity 20, and based on the file name, the file ID and file version, and the file storage location and update based on the file management table or the like. Get the year and month. The acquired file name, file ID, file version, and file storage location are stored in a storage area that is associated and temporarily stored (hereinafter simply referred to as “file information temporary storage area”). The file name stored in the file information temporary storage area is scrolled and displayed in the file name display field 2104 in the file information display area 2102, and a file selection check box 2103 is displayed corresponding to the file name display field 2104. .

  Here, the arrangement order of the file name display fields can be determined from the viewpoint of convenience of browsing, for example, the descending order of the file IDs, the ascending order of the file names easy to understand for the user, so as to represent the newly created order, etc. . In addition, for use in later processing, related information including the file name, file ID, file version, file storage location, and update date in the file information temporary storage area is also combined with the arrangement order of the file name display column. It shall be rearranged.

  The file adding unit 14 continues to wait for a notification that the button has been pressed, and when receiving the notification (S1002), determines whether the pressed button is an “add” button (S1003). If it is determined in step S1003 that the push button is not an “add” button, the push button is a “cancel” button, and the file addition unit 14 ends the processing.

  If it is determined in step S1003 that the pressed button is the “add” button, the file adding unit 14 determines whether the input content is appropriate (S1004).

  Here, the determination as to whether or not the input content is appropriate is made in the same manner as in the document name appropriateness determination as to whether or not an appropriate document name has been input in the document name input field. For example, when the input document name is set in any of the document names 312 in the document management table 31, it is determined as an appropriate document name. Next, it is a condition that it is deemed appropriate that any one or more file selection check boxes are selected. In summary, when an appropriate document name is input and any one or more file selection check boxes are selected, it is determined that the input content is appropriate.

  If it is determined in step S1004 that the input content on the file addition screen is not appropriate, the file addition unit 14 displays an error message or the like on the file addition screen, returns to step S1002, and waits for the button to be pressed again.

  If it is determined in step S1004 that the input content on the file addition screen is appropriate, the file addition unit 14 copies the file selected by the file selection check box (S1005).

  Specifically, first, information indicating the number of the selected file selection check box is acquired, and the file name, file ID, file version, and file storage location in this order in the file information temporary storage area (hereinafter referred to as the file storage check box) , “Addition source file name”, “addition source file ID”, “addition source file version”, and “addition source file storage location”).

  Next, among the file management records 330 assigned to the file management table 33, the maximum value of the file version 332 (hereinafter simply referred to as “addition destination file version”) from the file management record 330 having the same file ID 331 as the addition source file ID. Obtained and incremented by one. Here, when the file ID 331 equal to the addition source file ID is not set in the file management table 33, the acquired file version itself ("0001" in FIG. 4) is set as the addition destination file version. Is done.

  Next, the file addition unit 14 copies the file entity of the addition source file storage location into the file folder entity 20. At this time, the file version given to the file name of the copy destination file is changed to the addition destination file version. Also, the file storage location of the copy destination file and the copy date and time are acquired.

  Next, the file addition unit 14 creates a file management record 330 (S1006). Specifically, the copy source file ID 331 is the copy source file ID, the file version 332 is the add destination file version, the file storage location 333 is the file storage location of the copy destination file, and the last update date and time 334 is the copy process. Each date and time is set. The setting values of these data items are written in the file management record 330, and form a file management table 33 as management information for a new file.

  Next, the file addition unit 14 creates and updates the in-document file management record 320 (S1007).

  Specifically, first, the record assigned to the document management table 31 is searched for the same document name as the input document name 312, and the document ID 311 of this record is set as the document ID 321. Further, an addition source file ID is set as the file ID 322, and an addition destination file version is set as the file version 323, respectively. Next, the latest value of the last update date and time 334 is acquired from the file management record 330 (hereinafter referred to as “same group record”) assigned to the file management table 33 and having the file ID 331 and the file version 332 written in S1006. The file group last update date and time 324 is set. Then, the setting values of these data items are written in the in-document file management record 320 to form the in-document file management table 32 as new file management information. Further, the latest value of the last update date and time 334 is written and updated as the file group last update date and time 324 of the same group record.

  Here, the file addition unit 14 repeatedly executes the above-described processing from step S1005 to S1007 by the number of selected files, that is, the number of selected file selection check boxes.

  In the above description, regardless of the diversion method of the file addition target document, it is assumed that the file entity of all the files to be added is copied and created, but the processing is changed depending on the diversion method of the document. But you can. For example, for a document whose diversion method 313 is “new”, the above-described processing is performed. For a document whose diversion method 313 is “link diversion” or “branch diversion”, among the above processing, file copying and For the document whose diversion method 313 is “translation”, the process may be changed according to the type of the file, omitting the process of creating the file management record 330.

FIG. 11 is a flowchart illustrating file display processing performed by the file display unit on the server side.
First, when activated, the file display unit 15 displays a file display screen on the screen display device 7 (S1001). FIG. 22 is a diagram illustrating an example of a file display screen. On the file display screen, a document name input field 2201, a file information display area 2102, a “display” button 2204, and an “end” button 2205 are displayed. No information is displayed in the file information display area of the file display screen displayed in step S1001.

  Next, the file display unit 15 continues to wait for notification that the button has been pressed. When the notification is received (S1102), the file display unit 15 determines whether the pressed button is a “display” button (S1103). If it is determined in step S1103 that the pressed button is not a “display” button, the file display unit 15 ends the process because the pressed button is an “end” button.

  If it is determined in step S1103 that the pressed button is the “display” button, the file display unit 15 determines whether an appropriate document name is input in the document name input field (S1004). Here, the determination of whether or not the input document name is appropriate is performed in the same manner as the above-described document name appropriateness determination. For example, when the input document name is set in any of the document names 312 in the document management table 31, it is determined as an appropriate document name.

  If it is determined in step S1104 that an appropriate document name has not been input, the file display unit 15 displays an error message or the like on the file display screen, returns to step S1002, and waits for the button to be pressed again.

  If it is determined in step S1104 that an appropriate document name has been input, the file display unit 15 displays a file referred to by the document having the input document name in the file information display area (S1105).

  Specifically, first, the record assigned to the document management table 31 is searched for the same document name as the input document name 312 and the document ID 311 of this record is acquired. Next, the record assigned to the in-document file management table 32 and having the document ID 311 written as the document ID 321 is searched, and the file ID 322, the file version 323, and the file group last update date and time 324 of the record are searched from all the searched records. Acquired, correlated, and temporarily stored in the file information temporary storage area.

  Next, the file management record 330 assigned to the file management table 33 is searched for a file ID 331 and a file version 332 that are the same as the file ID and file version stored in the file information temporary storage area. The file storage location 333 and the last update date and time 334 are acquired, and the file name is acquired based on the acquired file storage location 333. The acquired file name and last update date / time are stored in the file information temporary storage area in association with the file ID, file version, and file group last update date / time.

  Next, the file display unit 15 scrolls and displays the file name stored in the file information temporary storage area in the file name display field 2203 in the file information display area. At this time, the last update date stored in the file information temporary storage area in association with each file name is compared with the last update date of the file group, and if they do not match, the file name is displayed in a prominent color (for example, red). May be. As a result, for example, after the file referred to by the target document is last updated, a file having the same file ID and a different file version is created or updated, and a file that is not appropriately changed may be referred to. When there is, etc., the user can be alerted, which is preferable. Alternatively, or in addition to this, the last update date and time and the file group last update date and time may be displayed in the file information display area in association with each file name.

  After the display is completed, the file display unit 15 returns to step S1102 and continues to wait until the button is pressed again.

FIG. 12 is a flowchart for explaining data transmission processing performed by the data transmission processing unit on the server side.
Although the data transmission processing unit 16 of the server 1 continues to operate from the start to the stop of the server 1, a series of related data transmission processes will be described below.

  First, the data transmission processing unit 16 continues to wait until it receives messages 61, 63, 65 from the client 4 (S1201).

  When the messages 61, 63, and 65 are received in step S1201, the data transmission processing unit 16 reads the setting values of the message IDs 611, 631, and 651 from the messages 61, 63, and 65 to determine whether the message is a “document transmission request message”. Is determined (S1202).

  If it is determined in step S1202 that it is a “document transmission request message”, the data transmission processing unit 16 transmits the information set in the document management record 310 to the client 4 (S1203).

  Specifically, the document ID 311 and the document name 312 are acquired from all the document management records 310 assigned to the document management table 31, and the document ID 621 and the document name 622 of the document transmission message 62 are equal to the number of records (n). Is set. Next, the document transmission message 62 set with data is transmitted to the client 4 specified by the client identification 612. Then, the process returns to step S1201 and again waits for reception of a message from the client 4.

  If it is determined in step S1202 that it is not a “document transmission request message”, the process jumps to step S1204, and the data transmission processing unit 16 determines whether the setting values of the message IDs 611, 631, and 651 are “file transmission request messages”. Is determined (S1204).

  If it is determined in step S1204 that the message is a “file transmission request message”, the data transmission processing unit 16 performs file transmission processing (S1205 to S1213). If it is determined in step S1204 that the message is not a “file transmission request message”, that is, if it is determined that the message is neither a “document transmission request message” nor a “file transmission request message”, the process returns to step S1201, and the client 4 again Message waiting is received.

Hereinafter, the file transmission process will be described.
In the file transmission process, first, the data transmission processing unit 16 transmits the file requested to be transmitted to the client 4 (S1205).

  Specifically, first, the in-document file management record 320 assigned to the in-document file management table 32 is searched for the same document ID 321 as the document ID 633 of the file transmission request message 63, and from the searched records. A file ID 322 and a file version 323 are acquired. Next, among the file management records 330 assigned to the file management table 33, the same record as the file ID 322 and the file version 323 in which the file ID 331 and the file version 332 are acquired is searched, and the file is searched from the searched record. A storage location 333 is acquired, and a file entity is read based on the acquired file storage location 333.

  Next, the file ID 331 (that is, the file ID 322), the file version 332 (that is, the file version 323), the acquired file storage location 333, and the file entity are the file ID 642, the file version 643, and the file of the file transmission message 64, respectively. Name 644 and file entity 645 are set. For example, the file ID 331 as the file ID 642 and 1 added to the file version 332 as the file version 643, the file name described after the path of the file storage location 333 as the file name 644, the file entity as the file entity 645, Each is set. A document ID 633 is set as the document ID 641. Then, the file transmission message 64 in which the data is set is transmitted to the client 4 specified by the client identification 632.

  Next, the data transmission processing unit 16 determines whether or not the document diversion method 313 is “branch diversion” for all the same files transmitted to the client 4 (S1206). If it is determined in step S1206 that it is not “branch diversion” (in the case of “new”, “translation” or “link diversion”), file version upgrade processing (S1208 to S1210) is performed.

  If it is determined in step S1206 that the diversion method is branch diversion, the data transmission processing unit 16 determines whether the file is in a shared state (S1207). For example, there are other records in which the same file ID 322 and file version 323 as the file ID 642 and file version 643 set in the file transmission message 64 in step S1205 exist, respectively, and the document ID 321 of this record is the file transmission message. If the document ID is different from the document ID 641 set to 64, the same file entity is referred to by a plurality of documents, and it is determined that the document is in a shared state.

  If it is determined in step S1207 that the file is not in a shared state, a file upgrade process is performed. If it is determined that the file is in a shared state, a file copy process (S1211 to S1213) is performed.

The file upgrade process will be described below.
In the file upgrade process, first, the data transmission processing unit 16 sets the file management record 330 in which the file ID 322 and the file version 323 that are the same as the file ID 642 and the file version 643 set in the file transmission message 64 in step S1205, respectively. Is retrieved, the file storage location 333 in this record is obtained, and the file name of the file entity is changed based on the obtained file storage location 333 (S1208). Specifically, the file version assigned to the file name is changed to a name obtained by adding 1. The file name can be changed based on the file storage location 333 (that is, the absolute path of the file) by using a general OS API.

  Next, the data transmission processing unit 16 adds 1 to the file version 332 of the file management record 330 searched above, sets the date and time when the file name was changed in step S1205 as the last update date and time 334, and performs file management. The record 330 is updated (S1209).

  Next, the data transmission processing unit 16 searches the in-document file management record 320 in which the same file ID 322 and file version 323 as the file ID 642 and file version 643 set in the file transmission message 64 in step S1205 are set, respectively. For all retrieved records (there may be two or more records that satisfy the condition), the file version 323 is incremented by 1, and the date and time when the file name was changed in step S1205 as the file group last update date and time 324 The document file management record 320 is set and updated (S1210).

Next, file copy processing will be described.
In the file copy process, first, the data transmission processing unit 16 stores the file management record 330 in which the file ID 331 and the file version 332 set to be the same as the file ID 642 and the file version 643 set in the file transmission message 64 in step S1205, respectively. Retrieve the file storage location 333 in this record, read the file entity based on the acquired file storage location 333, change the file name to the one added to the file version assigned to it, and copy (S1211).

  Next, the data transmission processing unit 16 creates a file management record 330 corresponding to the file obtained by copying in step S1211 (S1212). More specifically, the file ID 331 of the file management record 330 searched in step S1211 as the file ID 331 and the file version 332 of the file management record 330 added by 1 as the file version 332 are the copy destination as the file storage location 333. The absolute path of the file and the date and time when the file copy was performed are set as the last update date and time 334, respectively, and written to the new file management record 330.

  Next, the data transmission processing unit 16 searches the in-document file management record 320 in which the same file ID 322 and file version 323 as the file ID 642 and file version 643 set in the file transmission message 64 in step S1205 are set, respectively. For all the retrieved records (there may be two or more records that satisfy the condition), the update is performed as follows (S1213).

  That is, for the in-document file management record 320 in which the same document ID 321 as the document ID 641 set in the file transmission message 64 in step S1205 is set, the file version 323 is incremented by 1, and the file group last update date and time 324 is set. The date and time when the file name is changed is set, and the in-document file management record 320 is updated.

On the other hand, for the in-document file management record 320 in which the document ID 321 different from the document ID 641 is set, the date and time when the file name is changed is set as the file group last update date and time 324, and the in-document file management record 320 is updated.
The data transmission process is then terminated.

FIG. 13 is a flowchart for explaining data reception processing performed by the data reception processing unit on the server side.
The data reception processing unit 17 of the server 1 continues to operate from the start to the stop of the server 1, but the following description will be made taking reception of the file return message 65 as an example.

  First, the data reception processing unit 17 continues to wait for reception of a file from the client 4, that is, reception of the file return message 65 in which the message IDs 611, 631, and 651 are set from the client 4 (S1301).

  When the file return message 65 is received in step S1301, the data reception processing unit 17 is set in the received message, and all of the p pieces of file information including the file ID 654, the file version 655, and the file entity 656 are as follows. Process.

  First, the data reception processing unit 17 searches the file management record 330 in which the same file ID 331 and file version 332 as the file ID 654 and file version 655 set in the received message are searched, The file storage location 333 is acquired, the file entity is read based on the acquired file storage location 333, and the file entity 656 is set and updated (S1302).

  Next, the data reception processing unit 17 sets the date and time when the file was updated in step S1302 as the last update date and time 334 of the file management record 330 searched in step S1302, and updates the file management record 330 (S1303). .

  Next, the data reception processing unit 17 searches the file management record 320 in the document in which the same file ID 322 and file version 323 as the file ID 654 and file version 655 set in the received message are searched and searched. For all the recorded records (there may be two or more records that satisfy the condition), the date and time when the file was updated in step S1302 is set as the file group last update date and time 324, and the in-document file management record 320 is set. Update (S1304).

FIG. 14 is a flowchart for describing processing and control performed by the processing control unit on the client side.
The processing control unit 41 on the client 4 side is activated when an instruction to activate the client side processing of the document management system is input via the input device A by the user.

  First, the process control unit 41 displays an initial screen on the screen display device 9 (S1401). FIG. 23 is a diagram showing an example of the initial screen. In FIG. 23, a portion where “file acquisition” or the like is described shows so-called buttons 2301 to 2303, and when this portion is clicked with a mouse or the like that forms part of the input device A, the process control unit 41 Receive notification that the button has been pressed.

  Next, the process control unit 41 continues to wait for notification that the button has been pressed. When the notification is received (S1402), the process control unit 41 determines whether the pressed button is an “end” button (S1403). If it is determined in step S1403 that the pressed button is the “end” button, the process control unit 41 deletes the initial screen (S1404) and ends the process.

  If it is determined in step S1403 that the pressed button is not an “end” button, the process control unit 41 executes processing corresponding to the pressed button (S1405). Specifically, the file acquisition unit 42 is activated when the “file acquisition” button is pressed, and the file return unit 43 is activated when the “file transmission” button is pressed. When the processing by the file acquisition unit 42 and the file return unit 43 is completed, the process control unit 41 receives a notification to that effect, returns to step S1401, and causes the screen display device 9 to display the initial screen again.

FIG. 15 is a flowchart illustrating file acquisition processing performed by the file acquisition unit on the client side.
First, the file acquisition unit 42 uses data identifying a “document transmission request message” as the message ID 611 in the document transmission request message 61 and data (for example, an IP address) identifying the client 4 as the client identification 612. Each is set and transmitted to the server 1 (S1501).

  Next, the file acquisition unit 42 continues to wait until a response from the server 1, that is, the document transmission message 62 is received (S1502), and when the document transmission message 62 is received, the acquired document selection screen is displayed on the screen display device 9. It is displayed (S1503). FIG. 24 is a diagram illustrating an example of an acquired document selection screen. On the acquired document selection screen, a document information display area 2401, an “acquire” button 2404, and a “cancel” button 2405 are displayed.

  In step S1503, the file acquisition unit 42 also scrolls and displays the document name 622 set in the document transmission message 62 in the document name display field 2403 in the document information display area 2401 to correspond to the document name display field 2403. The document selection radio button 2402 is displayed.

  At this time, the arrangement order of the document name display column may be determined from the viewpoint of convenience of browsing such as descending order of the document ID 621 and ascending order of the document name 622 that is easy for the user to represent the newly created order. it can. It is assumed that information obtained by pairing the document ID 621 and the document name 622 in the document transmission message 62 is rearranged in accordance with the arrangement order of the document name display column for the subsequent processing.

  Next, the file acquisition unit 42 continues to wait for notification that the button has been pressed. When the notification is received (S1504), the file acquisition unit 42 determines whether the pressed button is an “acquire” button (S1505). If it is determined in step S1505 that the pressed button is not an “acquire” button, the file acquisition unit 42 ends the process because the pressed button is a “cancel” button.

  If it is determined in step S1505 that the pressed button is the “acquire” button, the file acquisition unit 42 determines whether an acquired document is selected, that is, one of the document selection radio buttons is selected ( S1506).

  If it is determined in step S1506 that no document selection radio button is selected, an error message or the like is displayed on the acquired document selection screen, and the process returns to step S1504 to wait for the button to be pressed again. The document selection radio button has a function as a so-called “radio button” and cannot select two or more buttons at the same time.

  If it is determined in step S1506 that any one of the document selection radio buttons is selected, the file acquisition unit 42 sets data identifying the “file transmission request message” as the message ID 631 in the file transmission request message 63. Data for identifying the client 4 (for example, IP address) is set as the client identification 632, and the document ID 621 of the document selected by the document selection radio button is set as the document ID 633, and transmitted to the server 1 (S1507).

  Next, the file acquisition unit 42 continues to wait until the response from the server 1, that is, the file transmission message 64 is received (S1508). When the file transmission message 64 is received, all the received n pieces of file information are temporarily stored in the file. The update management record 520 is created while being stored in the storage folder 51 (S1509).

Specifically, the file entity 645 is stored (that is, stored) in the temporary file storage folder 51 as a file having a file name set in the file name 644. In addition, the document ID 641 of the file transmission message 64 as the document ID 521 of the update management record 520, the document name 622 in the document transmission message 62 in which the same document ID 621 as the document ID 641 is set as the document name 522, and the document ID 642 as the file ID 523 are set. However, the file version 643 as the file version 524 and the absolute path of the file entity stored in the temporary file storage folder 51 as the file storage location 525 are updated from the OS of the client 4 as the file storage date and time 526. The date and time are respectively set, and the update management record 520 is created (that is, stored).
Thereafter, the file acquisition unit 42 ends the process.

FIG. 16 is a flowchart for describing file return processing performed by the file return unit on the client side.
First, the file return unit 43 displays a return document selection screen on the screen display device 9 (S1601). FIG. 25 is a diagram showing an example of a return document selection screen. On the return document selection screen, a document information display area 2501, a “return” button 2504 and a “cancel” button 2505 are displayed.

  In step S1601, the file return unit 43 acquires the document ID 521 and the document name 522 for all the update management records 520 assigned to the update management table 52, and has different setting values as the document ID 521. All are temporarily stored (hereinafter simply referred to as “document name temporary storage area”). Then, the document name stored in the document name temporary storage area is scrolled and displayed in the document name display field 2503 in the document information display area, and a document selection radio button 2502 is displayed in association with the document name display field.

  At this time, the arrangement order of the document name display fields can be determined from the viewpoint of convenience of browsing, for example, the descending order of the document ID 621 to indicate the newly created order, the ascending order of the document names easy to understand for the user, and the like. . It is assumed that information obtained by pairing the document ID and the document name in the document information temporary storage area is rearranged in accordance with the arrangement order of the document name display column for the later processing.

  Next, the file return unit 43 continues to wait for notification that the button has been pressed. When the notification is received (S1602), the file return unit 43 determines whether the press button is a “return” button (S1603). If it is determined in step S1603 that the pressed button is not a “return” button, the file return unit 43 ends the process because the pressed button is a “cancel” button.

  If it is determined in step S1603 that the pressed button is the “return” button, the file return unit 43 determines whether a return document is selected, that is, one of the document selection radio buttons is selected (step S1603). S1604). If it is determined in step S1604 that no document selection radio button has been selected, the file return unit 43 displays an error message or the like on the return document selection screen, returns to step S1602, and presses the button again. wait. The document selection radio button has a function as a so-called “radio button” and cannot select two or more buttons at the same time.

  If it is determined in step S1604 that any one of the document selection radio buttons is selected, the file return unit 43 determines whether or not there is an updated file referred to by the selected document in the temporary file storage folder 51. Is determined (S1605).

  Here, out of the update management records 520 assigned to the update management table 52, the records set with the same document ID 521 as the document ID of the selected document are retrieved, and whether or not all the retrieved records are updated. If it is determined that even one record has been updated, it is determined that an update file exists. Whether or not each update management record 520 is updated indicates that the update date and time managed by the OS for the file stored in the file storage location 525 is acquired, and there is no update when the acquired data is the same as the file storage date and time 526. If it is different, it is determined that there is an update.

If it is determined in step S1605 that the updated file does not exist, the process ends.
If it is determined in step S1605 that the updated file exists, the file return unit 43 uses the data identifying the “file return message” as the message ID 651 of the file return message 65, and uses the client 4 as the client identification 652. The identification data (for example, IP address) is set as the document ID of the selected document as the document ID. Further, for all the files determined to be “updated” in step S1605 (p files), the file ID 522 is the file ID 654, the file version 523 is the file version 655, and the content information of this file entity is the file entity 656. These are set and transmitted to the server 1 (S1605).

Next, the file return unit 43 sets the update date and time of the file managed by the OS as the file storage date and time 525 of the corresponding update management record 520 for all the files determined to be “updated” in step S1605. The update management record 520 is updated to match the file update date managed by the update management table 52 with the update date of the file entity (S1607).
Thereafter, the file return unit 43 ends the process.

  FIG. 26 is a diagram showing another configuration of the table constituting the document management DB. 3 is different from the configuration shown in FIG. 3 in that an in-document folder management table 34 is added and a folder ID 325 is added as a data item of the in-document file management table 32.

  Here, the in-document folder management table 34 is a table for displaying the file referred to by the document so as to be managed in a hierarchical structure when the file referred to by the document is displayed on the file display screen or the like. For example, as in the case where the file display browser on the OS displays a file list, it is possible to display that a folder or file exists immediately under the document and another folder or file exists immediately below the folder. In order to realize this function, as many records as the number of folders included in the target document are created for each document. Here, the creation of the in-document folder management record 340 is most simply performed using, for example, an SQL (Structured Query Language) command in the RDB. Further, the document management system may be configured to include a folder creation unit on the server 1 side for creating a folder by a normal method using a GUI.

  In the document folder management record 340, data having the document ID 341, the folder ID 342, the folder level 343, the folder name 344, and the upper folder ID 345 as data items is written.

As the document ID 341, the document ID 311 of any document management record 310 is set.
As the folder ID 342, data that can uniquely identify a folder having the same document ID 341 is set.
The folder level 343 is a data item indicating the hierarchy of the folder. For example, “0001” is set for the folder directly under the document in the folder level 343, and this folder is set separately for the folder directly under another folder. A value obtained by adding 1 to the folder level 343 of the folder is set.
The folder name 344 is a display name when a file referred to by a document is displayed on a file display screen or the like.
The upper folder ID 345 is set to “0000” for a folder directly under the document, and a folder ID 342 of this other folder is set for a folder immediately under another folder.

  As the folder ID 325 of the in-document file management table 32, information indicating in which folder the target file is displayed when the file referred to by the document is displayed on the file display screen or the like is set. Specifically, “0000” is set for a file directly under a document, and a folder ID 342 of this folder is set for a file immediately under a folder.

  By defining the hierarchical structure in the document management system as described above, the document structure can be copied when the document is diverted as described below. That is, in the document file management record creation process (S912) when the diversion method 313 creates a diversion or translation document, the folder ID 325 is set and the document folder management record is created. Specifically, what is written in the copy source record is set as the folder ID 325.

  The in-document folder management record 340 is created as follows. That is, of the in-document folder management records 340 assigned to the in-document folder management table 34, all records having the same document ID 341 as the selected document ID are copied.

  Here, the document ID 311 of the document management record 310 created in the diverted translation document creation process is set as the document ID 341. Further, as the folder ID 342, the folder level 343, the folder name 344, and the upper folder ID 345, corresponding ones of the copy source records are set. The record created by copying in this way is written and forms a new document management record 310 assigned to the in-document folder management table 34.

  By configuring in this way, not only the hierarchical structure (folder) of the diversion source document can be copied, but the document whose diversion method 313 is “translation” has the same hierarchical structure as the diversion source document. , It is possible to realize the use that the files to be referred to (that is, files directly under the document or folder) are different. Also, it is possible to copy only the hierarchical structure without copying the file.

  Further, for a document whose diversion method 313 is “link diversion” or “branch diversion”, similarly to the case where the diversion method 313 is “translation”, only the hierarchical structure is copied, and the hierarchical structure and only a part of files are copied. Is possible.

  In the above description, the file diversion method is stored in the document management record 310 as the diversion method 313. In addition to this, the diversion method 325 is provided in the in-document file management record 320 to further share the file. The usage flexibility can be improved.

  In the diversion method 325, the same contents as the diversion method 313 are set when the intra-document file management record 320 is created in the diversion translation document creation process (FIG. 9). That is, the diversion method set in the diversion method 313 is the default diversion method of the target document.

  Then, in the file addition screen (FIG. 20) displayed in the file addition process (FIG. 10), it is possible to input a diversion method (diversion diversion or link diversion) for each selected file, and when the diversion method is input. Sets the input diversion method to the diversion method 325, and if the diversion method is not input, sets the diversion method 313 of the file addition target document management record 310 to the diversion method 325.

  In addition, the server 1 is provided with a diversion method changing unit for changing the setting contents of the diversion method 325 in the file management record 320 in the created document according to a user instruction.

  Then, the data transmission processing unit 16 determines whether the file diversion method is “branch diversion” in the data transmission process (S1206 in FIG. 12) in the document management record 310 instead of the diversion method 313. This is done by referring to the diversion method 325 of the file management record 320.

  By making improvements as described above, for example, when creating a revised version of a catalog, it is set as “link diversion” at the time of creation of the diverted document, and among the files referenced by the document, a file that changes for each version, for example, Only the files related to the price list can be changed to "Diversion".

  Furthermore, information for identifying the diversion classification of the file is added to the end of the file name of the file stored in the file folder entity 20, and stored as, for example, “ABC.txt_00010001_link diversion” or “ABC.doc_00020001_branch diversion”. You may make it do.

  With this configuration, when the in-document file management record 320 is created in the diverted translation document creation process (FIG. 9), for the file whose diversion method is specified at the end of the file name, the specified diversion method is used. When the diversion method 325 is set and the file addition screen (Fig. 20) is displayed in the file addition process (Fig. 10), it is specified at the end of the file name as the initial value in the input field of the diversion method (diversion diversion or link diversion) The diversion method used can be displayed.

  By adding “branch diversion” to the end of the file name for a file that changes for each diverted document, for example, a file related to a price list, the diversion method 325 without being aware of every document creation and after the document creation. It is possible to select an appropriate diversion method for each file without performing an operation of changing the file name.

1 is a system configuration diagram of a document management system according to the present invention. FIG. It is a system block diagram which shows the structure by the side of the server of a document management system in detail. It is a figure which shows the structure of the table which makes document management DB. It is explanatory drawing about the document management method by this invention. It is a figure which shows the data structure of an update management table. It is a figure which shows the data structure of the main communication message transmitted / received between a server and a client. It is a flowchart explaining the GUI process control which the GUI process control part by the side of a server performs. It is a flowchart explaining the new document creation process which the new document creation part by the server side performs. It is a flowchart explaining the diversion translation document creation process which the diversion translation document preparation part by the side of a server performs. It is a flowchart explaining the file addition process which the file addition part by the side of a server performs. It is a flowchart explaining the file display process which the file display part by the side of a server performs. It is a flowchart explaining the data transmission process which the data transmission process part by the side of a server performs. It is a flowchart explaining the data reception process which the data reception process part by the side of a server performs. It is a flowchart explaining the process and control which a process control part by the side of a client performs. It is a flowchart explaining the file acquisition process which the file acquisition part by the side of a client performs. It is a flowchart explaining the file reply process which the file return part by the side of a client performs. It is a figure which shows the Example of an initial screen. It is a figure which shows the Example of a new document creation screen. It is a figure which shows the Example of a diversion source selection screen. It is a figure which shows the Example of a file addition screen. It is a figure which shows the Example of a file display screen. It is a figure which shows the Example of a file display screen. It is a figure which shows the Example of an initial screen. It is a figure which shows the Example of an acquisition document selection screen. It is a figure which shows the Example of a return document selection screen. It is a figure which shows the other structure of the table which makes | forms document management DB.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Server 1A Central control device 1B Storage device control device 1C Output device control device 1D Input device control device 1E Internal bus 2 Storage device 3 Storage device 4 Client 5 Storage device 6 Communication line 7 Screen display device 8 Input device 9 Screen display device 10 Main storage device 11 GUI processing control unit 12 New document creation unit 13 Diverted translation document creation unit 14 File addition unit 15 File display unit 16 Data transmission processing unit 17 Data reception processing unit 18 OS etc. 10 Main storage device 11p GUI processing control program 12p New document creation program 13p Diverted translation document creation program 14p File addition program 15p File display program 16p Data transmission processing program 17p Data reception processing program 18p OS etc. 20 Folder file entity storage 30 Document management DB
31 Document management table 32 Document file management table 33 File management table 41 Processing control unit 42 File acquisition unit 43 File return unit 51 File temporary storage folder 52 Update management table 61 Document transmission request message 62 File transmission request message 63 File return message A Input device B Storage device B0 Server function program

Claims (2)

A document management system having a server that manages a document, which is a collection of one or more files, using information indicating which file the document refers to .
(A) When creating a document using an existing document as a diversion source document, correspondence is made between the document identification information, diversion method information in which one of a plurality of diversion methods from the diversion source document is set, and the diversion source document identification information Means for storing in the document management table,
(B) means for storing the document identification information, the file identification information of each of one or more files referred to by the document, and the file version of each file in association with each other in a file management table in the document;
(C) means for associating file identification information, a file version, and a storage location of a file entity in a file management table,
(D) When a first diversion method that is one of the plurality of diversion methods is set as the diversion method information, the server
(D1) At the time of creating a document, means for sharing all files referred to by the created document with the diversion source document;
(D2) When a file referred to by the created document is requested for updating, it is determined by referring to the file management table in the document whether or not the requested file is shared with other documents. Means,
(D3) When the requested file is in a shared state, the new file entity obtained by copying the file entity acquired based on the file management table is updated to obtain the file identification information and the new file version. Storing in the file management table in association with each other, and storing the document identification information, the file identification information, and the new file version in the document file management table in association with each other;
(D4) When the requested file is not in the shared state, the file management table is updated by updating the file entity acquired based on the file management table so that the file identification information and the new file version are associated with each other. And a means for storing the document identification information, the file identification information, and the new file version in association with each other in the file management table in the document. (E) When a second diversion method that is one of the plurality of diversion methods is set as the diversion method information, the server
  (E1) When creating a document, means for sharing all files referred to by the created document with the diversion source document;
  (E2) When a file referred to by a document is requested for updating, the file entity acquired based on the file management table is updated to associate the file identification information with a new file version, and Means for storing the file identification information, the file identification information, and the new file version in association with each other in the file management table.
  The document management system according to claim 1.

Images