JP5517779B2 - Document management apparatus, document management method, and program - Google Patents

Description

  The present invention relates to a document management system, and more specifically, to a document management system that provides a flexible version management function in a document management system capable of managing a plurality of files as a version of one document. .

  As a basic function of the document management system, there is a function of managing a plurality of files as a single document. In this function, the file format of the file registered at the time of document registration is determined as the file format to be used later, and when updating the document version thereafter, only the file format determined at the time of document registration can generally be used. is there. However, there are document management systems that have a function of updating versions in different file formats. When transferring document data operated in such a document management system to a document management system that can only be updated in the same file format, it may not be possible to manage the data as one document. there were.

  Conventionally, as a countermeasure for such a case, there is one that provides a linkage function between a system that is not version-controlled and a version-managed document management system. Specifically, a method is provided in which file update on a system that is not version-controlled is monitored, and when a file update occurs, the version of the version-managed document management system is updated (for example, Patent Document 1).

JP 2005-316715 A

  However, the system linkage of Patent Document 1 has a problem that two systems must be operated simultaneously. In addition, since the update of the file is a trigger, only the update of the version of the file having the same file format can be managed, so the problem between the different document management systems cannot be solved.

  In order to solve the above problems, a document management apparatus according to the present invention is a document management apparatus capable of managing a plurality of files having the same file format as versions of one document, and is capable of managing a plurality of files having different file formats. An acquisition unit that acquires a document managed by another device from another device that can be managed as each version of one document, and the latest version file included in the document acquired by the acquisition unit First registration means for registering in the designated folder of the document management device, and a file having a file format different from the file format of the latest version file is included in the document acquired by the acquisition means, Of the files included in the document, a file of a version before the file of the different file format is regarded as another document. Second registration means for registering in a different folder different from the designated folder and registering extended information for linking the registered other document and the migration document; and the file of the latest version file When a file having a file format different from the format is included in the document acquired by the acquisition unit, among the files included in the document, each version of the file after the file having the different file format is And third registration means for registering as a version file corresponding to the migration document.

  The method of the present invention is a document management method in a document management apparatus capable of managing a plurality of files having the same file format as each version of one document, wherein a plurality of files having different file formats are stored in one document. An acquisition step of acquiring a document managed by the other device from another device that can be managed as each version, and the latest version of the file included in the document acquired in the acquisition step as the migration document. A first registration step of registering in a specified folder of the device, and a file having a file format different from the file format of the latest version of the file included in the document acquired in the acquisition step; File of the different file format from the previous version, A second registration step of registering in a different folder different from the designated folder as a document, and registering extended information for linking the registered other document and the migration document, and the latest version of the file If a file having a file format different from that of the file is included in the document acquired in the acquisition step, each file of a version later than the file having the different file format is included in the files included in the document. And a third registration step of registering as a file of a corresponding version of the migration document.

  According to the present invention, document data can be moved between document management systems having different version management methods, and integrated version management can be provided to the user.

It is a block diagram which shows the apparatus structure of the whole system showing embodiment of this invention. It is a figure which shows the function structure regarding the document management server apparatus of one Embodiment of this invention. It is a figure which shows the function structure regarding the client apparatus of one Embodiment of this invention. It is a figure which shows the concept of the version management in the existing document management server apparatus of one Embodiment of this invention. It is a figure which shows the concept of the integrated version management in the document management server apparatus in Example 1. FIG. FIG. 6 is a diagram illustrating a data format and a structure of document information managed by the document management server apparatus in the first and second embodiments. 3 is a diagram illustrating a data format and a structure of version management information managed by the document management server apparatus of FIG. 1 in Embodiment 1. FIG. It is a figure which shows the data format and structure of the extended version management information managed with the document management server apparatus of FIG. FIG. 10 is a diagram illustrating a data migration processing procedure from the existing document management server apparatus in FIG. 1 to the document management server apparatus in the first and second embodiments. FIG. 7 is a diagram illustrating a document data migration processing procedure from the existing document management server apparatus in FIG. 1 to the document management server apparatus in the first embodiment. It is a figure which shows an integrated version document management screen. FIG. 6 is a diagram illustrating a procedure for acquiring version information of the document management server apparatus in FIG. 1 according to the first embodiment. FIG. 6 is a diagram illustrating a file acquisition processing procedure from the document management server apparatus of FIG. 1 in the first embodiment. FIG. 10 is a diagram illustrating a version deletion processing procedure from the document management server apparatus of FIG. 1 in the first embodiment. FIG. 10 is a diagram illustrating a data format and a structure of document information managed by the document management server apparatus of FIG. FIG. 10 is a diagram illustrating a data format and a structure of extended version management information managed by the document management server apparatus of FIG. 1 in Embodiment 2. FIG. 10 is a diagram illustrating a document data migration processing procedure from the existing document management server apparatus in FIG. 1 to the document management server apparatus in the second embodiment. FIG. 10 is a diagram illustrating a version information reference procedure of the document management server apparatus in FIG. 1 according to the second embodiment. FIG. 10 is a diagram illustrating a procedure for obtaining a file from the document management server apparatus in FIG. 1 according to the second embodiment.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  The best mode of the present invention will be exemplarily described in detail below with reference to the drawings. However, among the components described in this embodiment, relative arrangement, data contents, and the like are not intended to limit the scope of the present invention unless otherwise specified. .

[Example 1]
Embodiment 1 relating to the document management system of the present invention will be described below.

