JP2011134267A - Information processing apparatus, information processing method, information processing system, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow association that is not limited to "one-to-one" by registering multiple associations of source data with secondary data. <P>SOLUTION: An information processing apparatus receives a registration request of an electronic file and information for indicating an electronic file associated with the electronic file, generates association information on the basis of the received electronic file and the information for indicating the electronic file associated with the electronic file, and controls the information by associating the generated association information with the information indicating the electronic file. The apparatus receives: a browsing request of the electronic file from a client terminal; generates the information indicating the electronic file associated as a parent of the electronic file, and association list information that is list information with the information indicating the electronic file associated as the parent, from the managed association information, by using the information indicating the received electronic file; and transmits the electronic file receiving the browsing request and the generated association list information to the client terminal of a browsing request source. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for managing source data and secondary data in association with each other.

  The electronic form system converts form data acquired from a host computer into a data format (electronic form) that can be viewed and searched electronically and stores it.

  In the business of handling forms using the electronic form system, data is often processed based on the electronic form and secondary forms are created by general office applications such as spreadsheet software. The secondary form was stored in a system separate from the electronic form system for sharing and storage.

  Here, each business person in charge performs processing based on the data of the electronic form and creates a secondary form, but this work is a common work in performing the business.

  However, since each person in charge of work is working independently, there have been problems such as “duplication of work”, “unification of processing methods”, “difficult to share secondary forms”.

  Therefore, it takes a lot of time and effort to synchronize the management of secondary forms, such as when it takes time to find the original electronic form from the created secondary form, or when the original electronic form is deleted. There was a problem.

  FIG. 14 shows an example of business. In this example, it is assumed that work is performed according to the following procedure. (1) End user A refers to the electronic form. (2) The end user A creates a secondary form by processing the form data using a general application based on the electronic form. (3) End user A performs operations such as analysis and reporting using the secondary form. (4) The end user A stores the secondary form on the file server in order to share the created secondary form for evidence or with another user who performs the same business. (Or distributed by e-mail or the like) (5) The end user B refers to the shared secondary form and performs tasks such as analysis and reporting. (6) The administrator C refers to the secondary form and the original electronic form and confirms the contents. (7) The administrator C periodically deletes old forms and secondary forms from the server.

In such cases, multiple users (end users A and B) create secondary forms for analysis and reporting based on electronic forms, but the secondary forms are shared. Since the mechanism is not linked to the electronic form reference, it may not be shared well. In the above example, there are cases where end user A and end user B each create a secondary form. In this case, there are problems that it takes extra time to create secondary forms and that the created secondary forms are not unified.

In addition, the administrator C looks at the secondary form that has been analyzed and reported and matches it with the original electronic form. For example, the administrator C searches only from a title such as the October 2009 monthly report. There is a problem that it takes time to search for the original electronic form.

Further, when the administrator C organizes the results of the electronic form, the related secondary form cannot be arranged efficiently and accurately, and there is a problem that unnecessary data increases more and more.

This will be described below with a more specific business example (assuming that this business is performed according to the following procedure). (1) The sales data of the month is referred to from the electronic forms registered every month by accounting, and exported as csv data. (2) Create a sales graph for each branch and each product based on the above data. (3) Based on the created secondary form, analyze sales at each branch and report to the supervisor. (4) The created secondary form is stored on the server and shared among the parties concerned. (5) Based on the secondary forms stored on the server, analyze the sales for each product and report to the supervisor. (6) In order to confirm the support of the reported report, matching with the electronic form data is performed. (7) Delete unnecessary old electronic form records and delete related secondary forms.

In this business, since there is no association with the original data, sharing of the secondary form becomes insufficient, and it is considered that a plurality of end users create secondary forms. In addition, it is difficult to find an original electronic form from the created secondary form.

Similarly, there is a problem that it is difficult for the administrator to synchronize and manage the electronic form and the secondary form, and the secondary form remains even though it is no longer necessary because the electronic form has already been deleted.

  Here, by using the technique described in Patent Document 1, an office document created by an office application can be registered in the electronic form system.

  However, since the electronic form and the secondary form are registered independently, there is a problem that it takes time to find the original electronic form from the secondary form, or when the original electronic form is deleted. The problem of synchronizing the management of secondary forms cannot be solved.

  As another method, Patent Document 2 discloses a technique of processing source data using Excel and storing it in a server.

