JP2008165416A - Data input management device, data input management system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily and freely perform a layout of a data input screen by a browser, and to perform data input. <P>SOLUTION: This data input management device has: a storage means; an editor part 11A generating page information of an editor screen for the browser allowing setting of the layout of items of the data input screen, making it displayed, generating a specification file 151 storing data of the data input screen from setting data of the layout of the items input through the editor screen, and a data storage file 152 storing the data input through the data input screen, and storing them into the storage means; and a data input control means generating page information of the data input screen for the browser based on the specification file 151 and the data storage file 152, making it displayed, and storing the input data input through the data input screen into the data storage file 152. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a data input management device, a data input management system, and a program.

  In the past, when making various WEB applications (data entry processing for application forms (notification forms)) that had been done in writing, the development was mostly entrusted to a specialized team that created the system.

Some data processing devices for inputting data into a database create and display a data input screen. A data input screen is automatically created and displayed based on the item number selected and input by the user, and data input work is performed by the user via the data input screen (see, for example, Patent Document 1).
JP 11-345152 A

  However, the conventional system for inputting a notification application by a third party requires a lot of reception meetings, costs, time, etc., and for that reason, it has been abandoned or reduced in scale. Another problem is that the intention of the business person who is the user is not well communicated to the developer, something that is not suitable for the business is created, and correction is made after completion.

  In addition, the development tools for programming the content you want to realize are specialized and difficult to learn, and due to variations in the quality of the program depending on the degree of experience, you will be troubled by problems after completion or not finished as intended There was a problem such as. In this way, it was difficult for the person in charge of the business to easily create a notification application input system without going through a third party.

  Moreover, the above problems can be suppressed by using the application program provided in the package instead of creating a new notification application input system. However, if the application program for the package application is not exactly the same as the application, or if there is no application required for the application, it must be customized separately. If this customization occurs even with a slight revision, the same problem as above will occur. As described above, even if the application program of the package is used, it is difficult for the business person in charge to easily create a notification application input system without going through a third party.

  In addition, in a conventional data processing apparatus that automatically generates a data input screen, the person in charge of business can only select items to be input, and the data input screen such as the arrangement of data input fields cannot be freely customized.

  On the other hand, when viewed as a WEB system, in the server client system, the application program body is placed on the server side, and the client displays a data input / output interface screen on the browser. Today, with the spread of the Internet, browser operations are not so difficult for business personnel and learning is easy.

  However, looking at the development side, the development tools used in the server environment are highly specialized to develop applications in a closed world within the server environment, and the work screen is also the server OS (Operating System). Most of the dedicated screens depended on. There was a problem that it was difficult for the person in charge of business to use the dedicated screen to create a system easily. In addition, since the tool is closed in the server environment, there is a problem that the OS on which the tool operates is limited.

Furthermore, there are the following two types of browser screen development tools as data input screens.
(1). A tool that uses a dedicated editor.
(2). Editor tool that uses a browser.

  Regarding (1), there are problems that the operating OS is limited as described above, and that it is difficult to learn operations. In addition, some tools require special plug-in software (additional tools) in order to display the created screen in the browser, and HTML (HyperText Markup Language) and Javascript ( There is a problem that it cannot be realized only in a registered trademark) or CSS (cascade styling seat) environment.

  Regarding (2) above, since the interface is a browser, there is no OS restriction or the like as long as the computer operates the browser, and it can be created if the browser can be operated. However, the arrangement of character strings formed as screens, text boxes for data entry, drop-down lists, and the like has to be arranged according to rules determined in order from a predetermined starting point. For this reason, it is not possible to create a free screen layout, and it is necessary to create a layout screen that is different from the document that you are familiar with in the work, which is troublesome to rebuild the screen, and it takes time to use it thoroughly later. It was.

  An object of the present invention is to input data by laying out a data input screen easily and freely by a browser.

In order to solve the above problem, a data input management device according to claim 1 is provided.
Storage means;
Generates and displays the page information of the editor screen for browsers that can set the layout of items on the data input screen, and stores the data on the data input screen from the setting data of the layout of the items input via the editor screen An editor control unit that generates a spec file, a data storage file that stores data input via the data input screen, and stores the generated data file in the storage unit;
Based on the stored specification file and data storage file, page information of a data input screen for a browser is generated and displayed, and input data input via the data input screen is stored in the data storage file. And a data input control means.

The invention according to claim 2 is the data input management device according to claim 1,
The data input screen includes a data selection area indicating that the data to be changed can be selected and indicating the change state, a data editing area indicating the item for which the layout is set, and operation button areas indicating various operation buttons. Have
The data input control unit reflects the input data input through the data editing area and the change state thereof in the data selection area in response to an operation button input in the operation button area.

The invention according to claim 3 is the data input management device according to claim 1 or 2,
A display means and an operation means,
The editor control means displays the editor screen on the display means based on the page information of the editor screen, and from the setting data of the layout of items input via the operation means according to the editor screen, Generating the spec file and the data storage file;
The data input control means displays page information of the data input screen on the display means, and stores the input data input via the operation means in the data storage file according to the data input screen. Features.

The data input management system of the invention according to claim 4
The data input management device according to claim 1 or 2,
A terminal device comprising display means, operation means, and first communication means for communicating with the data input management device,
The data input management device includes:
A second communication means for communicating with the terminal device;
The editor control means transmits page information of the editor screen to the terminal device via the second communication means, and sets layout data of items input via the editor screen as the second communication. Receiving from the terminal device via means,
The data input control means transmits page information of the data input screen to the terminal device via the second communication means, and sends the data input via the data input screen to the second communication means. Via the terminal device via
The terminal device
The item received from the data input management device via the first communication unit and the editor screen or the page information of the editor screen, and input via the operation unit according to the editor screen or the editor screen Control means for transmitting the layout setting data or input data to the data input management device via the first communication means.