<Overall configuration including document management server device>
The configuration of the entire system including the document management server device of this embodiment will be described with reference to the block diagram of FIG. As shown in FIG. 1, the system of this embodiment includes a document management server apparatus 101, a client apparatus 102, an old document management server apparatus 103, and a network 104.

  The document management server apparatus 101 has a function of managing a document by version, and provides managed document information and files in response to a request from the client apparatus 102. The document information of the document management server apparatus 101 is displayed and operated via the client apparatus 102. As shown in the figure, the number of client devices 102 is not particularly limited in the network 104, and an arbitrary number of client devices 102 may exist and may be configured with devices having different capabilities.

  The old document management server device 103 has a function of managing a document by version, similar to the document management server device 101, but the version management system is different from the document management server device 101. The old document management server apparatus 103 is a source of document data migration to the document management server apparatus 101. The network 104 is a network through which the document management server apparatus 101, the client apparatus 102, and the old document management server apparatus 103 can communicate with each other. The network 104 is a network system such as Ethernet (registered trademark) and can be a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet, but is not limited thereto.

<Configuration of document management server device>
The document management server apparatus 101 is a server personal computer, and includes hardware such as a CPU, RAM, ROM, HDD, and network interface card (hereinafter abbreviated as NIC). In addition, it is connected to a display, a keyboard (hereinafter abbreviated as KB), and a mouse (hereinafter abbreviated as MOUSE), which are externally attached or incorporated, and processes input / output from the user.

  The functional configuration of the document management server apparatus 101 will be described below with reference to the block diagram shown in FIG. As shown in FIG. 2, the document management server apparatus 101 includes a document information management unit 201, a version information management unit 202, and an extended version information management unit 203 as parts used internally. In addition, the document registration processing control unit 204, the document migration processing control unit 205, the version processing control unit 206, the display content generation unit 207, the request processing control unit 208, and the network communication unit 209 are provided as parts for receiving external processing.

  The document information management unit 201 is an execution program installed on the RAM and executed by the CPU, and performs document information management and input / output processing. Further, the document information management unit 201 stores the above-described document information in a specific area of the RAM or HDD. The version information management unit 202 is an execution program installed on the RAM and executed by the CPU, and performs version information management and input / output processing. The version information management unit 202 stores the above-described user information in a specific area of the RAM or HDD.

  The extended version information management unit 203 is an execution program installed on the RAM and executed by the CPU, and manages and inputs / outputs extended version information. Further, the extended version information management unit 203 stores the above-described extended version information in a specific area of the RAM or HDD.

  The document registration process control unit 204 is installed on the RAM and executes a request process related to document registration transmitted from the client apparatus 102. The document migration processing control unit 205 is installed on the RAM and executes document migration processing from the old document management server apparatus 103. The sentence version processing control unit 206 is installed on the RAM, and receives and executes a request for a version list acquisition process and a version file acquisition process from the client apparatus 102.

  A display content generation unit 207 that is an integrated version access unit is installed on the RAM, and executes a process of generating / editing display information for transmitting the processing result of another processing control unit to the client apparatus 102. In the present embodiment, since the information is exchanged via the WEB browser in the client apparatus 102, the display information is mainly in the HTML format.

  The request processing control unit 208 first receives a request installed from the RAM and transmitted from the client from the network communication unit 209 described later, and performs primary processing on all requests. The request processing control unit 208 requests the document registration processing control unit 204, the document migration processing control unit 205, the version processing control unit 206, and the display content generation unit 207 to perform processing according to the content of the request.

  The network communication unit 209 controls the communication for notifying the request processing control unit 208 of the processing request received from the client apparatus 102 and returning the processing result to each processing request source. A network communication unit 209 is a NIC of the document management server apparatus 101 and is connected to the network 104.

<Configuration of client device>
The client device 102 is a personal computer, and includes hardware such as a CPU, RAM, ROM, HDD, and network interface card (hereinafter abbreviated as NIC). Each is connected to an external or built-in display, a keyboard (hereinafter abbreviated as KB), and a mouse (hereinafter abbreviated as MOUSE) to control input / output from the user. A functional configuration of the client apparatus 102 will be described with reference to a block diagram shown in FIG.

  As shown in FIG. 3, the client device 102 includes a display content processing control unit 301 and a network communication unit 302. The display content processing control unit 301 interprets the display content transmitted from the document management server apparatus 101 and displays it on the display, or transmits transmission information such as document information input by KB or MOUSE to the document management server apparatus 101. To execute the process. The network communication unit 302 notifies the display content processing control unit 301 of the processing result received from the document management server apparatus 101 via the network 104, and the processing request content from the display content processing control unit 301 is notified to the document management server. Send to the device 101. The network communication unit 302 is a NIC of the client device 102 and is connected to the network 104.

