JP2009104293A - Data management system, data management method, and data management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data management system, a data management method and a data management program for exactly managing a management object file including a logic and an operartion object data under the consideration of the convenience of a user. <P>SOLUTION: A developer or an operator edits a spread sheet file by a client terminal 10. Then, the control part 21 of a file management server 20 which has received an access request performs user authentication processing. When an upload person whose user authentication has been performed is a "developer", the control part 21 registers the spread sheet file acquired from the client terminal 10 as the temporary version of spread sheet file. Meanwhile, when the upload person is an "operator", the control part 21 extracts a logic from the spread sheet file, and compares the logic with the logic of the temporary version of spread sheet file. When both the logics are matched, the control part 21 executes the registration processing of a formal version of spread sheet file. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a data management system, a data management method, and a data management program for managing a management target file including logic and calculation target data.

  Today, with the Corporate Reform Act, internal control is emphasized in corporate activities (for example, see Non-Patent Document 1). In this internal control, prescribed standards and procedures are established for each business, and management, monitoring and assurance are performed based on these standards so that the organization can be operated in a sound, effective and efficient manner. It is required to keep a record (a trail) of activities and processes. The financial reporting process is operated by the IT system, and it is necessary to evaluate the IT system together with other important processes in order to comply with the Corporate Reform Act.

  For this reason, an integrated log management system for providing information useful for internal control in an organization such as a company has been studied (for example, see Patent Document 1). In the technology described in this document, logs recorded in a plurality of systems connected by an internal network such as a security gate, a security cabinet, an authentication system, a mail server, a network management server, a business terminal, and a PBX are recorded. Collect and create an integrated log that is organized by organization members.

  On the other hand, in business management in a company, a spreadsheet program is used in each department in charge, and an information management apparatus for efficiently reflecting such data in a database is being studied (for example, Patent Document 2). reference.). In the technique described in this document, the table creation unit creates various conversion tables for designating data to be extracted from the management information file created by the spreadsheet application. The capture processing unit captures data from a file created by a spreadsheet application in accordance with various conversion tables stored in the conversion table storage unit. The database write processing unit writes the data captured from the spreadsheet application by the capture processing unit to the database.

In addition, a database update system for updating a sheet of spreadsheet software to a database has been studied (for example, see Patent Document 3). In the technique described in this document, the administrator defines the conditions for updating the database for the spreadsheet sheet created using the function of the spreadsheet software. When a spreadsheet with data entered by the user is entered into the server on the administrator side, the server analyzes the update condition definition pasted on the spreadsheet and inputs the data into the spreadsheet. The database corresponding to is updated.
“News of the Internal Control of Financial Institutions—Evaluation and Documentation Procedures”, revised edition, Kinzai Co., Ltd., September 2007, p. 222-236 JP 2007-233661 A (first page) Japanese Patent Laying-Open No. 2005-284754 (first page) Japanese Patent Laying-Open No. 2003-15920 (first page)

In particular, in the “IT control target for compliance with the Sarbanes-Oxley Act (Corporate Reform Act)” described in Non-Patent Document 1, the prevention of unauthorized programs from being registered in the production environment, the prevention of unauthorized alteration of programs It is required to restrict the authority to transfer the program to production, to separate the duties of program developers and operators, and to keep records (trails) of these activities and processes.

  However, the technique described in Patent Document 1 focuses on heuristic control for fraud and is not sufficient for preventive control. In particular, the logic such as calculation formulas used in the financial reporting process is enormous and complex.

  On the other hand, it is preferable from the viewpoint of work efficiency that the user can use commercially available software as familiar as possible as the spreadsheet software. However, ordinary commercially available software can be edited relatively freely, and it is difficult to individually manage and set data and logic. Therefore, with the techniques described in Patent Document 1 and Patent Document 2, the above-described internal control cannot be achieved for data created by spreadsheet software.

  The present invention has been made to solve the above-mentioned problems, and its purpose is to accurately manage a management target file including logic and calculation target data while considering user convenience. A data management system, a data management method, and a data management program are provided.

  In order to solve the above-mentioned problems, the invention described in claim 1 includes a user information storage means that records type information for identifying a logic developer and a data input person with respect to a user identifier, A data management system comprising file information storage means for storing a management target file in association with an identifier and control means connected to the client terminal, wherein the control means specifies a user who accesses from the client terminal When the upload of the management target file including the logic and the calculation target data is received from the authentication unit and the client terminal, and the type information of the logic developer is recorded for the user identifier of the accessor, The uploaded management target file is registered in the file information storage means as a temporary version, and the user of the accessor When the type information of the data input person is recorded for the separate child, the logic is extracted from the uploaded management target file, checked against the logic included in the provisional version, and the two match The gist of the present invention is that it includes file registration means for registering the management target file in the file information storage means as an official version.

  According to a second aspect of the present invention, in the data management system according to the first aspect, when the control unit receives a print instruction for the official version of the management target file, the control unit is valid for the management target file. The gist of the invention is that it further includes print control means for generating print data to which the property display data is added and outputting the print data in the printing apparatus.

  According to a third aspect of the present invention, in the data management system according to the first or second aspect, the management target file is composed of a plurality of element sheets that are data-linked to each other, and the logic is recorded on the sheet. The gist is that the calculation target data is separated from the sheet on which the calculation target data is recorded.