The program of the invention described in claim 5 is:
Computer
Storage means,
Generates and displays the page information of the editor screen for browsers that can set the layout of items on the data input screen, and stores the data on the data input screen from the setting data of the layout of the items input via the editor screen An editor control means for generating a spec file and a data storage file for storing data input via the data input screen and storing them in the storage means,
Based on the stored specification file and data storage file, page information of a data input screen for a browser is generated and displayed, and input data input via the data input screen is stored in the data storage file. Data input control means,
It is made to function as.

  According to the present invention, a data input screen can be easily and freely laid out by a browser operation.

  DESCRIPTION OF EMBODIMENTS Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. The present invention is not limited to the illustrated example.

  First, the apparatus configuration of the present embodiment will be described with reference to FIGS. FIG. 1 shows a configuration of a data input system 100 according to the present embodiment. FIG. 2 shows the internal configuration of the server 10. FIG. 3 shows the internal configuration of the PC 20. FIG. 4 shows a functional configuration of the data input system 100.

  As shown in FIG. 1, the data input system 100 according to the present embodiment includes a server 10 and a PC (Personal Computer) 20, and each device is connected via a communication network N.

  For example, in the data input system 100, based on an application form for applying to change employee information of a company, a user (person in charge of personnel) operates the PC 20 to input data described in the application form to the server 10 The system to be registered. However, the data input system 100 may be configured to input other types of data.

  The server 10 as a data input management device and the PC 20 as a terminal device are representatively shown, and are not limited to this type and number. The terminal device may be a device having a browsing function such as a PDA (Personal Digital Assistant), a mobile phone, and a PHS (Personal Handyphone System).

  The communication network N is the Internet, and may include a LAN (Local Area Network), a WAN (Wide Area Network), an Internet provider, and the like.

  As illustrated in FIG. 2, the server 10 includes a CPU (Central Processing Unit) 11, an input unit 12, a RAM (Random Access Memory) 13, a display unit 14, a storage unit 15 as a storage unit, and a communication unit. 16, and each unit is connected via a bus 17.

  The CPU 11 centrally controls each unit of the server 10. The CPU 11 expands a program designated from the system program and various application programs stored in the storage unit 15 in the RAM 13 and executes various processes in cooperation with the program expanded in the RAM 13. The CPU 11 functions as an editor unit 11A, a data input unit 11B, and a document / help generation unit 116, which will be described later, in cooperation with various programs.

  The input unit 12 includes a keyboard including cursor keys, numeric input keys, various function keys, and the like, and outputs a pressing signal pressed by the operator using the keyboard to the CPU 11. Further, the input unit 12 may include a pointing device such as a mouse.

  The RAM 13 is a volatile memory, has a work area for storing various programs to be executed, data related to these various programs, and the like, and temporarily stores information.

  The display unit 14 includes an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), and the like, and performs screen display according to a display signal from the CPU 11.

  The storage unit 15 includes a recording medium (not shown) in which various programs, various data, and the like are stored or writable in advance, and a storage such as an HDD (Hard Disk Drive) that stores various information in the recording medium in a readable manner. Part. The storage unit 15 is not limited to a fixed one such as an HDD, but is a CD-R (Recordable) / RW (Rewritable), DVD (Digital Versatile Disk) -R / RW, memory card, portable hard disk, blue A portable storage unit to which a recording medium such as a large-capacity information recording medium using a laser is detachably mounted may be used.

  The storage unit 15 stores a specification file 151, a data storage file 152, a master file 153, a data input reference file 154, a data registered management file 155, an item object property file 156, and an item object management file 157, which will be described later.

  The communication unit 16 includes a modem, a TA (Terminal Adapter), a router, a network card, and the like, and transmits / receives information to / from an external device such as the PC 20 on the connected communication network N.

  As illustrated in FIG. 3, the PC 20 includes a CPU 21, an input unit 22 as an operation unit, a RAM 23, a display unit 24 as a display unit, a storage unit 25, and a communication unit 26. Each unit is connected via a bus 27.

  The CPU 21, input unit 22, RAM 23, display unit 24, storage unit 25, and communication unit 26 have the same configuration as the CPU 11, input unit 12, RAM 13, display unit 14, storage unit 15, and communication unit 16 of the server 10. The different parts will be explained.

  The CPU 21 starts the browser in cooperation with the browser program read from the storage unit 25 and stored in the RAM 23, and receives page information from the server 10 via the communication unit 26, and corresponds to the page information. The browser screen to be displayed is displayed on the display unit 24, and various information input via the input unit 22 is transmitted to the server 10 via the communication unit 26.

  The input unit 22 includes a keyboard and a pointing device such as a mouse, and is capable of character input and pointer position input. The storage unit 25 stores a browser program. The communication unit 26 transmits and receives information to and from devices such as the server 10 on the communication network N.

  As shown in FIG. 4, the server 10 includes, as functional components, an editor unit 11A as an editor control unit, a data input unit 11B as a data input control unit, a document / help generation unit 116, and a specification file. 151, a data storage file 152, a master file 153, a data input reference file 154, and a data registered management file 155.

  The editor unit 11A includes an editor processing unit 111, a data storage file generation unit 112, and a screen generation unit 113. The data input unit 11B includes a screen generation unit 113, a screen provision unit 114, and a data storage unit 115.

  The editor unit 11A executes an editing process described later. The editor processing unit 111 transmits page information of the editor screen 241 as a browser screen generated by the screen generation unit 113 to the PC 20 and receives operation information of the editor screen 241 from the PC 20. Further, the editor processing unit 111 outputs the operation information on the editor screen 241 to the data storage file generation unit 112 and the screen generation unit 113. Further, the editor processing unit 111 generates a spec file based on the operation information on the editor screen 241 and stores the spec file in the spec file 151.

  The data storage file generation unit 112 generates a data storage file based on the operation information on the editor screen 241 and stores it in the data storage file 152.

  The screen generation unit 113 generates page information for the (new) editor screen 241 based on the data stored in the data storage file 152, the master file 153, the data input reference file 154 and the operation information on the editor screen 241, and performs editor processing. Output to the unit 111. The screen generation unit 113 also uses the data storage file 152, the master file 153, the data input reference file 154 data, and the operation information of the data input screen 242 as a browser screen to display a (new) data input screen 242. The page information is generated and output to the screen providing unit 114.

  The screen providing unit 114 outputs the page information of the data input screen 242 generated by the screen generating unit 113 to the PC 20 using the data of the specification file 151.

  The data storage unit 115 receives the operation information on the data input / output screen from the PC 20 and updates the data registration management file 155 and the data storage file 152 based on the operation information on the data input screen 242.

  The document / help generation unit 116 generates page information of a document screen (source display screen) 243 as a browser screen of the spec file described in the XML (eXtensible Markup Language) format of the spec file 151 and transmits the page information to the PC 20. Further, the document / help generation unit 116 generates page information of a help screen 243 as a browser screen and transmits it to the PC 20.

  The CPU 21 of the PC 20 receives the page information of the browser screen of the editor screen, the data input / output screen, and the document / help screen received from the server 10, displays the browser screen on the display unit 24, and displays the browser screen via the input unit 22. The input of operation information is accepted and transmitted to the server 10.

  Next, various types of information stored in the storage unit 15 of the server 10 will be described with reference to FIGS. FIG. 5 shows the internal structure of the item object property file 156. FIG. 6 shows the internal configuration of the item object management file 157. FIG. 7 shows the data structure of the specification file 151. FIG. 8A shows an example of the specification file 151. FIG. 8B shows the internal configuration of the data storage file 152 generated from the specification file 151 shown in FIG.

  The master file 153 is a file indicating information of all members who are targets of data input. For example, the master file 153 includes personal information such as employee number, employee name, sex, and age, and information such as the name, sex, and age of each family member of all employees of a company.

  The data input reference file 154 has information for reference at the time of data input. The data input reference file 154 has, for example, information on a list of national university names used when inputting a university name of a certain employee's family.

  The data registration management file 155 has information indicating whether or not data input has been completed for each application form (continuing).

  The item object property file 156 has information on each item object arranged for each data input screen to be edited. As shown in FIG. 5, the item object property file 156 includes item basic information, valid value information indicating a data type that can be input for the item object, item layout information indicating the arrangement of the item object in the data input screen, and the like. And an item description that supplementarily explains the item object.

  The item basic information includes an item name, a type indicating an inputable data type (character, numerical value, etc.), a number of digits indicating the length of inputable data, a KEY item Flag indicating whether the item is a KEY item, and Index. It is composed of an Index Flag indicating whether or not there is, an essential Flag indicating whether or not it is an essential item, and the like.

  The valid value information includes value information that can be input by the input data, character type of the input data, and the like. Possible value information includes value type, maximum value / minimum value, reference table specifying information, and candidate value information. For example, if the value type is 0: no restriction, there is no restriction on data that can be input. If the value type is 1: fixed value range, the data that can be input is limited by the maximum value and the minimum value. When the value type is a plurality of candidate externally acquired information, the data that can be input is limited by the reference table of the data input reference file 154 specified by the reference table specifying information. If the value type is fixed value information of 3: multiple candidates, the data that can be input is limited by the fixed value defined by the fixed value information.

  The item layout information includes a non-display flag indicating whether or not the item of the item object is hidden on the screen, a display label, a display form (text box, radio button, check box, drop-down list, subform, etc.), X coordinate, Y coordinate, display label width, input area width, etc. on the data input screen. The item description includes guidance help text and the like.

  The item object management file 157 is information for managing item objects set on the data input screen for each application. As shown in FIG. 6, in the item object management file 157, set item object names are arranged.

  The spec file 151 includes information describing a data input screen for each application form. The spec file 151 includes information (type, arrangement coordinates, etc.) of item objects in the data input screen. The specification file 151 is described in XML, for example.

  FIG. 7 shows an example of the data structure of the specification file 151 in which the “sex” item object is set for the application form “family change notification”. As shown in FIG. 7, the data of the specification file 151 includes item basic information, appropriate value information, item layout information, item description, and the like. The item object data included in the data input screen of the spec file 151 is reflected from the item object property file 156 and the item object management file 157.

  In the specification file 151, “Family Change Notification” is defined as the name of the DB file definition between <table> and </ table>. Also, information on each item object is defined between <item> and </ item>. “Sex” is defined as the name of the item object between <itemName> and </ itemName>. Between <itemAttrs> and </ itemAttrs>, the type, number of digits, possible values, etc. of the item object are defined. Between <itemInterface> and </ itemInterface>, the type of form (radio button, control, etc.) to be used and its position are defined. Also, the entire reference information is defined between <query> and </ query> of the specification file 151. For example, a record referred to by the master file 153, items of the record, and the like are defined.

  The data storage file 152 is a file for storing data input based on the data input screen, and is generated from the specification file 151. An example of the specification file 151 for the application form “Family Change Notification” is shown in FIG. An example of the data storage file 152 generated from the specification file 151 of FIG. 8A is shown in FIG.

  The specification file 151 of FIG. 8A includes (1) information of the table name “family change notification”, (2) information of the item object of the application date, (3) information of the item object of the name, (4 ) Information on the item object of the name Kana. From such a spec file 151, a data storage file 152 is generated for storing input data of application date, name, and name kana with the table name “family change notification”.

  Next, the operation of the data input system 100 will be described with reference to FIGS. First, an outline of the operation of the server 10 will be described with reference to FIG. FIG. 9 shows a flow of editing processing (outline) and data input processing (outline) executed in the server 10.

  The editing process (outline) shown in FIG. 9 is executed by the editor unit 11A. The editing process (outline) is a process for causing the PC 20 to edit the data input screen to generate and save a data storage file relating to the editing.

  First, the data of the spec file 151 is read by the editor unit 11A of the server 10, and the page information of the created application form list is created as a spec file and transmitted to the PC 20 (step S11). Further, on the PC 20, an application form list screen is displayed on the display unit 24.

  In the PC 20, whether or not an application form (spec file) is selected from the list and operation information for selecting the application form are input by the user via the input unit 22 and transmitted to the server 10. When editing an existing application, the application name to be edited from the application list is selected and input by the user via the input unit 22 and included in the operation information. Then, the editor unit 11A determines whether or not to select an application form (spec file) from the list based on the received operation information (step S12).

  When the application form is not selected from the list (step S12; NO), the application form name is input by the user via the input unit 22 in the PC 20. Then, the input application name is received from the PC 20 by the editor unit 11A, and page information of a new editor screen is generated and transmitted to the PC 20 (step S13). When selecting the application form from the list (step S12; YES), the editor unit 11A reads the specification file of the selected application form name in the operation information from the specification file 151 and displays the data entry editor screen together with the set item objects. Page information is generated and transmitted to the PC 20 (step S14).

  Then, the PC 20 receives the page information of the editor screen for the new application form name in step S13 or the spec file editor screen in step S14, and the editor screen for the page information is displayed on the display unit 24. The editing operation information is selected and input by the user via the input unit 22, and the operation information is transmitted to the server 10. Then, the editor unit 11A receives the editing operation information from the PC 20 (step S15). When the PC 20 inputs editing completion / editing cancellation, the operation information includes editing completion.

  Then, the editor unit 11A determines whether or not editing is completed based on the received operation information (step S16). If the editing is to be stopped (step S16; NO), the editing process (outline) ends. When editing is completed (step S16; YES), a spec file is generated based on the operation information received in step S15 and stored in the spec file 151, and a data storage file is generated from the generated spec file and data is stored. It is stored in the storage file 152 (step S17), and the editing process (outline) ends.

  Further, the data input process (outline) shown in FIG. 9 is executed by the data input unit 11B. The data input process (outline) is a process for causing the PC 20 to input data based on the data input screen generated by the editing process and saving the input data in the data storage file 152.

  First, the data of the specification file 151 is read by the data input unit 11B of the server 10, and the page information of the generated application form list is created as a specification file and transmitted to the PC 20 (step S21). On the PC 20, an application list screen is displayed on the display unit 24.

  In the PC 20, the name of the application form to be edited from the application list is selected and input by the user via the input unit 22 and is transmitted to the PC 20 as operation information. Then, in the data input unit 11B, operation information for selecting an application form is received from the PC 20 (step S22).

  Then, the data input management file 155 is read by the data input unit 11B, and it is determined whether or not there is a registered record corresponding to the application form name selected in step S22 (step S23). If there is a registered record (step S23; YES), the data input process (outline) is terminated. If there is no registered record (step S23; NO), the data input unit 11B reads the spec file with the application form name selected in step S22 from the spec file 151 and transmits the page information of the spec file to the PC 20. (Step S24).

  In the PC 20, a data input screen of the spec file is displayed on the display unit 24, data is input by the user via the input unit 22, and operation information of the input data is transmitted to the server 10. The data input unit 11B receives the operation information of the input data of the application form from the PC 20, and reads the data storage file from the data storage file 152 (step S25).

  Then, based on user operation information or the like, it is determined whether or not the input data is stored in the data storage file and data registration is performed (step S26). When data registration is not performed (step S26; NO), the data input process (outline) is terminated. When data registration is performed (step S26; YES), the input data is stored in the data storage file, and the data storage file is stored in the data storage file 152 (step S27).

  Then, the registered record of the input data updated in step S27 is added and stored in the data registration management file 155 (step S28), and the data input process (outline) is terminated.

  Next, browser processing executed on the PC 20 will be described with reference to FIG. FIG. 10 shows a flow of browser processing executed on the PC 20. The browser process is a process of receiving page information from the server 10 and displaying it on the display unit 24 and transmitting operation information input from the user via the input unit 22 to the server 10 based on the displayed screen.

  In advance, in the PC 20, triggered by the input of a browser activation instruction from the user via the input unit 22 as a trigger, the CPU 21 cooperates with the browser program read from the storage unit 25 and expanded in the RAM 23. As a result, browser processing is executed.

  First, the browser is activated, the address of the server 10 is input via the input unit 22, and is transmitted to the server 10 (step S31). Then, the page information is received from the server 10, and the page information is displayed in the browser of the display unit 24 (step S32).

  Then, an operation input from the user via the input unit 22 is accepted (step S33). The operation input is various operation inputs, and includes an edit operation input of a data input screen and data input of an application form. Then, it is determined whether or not the operation information is transmitted to the server 10 by moving the screen page, inputting an operation information transmission instruction, or the like (step S34).

  When transmitting the operation information to the server 10 (step S34; YES), the operation information is transmitted to the server 10 (step S35), and the process proceeds to step S32. When the operation information is not transmitted to the server 10 (step S34; YES), it is determined whether or not to end the browser processing based on whether or not an end instruction is input from the user (step S36). If the browser process is not terminated (step S36; NO), the process proceeds to step S33. When the browser process is terminated (step S36; YES), the browser process is terminated.

  Next, the relationship between the editor screen of the data input screen and the data input screen will be described with reference to FIGS. FIG. 11 shows an editor screen 201 of the initial screen. FIG. 12 shows an editor screen 202 in which item objects are set. FIG. 13 shows an item setting screen 221. FIG. 14 shows a data input screen 301. FIG. 15 shows a layer structure of item objects and grid objects. FIG. 16 shows the relationship between the editor screen 201 and the data input screen 301. FIG. 17 shows the relationship between the editor screen 201 and the data storage file 152. FIG. 18 shows the relationship between the definition of items on the editor screen 201 and the data input screen 301. FIG. 19 shows the relationship between the data storage file 152 and the master file 153 and the data input screen 301.

  As shown in FIG. 11, the editor screen 201 as an initial screen includes a save button 211, a completion button 212, a close button 213, an application form name 214, and a grid object 215. The completion button 212 is a button for accepting an instruction to save the editor screen 201 as a spec file. The close button 213 is a button for accepting an instruction to close the editor screen 201. The grid object 215 is a base object for arranging item objects, and has, for example, a lattice pattern to facilitate layout.

  As shown in FIG. 12, when an item object 216 is arranged on the editor screen 201, an editor screen 202 is displayed. The item objects 216 are arranged on the grid object 215 of the editor screen 202, and are displayed so as to constitute one image by overlapping each other. The grid object 215 and the item object 216 are independent, and each recognizes the pointer position input by the input unit 22. Further, if the coordinate position of an object is changed, the position of only the item object is changed without affecting other objects. When the form property of the object is changed, the form is changed without changing the coordinates.

  The item object 216 can set the item type and the like on the item setting screen 221 shown in FIG. On the item setting screen 221, setting values of item information such as an item label, item name, item type, number of digits, form (text box, etc.), position in the grid object 215, and the like can be set.

  As shown in FIG. 14, the data input screen 301 includes a header part 310, a data input area 320, and a footer part 360. The data input area 320 includes a data selection area 330, a data editing area 340, and an operation button area 350. The header part 310 has an application form name 311.

  The data selection area 330 includes an add button 331, a correction button 332, a delete button 333, a cancel button 334, and a data selection table 335. The add button 331 receives a data addition instruction. The correction button 332 receives a data correction instruction. The delete button 333 receives a data deletion instruction. The cancel button 334 accepts a data state change cancel instruction. The data selection table 335 accepts an instruction for selecting a record data, and displays the selection, status, and data contents of the record.

  The data editing area 340 includes item objects 341 for data input that are arranged and set on the editor screen 202. The operation button area 350 includes a return button 351, a clear button 342, and an OK button 343. A return button 351 accepts an instruction to cancel data input in the data editing area 340 and return to the previous page. The clear button 352 receives an instruction to clear data being input. The OK button 353 accepts an instruction to clear data being input.

  As shown in FIG. 15, as a layer structure of item objects and grid objects, for example, there is an editor screen 201 in which a name object 216 a and an age object 216 b are arranged and set on the grid object 215 as the item object 216. Corresponding to the editor screen 201, a data editing area 340 is generated. As illustrated in FIG. 16, the application form name 214 on the editor screen 201 and the grid object 215 on which the item objects are arranged correspond to the application form name 311 and the data editing area 340 on the data input screen 301.

  As shown in FIG. 17, on the editor screen 201, a data storage file is generated based on each item object set on the item setting screen 221 and stored in the data storage file 152. Further, as shown in FIG. 18, the item object 341 in the data editing area 340 is set in detail by the items set on the item setting screen 221 on the editor screen 201 and set on the detailed setting screen 231 of the form. In FIG. 18, when it is set that the sex item can be selected by men and women in the form of a drop-down list, a man or a woman can be selected and input as data in the drop-down list in the data editing area 340.

  As shown in FIG. 19, the data type to be input is set by the data storage file 152, the actual data of the set data type is read from the master file 153, the data is merged, and the data selection area 330. The data selection table 335 is generated. The data set in the data selection table 335 is stored in the data storage file 152.

  Next, details of the operation of the server 10 will be described with reference to FIG. FIG. 20 shows a flow of editing processing (details) executed in the server 10.

  The editing process (details) shown in FIG. 20 is executed by the editor unit 11A. The editing process (details) is a process in which the data input screen is edited by the user on the PC 20, and a data storage file relating to the editing is generated and saved.

  First, in the server 10, page information of an application form name setting screen 200 (described later) is generated and transmitted to the PC 20. In the PC 20, an application form name setting screen 200 based on the received page information is displayed on the display unit 24, and whether or not a new specification file is instructed from the user via the input unit 22, and specification of a specification file when not creating a new specification file Operation information with a name is input and transmitted to the server 10. Then, the editor unit 11A determines whether or not to create a new spec file based on the operation information indicating whether or not to instruct a new creation (step S41).

  When creating a new file (step S41; YES), the editor unit 11A reads the spec file having the specified name of the operation information from the spec file 151 (step S42). Then, an item object is generated from the read spec file by the editor unit 11A (step S43).

  If not newly created (step S41; NO), in the PC 20, the operation information of the screen name (new application form name) of the data input screen is input from the user via the input unit 22 and transmitted to the server 10. Then, the operation information of the screen name is input and received from the PC 20 by the editor unit 11A (step S44).

  Then, the editor unit 11A generates the page information of the editor screen 201 of the data input screen in which the specification file including the item object or the screen name is set and transmits it to the PC 20 (step S45). In the PC 20, an editor screen 201 based on the received page information is displayed on the display unit 24. Thereafter, on the PC 20, the user clicks the save button 211, the complete button 212, the close button 213 on the editor screen 201 via the input unit 22, the grid object 215, the item object 216, the click point coordinates of the marker object 217, and the items. Operation information including deletion of the object 216 is input and transmitted to the server 10 as needed.

  Then, the editor unit 11A determines whether or not the close button 213 is pressed based on the operation information (step S46). If the close button 213 is pressed (step S46; YES), the editing process (details) is terminated.

  If the close button 213 is not pressed (step S46; NO), it is determined whether or not the save button 211 is pressed based on the operation information (step S47). When the save button 211 is pressed (step S47; YES), the information (type, arrangement, etc.) of the item object being set is read from the item object property file 156 and the item object management file 157, and is generated as a spec file. The file 151 is stored (step S48), and the editing process (details) is terminated.

  If the save button 211 has not been pressed (step S47; NO), it is determined whether the completion button 212 has been pressed based on the operation information (step S49). When the complete button 212 is pressed (step S49; YES), the information (type, arrangement, etc.) of the item object being set is read from the item object property file 156 and the item object management file 157, and is generated as a spec file. It is stored in the file 151 (step S50). Then, a data storage file is created from the spec file generated in step S50 and stored in the data storage file 152 (step S51), and the editing process (details) ends.

  If the completion button 212 has not been pressed (step S49; NO), it is determined whether or not the grid object 215 has been clicked based on the operation information (step S52). When the grid object 215 is clicked (step S52; YES), the click point coordinates of the grid object 215 included in the operation information are acquired (step S53). Then, page information of the editor screen 201 in which the marker object 217 is arranged at the click point coordinates acquired in step S53 is generated and transmitted to the PC 20 (step S54), and the process proceeds to step S46. In the PC 20, an editor screen 201 having a marker object 217 is displayed on the display unit 24.

  If the grid object 215 has not been clicked (step S52; NO), it is determined whether or not the marker object 217 has been clicked based on the operation information (step S55). When the marker object 217 is clicked (step S55; YES), the setting value of the item information included in the operation information is acquired (step S56). For example, in the server 10, page information of the editor screen 201 including the item setting screen 221 and the detailed setting screen 231 is generated and transmitted to the PC 20, and items displayed on the display unit 24 based on the received page information in the PC 20. Operation information such as item setting values and item object coordinates set by the user via the input unit 22 based on the setting screen 221 and the detailed setting screen 231 is transmitted to the server 10. In the server 10, information such as the setting value of the item included in the operation information is acquired, and information such as the setting value of the item is stored in the item object property file 156 and the item object management file 157.

  Then, page information of the editor screen in which the item object of the information acquired in step S56 is arranged at the position of the marker object 217 is generated and transmitted to the PC 20 (step S57), and the process proceeds to step S46. On the PC 20, an editor screen 201 having an item object 216 is displayed.

  If the marker object 217 has not been clicked (step S55; NO), it is determined whether or not the item object 216 has been clicked based on the operation information (step S58). When the item object 216 has not been clicked (step S58; NO), the process proceeds to step S46. When the item object 216 is clicked (step S58; YES), it is determined whether or not to delete the item object being clicked based on the operation information (step S59).

  When the item object is not deleted (step S59; NO), page information of the editor screen 201 including the item setting screen 221 and the detailed setting screen 231 is generated and transmitted to the PC 20 in the server 10 as modification of the item object. The item setting screen 221 displayed on the display unit 24 based on the received page information, the setting value of the item set by the user via the input unit 22 based on the detailed setting screen 231, the coordinate information of the item object, etc. Is transmitted to the server 10. Then, the editor unit 11A acquires information such as the setting value of the item being clicked from the operation information, and stores (updates) it in the item object property file 156 and the item object management file 157 (step S60).

  Then, the item information acquired in step S60 is reflected in the item object 216 being clicked (step S61), and the process proceeds to step S46. Then, the setting value of the item information acquired in step S60 is reflected in the item object 216 being clicked, the reflected editor screen page information is generated and transmitted to the PC 20 (step S61), and the process proceeds to step S46. On the PC 20, an editor screen 201 in which the item object 216 is corrected is displayed.

  When deleting an item object (step S59; YES), the item object property file 156 and the item object management file 157 are updated with the deletion information of the item object 216 being clicked, and the editor object screen in which the item object 216 is deleted is displayed. The page information is generated and transmitted to the PC 20 (step S62), and the process proceeds to step S46. On the PC 20, an editor screen from which the item object 216 has been deleted is displayed.

  Next, a specific example of screen transition of the editing process (details) will be described with reference to FIGS. FIG. 21A shows an application form name setting screen 200. FIG. 21B shows an editor screen 201 on which the marker object 217 is arranged. FIG. 21C shows an editor screen 201 that displays the item setting screen 221. FIG. 22A shows an editor screen 201 on which a name object 216a is arranged. FIG. 22B shows an editor screen 201 on which a name object 216a and a marker object 217 are arranged. FIG. 22C shows an editor screen 201 displaying a name object 216a and an age object 216b.

  As shown in FIG. 21A, an application form name setting screen 200 is displayed on the display unit 24 of the PC 20. The application form name setting screen 200 has an application form name drop-down list 251, a new button 252, and an OK button 253. The application form name drop-down list 251 accepts selection input of an existing application form name via the input unit 22 by the user in response to step S42. The new button 252 accepts an input to the effect that a new application form is created via the input unit 22 by the user corresponding to step S44. At that time, a new application form name is arbitrarily entered in the application form name drop-down list 251.

  As shown in FIG. 21B, when the editor screen 201 of the initial screen is clicked on a point on the grid object 215 corresponding to step S53, the marker object 217 is positioned at that position corresponding to step S54. Is displayed.

  As shown in FIG. 21C, when the marker object 217 is (double) clicked on the editor screen 201 on which the marker object 217 is displayed, corresponding to step S55, item setting is performed corresponding to step S56. A screen 221 is displayed, and the setting value of the item information is input. Here, it is assumed that the setting value of the name object is input.

  As shown in FIG. 22A, in the editor screen 201 on which the marker object 217 is displayed, a name object 216a is displayed at the position of the marker object 217 corresponding to step S57.

  As shown in FIG. 22B, in the editor screen 201 on which the name object 216a is displayed, when a point on the side of the name object 216a on the grid object 215 is clicked corresponding to step S53, the process proceeds to step S54. Correspondingly, a marker object 217 is displayed at that position. When the marker object 217 is (double) clicked corresponding to step S55, the item setting screen 221 is displayed corresponding to step S56, the setting value of the item information is input, for example, setting of the age object Assume that a value has been entered.

  As shown in FIG. 22C, in the editor screen 201 on which the marker object 217 is displayed, the age object 216b is displayed at the position of the marker object 217 corresponding to step S57.

  FIG. 23A shows an editor screen 203 on which a plurality of item objects are arranged. FIG. 23B shows an editor screen 203 displaying the item setting screen 221. FIG. 23C shows an editor screen 203 in which the age object 216b is corrected and the name object 216a is deleted.

  As shown in FIG. 23A, an editor screen 203 on which a name object 216a, an age object 216b, and a contact address object 216c are arranged is set. Here, as shown in FIG. 23B, the age object 216b is clicked corresponding to step S58, and the item setting screen 221 of the age object 216b is displayed corresponding to step S60.

  The item label and item name on the item setting screen 221 are changed from age to age. Then, as shown in FIG. 23C, an editor screen 203 on which the age object 216d is arranged is displayed.

  Further, when the name object 216a is clicked corresponding to step S58 and the deletion is input corresponding to step S59, as shown in FIG. An editor screen 203 on which the address object 216c and the age object 216d are arranged is displayed.

  FIG. 24A shows a radio button detail setting screen 232. FIG. 24B shows a detailed setting screen 233 for the drop-down list. FIG. 24C shows a detailed setting screen 234 for control.

  The detailed setting screen of the item setting screen 221 includes a radio button detailed setting screen 232 shown in FIG. 24A, a drop-down list detailed setting screen 233 shown in FIG. 24B, and FIG. 24C. There is a detailed setting screen 234 of the control shown. Control is a general term for GUI (Graphical User Interface), and is, for example, a GUI of a calendar that has been completed in advance.

  Next, with reference to FIGS. 25 and 26, data input processing (details) executed in the data input unit 11B of the server 10 will be described. FIG. 25 shows the flow of data input processing (details). FIG. 26 shows a flow of data input area processing of data input processing (details).

  First, in the PC 20, operation information of a spec file to be read for use in data input is designated by the user via the input unit 22 and transmitted to the server 10. Then, the operation information of the specified spec file is received from the PC 20 by the data input unit 11B (step S71). Then, the data registered management file 155 is read, and it is determined whether or not there is a registered record corresponding to the spec file of the operation information (step S72). If there is a registered record (step S72; YES), data input has been completed for the specified spec file, and the data input process (details) is terminated.

  If there is no registered record (step S72; NO), the spec file of operation information is read from the spec file 151 (step S73). Then, the specified spec file is referred to, and it is determined whether or not there is data of the master file 153 corresponding to the spec file (step S74). If there is data of the master file 153 (step S74; YES), the corresponding master file is read from the master file 153 (step S75).

  Then, the designated spec file is referred to, and it is determined whether or not there is data in the data storage file 152 corresponding to the spec file (step S76). If there is no data in the master file 153 (step S74; NO), the process proceeds to step S76. If there is data in the data storage file 152 (step S76; YES), the corresponding data storage file is read from the data storage file 152 (step S77).

  Then, the master file data record read in step S75 and the data storage file data record read in step S77 are merged (step S78). If there is no data in the data storage file 152 (step S76; NO), the process proceeds to step S78.

  Then, the page information of the data input screen 301 having the data selection table 335 of the records of the master file and the data storage file merged in step S78 is generated and transmitted to the PC 20 (step S79). In the PC 20, page information on the data input screen 301 is received and displayed on the display unit 24 as the data input screen 301.

  Then, the data input area process is executed by the data input unit 11B (step S80). Here, the data input area processing will be described in detail with reference to FIG. Thereafter, the data input screen 301 is displayed on the PC 20, and the user selects the data selection table 335 on the data input screen 301 via the input unit 22, the add button 331, the correction button 332, the delete button 333, and the cancel button 334. , A return button 351, a clear button 352, an OK button 353, a clear button 361, a save button 362, a registration button 363, a press input of the close button 364, and data input of the item object 341 are performed, and the operation information is appropriately transmitted to the server 10. Sent. In the server 10, each process is executed based on the operation information received from the PC 20.

  First, the data input unit 11B determines whether or not a record in the data selection table 335 on the data input screen has been selected based on the operation information (step S89). When a record in the data selection table 335 is selected (step S89; YES), it is determined whether or not the add button 331 has been pressed based on the operation information (step S90). When the add button 331 is pressed (step S90; YES), the page information of the data input screen 301 in which the data editing area 340 is cleared is transmitted to the PC 20 (step S91). In the PC 20, a data input screen 301 in which the data editing area 340 is cleared based on the received page information is displayed on the display unit 24.

  Then, data input to the item object in the data editing area 340 is awaited (step S92). Then, based on the operation information, it is determined whether or not the clear button 352 is pressed (step S93). When the clear button 352 is pressed (step S93; YES), the process proceeds to step S91.

  If the clear button 352 has not been pressed (step S93; NO), it is determined whether or not the return button 351 has been pressed based on the operation information (step S94). If the return button 351 has not been pressed (step S94; NO), it is determined whether or not the OK button 353 has been pressed based on the operation information (step S95). If the OK button 353 has not been pressed (step S95; NO), the process proceeds to step S92.

  When the OK button 353 is pressed (step S95; YES), the record of the edited content edited in step S92 is added to the bottom row of the data selection table 335 based on the operation information (step S96). Then, the state of the record to which the edited content of the data selection table 335 is added is set to “added”, and page information of the data input screen 301 is generated and transmitted to the PC 20 (step S97). In the PC 20, a data input screen 301 to which editing content is added based on the received page information is displayed on the display unit 24.

  Then, page information of the data input screen 301 in which the data editing area 340 is cleared is generated and transmitted to the PC 20 (step S98), and the process proceeds to step S89. In the PC 20, a data input screen 301 in which the data editing area 340 is cleared based on the received page information is displayed on the display unit 24. When the return button 351 is pressed (step S94; YES), the process proceeds to step S98.

  If the add button 331 has not been pressed (step S90; NO), it is determined whether or not the correction button 332 has been pressed based on the operation information (step S99). When the correction button 332 is pressed (step S99; YES), page information of the data input screen 301 in which the designated record of the data selection table 335 is reflected in the data editing area 340 based on the operation information is generated and transmitted to the PC 20. (Step S100). In the PC 20, the data input screen 301 in which the specified record of the data selection table 335 is reflected in the data editing area 340 is displayed on the display unit 24.

  Then, steps S101 to S104 are executed. Steps S101 to S104 are the same as steps S92 to S95. In step S 101, correction data is input in the data editing area 340. When the OK button 353 is pressed (step S104; YES), the specified record in the data selection table 335 is replaced with the edited content (corrected content) based on the operation information (step S105). Then, the state of the edited record in the data selection table 335 is “corrected”, the page information of the data input screen 301 is generated and transmitted to the PC 20 (step S106), and the process proceeds to step S98. In the PC 20, a data input screen 301 in which editing contents are corrected based on the received page information is displayed on the display unit 24.

  If the correction button 332 has not been pressed (step S99; NO), it is determined whether or not the delete button 333 has been pressed based on the operation information (step S107). When the delete button 333 is pressed (step S107; YES), page information of the data input screen 301 in which the specified record of the data selection table 335 is reflected in the data editing area 340 based on the operation information is generated and transmitted to the PC 20. (Step S108). In the PC 20, the data input screen 301 in which the specified record of the data selection table 335 is reflected in the data editing area 340 based on the received page information is displayed on the display unit 24.

  Then, instruction information for protecting the data editing area 340 of the data input screen 301 from being edited is generated and transmitted to the PC 20 (step S110). In the PC 20, a data input screen 301 in which the data editing area 340 is protected based on the received page information is displayed on the display unit 24. Then, steps S110 and S111 are executed. Steps S110 and S111 are the same as steps S94 and S95.

  When the OK button 353 is pressed (step S111; YES), the state of the designated record in the data selection table 335 is set to “deleted” based on the operation information, and the page information of the data input screen 301 is generated and stored in the PC 20. It is transmitted (step S112), and the process proceeds to step S98. In the PC 20, a data input screen 301 from which editing content has been deleted based on the received page information is displayed on the display unit 24.

  If the delete button 333 has not been pressed (step S107; NO), it is determined whether or not the cancel button 334 has been pressed based on the operation information (step S113). If the cancel button 334 has not been pressed (step S113; NO), the process proceeds to step S89. When the cancel button 334 is pressed (step S113; YES), steps S114 to S117 are executed. Steps S114 to S117 are the same as steps S108 to S111.

  When the OK button 353 is pressed (step S117; YES), the data of the designated record in the data selection table 335 is read from the master file 153 based on the operation information (step S118). Then, the data of the designated record on the data input screen 301 is replaced with the data of the record read in step S118, and page information in which the editing of the record is canceled is generated and transmitted to the PC 20 (step S119). The process proceeds to S98. In the PC 20, a data input screen 301 in which the record editing is canceled based on the received page information is displayed on the display unit 24.

  If no record is selected in the data selection table 335 (step S89; NO), the process returns to FIG. 25, and it is determined whether or not the save button 362 is pressed based on the operation information (step S81). When the save button 362 is pressed (step S81; YES), the corresponding data storage file is updated and stored in the data storage file 152 based on the operation information input as data (step S82). Then, page information in which the data input screen is deleted is generated and transmitted to the PC 20 (step S83), and the data input process (details) ends. In the PC 20, the data input screen 301 is erased and displayed on the display unit 24 based on the received page information.

  If the save button 362 has not been pressed (step S81; NO), it is determined whether or not the registration button 363 has been pressed based on the operation information (step S84). When the registration button 363 is pressed (step S84; YES), the corresponding data storage file is updated and stored in the data storage file 152 based on the operation information input as data (step S85). Then, a registered record is added to the data registered management file 155 corresponding to the name of the application form being input (step S88), and the process proceeds to step S83.

  If the registration button 363 has not been pressed (step S84; NO), it is determined whether or not the close button 364 has been pressed based on the operation information (step S87). When the close button 364 is pressed (step S87; YES), the process proceeds to step S83. If the close button 364 has not been pressed (step S87; NO), it is determined whether or not the clear button 361 has been pressed based on the operation information (step S88). If the clear button 361 has not been pressed (step S88; NO), the process proceeds to step S81. When the clear button 361 is pressed (step S88; YES), the process proceeds to step S74.

  Next, a specific example of screen transition in the data input process (details) will be described with reference to FIGS. FIG. 27A shows a data input screen 301 before data correction. FIG. 27B shows a data input screen 301 after data correction. FIG. 28A shows a data input screen 301 before data deletion. FIG. 28B shows a data input screen 301 after data deletion. FIG. 29A shows a data input screen 301 before data addition. FIG. 29B shows a data input screen 301 after data addition. FIG. 30A shows a data input screen 301 before canceling data deletion. FIG. 30B shows a data input screen 301 after canceling data deletion. FIG. 31 shows a data input screen 301 after data registration. FIG. 32A shows a data input screen 301 reflecting the master file. FIG. 32B shows a data input screen 301 reflecting the data storage file.

  Here, a case is considered in which the data of a family member change due to a family change notification is input as an application. In the data input screen, for example, records of a plurality of members constituting one family are displayed in the data selection table 335, and data input for changing all members is performed. First, data correction in the data input process will be described. As shown in FIG. 27A, it is assumed that a data input screen 301 having a data selection table 335 including records 3351 to 353 is displayed on the display unit 24 of the PC 20. First, in response to step S89, a record 3351 is selected and displayed. Then, the correction button 332 is pressed corresponding to step S99, and the data of the record 3351 being selected is displayed in the data editing area 340 corresponding to step S100. Then, the gender of the data editing area 340 is edited from “m” to “female” corresponding to step S101, and the OK button 353 is pressed corresponding to step S104.

  Then, as shown in FIG. 27 (b), corresponding to step S106, the state of the record 3351 is “corrected” and the data input screen 301 having the data selection table 335 including the record 3351a having the sex “female”. Transition to. Corresponding to step S98, the data editing area 340 is cleared.

  Next, data deletion will be described. Consider a data input screen 301 having a data selection table 335 including records 3351a to 3353 as shown in FIG. First, the record 3352 is selected and displayed corresponding to step S89. Then, the delete button 333 is pressed corresponding to step S107, and the data of the record 3352 being selected is displayed in the data editing area 340 corresponding to step S108. Then, in response to step S111, the OK button 353 is pressed.

  Then, as shown in FIG. 28B, in response to step S112, the screen shifts to a data input screen 301 having a data selection table 335 including a record 3352a in which the state of the record 3352 is “deleted”. Corresponding to step S98, the data editing area 340 is cleared.

  Next, data addition will be described. Consider a data input screen 301 having a data selection table 335 including records 3351a-3353 as shown in FIG. First, the add button 331 is pressed corresponding to step S90, and the data of the record to be added to the data editing area 340 is input corresponding to step S92. In response to step S95, the OK button 353 is pressed.

  Then, as shown in FIG. 29 (b), a transition is made to a data input screen 301 having a data selection table 335 including the added record 3354 whose state is “added”, corresponding to steps S 96 and S 97. Corresponding to step S98, the data editing area 340 is cleared.

  Next, cancellation of data deletion will be described. Consider a data input screen 301 having a data selection table 335 including records 3351a-3354 as shown in FIG. First, in response to step S89, the record 3352a is selected and displayed. Then, the cancel button 334 is pressed corresponding to step S113, and the data of the record to be canceled is input to the data editing area 340 corresponding to step S114. In response to step S117, the OK button 353 is pressed.

  Then, as shown in FIG. 30 (b), in response to steps S 118 and S 119, the state transitions to a data input screen 301 having a blank state and a data selection table 335 including a record 3352 before deletion. Corresponding to step S98, the data editing area 340 is cleared.

  Next, data registration will be described. Consider a data input screen 301 having a data selection table 335 including records 3351a, 3352a, 3353, 3354 as shown in FIG. Corresponding to step S84, the registration button 363 is pressed, and the data storage file in which the records 3351a, 3352a, 3354 are updated is stored in the data storage file 152 in correspondence with step S85. Record 3353 is not updated.

  Next, generation of the data input screen 301 of the initial screen will be described. As shown in FIG. 32A, first, corresponding to step S75, a master file of records 3351, 3352, 3353 is read from the master file 153, and data selection including records 3351, 3352, 3353 is read from the master file. A data input screen 301 having a table 335 is generated. Corresponding to step S77, the data storage file including the records 3351a, 3352a, and 3354 is read from the data storage file 152. Then, as shown in FIG. 32 (b), the data selection table including the records 3351a, 3352a, 3353, and 3354 is reflected in the read master file, corresponding to steps S78 and S79. A data input screen 301 having 335 is displayed.

  As described above, according to the present embodiment, the server 10 generates page information of the editor screen for the browser and transmits it to the PC 20, displays the editor screen as the browser screen of the display unit 24 of the PC 20, and the user inputs the data input screen. The item 10 layout setting operation is performed, and the server 10 generates / updates the spec file 151 and the data storage file 152 according to the operation information. Further, the server 10 generates page information of the data input screen for the browser based on the spec file 151 and transmits it to the PC 20, and displays the data input screen as the browser screen of the display unit 24 of the PC 20, so that the user can An input operation is performed, and input data is stored in the data storage file 152 in accordance with the data input operation.

  Therefore, since only the browser is used without using a complicated integrated development environment or special tools, the data input screen can be easily and freely laid out and data can be input by the browser. In particular, since a mechanism for recognizing input coordinates on a browser is realized using only HTML, Javascript, and CSS without using special plug-ins or add-on software, the browser can be used as a data input screen editor.

  Further, the data input screen has a data selection area 330, a data editing area 340, and an operation button area 350, and the data changed by the operation of the data editing area 340 and the operation button area 350 and its state are displayed in the data selection area 330. . For this reason, the input data can be automatically checked by defining the range that the data editing area 340 can take. Further, by referring to the data selection area 330, the user can check the data being input and the state of the data at any time without the user programming an algorithm necessary for the data input process. Therefore, data input can be performed more accurately.

  Further, the server 10 generates page information of the editor screen and the data input screen and transmits it to the PC 20, and the PC 20 displays the editor screen and the data input screen as a browser screen and performs operation input. For this reason, it is possible to freely set the location where the user performs the data input screen editing operation and the data input operation. Moreover, since the item name on the data input screen is the same as the item name in the database, it is easy to divert the data.

  The description in the above embodiment is an example of the data input management device, the data input management system, and the program according to the present invention, and the present invention is not limited to this.

  In the above embodiment, the server 10 as the data input management device and the PC 20 as the terminal device are provided separately, but the present invention is not limited to this. For example, the server 10 and the PC 20 are integrated to display an editor screen and a data input screen as a browser screen on the display unit 14 as a display unit of the server 10, and a user operation input is performed via the input unit 12 as an operation unit. It is good also as a structure which receives. According to this configuration, the configuration of the apparatus can be simplified.

  In the above embodiment, the data input screen is divided into the data selection area, the data editing area, and the operation button area. However, the present invention is not limited to this. For example, if there is no need to change existing data and only new data is input, the data input screen may not have a data selection area, but may have a data editing area and an operation button area. Good.

  In the above embodiment, the values that can be taken by the input data in the item object are set and checked using a drop-down list, a radio button, a check box, a control, and the like. However, the present invention is not limited to this. For example, the possible values of the item object may be displayed separately as a separate table, and the user may check the input data by referring to the table.

  In the above embodiment, the layout of the data editing area on the data input screen is based only on the items set by the editing process, but is not limited to this. For example, fixed item information may be prepared in advance for cooperation with other systems, and the fixed item information may be combined with the item set by the editing process and laid out.

  Of course, the detailed configuration and detailed operation of each component of the data input system 100 in the above embodiment can be changed as appropriate without departing from the spirit of the present invention.