<Folder hierarchy>
FIG. 4 is a schematic diagram showing a logical structure of a document managed on the old document management server apparatus 103. The document information of the old document management server device 103 includes a folder 401 for storing documents and files 402 to 406.

  The folder 401 is an element for constructing a logical hierarchical structure, and the folder can be composed of a plurality of hierarchies. In order to describe the present embodiment, it is not necessary that the folder has a plurality of hierarchies, and therefore a description will be given using a single folder.

  Files 402, 403, and 404 represent documents 407 that are version-managed as version 1, version 2, and version 3, respectively. Similarly, files 405 and 406 represent documents 408 that are version-managed as version 1 and version 2 respectively. The old document management server apparatus 103 handles these version-managed files together in the form of documents 407 and 408. Although only two documents are shown under the folder 401 in this configuration, the present invention is not limited to this, and an arbitrary number of documents can be actually stored.

  The feature of the version management of the old document management server device 103 is that it allows the file format (identifiable by extension in the figure) constituting the document to be different. The files 402 to 404 are configured as versions of one document 407, but the files 402 and 404 and the file 403 have different file extensions.

  FIG. 5 is a schematic diagram showing a logical structure of a document managed on the document management server apparatus 101. Since the document of the document management server apparatus 101 cannot be stored in a plurality of file formats, it cannot be handled in the same manner as the document structure shown in FIG.

  Therefore, as shown in FIG. 5, the document management server apparatus 101 stores one document in a method that can be managed in a plurality of file formats. The folders and files shown in FIG. 5 are described corresponding to those in FIG. That is, the folder 501 corresponds to the folder 401 in FIG. 4, and the files 502 to 506 correspond to the files 402 to 406 in FIG.

  Two documents 507 and 508 are registered in the folder 501. However, the document 507 corresponds to the document 407 described above, but the document management server apparatus 101 cannot store versions of different file formats as one document. For this reason, files 502 and 503 of different formats cannot be included in the document 507 even in the past version. Therefore, the files 502 and 503 that are past versions (version 1 and version 2) of the document 507 are managed by the document management server apparatus 101 as separate documents.

  Among the files constituting the document, the earlier files 502 and 503 having an extension different from that of the file 504 which is the latest version are respectively stored as separate documents 510 and 511 under the separately prepared extended version folder 509. Deploy. Incidentally, as shown in FIG. 5, the files 505 and 506 included in the document 508 have the same extension, that is, the same file format, and therefore, the same management as the document 408 is performed.

<Handling data format and configuration>
Next, a data structure for realizing the logical configuration shown in FIG. 5 will be described with reference to FIG. 6 to 8 are diagrams showing data formats and data examples handled by the document management server apparatus 101 shown in FIG. The data example shown below shows only the minimum items necessary to achieve the object of the present invention, but other items can be added as necessary.

  The document information shown in FIG. 6 represents the format of information held in units of documents, and includes a document ID 601, a document name 602, a file format 603, and a storage location 604. The document information shown in FIG. 6 is document information used by the document information management unit 201 of the document management server apparatus 101 shown in FIG. The document ID 601 is information for uniquely identifying the document information represented in the document information columns 611 to 614. The document name 602 is information for representing the name of the document represented by the document ID 601. The file format 603 is information representing a file extension indicating the file format of the document represented by the document ID 601. The storage location 604 is information indicating a storage destination folder in which the document represented by the document ID 601 is registered. Document information columns 611, 612, 613, and 614 represent actual document information, and correspond to the documents 507, 508, 510, and 511 shown in FIG.

  FIG. 7 also shows the file information format related to the version of the document identified by the document ID 601, and is composed of the document ID 701, the version 702, and the file 703. The version information shown in FIG. 7 is version information used by the version information management unit 202 of the document management server apparatus 101 shown in FIG. The document ID 701 identifies the document using one of the document IDs 601 shown in FIG. The version 702 represents a version number indicating the version of the document represented by the document ID 701, and holds unique values (for example, Ver1 and Ver2) for the document represented by the same document ID 701. A file 703 represents a document file whose version is uniquely specified by the document ID 701 and the version 702, and the substance of the file is stored in this information.

  The combination of the document ID 701 and the version 702 can uniquely represent the version information represented in the version information fields 711 to 715. The version information fields 711, 712, 713, 714 and 715 represent the version information of the actual document, and are the version information of the files 504, 505, 502, 503 and 506 shown in FIG.

  The information shown in FIG. 8 is information for identifying a document that cannot be handled as the same document by the document management server apparatus 101 because the extensions are different among the documents represented by the document ID 601 described above. This includes a document ID 801, an old version 802, and a link 803. The information shown in FIG. 8 is used as extended version information handled by the extended version information management unit 203 of the document management server apparatus 101 shown in FIG. According to the information shown in FIG. 8, the document management server apparatus 101 can conventionally only manage versions of documents having the same extension, but can also consistently manage versions of documents having different file formats.

  The document ID 801 is extended information for uniquely identifying the information fields 811 to 812. By using any of the information of the document ID 601 in FIG. 6 described above, any extension of the document having the document information shown in FIG. Can indicate information. The old version 802 represents the value of the version of the document represented by the document ID 801 before migration. A link 803 represents a link that defines the correspondence between the version of the document file extended in the present embodiment and the version of the document file originally. In order to identify the version of the document file to be associated with the link 803, FIG. One of the values of the document ID 601 is taken.

  Information columns 811 and 812 represent extended information of individual documents, and express that the files 502 and 503 shown in FIG. 5 correspond to the files 402 and 403 shown in FIG. 4, respectively. Therefore, the extended information shown in FIG. 8 is only information for documents belonging to the folder 509 (extended folder EXT) shown in FIG. 5 as the storage location 604 shown in FIG.