The invention described in claim 4 stores user information storage means for recording type information for identifying a logic developer and a data input person with respect to a user identifier, and stores a management target file in association with the version identifier. A method of managing data using a data management system comprising file information storage means for controlling and control means connected to the client terminal, wherein the control means specifies an accessor from the client terminal; When receiving the upload of a management target file including logic and calculation target data from the client terminal, and when the type information of the logic developer is recorded for the user identifier of the accessor, The uploaded management target file is registered in the file information storage means as a temporary version, and the user of the accessor When the type information of the data input person is recorded for the separate child, the logic is extracted from the uploaded management target file, checked against the logic included in the provisional version, and the two match And executing the step of registering the management target file in the file information storage means as the official version.

  The invention according to claim 5 stores user information storage means for recording type information for identifying a logic developer and a data input person with respect to a user identifier, and stores a management target file in association with the version identifier. A program for managing data using a data management system comprising file information storage means for controlling and control means connected to the client terminal, wherein the control means identifies an accessor from the client terminal When the upload of the management target file including the logic and the calculation target data is received from the user authentication unit and the client terminal, and the type information of the logic developer is recorded for the user identifier of the accessor The uploaded management target file is registered in the file information storage means as a temporary version, and the access is made. If the type information of the data input person is recorded for the user identifier of the user, the logic is extracted from the uploaded management target file and checked against the logic included in the provisional version. In this case, the gist is to make this managed file function as a file registration means for registering the file as a formal version in the file information storage means.