JP 2008-181503 A JP 2001-67422 A

  However, with the technique described in Patent Document 2, a link is automatically generated when creating secondary data from the original data, and secondary data with a plurality of source data as parents cannot be created.

  In recent years, analysis is required to be multidimensional, and a plurality of forms are often combined to create a single secondary data. However, the technique described in Patent Document 2 can solve such a problem. Can not.

  That is, the original data and the secondary data cannot be associated with “one-to-many”, “many-to-one”, and “many-to-many”.

  An object of the present invention is to solve the above-described problems, and to register a plurality of associations between original data and secondary data, thereby enabling associations not limited to “one-to-one”.

  Yet another object is to facilitate the management of secondary data when the original data is deleted.

  The present invention is an information processing apparatus that manages association of a plurality of electronic files, and includes a first receiving unit that receives a registration request for an electronic file and information indicating the electronic file to be associated with the electronic file, The association information generating means for generating association information based on the electronic file received by the receiving means and information indicating the electronic file to be associated with the electronic file, the association information generated by the association information generating means, Management means for managing the information indicating the electronic file in association with each other, second receiving means for receiving an electronic file browsing request from the client terminal, and information indicating the electronic file received by the second receiving means Using the association information managed by the management means from the parent of the electronic file. Association list information generating means for generating association list information that is list information of information indicating an electronic file associated with the electronic file and information indicating an electronic file associated with the electronic file as a parent, and the second And a transmission unit configured to transmit the electronic file received by the receiving unit to the browsing request source client terminal and the association list information generated by the association list information generating unit.

  According to the present invention, by registering a plurality of associations between the original data and the secondary data, associations that are not limited to “one-to-one” are possible.