<Migration processing of document management server>
A document migration processing procedure for moving a document stored in the old document management server apparatus 103 to the document management server apparatus 101 will be described with reference to FIGS. FIG. 9 shows the overall flow of the document migration process, and FIG. 10 shows the detailed flow of a part of the process (document registration process). The document migration processing of this embodiment is executed by the CPU of the document management server apparatus 101. Specifically, the document migration processing is executed by the document migration processing control unit 205 instructed from the request processing control unit 208.

  As shown in FIG. 9, in step S901, a list of folders existing under the instructed folder is acquired from the old document management server apparatus 103. The list of acquired folders is stored in the RAM, and the process proceeds to the next step S902. In step S902, one arbitrary folder is selected from the list of folders stored in the RAM, the folder information is acquired, and the process proceeds to the next step S903. At this time, if the folder information of the selected folder does not exist, that is, if the folder does not exist in the meeting, the process proceeds to step S904 to perform document registration processing. In step S903, the folder setting process is performed by recursively calling the process flow of FIG. 9 by returning the process to step S901 with the folder instructed by the folder information acquired in step S902 as an instructed folder. That is, the folder designated first and all the folders existing below it are registered as processing targets, and the document migration processing shown in FIG. 10 is executed for each folder. As a result, all documents related to the designated folder are transferred.

  When this process ends, the processed folder information is deleted from the RAM, and the process returns to step S902.

  In step S904, a document registration process directly under the folder instructed by calling a processing flow described later with reference to FIG. 10 is performed. When the process of step S904 is completed, the process flow ends.

  FIG. 10 is a flowchart showing a specific process of moving a document existing under a specified specific folder in the old document management server apparatus 103 to the document management server apparatus 101. This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the document migration processing control unit 205 instructed by the request processing control unit 208. In step S <b> 1001, a list of documents existing in the designated folder is acquired from the old document management server apparatus 103. The list of acquired documents is stored in the RAM, and the process proceeds to the next step S1002.

  In step S1002, one document is selected from the document list stored in the RAM, the document information of the selected document is acquired, and the process proceeds to the next step S1003. At this time, if there is no document information to be acquired, this processing flow ends.

  In step S1003, information on all versions of the document and files included in the document information acquired in step S1002 are acquired from the old document management server apparatus 103. A document ID that is unique within the document management server apparatus 101 is issued to each acquired version of the document file. The acquired information, file, and issued document ID are stored in the RAM, and the process proceeds to the next step S1004.

  In step S1004, it is checked whether the number of file versions of the document acquired in step S1003 is one. When there is one version information, the process proceeds to the next step S1005, and when there are two or more version information, the process proceeds to step S1006.

  In step S1005, a document having only one version is registered. In this case, since it is not necessary to use the extended version information, the following information is registered using the document information management unit 201 and the version information management unit 202.

Document information Document ID 601: Issued document ID stored in RAM
Document name 602: Name obtained by removing the extension from the file name in the information stored in the RAM File format 603: File name extension in the version information stored in the RAM Storage location 604: Document registration Folder path specified when starting the process

Version Information Document ID 701: Issued Document ID 601 stored in RAM
-Version 702: "Ver1" fixed-File 703: File entity stored in RAM

  When the registration of information is completed, the information stored in the RAM, the file, and the document information acquired from the RAM in step S1002 are deleted. When this process ends, the process returns to step S1002.

  In step S1006, the version information of the document having the largest version number among the document versions stored in the RAM is acquired, and the document information is registered using the document information management unit 201.

Document information Document ID 601: Issued document ID stored in RAM
Document name 602: Name obtained by removing the extension from the file name in the acquired information File format 603: Extension of the file name in the acquired information Storage location 604: Folder specified when the document registration process is started When the registration of the pass document information to is completed, the process proceeds to the next step S1007.

  In step S1007, it is checked whether the file name extensions in the document information stored in the RAM are all the same. If all the extensions are the same, the process proceeds to step S1011. If any one of the extensions is different, the process proceeds to the next step S1008.

  In step S1008, the extension of the file name is checked in order from the new version from the document information stored in the RAM, and the file name of the version whose extension is different from the latest version is searched. The version number of a file having a version different from the latest version found by this search is stored in the RAM. After the storage, the process proceeds to the next step S1009.

  In step S1009, one piece of information of a file having a version number older than the version number found in step S1008 is acquired from the RAM, and the process proceeds to the next step S1010. If the version information to be acquired does not exist, the process proceeds to step S1011.

  In step S1010, the document information management unit 201, the version information management unit 202, and the extended version information management unit 203 are used to register the following information from the information acquired from the RAM.

Document information Document ID 601: Document ID unique within the document management server apparatus 101 is issued Document name 602: Name obtained by removing the extension from the file name in the information stored in the RAM File format 603: In the RAM File name extension in stored information-Storage location 604: Path to the "EXT" folder directly under the folder specified when starting the document registration process

Version information Document ID 701: Document ID 601 issued above
-Version 702: "Ver1" fixed-File 703: File entity stored in RAM

Extended version information Document ID 801: Document ID 601 issued above
Old version 802: Version number acquired in step 1003 Link 803: Issued document ID stored in RAM

  When the registration of information is completed, the version information stored in the RAM, the file, and the version number stored in step S1008 are deleted. After this process ends, the process returns to step S1009.

  In step S1011, the information of the document file with the smallest version number stored in the RAM is acquired, and the process proceeds to the next step S1012. If there is no version number to be acquired, the process returns to step S1002. In step S1012, the document information management unit 201 and the version information management unit 202 are used to register the following information from the acquired version information.

Version information Document ID 701: Issued document ID stored in RAM
-Version 702: Acquired version number-Version number stored in the RAM in step S1008-File 703: File entity stored in the RAM of the acquired version information After this processing is completed, the process returns to step S1011.