(Function)
According to the first, fourth, or fifth aspect of the invention, the control means specifies the access person from the client terminal. And the upload of the management object file containing a logic and calculation object data is received from a client terminal. Here, when the type information of the logic developer is recorded for the user identifier of the accessor, the uploaded management target file is registered in the file information storage unit as a temporary version. On the other hand, when the type information of the data input person is recorded for the user identifier of the accessor, the logic is extracted from the uploaded management target file and collated with the logic included in the provisional version. When the two match, the management target file is registered in the file information storage means as the official version. Since the management target file includes logic and calculation target data, calculation processing can also be performed at the client terminal. Then, the logic developer can create the management target file considering only the accuracy of the logic included in the management target file. On the other hand, it is possible to ensure the accuracy of the logic in the management target file acquired from the data input person and registered in the file information storage means.

  According to the second aspect of the present invention, when a print instruction is received for the official version of the management target file, print data in which the validity display data is added to the management target file is generated and output by the printing apparatus. To do. Thereby, the accuracy can be identified in the printed form.

  According to the third aspect of the present invention, the management target file is composed of a plurality of element sheets that are data-linked to each other, and is divided into a sheet on which logic is recorded and a sheet on which calculation target data is recorded. Configured. Thereby, logic can be efficiently extracted from the management target file.

  ADVANTAGE OF THE INVENTION According to this invention, the management object file containing a logic and calculation object data can be managed exactly, considering a user's convenience.

Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that a file used for business is managed for internal control in a company.

  In this embodiment, a spreadsheet file is managed as a management target file. This spreadsheet file is composed of a plurality of worksheets. Further, the worksheet is divided into a worksheet (logic sheet) on which logic is recorded and a worksheet (data sheet) on which calculation target data is recorded. In the logic sheet, cell specifying data for specifying a cell in the data sheet and function data for performing calculation processing using calculation target data recorded in the cell are recorded.

  In order to manage such a file, as shown in FIG. 1, a file management server 20 connected via a network, a client terminal 10 of a user (an administrator terminal, a developer terminal, an operator terminal) ) Or the printer 15. Here, the manager includes an administrator of the organization that controls the internal control (overall manager) and an administrator of each department in charge (department manager). The general manager is a user who has the authority to register and delete the user identifier and initial password of each department manager. The department manager is a user who has the authority to register and delete user identifiers and initial passwords of operators and developers in each department. The operator is a user who is permitted to update calculation target data (for example, numerical data) recorded in the data sheet of the spreadsheet file. The developer is a user who is permitted to update the logic recorded in the logic sheet of the spreadsheet file.

  Each client terminal 10 is a computer terminal connectable to a network, and includes a control unit configured by control means such as a CPU, RAM, ROM, data storage means, input means, output means, communication means, and the like. A keyboard or pointing device is used as the input means. A display or a printer is used as the output means. These client terminals 10 store known browser programs, and realize browsing and data transmission of data acquired via the network. Further, a spreadsheet program is stored in the client terminal 10 of the developer or operator, and the spreadsheet file can be edited.

  The file management server 20 is a computer system that manages a spreadsheet file to be managed. For this reason, the file management server 20 includes a control unit 21 composed of control means such as a CPU, a RAM, a ROM, and the like (steps described later (user authentication step, file transfer step, file registration step, logic confirmation step, print control) Process including stages). By executing the data management program for this purpose, the control unit 21 of the file management server 20 functions as a user authentication unit 211, a file transfer unit 212, a file registration unit 213, a logic confirmation unit 214, and a print control unit 215.

The user authentication unit 211 performs user authentication in response to access from the client terminal 10.
The file transfer unit 212 provides the client terminal 10 with the file registered in the file management data storage unit 23 in response to a download request from the client terminal 10.

The file registration unit 213 registers the file received from the client terminal 10 in the file management data storage unit 23.
The logic confirmation unit 214 compares the logic included in the file received from the client terminal 10 with the logic registered in the provisional version, and confirms whether the logic has been altered.

The print control unit 215 executes file printing processing in response to a request from the client terminal 10.
Further, the file management server 20 includes a user management data storage unit 22 as user information storage means, a file management data storage unit 23 as file information storage means, and a management target logic storage unit 24.

  As shown in FIG. 2A, user management data 220 relating to the user of the file management server 20 is recorded in the user management data storage unit 22. This user management data 220 is registered when a user application for the file management server 20 is made. The user management data 220 includes data relating to a user identifier, a password, and a user type.

Data relating to an identifier for specifying each user is recorded in the user identifier data area.
Data relating to a password for authenticating the user is recorded in the password data area.

  In the user type data area, data relating to an identifier for specifying the role of the user is recorded. In the present embodiment, data relating to an identifier for identifying the general manager, department manager, developer, and operator is recorded in the user type data area.

  In the file management data storage unit 23, as shown in FIG. 2B, file management data 230 for a file to be managed in the internal control is recorded. The file management data 230 is registered when a management target file is received from the client terminal 10. The file management data 230 includes data relating to a file identifier, a version identifier, a registration date, and a spreadsheet file.

In the file identifier data area, data relating to an identifier for specifying a management target file is recorded. In the present embodiment, the file name is used as the file identifier.
In the version identifier data area, data relating to an identifier for specifying the version of this file is recorded. This version identifier is set with a numbering system for identifying a provisional version or a formal version.

In the registration date data area, data relating to the date and time when this file was registered is recorded.
A spreadsheet file received from the client terminal 10 is stored in the spreadsheet file data area.

  In the management target logic storage unit 24, management target logic data regarding logic to be managed in internal control is recorded. This management target logic data is registered when the management target is determined. In this embodiment, as the logic to be managed, “arithmetic symbols” for calculation of other cells, “macro” describing a specific operation procedure, “name definition”, “cross tabulation function” such as a pivot table, etc. And

  The file management processing procedure using the system configured as described above will be described with reference to FIGS. Here, an outline of file management (FIG. 3), download processing (FIG. 4), upload processing (FIG. 5), and print processing (FIG. 6) will be described in this order.