It is a figure which shows the structure of the electronic form system of embodiment of this invention. It is a figure which shows the hardware constitutions of the various terminals of embodiment of this invention. It is a figure which shows the basic composition of the electronic form system of embodiment of this invention. It is a flowchart which shows the flow of the process which links | relates the secondary form file which the user produced with the parent form file, and registers into a form server. It is a figure which shows the flow of a user's operation screen. It is an example of a table showing form generation information and association information. It is a flowchart which shows the flow of the process which refers a parent form file from a secondary form file. An example of selecting a parent (child) form file associated with a form file being viewed is shown. An example of selecting a parent (child) form file associated with a form file being viewed is shown. It is a form file list screen. It is a flowchart which shows the flow of the process which produces | generates correlation list information. An example of association list information is shown. 10 is a flowchart showing a flow of processing for deleting a secondary form file by deleting a parent form file. It is a figure which shows the basic composition of the conventional electronic form system.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of an electronic form system (information processing system) having an automatic form generation function in an embodiment of the present invention.

  In FIG. 1, reference numeral 101 denotes a host computer or host printer, which generates form data to be registered in the electronic form system 102.

  A form system 102 records form data and management information of an electronic form (= electronic file, hereinafter simply referred to as a form), and is sent to the client PCs 103 and 104 via the network 105. Provide services such as browsing and searching. The electronic form system can provide a service by a single server (information processing apparatus). In the present embodiment, the form system is described as being synonymous with the form server.

  The client PCs 103 and 104 are client terminals used by a person who views a form and acquires a calculation result, and can send and receive data to and from the electronic form system 102 via the network 105.

  The network 105 is, for example, a LAN (Local Area Network) or the Internet.

  The configuration of various terminals connected to the network in FIG. 1 is an example, and there are various configuration examples depending on the application and purpose.

  Next, the hardware configuration of the electronic form system 102 in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a diagram showing a hardware configuration of various terminals according to the embodiment of the present invention.

  As shown in FIG. 2, the form server 102 includes a CPU 101, a RAM 102, a ROM 103, an input unit 104, an input controller 105, a display unit 106, a display controller 107, an external memory 108, an external memory controller 109, a communication interface (I / F). A controller 110 and a system bus 111 are included.

  The CPU 101 controls the operation of the form server 102 in an integrated manner, and controls each component (102, 103, 105, 107, 109, and 110) of the form server 102 via the system bus 111.

  The RAM 102 functions as a main memory, work area, and the like for the CPU 101. When executing the processing, the CPU 101 loads a necessary program 103a or the like from the ROM 103 into the RAM 102, and executes the program 103a or the like to realize various operations.

  The ROM 103 stores a BIOS (Basic Input / Output System) that is a control program of the CPU 101, an operating system program (OS), and a program 103a such as a program necessary for the CPU 101 to execute processing to be described later. Note that the program 103 a may be stored in the external memory 108.

  The input controller 105 controls input from the input unit 104 configured with a keyboard, a mouse, and the like.

  The display controller 107 controls display on the display unit 106 configured by a CRT, a liquid crystal display, or the like.

  The external memory controller 109 controls the writing (storing) of information to the external memory 108 configured by, for example, a hard disk (HD) or a flexible disk (FD), and the reading of information from the external memory 108. The external memory 108 also includes an office document file 108a, EMF (Enhanced Metafile Format) data 108b, a new format form file 1081 converted from the office document file 108a, and form printing from the host computer. A form file 1082 in a conventional format converted from data is stored.

  Each form file represents the display data of the form, and is composed of one or a plurality of files and contains one or a plurality of pages. Within the electronic form system 102, the same type of plural form files are managed as a group, and each form file is called a generation within the group.

  As the new format form file 1081, a form file (image) 108c, a form file (search map data) 108d, a dummy page definition file 108e, and a dummy form definition file 108f are stored. Further, as the form file 1082 in the conventional format, a form text file 108g, a form map file 108h, a page definition file 108i, and a form definition file 108j are stored. As shown in FIG. 2, the new format form file 1081 and the conventional format form file 1082 correspond to the form file (image) 108c and the form text file 108g, and the form file (search map data) 108d and the form map. The file 108h corresponds, the dummy page definition file 108e and the page definition file 108i correspond, and the dummy form definition file 108f and the form definition file 108j correspond. In addition, the external memory 108 stores various files, various data, and the like as necessary.

  The form file 1082 in the conventional format is created based on the form print data when it is detected that form print data is input from the host computer.

  The communication I / F controller 110 performs control for communicating with the client PCs 201 and 202 via the network 300 shown in FIG.

  The system bus 111 is for connecting the CPU 101, the RAM 102, the ROM 103, the input controller 105, the display controller 107, the external memory controller 109, and the communication I / F controller 110 so that they can communicate with each other.

  Next, an outline of the flow of processing for registering and associating secondary forms in the electronic form system in the present embodiment will be described with reference to FIG.

  The business person 301 refers to the electronic form 302, creates a secondary form 303 based on the electronic form 302, and performs analysis and reporting work. Here, the secondary form is created as an office document by an office application such as spreadsheet software. Thereafter, the business person 301 registers the created secondary form 303 in the electronic form system 304 as a child form of the electronic form 302.

  The business person 305 refers to the secondary form 303 that has already been created and registered and the original electronic form 301 to perform analysis and reporting work.

  The administrator 306 manages (deletes) the electronic form 302 and the secondary form 303 that are no longer needed.

  Next, each detail shown in FIG. 3 will be described with reference to the drawings.

  First, the flow of the operation of the user who created the secondary form will be described with reference to FIGS.

  FIG. 4 is a flowchart showing a flow of processing for registering the secondary form file created by the user in the form server in association with the parent form file.

  FIG. 5 is a diagram showing the flow of the user operation screen.

  It is assumed that the secondary form file is created as an office document by an office application such as spreadsheet software. The user is assumed to operate the client terminal.

  In step S501, the client terminal requests a form file list screen from the form server. This request is made when a user who logs in to the electronic form system requests from the menu screen or the like.

  In step S502, the form server accepts the request, and in step S503, the form file list screen is transmitted to the client terminal.

  In step S504, the client terminal displays the received form file list screen. An example of a form file list screen is shown at 40 in FIG.

  In step S505, the client terminal determines whether the generation list screen request button has been pressed. If Yes, the process proceeds to S506, and if No, the process returns to S505. Specifically, it is determined whether 401 in the form file list screen 40 in FIG. 5 has been selected by the user. In this example, the generation list for the form name “monthly report” is selected.

  In step S506, the client terminal requests a list screen of generations from the form server.

  In step S507, the form server accepts the request, and in step S508, transmits a generation list screen to the client terminal.

  In step S509, the client terminal displays a generation list screen. An example of a list of generations is shown at 41 in FIG. In this example, one generation of the creation date “2009/07/31 20:06:53”, the registrant “system”, the size “14 KB”, and the comment “monthly report December” is registered.

  The user presses a reference button 402 on the displayed generation list screen 41 to display a dialog 42 for selecting a file. A secondary form file stored in the client terminal is selected via the dialog 42 and 403 is pressed. If it is desired to set a parent form file, a check box 404 for setting association is checked, and a parent form file selection button 405 is pressed. From the displayed form file list screen 43, the parent form file link 406 is pressed. Thereafter, the deletion timing is set in 407 and the file registration button 408 is pressed, whereby the secondary form file is registered in the electronic form system.

  For the deletion timing of 407, select “Delete when all parent forms are deleted”, “Delete when one or more parent forms are deleted”, and “Do not delete even when a parent form is deleted”. Can do.

  In step S510, the client terminal determines whether the registration button 408 has been pressed. In the case of Yes, it progresses to step S511, and in No, it returns to step S510.

  In step S511, the client terminal requests the form server to register a secondary form file.

  In step S512, the form server accepts a secondary form file registration request.

  In step S513, the form server performs a secondary form file registration process. The registration method here can be realized by using a technique described in, for example, Japanese Patent Application Laid-Open No. 2008-181503.

  In step S514, the form server determines whether a parent form file to be associated with the secondary form file is specified. In the case of Yes, it progresses to step S515, and in No, a process is complete | finished.

  In step S515, the form server reads the designation of association with the parent form file one by one.

  In step S516, the form server creates parent form file information (association information) associated with the generation information of the secondary form file to be registered in the database. Here, the association information will be described with reference to FIG.

  FIG. 6 is a diagram showing association information for specifying the association between the secondary form file and the parent form file.

  The generation information of the form file is unique by the form ID, the storage directory ID, and the generation date. Therefore, a data structure (association) for associating the “form file generation specific item” included in the form generation information 601 of the parent form file with the “form file generation specific item” included in the form generation information 602 of the secondary form file. Information) is 603. In this example, a form file generation specifying item (form ID “NIJI001”, directory ID “DIR001”, generation date “20091010101030”) of the secondary form file, and a generation specifying item (form ID “BUNSY0001”) of the parent form file, directory ID “DIR001” and generation date “20091010101010”) are associated with the association information.

  In step S517, the form server determines whether there is remaining data for specifying the association with the parent form file. If Yes, the process returns to step S514. If No, the process ends.

  In the above example, an example has been described in which a form file that has already been registered for one secondary form file is specified as a parent form file. However, a file that is specified as a parent form file of a secondary form file to be registered is described. It may be a secondary form file. For example, when registering the secondary form file B, when the secondary form file A is designated as the parent form file, when viewed from the secondary form file A, the secondary form file B becomes a child form file.

  Therefore, by referring to the association information, not only the parent form file but also the child form file can be specified.

  The method for registering the secondary form file and specifying the parent form file has been described above.

  Next, the flow of processing for reading a parent form file from a secondary form file registered in association will be described with reference to FIGS.

  FIG. 7 is a flowchart showing a flow of processing for referring to the parent form file from the secondary form file.

  The user operates the client terminal.

  In step S701, the client terminal transmits authentication information to log in to the form server.

  In step S <b> 702, the form server performs authentication, and in step S <b> 703, the form file list information that can be referred to by the authenticated user is transmitted.

  In step S704, the client terminal receives and displays the form file list information.

  In step S705, the client terminal requests acquisition of a form file selected by the user from the list.

  In step S706, the form server accepts a form file acquisition request.