It is a block diagram which shows the structure of the data input system 100 of embodiment which concerns on this invention. 2 is a block diagram showing an internal configuration of a server 10. FIG. It is a block diagram which shows the internal structure of PC20. 2 is a block diagram showing a functional configuration of a data input system 100. FIG. It is a figure which shows the internal structure of the item object property file. It is a figure which shows the internal structure of the item object management file 157. FIG. It is a figure which shows the data structure of the specification file 151. FIG. (A) is a figure which shows an example of the specification file 151. FIG. (B) is a figure which shows the internal structure of the data storage file 152 produced | generated from the specification file 151 of (a). 4 is a flowchart showing an editing process (outline) and a data input process (outline) executed in the server 10. It is a flowchart which shows the browser process performed in PC20. It is a figure which shows the editor screen 201 of an initial screen. It is a figure which shows the editor screen 202 which set the item object. It is a figure which shows the item setting screen. It is a figure which shows the data input screen. It is a figure which shows the layer structure of an item object and a grid object. It is a figure which shows the relationship between the editor screen 201 and the data input screen 301. FIG. FIG. 6 is a diagram showing a relationship between an editor screen 201 and a data storage file 152. FIG. 5 is a diagram illustrating a relationship between definition of items on an editor screen 201 and a data input screen 301. It is a figure which shows the relationship between the data storage file 152 and the master file 153, and the data input screen 301. FIG. 4 is a flowchart showing editing processing (details) executed in the server 10. (A) is a figure which shows the application name setting screen 200. FIG. (B) is a diagram showing an editor screen 201 on which marker objects 217 are arranged. (C) is a diagram showing an editor screen 201 displaying the item setting screen 221. FIG. (A) is a figure which shows the editor screen 201 which has arrange | positioned the name object 216a. (B) is a diagram showing an editor screen 201 on which a name object 216a and a marker object 217 are arranged. (C) is a figure which shows the editor screen 201 which displayed the name object 216a and the age object 216b. (A) is a figure which shows the editor screen 203 which has arrange | positioned several item object. (B) is a diagram showing an editor screen 203 displaying an item setting screen 221. FIG. (C) is a figure which shows the editor screen 203 which corrected the age object 216b and deleted the name object 216a. (A) is a figure which shows the detailed setting screen 232 of a radio button. (B) is a figure which shows the detailed setting screen 233 of a drop-down list. (C) is a diagram showing a detailed setting screen 234 of the control. It is a flowchart which shows a data input process (details). It is a flowchart which shows the data input area process of a data input process (detail). (A) is a figure which shows the data input screen 301 before data correction. (B) is a figure which shows the data input screen 301 after data correction. (A) is a figure which shows the data input screen 301 before data deletion. (B) is a figure which shows the data input screen 301 after data deletion. (A) is a figure which shows the data input screen 301 before data addition. (B) is a figure which shows the data input screen 301 after data addition. (A) is a figure which shows the data input screen 301 before cancellation of data deletion. (B) is a figure which shows the data input screen 301 after cancellation of data deletion. It is a figure which shows the data input screen 301 after data registration. (A) is a figure which shows the data input screen 301 reflecting the master file. (B) is a figure which shows the data input screen 301 reflecting the data storage file.