<Integrated version management screen>
An integrated version management screen for operating document information by integrated version management displayed on the display of the client apparatus 102 in FIG. 1 will be described with reference to FIG. The integrated version management screen 1101 shown in FIG. 11 includes the following parts.

  The folder tree display unit 1102 is a block that displays a logical folder hierarchy structure of documents stored in the document management server apparatus 101, and represents the folder hierarchy (folder 501 and folder 509) described with reference to FIG. ing. When a folder 501 (shaded) in the folder tree display unit 1102 is selected, document information belonging to the folder 501 is displayed on a document list display unit 1103 described later.

  The document list display unit 1103 includes a document name list 1105, a document registration button 1107, and a document deletion button 1108. The document name list 1105 displays a list of document names stored in the folder selected by the folder tree display unit 1102 described above. That is, when a folder is selected, the document name indicating the folder in which the storage location 604 is selected is acquired from the document information management unit 201 of the document management server apparatus 101 and displayed.

  A document registration button 1107 is used to register a new document in the document name list 1105 described above. For example, when the file “C.PPT” is registered by clicking the document registration button 1107, the document information management unit 201 and the version information management unit 202 of the document management server apparatus 101 are used, and the document information shown in FIG. The following information is added as the version information of FIG.

Document information Document ID: D005
Document name: C.I. PPT
·file format:. PPT
・ Storage location: / Z

Version information-Document ID: D005
・ Version: Ver1
-File: C.I. File entity represented by PPT

  The document deletion button 1108 is used to perform a deletion process on the document (shaded document A in the figure) selected from the document name list 1105 described above. For example, when the document deletion button 1108 is clicked to instruct deletion of the document with the document name A shown as the data example of the data structure in FIGS. 6 to 8, the document management server apparatus 101 performs the following processing. Do.

  Using the document information management unit 201 and the version information management unit 202, information 611 and 711 in which the document ID 601 representing the document A is “D001” are deleted. The extended version information management unit 203 is used for the next deletion. The document data of “D003” and “D004” represented by the document ID 801 of the information 811 and the document ID 801 of the link 803 that is held as an extended version indicating the original version document “D001” is described above as “D001” Delete as well.

  The version list display unit 1104 includes a version list 1106, a file acquisition button 1109, and a version deletion button 1110. The version list 1106 is a list of versions of the document selected in the document name list 1105 described above. When an arbitrary document is selected in the document name list 1105, the version information management unit 202 and the extended version information management unit 203 of the document management server apparatus 101 acquire version information and display the version list 1106.

  A file acquisition button 1109 is used to transmit a file entity represented by an arbitrary version selected in the above-described version list 1106 to the client apparatus 103. The version deletion button 1110 is for deleting an arbitrary version selected in the version list 1106 described above.

  The display of the version list 1106, the file acquisition by the file acquisition button 1109 and the version deletion by the version deletion button 1110 will be described in the following <Version information acquisition processing>, <File acquisition processing>, and <Version deletion processing>, respectively.

<Version data acquisition processing>
The version information acquisition processing procedure by the document management server apparatus 101 will be described with reference to FIG. FIG. 12 shows a processing flow executed in response to the user selecting an arbitrary document displayed in the document name list 1105 in the integrated version management screen 1101 displayed on the display of the client apparatus 103. It is a representation. This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the version processing control unit 206 instructed by the request processing control unit 208. In this processing flow, it is assumed that the document name “A” is selected in the document name list 1105 as an example. That is, when the user selects the document name “A” (the selection is indicated by shading, for example), the client device 103 selects a request for requesting version data of the document with the selected document name. The document name including the received document name is transmitted to the document management server 101.

  As shown in FIG. 12, in step S1201, the document name selected in the document name list 1105 of the integrated version management screen 1101 is acquired from the request from the client apparatus 103. Then, the document information with the document name “A” is acquired from the acquired document name using the document information management unit 201. The content of the acquired document information is stored in the RAM. After the acquisition process ends, the process proceeds to the next step S1202.

  In step S <b> 1202, version information having a document ID 701 that matches the document ID of the document information stored in the RAM is acquired using the version information management unit 202. The acquired version information is sorted in descending order by version 702 and stored in the RAM. After the acquisition process ends, the process proceeds to the next step S1203.

  In step S1203, the extended version information having the link 803 that matches the document ID of the document information stored in the RAM is searched, and the presence / absence of the extended version is confirmed based on the presence / absence of the extended version information. If the extended version exists, the process proceeds to the next step S1204, and if not, the process proceeds to step S1206.

  In step S1204, the extended version information found by the search is acquired. The extended versions included in the acquired extended version information are sorted in descending order by the old version 802 and stored in the RAM. After the acquisition process ends, the process proceeds to the next step S1205.

  In step S1205, the version information and the extended version information stored in the RAM are acquired, and version merging processing is performed. First, the number of extended version information stored in the RAM is calculated, and the number is added to the version 702 of the version information stored in the RAM to be updated. That is, for example, when the number of extended versions is 2 and the version 702 is “Ver1”, the version 702 is updated to “Ver3”.

  Next, temporary version information is generated from the extended version information, and stored in the RAM in the sort order of the extended version information. The correspondence between the generated version information and the extended version information is as follows.

Version information Document ID: Document information document ID 601
Version: Old version 802 of extended version information
-File: Not set because it is not required in the list. As a result, the version number stored in the RAM becomes the following three cases.

1) D001, Ver3, (file entity)
2) D001, Ver2, (no file entity)
3) D001, Ver1, (no file entity)
After the merge process is completed, the process proceeds to the next step S1206.

  In step S 1206, the acquired and generated version information is generated as a version list by the display content generation unit 207 and transmitted to the client device 103. After the transmission process in step S1206 is completed, this process flow is terminated.