In step S707, the form server specifies a form file. In step S708, the form server determines whether related information exists in the specified form file. In the case of Yes, it progresses to step S709, and in No, it progresses to step S710. Specifically, the existence is determined by extracting the association information using the form file generation specifying item (see FIG. 6) of the specified form file. Here, not only the association information that the form file designates as the parent form file, but also the association information of the child form file that designates the form file as the parent form file is extracted.

  In step S709, association list information of the parent (child) form file is generated from the association information.

  In step S710, when the form server can extract the association information together with the identified form file, the form server also transmits the association list information.

  In step S711, the client terminal acquires a form file (including association list information).

  In step S712, the client terminal displays the form file. If there is association list information, it is displayed in a format selectable by the user.

  FIG. 8 and FIG. 9 show an example of selecting a parent (child) form file associated with the form file being browsed.

  FIG. 8 shows that the parent form file and the child form file can be referred to the form file being browsed. Here, when the user clicks 801, a parent form file selection dialog 901 is displayed as shown in FIG. The user can browse the parent form file by selecting the parent form file to be called from this dialog. A mechanism for displaying a dialog on a form file such as 801 and 901 can be dynamically displayed by using an existing Web technology. As a result, it can be displayed as if it is floating in the form file, and even if the form file is scrolled, it can be displayed at a predetermined position. If you move the mouse to "+", it will be expanded and detailed information will be displayed. If you move the mouse to "-", it will be collapsed.

  In step S713, the client terminal determines whether a call request for a parent (child) form file has been made. In the case of Yes, it progresses to step S714, and in No, it returns to S713. Specifically, it is determined whether the parent (child) form file is selected in the dialogs 801 and 901.

  In step S714, the client terminal requests the form server to obtain the parent (child) form file selected by the user.

  In step S715, the form server accepts a parent (child) form file acquisition request.

  In step S716, the form server specifies the selected parent (child) form file, and in step S717, transmits the specified parent (child) form file to the client terminal. Here, the form file can be specified by using the form generation specifying item.

  In step S718, the client terminal acquires a parent (child) form file.

  In step S719, the client terminal displays the acquired parent (child) form file.

  In step S720, the client terminal determines whether to end the browsing operation for the form file. If yes, the process ends. If no, the process returns to S712.

  The flow of processing for reading a parent form file from a secondary form file registered in association has been described above.

  Another embodiment for reading the associated parent form file will be described with reference to FIG.

  FIG. 10 is a form file list screen.

  Another embodiment is a method of reading a parent form file from this screen. To achieve this, when the form server sends the form file list screen to the logged-in user, the form server determines whether or not there is association information for all the form files included in the screen, and there is association information. Generates an association information list and sends it to the client terminal together with the form file list screen (on the form server side, S707 to S709 shown in FIG. 7 are repeated). In the client terminal, a “call related document” item is provided on the screen of the form file list, and when there is an association information list, a selectable “♦” mark or the like is displayed. When the user selects this mark, an association information list 1002 is displayed. The user can select and refer to the associated parent (child) form file from this list.

  In addition, the association information list for displaying the presence / absence of the association information does not need to be the timing at which the client terminal acquires the form file list screen. For example, this button can be obtained by preparing a call button in the menu. It is also possible to request association list information from the form server at the timing when is pressed, and after obtaining this information, the screen may be updated and displayed.

  In the above description of the other embodiments, an example has been described in which all parent (child) form files associated with the form file viewed by the login user are displayed in a selectable list. However, among the form files associated with the form file being viewed by the login user, there is also a form file that cannot be viewed by the login user. Therefore, a process for generating association list information according to the access authority of the login user will be described next.

  FIG. 11 is a flowchart showing a flow of processing for generating association list information.

  In step S1101, the form server reads the form file that can be referred to by the login user one record at a time.

  In step S1102, the form server obtains “form file generation specifying item” of the form file from the database.

  In step S <b> 1103, the form server uses the “form file generation specifying item” to specify the form file associated as the parent form file from the association information one record at a time.

  In step S1104, the form server determines whether the logged-in user can view the identified parent form file. In the case of Yes, it progresses to step S1105, and in No, it progresses to step S1106. This determination of access right can be realized by using existing access control information.

  In step S1105, the form server adds the parent form to the association list information.

  In step S1106, the form server determines whether confirmation of all the parent form files associated as the parent form file has been completed. If Yes, the process proceeds to step S1107, and if No, the process returns to step S1103.

  In step S1107, the form server uses the “form file generation specifying item” to specify one record at a time for each record of the child form file that associates the form file as the parent form file from the association information.

  In step S1108, the form server determines whether the logged-in user can view the specified child form file. If Yes, the process proceeds to step S1109. If No, the process proceeds to step S1110. This determination of access right can be realized by using existing access control information.

  In step S1109, the form server adds the parent form to the association list information.

  In step S1110, the form server determines whether confirmation of all child form files associated with the form file as a parent form file has been completed. If Yes, the process proceeds to step S1111. If No, the process returns to step S1107.

  In step S <b> 1111, the form server determines whether confirmation of all referable form files has been completed. If yes, the process ends. If no, the process returns to step S1101.

  In step S1112, the form server generates association list information. FIG. 12 shows an example of association list information.

  In addition, although the example which produces | generates the list information which a login user can browse was demonstrated here, in addition to the list information which a login user can browse, a login user cannot browse, but browsing List information of other form files associated with the desired form file may be generated and transmitted to the client terminal together.

  In this case, the client terminal displays a form file that can be browsed and a form file that cannot be browsed. For example, a form file that can be viewed is displayed in a selectable state, and only a name is displayed for a form file that cannot be viewed.

  By doing so, the user cannot know what he / she can view but can know what form file is associated.

  Next, the flow of processing for deleting a secondary form file by deleting the parent form file will be described with reference to FIG.

  FIG. 13 is a flowchart showing a flow of processing for deleting a secondary form file by deleting the parent form file.

  First, as a premise, all secondary form files (child form files) in which the form file A is registered as a parent form file are “deleted when all the parent forms are deleted” at the deletion timing indicated by 407 in FIG. Is selected.

  The deletion of the form file is performed by the administrator operating the client terminal and designating the form file to be deleted to the form server from the administrator menu.

  In step S1301, the client terminal sends a request to delete the form file A designated through the administrator screen to the form server.

  In step S1302, the form server receives a deletion request.

  In step S1303, the form server reads the form file A that has been requested to be deleted.

  In step S1304, the form server acquires “form file generation specifying item” of the form file A.

  In step S1305, the form server determines whether there is a record that associates the form file A as the parent form file from the association information using the “form file generation specific item”. In the case of Yes, it progresses to S1306, and in No, it progresses to S1313.

  In step S1306, the form server uses the “form file generation specifying item” to specify one record at a time for each record that associates the form file A as the parent form file from the association information.

  In step S 1307, the form server obtains “form file generation specifying item” of the form file that associates the form file A as the parent form file.

  In step S1308, the form server uses the “form file generation specific item” to determine whether there is a record that associates a form other than the form file A as a parent form file from the association information. If Yes, the process proceeds to step S1309, and if No, the process proceeds to step S1310.

  In step S1309, the form server deletes the record specified in step S1306 from the association information.

  In step S1310, the form server deletes the record specified in step S1306 from the association information, and requests deletion of the generation information of the form file that associates the form file A as the parent form file.

  In step S1311, the form server performs processing for deleting the child form file of the form file for which the deletion request has been made. This process can be realized by recursively executing the processes in steps S1302 to S1312. Thereby, the grandchild form file of the form file A can be deleted.

  In step S1312, the form server determines whether confirmation of all the records that associate the form file A as the parent form file has been completed. If yes, then continue with step S1313, otherwise, return to step S1306.

  In step S1313, the form server determines whether there is a record in which the form file A is associated as a child form file from the association information using the “form file generation specific item”. If Yes, the process proceeds to step S1314. If No, the process proceeds to step S1316.

  In step S <b> 1314, the form server uses the “form file generation specifying item” to specify one record at a time for each record that associates the form file A as a child form file from the association information.

  In step S1315, the form server deletes the record specified in step S1314 from the association information.

  In step S1316, the form server determines whether confirmation of all the records associated with the form file A as a child form file has been completed. If yes, the process ends. If no, the process returns to step S1314.

  In step S1317, the form server deletes the generation information of the form file A.

  The processing flow for deleting the secondary form file by deleting the parent form file has been described above.

  As a result, the secondary form file itself can be deleted from the electronic form system at the timing when all the secondary form files of the secondary form file are deleted, so that it is easy to delete unnecessary secondary form files. Can do. It also helps reduce the load on system resources.

  In addition, when “deletion when at least one parent form is deleted” is selected at the deletion timing indicated by 407 in FIG. 4 at the time of registration, this is realized by performing step S1109 immediately after step S116. Can do.

  Therefore, by using different deletion timings when registering secondary forms, more flexible management is possible.

  As described above, according to the present invention, it is possible to associate not only “one-to-one” by registering a plurality of associations between the original data and the secondary data.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

  The object of the present invention is achieved by the following. That is, a storage medium (or recording medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded is supplied to the system or apparatus. Then, the central processing means (CPU or MPU) of the system or apparatus reads and executes the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium recording the program code constitutes the present invention.

  In addition, by executing the program code read by the central processing means of the system or apparatus, an operating system (OS) or the like operating on the system or apparatus performs actual processing based on the instruction of the program code. Do some or all. The case where the function of the above-described embodiment is realized by the processing is also included.

  Further, it is assumed that the program code read from the storage medium is written in a memory provided in a function expansion card inserted into the system or apparatus or a function expansion unit connected thereto. After that, based on the instruction of the program code, the CPU of the function expansion card or function expansion unit performs part or all of the actual processing, and the function of the above-described embodiment is realized by the processing. It is.

  When the present invention is applied to the storage medium, the storage medium (computer-readable storage medium) stores program codes corresponding to the flowcharts described above.

101 Host 102 Electronic form system 103 Client PC
104 Client PC

Claims (8)

An information processing apparatus that manages association of a plurality of electronic files,
First receiving means for receiving a registration request for an electronic file and information indicating the electronic file associated with the electronic file;
Association information generating means for generating association information based on the electronic file received by the first receiving means and information indicating the electronic file associated with the electronic file;
Management means for associating and managing association information generated by the association information generation means and information indicating the electronic file;
A second receiving means for receiving an electronic file browsing request from the client terminal;
Using the information indicating the electronic file received by the second receiving unit, the information indicating the electronic file associated as the parent of the electronic file from the association information managed by the management unit, and the electronic file Association list information generating means for generating association list information that is list information with information indicating an electronic file that is associated as a parent,
A transmission unit configured to transmit the electronic file whose browsing request has been received by the second receiving unit and the association list information generated by the association list information generating unit to the client terminal that is the browsing request source. Information processing apparatus. An authentication unit for performing user authentication for operating the client terminal;
The said association list information generation means produces | generates the list information of the information which shows the electronic file which the said user can browse according to the access authority of the user authenticated by the said authentication means. Information processing device. A third accepting means for accepting an electronic file deletion request;
Delete means for deleting the association information associated with the electronic file from the association information managed by the management means using information indicating the electronic file for which the deletion request has been accepted by the third accepting means. The information processing apparatus according to claim 1, further comprising:   The deletion means, when not associating an electronic file different from the electronic file as a parent, deletes the electronic file associated with the electronic file as a parent together with the association information. The information processing apparatus described. An information processing system capable of communicating between a client terminal and an information processing apparatus that manages association of a plurality of electronic files,
First receiving means for receiving a registration request for an electronic file and information indicating the electronic file associated with the electronic file;
Association information generating means for generating association information based on the electronic file received by the first receiving means and information indicating the electronic file associated with the electronic file;
Management means for associating and managing association information generated by the association information generation means and information indicating the electronic file;
A second receiving means for receiving an electronic file browsing request from the client terminal;
Using the information indicating the electronic file received by the second receiving unit, the information indicating the electronic file associated as the parent of the electronic file from the association information managed by the management unit, and the electronic file Association list information generating means for generating association list information that is list information with information indicating an electronic file that is associated as a parent,
A transmission unit configured to transmit the electronic file whose browsing request has been received by the second receiving unit and the association list information generated by the association list information generating unit to the client terminal that is the browsing request source. Information processing system. An information processing method in an information processing apparatus for managing association of a plurality of electronic files,
A first accepting step for accepting a registration request for an electronic file and information indicating an electronic file associated with the electronic file;
An association information generation step for generating association information based on the electronic file received in the first reception step and information indicating the electronic file associated with the electronic file;
A management step of associating and managing association information generated by the association information generation step and information indicating the electronic file;
A second accepting step for accepting an electronic file browsing request from the client terminal;
Using the information indicating the electronic file received in the second receiving step, the information indicating the electronic file associated as the parent of the electronic file from the association information managed in the management step, and the electronic file An association list information generating step for generating association list information that is list information with information indicating an electronic file associated with
A transmission step of transmitting the electronic file that has received the browsing request in the second receiving step and the association list information generated in the association list information generating step to the client terminal that is the browsing request source. Information processing method. A program that can be executed in an information processing apparatus that manages association of a plurality of electronic files,
First receiving means for receiving a registration request for an electronic file and information indicating an electronic file associated with the electronic file;
Association information generating means for generating association information based on the electronic file received by the first receiving means and information indicating the electronic file associated with the electronic file;
Management means for managing the association information generated by the association information generation means in association with the information indicating the electronic file;
A second accepting means for accepting an electronic file browsing request from the client terminal;
Using the information indicating the electronic file received by the second receiving unit, the information indicating the electronic file associated as the parent of the electronic file from the association information managed by the management unit, and the electronic file Association list information generating means for generating association list information that is list information with information indicating an electronic file associated with a parent as a parent,
The information processing as transmission means for transmitting the electronic file that has received the browsing request by the second receiving means and the association list information generated by the association list information generating means to the client terminal that is the browsing request source. A program that causes the device to function.   A recording medium on which the program according to claim 7 is recorded so as to be readable by a computer.

Images