(Overview of file management)
First, an outline of file management will be described with reference to FIG.
Here, the file management server 20 performs an initial registration process (step S1-1). First, the general manager creates a spreadsheet file to be managed using the client terminal 10. Then, the file management server 20 acquires the spreadsheet file to be managed from the client terminal 10 of the general manager and initially registers it in the file management data storage unit 23.

  Further, the general manager sets the user identifier and initial password of the department manager of the department in charge of managing each spreadsheet file. Then, the file management server 20 acquires data related to the user identifier and the initial password of the department administrator from the client terminal 10 of the general manager, and initially registers it in the user management data storage unit 22. Then, the general manager notifies each department manager that the initial registration has been performed. In this case, the department manager accesses the file management server 20 from the client terminal 10 using the user identifier and the initial password, and registers and changes the password recorded in the user management data storage unit 22.

  Next, the file management server 20 performs a user addition process (step S1-2). First, the department manager determines a developer who is responsible for registering logic and an operator who is responsible for registering calculation target data. Then, the login to the file management server 20 is performed from the client terminal 10 of the department manager using the user identifier and password of the department manager. In this case, the file management server 20 performs user authentication using the user identifier and password of the department manager. When the user authentication is completed, the file management server 20 acquires data on the developer and operator user identifiers and the initial password, and initially registers them in the user management data storage unit 22. The department manager notifies each developer and operator that initial registration has been performed. In this case, each developer and operator accesses the file management server 20 from the client terminal 10 using the user identifier and the initial password, and registers and changes the password recorded in the user management data storage unit 22.

  Next, the developer client terminal 10 performs a process of creating a spreadsheet file logic (step S1-3). Specifically, the developer acquires a spreadsheet file from the file management server 20 using the client terminal 10. In this case, the file management server 20 executes a download process described later. Then, the developer uses the spreadsheet program of the client terminal 10 to create logic in the spreadsheet file. Here, logic is set in the logic sheet of the spreadsheet file.

  Next, the file management server 20 performs a temporary registration process for the spreadsheet file (step S1-4). Specifically, the file management server 20 acquires a spreadsheet file in which logic is set from the developer's client terminal 10 and registers it in the file management data storage unit 23. In this case, the file management server 20 executes an upload process described later. Then, the file management server 20 registers the acquired spreadsheet file as a temporary version.

  Next, the data input process of the spreadsheet file is performed at the client terminal 10 of the operator (step S1-5). Specifically, the operator acquires a spreadsheet file from the file management server 20 using the client terminal 10. In this case, the file management server 20 executes a download process described later. Then, using the spreadsheet program of the client terminal 10, the calculation target data is input in the spreadsheet file. Here, calculation target data is input to the data sheet of the spreadsheet file.

  Next, the file management server 20 performs a formal registration process for the spreadsheet file (step S1-6). Specifically, the file management server 20 acquires a spreadsheet file to which calculation target data is input from the client terminal 10 of the operator, and registers it in the file management data storage unit 23. In this case, the file management server 20 executes an upload process described later. In this case, the file management server 20 registers the acquired spreadsheet file as the official version.

  Then, the file management server 20 performs a printing process to be described later (step S1-7). Specifically, when the file management server 20 receives a spreadsheet file print request from the client terminal 10, the file management server 20 specifies the version of the spreadsheet file to be requested. Here, when a print request for the official version is made, form data to which predetermined security information is added is generated and printed by the printer 15.