<File acquisition process>
A file acquisition processing procedure by the document management server apparatus 101 will be described with reference to FIG. FIG. 13 is a flowchart showing processing of the document management server apparatus 101 that is started when the file acquisition button 1109 in the integrated version management screen 1101 displayed on the display of the client apparatus 103 is pressed. This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the version processing control unit 206 instructed by the request processing control unit 208. This processing flow will be described in detail assuming that the document name “A” and the version number “Ver2” are selected in the document name list 1105 as an example. That is, the user selects the document name “A” and the version number “Ver2” (the selection is indicated by shading, for example), and clicks the file acquisition 1109. Then, the client apparatus 103 transmits a request for requesting the selected document file to the document management server 101 including the selected document name and version.

  As shown in FIG. 13, in step S1301, the document name selected in the document name list 1105 of the integrated version management screen 1101 and the version number selected in the version list 1106 are acquired from the request from the client apparatus 103. . The acquired document name and version number are stored in the RAM. After the acquisition process ends, the process proceeds to the next step S1302.

  In step S1302, the document name and version number stored in the RAM are acquired, and the following processing is performed. First, using the document information management unit 201, the document information with the document name “A” designated by the user is acquired. Next, the extended version information management unit 203 is used to acquire the number of pieces of extended version information having a link 803 that matches the document ID of the acquired document information, and an extended version exists depending on whether the number is 0 or not. Check whether or not. When the acquired number of extended versions is one or more, the number is stored in the RAM. If the number of extended versions is one or more, that is, if an extended version exists, the process proceeds to step S1303. If not, the process proceeds to step S1307.

  In step S1303, the number of extended versions stored in the RAM is compared with the size of the version number designated by the user. If the version number specified by the user is larger than the number of extended versions stored in the RAM, it is necessary to obtain a file from the version information, and the process advances to step S1305. On the other hand, if the number of extended versions is the same as the version number, or if the number of extended versions is larger, it is necessary to acquire a file from the extended version, and the process advances to step S1304.

  In step S1304, an extended version file for which acquisition is requested is specified, and the file entity is acquired. First, using the extended version information management unit 203, extended version information having a link 803 that matches the document ID of the document information of the document having the requested document name and having the version number designated by the user in the old version 802 To get. Next, version information is acquired from the information of the document ID 801 included in the acquired extended version information 812 using the version information management unit 202. Since the document for which the extended version is managed always has only one version, the version information is directly acquired here. Then, using the document information management unit 201, the file extension of the file format 603 of the document information whose document name specified by the user is “A” is transmitted to the client apparatus 103. After the transmission to the client apparatus 103 is completed, this processing flow is terminated.

  In step S1305, the version information is specified from the version number designated by the user. Specifically, the number of extended versions stored in the RAM is subtracted from the version number designated by the user. The numerical value of the subtraction result is the version number of the file to be acquired. After the completion of the calculation process, the process proceeds to the next step S1306.

  In step S1306, a file entity that matches the calculated version number is acquired. First, the document information management unit 201 is used to obtain document information whose document name specified by the user is “A”. Next, version information is acquired from the document ID of the acquired document information and the version number calculated in step S1305 using the version information management unit 202. The entity of the file stored in the obtained version information file 703 is transmitted to the client apparatus 103. After the transmission to the client apparatus 103 is completed, this processing flow is terminated.

  In step S1307, a file of a document for which no extended version exists is acquired. First, the document information management unit 201 is used to obtain document information whose document name specified by the user is “A”. Next, version information is acquired from the document ID of the acquired document information and the version number designated by the user using the version information management unit 202. The entity of the file stored in the obtained version information file 703 is transmitted to the client apparatus 103. After the transmission to the client apparatus 103 is completed, this processing flow is terminated.

<Version deletion process>
The version deletion processing procedure by the document management server apparatus 101 will be described with reference to FIG. FIG. 14 is a flowchart showing processing of the document management server apparatus 101 that is started when the version delete button 1110 in the integrated version management screen 1101 displayed on the display of the client apparatus 103 is pressed.

  This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the version processing control unit 206 instructed by the request processing control unit 208. In this version deletion process, the process procedure for specifying the version to be deleted is the same as the file acquisition process in FIG. 13 described above, so the description of that part is omitted, and only the part that is different is described.

  The target processes are steps S1401, S1402, S1403, and S1405, which correspond to steps S1301, S1302, S1303, and S1305 in FIG. 13, respectively, and the processing contents are the same except that the deletion target is specified.

  In step S1404, the extended version to be deleted is specified, and the version is deleted. That is, a process after a version deletion is requested and target document information is specified will be described. First, the extended version information management unit 203 is used to acquire extended version information having a link 803 that matches the document ID of the document information and having the version number designated by the user in the old version 802. Next, document information and version information are acquired from the document ID 801 information of the acquired extended version information 812 using the document information management unit 201 and the version information management unit 202.

  When document information, version information, and extended version information to be deleted are specified as described above, information deletion is performed using the document information management unit 201, the version information management unit 202, and the extended version information management unit 203, respectively. I do. After the deletion process ends, this process flow ends.

  In step S1406, the version information having the calculated version number is deleted. First, the document information management unit 201 is used to obtain document information whose document name specified by the user is “A”. Next, version information is acquired from the document ID of the acquired document information and the version number calculated in step S1405 using the version information management unit 202.

  When the version information to be deleted is specified, the version information management unit 202 is used to delete the information. After the deletion process ends, this process flow ends.

  In step S1407, the version of the document for which no extended version exists is deleted. First, the document information management unit 201 is used to obtain document information 611 having a document name “A” designated by the user. Next, version information is acquired from the document ID of the acquired document information and the version number designated by the user using the version information management unit 202.

  When the version information to be deleted is specified, the version information management unit 202 is used to delete the information. After the deletion process ends, this process flow ends.