Explanation of symbols

100 data input system 10 server 11 CPU
12 Input unit 13 RAM
14 Display unit 15 Storage unit 151 Spec file 152 Data storage file 153 Master file 154 Data input reference file 155 Data registered management file 156 Item object property file 157 Item object management file 16 Communication unit 17 Bus 11A Editor unit 111 Editor processing unit 112 data storage file generation unit 113 screen generation unit 11B data input unit 114 screen provision unit 115 data storage unit 116 document / help generation unit 20 PC
21 CPU
22 Input unit 23 RAM
24 display unit 25 storage unit 26 communication unit 27 bus N communication network

Claims (5)

Storage means;
Generates and displays the page information of the editor screen for browsers that can set the layout of items on the data input screen, and stores the data on the data input screen from the setting data of the layout of the items input via the editor screen An editor control unit that generates a spec file, a data storage file that stores data input via the data input screen, and stores the generated data file in the storage unit;
Based on the stored specification file and data storage file, page information of a data input screen for a browser is generated and displayed, and input data input via the data input screen is stored in the data storage file. And a data input control device. The data input screen includes a data selection area indicating that the data to be changed can be selected and indicating the change state, a data editing area indicating the item for which the layout is set, and operation button areas indicating various operation buttons. Have
The data input control means reflects input data input through the data editing area and a change state thereof in the data selection area in response to an operation button input in the operation button area. The data input management device according to 1. A display means and an operation means,
The editor control means displays the editor screen on the display means based on the page information of the editor screen, and from the setting data of the layout of items input via the operation means according to the editor screen, Generating the spec file and the data storage file;
The data input control means displays page information of the data input screen on the display means, and stores the input data input via the operation means in the data storage file according to the data input screen. The data input management device according to claim 1 or 2, characterized by the above. The data input management device according to claim 1 or 2,
A terminal device comprising display means, operation means, and first communication means for communicating with the data input management device,
The data input management device includes:
A second communication means for communicating with the terminal device;
The editor control means transmits page information of the editor screen to the terminal device via the second communication means, and sets layout data of items input via the editor screen as the second communication. Receiving from the terminal device via means,
The data input control means transmits page information of the data input screen to the terminal device via the second communication means, and sends the data input via the data input screen to the second communication means. Via the terminal device via
The terminal device
The item received from the data input management device via the first communication unit and the editor screen or the page information of the editor screen, and input via the operation unit according to the editor screen or the editor screen A data input management system comprising: control means for transmitting the layout setting data or input data to the data input management device via the first communication means. Computer
Storage means,
Generates and displays the page information of the editor screen for browsers that can set the layout of items on the data input screen, and stores the data on the data input screen from the setting data of the layout of the items input via the editor screen An editor control means for generating a spec file and a data storage file for storing data input via the data input screen and storing them in the storage means,
Based on the stored specification file and data storage file, page information of a data input screen for a browser is generated and displayed, and input data input via the data input screen is stored in the data storage file. Data input control means,
Program to function as.

Images