(Download process)
Next, the download process will be described with reference to FIG. This process is executed when a desired spreadsheet file is downloaded using the client terminal 10.

  First, the client terminal 10 executes an access process (step S2-1). Specifically, the client terminal 10 transmits an access request to the file management server 20.

  The control unit 21 of the file management server 20 that has received the access request executes user authentication processing (step S2-2). Specifically, the user authentication unit 211 of the control unit 21 transmits authentication screen data to the client terminal 10. In this case, a user authentication screen having a user identifier input field and a password input field is displayed on the display of the client terminal 10. When a transmission instruction is input after the user identifier and password are set using this user authentication screen, the client terminal 10 transmits a login request to the file management server 20. This login request includes data related to the user identifier and password set on the user authentication screen.

  In this case, the user authentication unit 211 confirms whether or not the user identifier and password received from the client terminal 10 are registered in the user management data storage unit 22. When the user identifier and password are registered in the user management data storage unit 22, the user authentication unit 211 transmits a login permission notification to the client terminal 10. In this case, the user authentication unit 211 transmits the file identifier and version identifier list display screen data of the management target file registered in the file management data storage unit 23 to the client terminal 10.

  In this case, the client terminal 10 executes a download request process (step S2-3). Specifically, the client terminal 10 outputs the list display screen received from the user management data storage unit 22 to the display. Then, the user selects a desired spreadsheet file on this list display screen. Then, the client terminal 10 to which the download instruction is input transmits a download request to the file management server 20. This download request includes data relating to the file identifier and version identifier of the spreadsheet file selected on the list display screen.

  The control unit 21 of the file management server 20 that has received the download request executes a spreadsheet file transmission process (step S2-4). Specifically, the file transfer unit 212 of the control unit 21 acquires the file identifier and the version identifier spreadsheet file included in the download request from the file management data storage unit 23 and transmits them to the client terminal 10.

  Then, the client terminal 10 executes input / edit processing (step S2-5). Specifically, the client terminal 10 stores the spreadsheet file received from the file management server 20 in the data storage unit in the client terminal 10. Then, the developer or operator uses the client terminal 10 to set logic and input / edit calculation target data in the spreadsheet file.

(Upload process)
Next, the upload process will be described with reference to FIG.
First, the client terminal 10 executes an access process (step S3-1). Specifically, the client terminal 10 transmits an access request to the file management server 20.

The control unit 21 of the file management server 20 that has received the access request executes user authentication processing (step S3-2). This process is performed in the same manner as step S2-2.
Then, the client terminal 10 executes upload request processing (step S3-3). Specifically, the user selects a spreadsheet file to be uploaded on the file list display screen stored in the data storage unit of the client terminal 10. Then, the client terminal 10 to which the upload instruction is input transmits an upload request to the file management server 20. The upload request includes the spreadsheet file selected on the file list display screen.

  Next, the control unit 21 of the file management server 20 executes a user type confirmation process (step S3-4). Specifically, the file registration unit 213 of the control unit 21 acquires the user type recorded in the user management data 220 that has been authenticated in step S3-2.

  When registered as “developer” in the user type of the user management data 220 (in the case of “developer” in step S3-4), the control unit 21 of the file management server 20 performs provisional version registration processing. Execute (Step S3-5). Specifically, the file registration unit 213 of the control unit 21 generates file management data 230 including the spreadsheet file acquired from the client terminal 10 and the registration date. In this case, the file registration unit 213 sets “provisional version” as the version identifier and registers it in the file management data storage unit 23.

  On the other hand, when the user type of the user management data 220 is registered as “operator” (in the case of “operator” in step S3-4), the control unit 21 of the file management server 20 performs logic from the spreadsheet file. The extraction process is executed (step S3-6). Specifically, the logic confirmation unit 214 of the control unit 21 uses the management target logic storage unit 24 to extract logic from the logic sheet of the received spreadsheet file.

  And the control part 21 of the file management server 20 performs a logic collation process (step S3-7). Specifically, the logic confirmation unit 214 of the control unit 21 uses the file management data storage unit 23 to store the spreadsheet file most recently registered as the provisional identifier in the spreadsheet file having the same file identifier as the received spreadsheet file. Extract from Then, the logic confirmation unit 214 uses the management target logic storage unit 24 to extract the logic set in the logic sheet of the provisional spreadsheet file. Next, the logic checking unit 214 compares the logic of the spreadsheet file received from the client terminal 10 with the logic of the provisional spreadsheet file (step S3-8). Then, the logic confirmation unit 214 supplies the collation result to the file registration unit 213.

  When both logics match and there is no change (in the case of “YES” in step S3-8), the control unit 21 of the file management server 20 executes a formal version registration process (step S3-9). Specifically, the file registration unit 213 of the control unit 21 generates file management data 230 including the spreadsheet file acquired from the client terminal 10 and the registration date. Then, the latest version identifier is assigned to the spreadsheet file and registered in the file management data storage unit 23.

  On the other hand, if the two logics do not match and a change in logic is detected (in the case of “NO” in step S3-8), the control unit 21 of the file management server 20 executes an alarm process (step S3-10). ). Specifically, the file registration unit 213 of the control unit 21 rejects registration of the received file and notifies the client terminal 10 that the spreadsheet file cannot be registered.