[Example 2]
A second embodiment relating to the document management apparatus of the present invention will be described below. In the second embodiment, only portions different from the first embodiment will be described. Therefore, the parts / specific procedures that are not specified are the same as those in the first embodiment.

  In the second embodiment, when an extended version is registered, the extension as a document is changed unlike the first embodiment. With this configuration, the document file in the extended version area can be excluded from the search target.

<Handling data format and configuration>
The data format and data to be changed as the extension is changed will be described using an example. The document information shown in FIG. 15 represents the format of information held in units of documents, and includes a document ID 1501, a document name 1502, a file format 1503, and a storage location 1504. These items have the same meaning as the document ID 601, the document name 602, the file format 603, and the storage location 604 described with reference to FIG. 6 in the first embodiment.

  The document information shown in FIG. 15 is used by the document information management unit 201 of the document management server apparatus 101 shown in FIG. The document ID 1501 is information for uniquely identifying the document information represented by the information columns 1511 to 1514. The document name 1502 is information for representing a name when the document represented by the document ID 1501 is displayed in a list or the like.

  The file format 1503 is information representing the file extension of the document represented by the document ID 1501. The storage location 1504 is information indicating a storage destination folder in which the document represented by the document ID 1501 is registered.

  Document columns 1511, 1512, 1513, and 1514 represent actual document information, and represent the documents 507, 508, 510, and 511 shown in FIG. Here, the difference from the document information shown in FIG. 6 is a registered file format 1503. That is, referring to the document information 1513 and 1514, the file format is “.BLK”.

  The extended version information as shown in FIG. 16 is information for identifying documents that cannot be handled as the same document due to different extensions among the documents represented by the document ID 1501 described above. The extended version information includes a document ID 1601, an old version 1602, a link 1603, and an old format 1604.

  The extended version information shown in FIG. 16 is used by the extended version information management unit 203 of the document management server apparatus 101 shown in FIG. According to the extended version information shown in FIG. 16, the conventional document management server apparatus can only manage the version of the extension of the same format, but the document management server apparatus of this embodiment can handle the document as one version. It becomes like this.

  The document ID 1601 is information for uniquely identifying the information columns 1611 to 1612. Any one of the documents having the document information shown in FIG. 15 by using any one of the document IDs 1501 in FIG. It can be shown whether it is extended information. An old version 1602 represents a version number before migration of a document having a document ID 1601.

  A link 1603 represents a link that defines the correspondence between the version of the document file originally extended with the extended version information of this embodiment and the version of the document file. The link 1603 takes one of the values of the document ID 1501 in FIG. 15 that identifies the version of the document file to be associated. An old format 1604 represents a file extension when registered on the old document management server apparatus 103.

  Information columns 1611 and 1612 represent information of individual documents, and express that the files 502 and 503 shown in FIG. 5 correspond to 402 and 403 shown in FIG. 4, respectively. Therefore, the extended information shown in FIG. 16 is only information for documents belonging to the folder 509 (extended folder EXT) shown in FIG. 5 as the storage location 1504 shown in FIG.

<Migration processing of document management server>
FIG. 17 is a flowchart showing a specific process of moving a document existing under a specified specific folder in the old document management server apparatus 103 to the document management server apparatus 101. This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the document migration processing control unit 205 instructed by the request processing control unit 208. This process basically corresponds to the process of the flowchart shown in FIG. 10 of the first embodiment, and steps S1701 to S1709 basically correspond to steps S1001 to S1009 of FIG. Similarly, steps S1711 to S1713 basically correspond to steps S1010 to S1012 in FIG.

  In the present embodiment, step S1710, which is an added process, which is different from the flowchart shown in FIG. 10 will be mainly described.

  After the processing similar to the flowchart shown in FIG. 10 is executed from step S1701 to S1709, step S1710 changes the extension of the file of the version information acquired in step S1709, and updates the information stored in the RAM. Thereby, in the next step S1711, the extension of the document registered as the extended version can be changed. After this update process is completed, the process proceeds to step S1711.

<Reference processing of version data>
FIG. 18 is a flow of processing executed in response to the user selecting a sentence in the integrated version management screen 1101 displayed on the display of the client apparatus 103 and an arbitrary document displayed in the book name list 1105. It represents.

  This process is processed by the CPU of the document management server apparatus 101, and is specifically executed by the version processing control unit 206 instructed by the request processing control unit 208. This process basically corresponds to the process of the flowchart shown in FIG. 12 of the first embodiment described above, and steps S1801 to S1806 basically correspond to steps S1201 to S1206 of FIG. In the present embodiment, step S1802 and step S1805, which are different from the processing in the first embodiment, will be mainly described.

  In step S1802, the version information management unit 202 acquires version information having the document ID 701 that is the document ID of the document information stored in the RAM. The acquired version information and the file format 1503 held in the document information are paired, sorted in descending order by the version 702, and stored in the RAM. After the storage process is completed, the process proceeds to the next step 1803.

  In step S1805, the version information and the extended version information stored in the RAM are acquired, and version merging processing is performed. First, the number of pieces of extended version information stored in the RAM is calculated, and the number is updated to the version 702 of the version information stored in the RAM. That is, for example, when the number of extended versions is 2 and the version 702 is “Ver1”, the version 702 is updated to “Ver3”. Next, temporary version information is generated from the extended version information, and the generated temporary version information and the old version 1603 held in the extended version information are paired to form the old version 1602 of the extended version information. Store in RAM in sort order.

  The correspondence between the generated version information and the extended version information is as follows.

Version information Document ID: Document information document ID 601
Version: Old version 702 of extended version information
-File: Not set because it is not required in the list. As a result, the version information stored in the RAM becomes the following three items.