(Printing process)
Next, the printing process will be described with reference to FIG.
First, the client terminal 10 executes an access process (step S4-1). Specifically, the client terminal 10 transmits an access request to the file management server 20.

The control unit 21 of the file management server 20 that has received the access request executes user authentication processing (step S4-2). This process is performed in the same manner as step S2-2.
Then, the client terminal 10 executes print request processing (step S4-3). Specifically, the client terminal 10 acquires file identifier and version identifier list display screen data of a management target file registered in the file management data storage unit 23 of the file management server 20. Here, the user selects a desired spreadsheet file on the list display screen. Then, the client terminal 10 to which the print instruction is input transmits a print request to the file management server 20. This print request includes data relating to the file identifier and version identifier of the spreadsheet file selected on the list display screen.

  The control unit 21 of the file management server 20 that has received the print request executes a version confirmation process (step S4-4). Specifically, the print control unit 215 of the control unit 21 checks whether the version identifier of the print request is the latest version identifier in the management target file registered in the file management data storage unit 23.

  When the version identifier of the print request is the latest version identifier (in the case of “YES” in step S4-4), the control unit 21 of the file management server 20 executes a print data generation process with security information added thereto ( Step S4-5). Specifically, the print control unit 215 of the control unit 21 acquires a spreadsheet file from the file management data storage unit 23, and adds data for displaying security information indicating that it is an official version to the spreadsheet file.

  Then, the control unit 21 of the file management server 20 executes print execution processing (step S4-6). Specifically, the print control unit 215 of the control unit 21 transmits print data to which security information as legitimacy display data is added to the printer 15. As a result, the form with security information added is output from the printer 15.

  On the other hand, when the version identifier of the print request is not the latest version identifier (in the case of “NO” in step S4-4), the control unit 21 of the file management server 20 executes an alarm process (step S4-7). Specifically, the print control unit 215 of the control unit 21 notifies the client terminal 10 that it is not an official version and ends the process.

According to this embodiment, the following effects can be obtained.
In the present embodiment, when registered as “Developer” in the user type of the user management data 220, the control unit 21 of the file management server 20 executes a provisional registration process (step S3- 5). Although an appropriate logic is set in the spreadsheet file received from the developer's client terminal 10, there is a possibility that test numerical values may be recorded for the calculation target data, which is not accurate. Therefore, it can be identified as the official version by registering it as a provisional version. Therefore, the developer only needs to ensure the accuracy of the logic and does not need to be aware of the data sheet.

  In the present embodiment, when registered as “operator” in the user type of the user management data 220, the control unit 21 of the file management server 20 extracts logic from the spreadsheet file (step S3- 6) A logic collation process is executed (step S3-7). When the logic of the spreadsheet file received from the client terminal 10 matches the logic of the provisional spreadsheet file, the control unit 21 of the file management server 20 executes a formal version registration process (step S3). -9). Thereby, it is possible to prevent logic modification by the operator. Therefore, the operator only needs to ensure the accuracy of the calculation target data and does not need to be aware of the logic.

  In this embodiment, a developer or an operator downloads a spreadsheet file from the user management data 220, and performs logic setting or calculation target data input or editing. Thereby, since the familiar spreadsheet program can be used in the client terminal 10, the convenience of the user can be maintained as in the conventional case.

  In this embodiment, the control unit 21 of the file management server 20 that has received the print request executes a version confirmation process (step S4-4). When the version identifier of the print request is the latest version identifier (in the case of “YES” in step S4-4), the control unit 21 of the file management server 20 executes a print data generation process with security information added thereto ( Step S4-5). As a result, the official version can be identified in the printed matter, and accurate form management can be performed.

  In the present embodiment, the spreadsheet file worksheet is divided into a worksheet (logic sheet) in which logic is recorded and a worksheet (data sheet) in which calculation target data is recorded. Thereby, the control part 21 of the file management server 20 can extract a logic efficiently.