1) D001, Ver3, (file entity),. PDF
2) D001, Ver2, (no file entity),. DOC
3) D001, Ver1, (no file entity),. PDF
After this merging process ends, the process proceeds to the next step S1806.

<Version document file acquisition processing>
FIG. 19 is a flowchart showing processing of the document management server apparatus 101 that is started when a file acquisition button 1109 in the integrated version management screen 1101 displayed on the display of the client apparatus 103 is pressed. This process is processed by the CPU of the document management server apparatus 101. Specifically, it is executed by the version processing control unit 206 instructed from the request processing control unit 208. This process basically corresponds to the process of the flowchart shown in FIG. Therefore, steps S1901 to S1903 correspond to steps S1301 to S1303 in FIG. 13, and steps S1906 to S1908 correspond to steps S1305 to S1307 in FIG. In the present embodiment, the modified step S1904 and the added processing step S1905, which are different from the processing of the flowchart shown in FIG.

  In step S1904, the extended version file to be acquired is specified, and the file entity is acquired. First, using the extended version information management unit 203, the extended version information having the link 803 that is the document ID of the document information of the document having the requested document name and having the version number designated by the user is stored in the old version 802. get. Next, version information is acquired from the information of the document ID 1601 included in the acquired extended version information using the version information management unit 202. Since the document in which the extended version is managed always has only one version, the version information is directly acquired here. After obtaining the file entity, the process proceeds to the next step S1905.

  In step S1905, the file extension of the entity of the separately acquired file is changed using the old version 1604 of the extended version information acquired in step S1904. The acquired file entity is transmitted to the client apparatus 103.

[Other embodiments]
The object of the present invention can also be achieved by executing the following processing. That is, a storage medium that records a program code of software that realizes the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus is stored in the storage medium. This is the process of reading the code. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code and the storage medium storing the program code constitute the present invention.

Claims (8)

A document management apparatus capable of managing a plurality of files of the same file format as each version of one document,
Obtaining means for obtaining a document managed by the other device from another device capable of managing a plurality of files of different file formats as respective versions of one document;
First registration means for registering a file of the latest version included in the document acquired by the acquisition means in a designated folder of the document management apparatus as a migration document;
When a file having a file format different from the file format of the latest version file is included in the document acquired by the acquisition unit, a version of the file included in the document prior to the file of the different file format A second registration means for registering the extended information for linking the registered document and the migrated document as another document in a different folder different from the designated folder; ,
When a file having a file format different from the file format of the latest version file is included in the document acquired by the acquisition unit, the file included in the document is later than the file of the different file format. And a third registration unit for registering each version file as a corresponding version file of the migration document.   When a file having a file format different from the file format of the latest version file is not included in the document acquired by the acquiring unit, the third registering unit stores a file having the same file format included in the document. The document management apparatus according to claim 1, wherein each of the files is registered as a file of a corresponding version of the migration document.   When a request for requesting version information of the document selected by the user is received from the client device, the version information included in the selected document and a link to the selected document based on the extended information 2. The apparatus according to claim 1, further comprising: a first transmission unit that merges version information included in another document that has been merged and transmits the merged version information to the client device. 2. The document management apparatus according to 2.   When receiving from the client device a request for obtaining a file of a version designated by the user from the merged version information, the entity of the file corresponding to the designated version is obtained and The document management apparatus according to claim 3, further comprising second transmission means for transmitting to the client apparatus.   Deletion means for deleting information of a file corresponding to the specified version when receiving a request for deleting a file of the version specified by the user from the merged version information from the client device The document management apparatus according to claim 3, further comprising:   When the second registration unit includes a file having a file format different from the file format of the latest version file in the document acquired by the acquisition unit, the second registration unit includes the file of the file included in the document. For a file of a previous version with a different file format, change the extension of the file, register the file with the changed extension as another document in another folder different from the specified folder, and The document management apparatus according to claim 1, wherein extended information for linking another document and the migration document is registered. A document management method in a document management apparatus capable of managing a plurality of files of the same file format as versions of one document,
An acquisition step of acquiring a document managed by the other device from another device capable of managing a plurality of files of different file formats as versions of one document;
A first registration step of registering the latest version file included in the document acquired in the acquisition step in a designated folder of the document management apparatus as a migration document;
When a file having a file format different from the file format of the latest version file is included in the document acquired in the acquisition step, a version of the file included in the document prior to the file of the different file format A second registration step of registering the file in a different folder different from the designated folder as another document, and registering extended information for linking the registered other document and the migrated document; ,
When a file having a file format different from the file format of the latest version file is included in the document acquired in the acquisition step, the file included in the document is later than the file of the different file format. A document management method comprising: a third registration step of registering each version file as a corresponding version file of the migration document. A program for causing a computer to function as a document management apparatus capable of managing a plurality of files having the same file format as versions of one document,
The computer,
An acquisition means for acquiring a document managed by another device from another device capable of managing a plurality of files of different file formats as versions of one document;
First registration means for registering the latest version file included in the document acquired by the acquisition means in a designated folder of the document management apparatus as a migration document;
When a file having a file format different from the file format of the latest version file is included in the document acquired by the acquisition unit, a version of the file included in the document prior to the file of the different file format A second registration means for registering the extended information for linking the registered document and the migrated document in a different folder different from the designated folder as another document,
When a file having a file format different from the file format of the latest version file is included in the document acquired by the acquisition unit, the file included in the document is later than the file of the different file format. Third registration means for registering each version file as a corresponding version file of the migration document;
Program to function as.

Images