In addition, you may change each said embodiment as follows.
In the above embodiment, the data management method is applied to the spreadsheet file. However, the present invention is not limited to this, and can be applied to other types of files including calculation target data and logic. .

In the above embodiment, the user management data is registered separately for the general manager and the department manager. However, the user registration method is not limited to this.
In the above embodiment, in the logic collation process (step S3-7), the logic confirmation unit 214 of the control unit 21 is most recently registered as a provisional identifier in the spreadsheet file having the same file identifier as the received spreadsheet file. The spreadsheet file is extracted from the file management data storage unit 23. Then, the logic confirmation unit 214 uses the management target logic storage unit 24 to extract the logic set in the logic sheet of the provisional spreadsheet file. Alternatively, when registering a temporary spreadsheet file, it is also possible to extract logic from the spreadsheet file and register it in advance in a logic registration data storage unit (not shown). As a result, the efficiency of the logic matching process can be improved.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on the data storage part, Comprising: (a) is a user management data storage part, (b) is explanatory drawing of the data recorded on the file management data storage part. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 15 ... Printer, 20 ... File management server, 21 ... Control part, 211 ... User authentication means, 212 ... File transfer means, 213 ... File registration means, 214 ... Logic confirmation means, 215 ... Print control means, 22 ... User management data storage unit, 23 ... File management data storage unit, 24 ... Managed object logic storage unit.

Claims (5)

User information storage means for recording type information for identifying a logic developer and a data input person with respect to a user identifier;
File information storage means for storing the management target file in association with the version identifier;
A data management system comprising control means connected to a client terminal,
The control means is
User authentication means for identifying the accessor from the client terminal;
From the client terminal, receiving an upload of a management target file including logic and calculation target data,
When the type information of the logic developer is recorded for the user identifier of the accessor, the uploaded management target file is registered in the file information storage unit as a temporary version,
If the type information of the data input person is recorded for the user identifier of the accessor, the logic is extracted from the uploaded management target file, collated with the logic included in the temporary version, A data management system comprising file registration means for registering the management target file in the file information storage means as an official version when the two match.   When the print instruction is received for the official version of the management target file, the control unit generates print data in which the validity display data is added to the management target file, and outputs the print data in the printing apparatus The data management system according to claim 1, further comprising: The management target file is composed of a plurality of element sheets data-linked to each other,
The data management system according to claim 1, wherein the sheet on which the logic is recorded and the sheet on which calculation target data is recorded are configured separately. User information storage means for recording type information for identifying a logic developer and a data input person with respect to a user identifier;
File information storage means for storing the management target file in association with the version identifier;
A method for managing data using a data management system comprising a control means connected to a client terminal,
The control means is
Identifying the visitor from the client device,
Receiving an upload of a management target file including logic and calculation target data from the client terminal;
When the type information of the logic developer is recorded for the user identifier of the accessor, the uploaded management target file is registered in the file information storage unit as a temporary version,
If the type information of the data input person is recorded for the user identifier of the accessor, the logic is extracted from the uploaded management target file, collated with the logic included in the temporary version, And a step of registering the file to be managed in the file information storage means as a formal version when the two coincide with each other. User information storage means for recording type information for identifying a logic developer and a data input person with respect to a user identifier;
File information storage means for storing the management target file in association with the version identifier;
A program for managing data using a data management system comprising control means connected to a client terminal,
The control means;
User authentication means for identifying the accessor from the client terminal;
From the client terminal, receiving an upload of a management target file including logic and calculation target data,
When the type information of the logic developer is recorded for the user identifier of the accessor, the uploaded management target file is registered in the file information storage unit as a temporary version,
If the type information of the data input person is recorded for the user identifier of the accessor, the logic is extracted from the uploaded management target file, collated with the logic included in the temporary version, A data management program for causing a file registration unit to register the management target file in the file information storage unit as an official version when the two match.

Images