JP2004326626A - Structured document file management apparatus and structured document file management method - Google Patents

Abstract

An object of the present invention is to efficiently create a structured document file.
A tag storage unit stores a plurality of tags categorized for each tag template. The user creates a document template by capturing the tag, and stores the document template in the document template storage unit 406. In addition, the user can define a hierarchical structure of tags in the document template and a new tag on a GUI basis. As a result, a structured document file can be efficiently created.
[Selection diagram] FIG.

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a structured document file management technique, and more particularly to a technique for managing tags constituting a structured document file.
[0002]
[Prior art]
2. Description of the Related Art In recent years, with the spread of computers and the development of network technologies, electronic information exchange via networks has become active. As a result, much of the paperwork conventionally performed on paper is being replaced with network-based processing.
[0003]
In companies as well, so-called knowledge management, which utilizes individual knowledge and information throughout the organization, has become an important management technique. Many companies have in-house database systems and store information from employees in electronic files. On the other hand, employees also access the files stored in the in-house database via a network. As a result, the operation efficiency of the entire organization is improved.
[0004]
Many of the files stored in the in-house database are created in a language called HTML (Hyper Text Markup Language). In recent years, the number of cases in which these files are created using a language called XML (extensible Markup Language) has been increasing.
[0005]
HTML is a language for describing web pages. That is, HTML is a type of markup language that defines a display method of a document file. On the other hand, XML is not a language for directly describing a web page like HTML. XML is a language having a function of defining a data structure of data included in a document file. The document file created by XML is converted into a document file described in a markup language by giving display layout information separately, and is displayed as a web page. That is, in the XML document, the data structure and its display layout are handled as separate ones. A language for generating a markup language, such as XML, is called a meta language.
[Non-patent document 1]
Fumiaki Yoshimatsu, "The Impact of InfoPath", [online], March 26, 2003, Atmark IT Co., Ltd., [Search April 8, 2003], Internet <URL:
http: // www. atmarkit. co. jp / fdotnet / special / infopath / infopath_01. html>
[Non-patent document 2]
Tetsuya Hori, "XDocs", the first to be demonstrated in Japan to integrate front-end applications with XML, [online], February 14, 2003, SoftBank G-DNet, Inc., [Searched April 8, 2003 ], Internet <URL:
http: // www. zdnet. co. jp / enterprise / 0302/14 / epn21. html>
[Non-Patent Document 3]
Joe Wilcox, “Is InfoPath hard to use“ out of the box ”? ", [Online], March 7, 2003, SoftBank G.D. Net, Inc., [Search April 8, 2003], Internet <URL:
http: // www. zdnet. co. jp / news / 0303/07 / ne00_infopath. html>
[0006]
[Problems to be solved by the invention]
Normally, when a document file is created by XML, first, a data structure is defined, and further a display layout is defined. Therefore, a plurality of display layouts can be defined for a document file created by XML, even if the data has the same contents.
[0007]
The display layout of a document file created by XML is defined by a language for describing a style sheet such as XSL (extensible Stylesheet Language), for example. Alternatively, there is a method of converting an XML document file into an HTML document file by using a language called XSLT (XML Stylesheet Transform).
[0008]
A document file created by a meta-language such as XML (hereinafter, a document file created by such a meta-language and having a data structure, particularly a “structured document file”) is compatible with a database. There is a merit that is high. This is because the data included in the structured document file is structured, so that it is easy to adapt to processes such as data search. However, on the other hand, the process of creating a document file in a meta-language such as XML and defining its display layout generally requires a lot of expertise, and places a heavy burden on the user.
[0009]
In other words, a meta-language such as XML has the potential to handle data to be handled by multiple application softwares in a unified scheme, but the difficulty of learning often makes this capability difficult. It is a hindrance factor in exerting it. As a solution, various methodologies have begun to be proposed, but the technology for efficiently creating a structured document file and effectively handling the structured document file is still developing.
[0010]
The present invention has been made in view of the above problems, and an object of the present invention is to provide a technique for effectively managing a structured document file.
[0011]
[Means for Solving the Problems]
One embodiment of the present invention relates to a structured document file management device. This apparatus obtains data input from a data input person via an input form display unit that displays an input form including an item for which a data input person should input data on a screen, and an item included in the input form. A data acquisition unit, including a data storage unit for storing the acquired data, and further including, as attribute information of an item for accepting data input from a data entry person at a stage of generating an input form, which is processed prior to display. A plurality of tags referred to when displaying the form are classified according to the purpose of use of the input form, and a tag storage unit that holds the library and a form creator instructs from among a plurality of tags included in the library A tag acquisition unit that acquires the acquired tags and an input form that arranges the acquired tags based on instructions from the form creator. Characterized in that it comprises a template creation unit that generates a template.
[0012]
The “tag” may be a software component having a function of acquiring data from a user.
[0013]
In addition, the template creating unit of the apparatus associates the tags included in the template with each other based on an instruction from the form creator to generate a template, and the data storage unit includes the data acquired by the data acquiring unit in the template. May be stored based on the tag association information.
[0014]
Further, the apparatus further includes a tag creation unit that acquires a newly created tag according to the instruction of the form creator, and the tag storage unit classifies the acquired tag according to a use purpose of the input form, It may be stored as a library. Further, the tag creation unit further has a function of acquiring a tag selected and edited according to the instruction of the form creator from a plurality of tags included in the library, and the tag storage unit stores the acquired tag Classification may be made according to the purpose of use of the input form, and the form may be stored as a library.
[0015]
Hereinafter, a category in which a plurality of tags are classified is referred to as a “tag template”. With this classification, it is possible to easily select a tag according to the purpose of creating the template. The template that is the basis of this input form is called a “document template”.
[0016]
Each functional block shown in FIG. 3 and the like may be provided on the server device side or may be provided on the client terminal side. Alternatively, it may be provided in both the server device and the client terminal, and in that case, each functional block may have the same name. Each of these functions is provided in the form of a program module, and may be executed by one or both of the server device and the client terminal, or may be downloaded from the server device to the client terminal upon execution.
[0017]
Another embodiment of the present invention relates to a structured document file management method. This method is a library that classifies and holds tags including attribute information referred to when displaying an input form as items of the input form for receiving data input from a data input user according to the purpose of use of the input form. A tag obtaining step of obtaining a tag specified by the form creator, and a template generating step of arranging the obtained tag and generating a template of the input form based on the instruction by the form creator. And
[0018]
Still another preferred embodiment according to the present invention relates to a structured document file management program. This program has a function of displaying on the screen an input form including an item for which a data entry person should input data, a function of acquiring data input from the data entry person via an item included in the input form, Includes a function to store the acquired data, and is referred to when displaying the input form as attribute information of an item that accepts data input from a data input person at the stage of generating the input form, which is processed prior to display. A function for classifying a plurality of tags according to the purpose of use of an input form and holding the same as a library, a function for acquiring a tag specified by a form creator from a plurality of tags included in the library, and a form Based on the creator's instructions, a function to place the obtained tags and generate a template for the input form is compiled. Characterized in that it be exhibited in over data.
[0019]
It is to be noted that any combination of the above-described components and any conversion of the expression of the present invention between a method, an apparatus, a system, a recording medium, a computer program, and the like are also effective as embodiments of the present invention.
[0020]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 schematically shows an embodiment. This embodiment is used for the following purposes. That is, users belonging to the development department of a certain company (hereinafter, referred to as “development staff”) and users belonging to the marketing department (hereinafter, referred to as “marketing staff”) manage information on a certain product project. There are situations that need to be performed. Here, it is assumed that the user wants to collect related data from the development department and the marketing department regarding the product project, and then collectively manage the data.
[0021]
In the present embodiment, a development department tag template 200 for a development department member and a marketing department tag template 210 for a marketing department are prepared in advance. Each of the development section tag template 200 and the marketing section tag template 210 has data input / output items called a plurality of tags as software components. In the figure, the development department tag template 200 has a tag group such as a name tag 202, a development phase tag 204, and a password tag 206. On the other hand, the tag template 210 for the marketing department has a tag group such as a name tag 212, a product name tag 214, and a number tag 216.
[0022]
By combining these tags, the project management document template 220 is created. The project management document template 220 defines a format of a structured document file for managing information on a product project. The project management document template 220 includes items such as a planned product name item 222, a development phase item 224, a test mode password item 226, a development leader item 228, a sales forecast item 230, and 232. That is, the development phase item 224 corresponds to the development phase tag 204, the test mode password item 226 corresponds to the password tag 206, and the development leader item 228 corresponds to the name tag 202. On the other hand, in the project management document template 220, the planned product name item 222 corresponds to the product name tag 214, and the sales forecast items 230 and 232 both correspond to the number tag 216.
[0023]
Data is input in accordance with the tag layout of the project management document template 220 created in this way, and a structured document file is created. Hereinafter, among the users, a person who has authority to create a document template and creates the document template is particularly called a “document template creator”.
[0024]
FIG. 2 is a configuration diagram of the structured document file management device 10 according to the embodiment. The server device 300 provides a service to a plurality of terminals (hereinafter simply referred to as “client terminals 50”) such as client terminals 50a and 50b connected via a LAN (Local Area Network) 16. Further, the client terminal 50 may be connected to the server device 300 via a WAN (Wide Area Network) 12.
[0025]
The server device 300 and the client terminal 50 can be realized in hardware by elements such as a CPU of a computer, and in software by a program having a data transmission / reception function. Etc. depict functional blocks realized by their cooperation. Therefore, these functional blocks can be realized in various forms by a combination of hardware and software. The server device 300 may have a configuration including a web server, and the client terminal 50 may have a configuration including a personal computer and a web browser installed therein.
[0026]
FIG. 3 is a functional block diagram of the structured document file management device 10 of FIG. Here, the functions of FIG. 3 are not realized by either the server device 300 or the client terminal 50, but the functions of FIG. 3 are realized by the structured document file management device 10 as a whole. It does not matter which of the server device 300 and the client terminal 50 is used to realize each functional block and each part in the functional block. In constructing the entire system, how to allocate various functions between the server device 300 and the client terminal 50 is determined in consideration of the operating environment of the structured document file management device 10 such as a communication environment and a computing function. It should just be designed.
[0027]
The functional blocks of the structured document file management device 10 shown in FIG. 1 are roughly divided into a user interface processing unit 310, a data processing unit 330, and a data storage unit 400. The user interface processing unit 310 is responsible for various user interface functions for the user. The data processing unit 330 performs various data processing on the structured document file. The data storage unit 400 stores various data related to the structured document file.
[0028]
The user interface processing unit 310 includes a general user user interface processing unit 312 and a document template creator user interface processing unit 314. The document template creator user interface processing unit 314 is responsible for user interface processing relating to the creation of a document template. The general user interface unit 312 is in charge of user interface processing relating to data input / output processing based on the document template. Hereinafter, among users, a user who inputs and outputs data via a document template is particularly referred to as a “general user”.
[0029]
The general user interface unit 312 and the document template creator user interface unit 314 may be separate. For example, a client terminal 50 for a document template creator and a client terminal 50 for a general user are separately provided, and each function of a general user interface 312 and a document template creator user interface 314 is provided. May be shared separately. Alternatively, the single user interface processing unit 310 may switch the user interface processing unit for general user 312 and the user interface processing unit for document template creator 314 as appropriate.
[0030]
The data processing unit 330 includes a user determination unit 332, a data search unit 334, a data conversion unit 336, a data acquisition unit 340, and a document template creation unit 360. The user determining unit 332 specifies a user and determines authority to perform various data processing. The data search unit 334 searches for desired data from various data included in the data storage unit 400. The data conversion unit 336 converts various types of data included in the data storage unit 400. For example, it is in charge of controlling the conversion of the data format, such as converting a document template into a web display format or processing data input by a general user into a predetermined format.
[0031]
The data acquisition unit 340 acquires data input from a general user based on the document template, and stores the data in the data storage unit 400. A functional block diagram inside the data acquisition unit 340 will be described later in detail. The document template creation unit 360 performs data processing accompanying the creation of a document template. A functional block diagram inside the document template creation unit 360 will also be described later in detail. The data search unit 334, the data conversion unit 336, the data acquisition unit 340, and the document template creation unit 360 determine the processing authority of the user by the user determination unit 332 when executing each process.
[0032]
The data storage unit 400 includes a user management information storage unit 402, a tag storage unit 404, a document template storage unit 406, a structured document file storage unit 408, and an input data storage unit 410. The user management information storage unit 402 stores information about a user. Specifically, various types of information for managing users (hereinafter, referred to as “user management information”), such as an ID number for identifying a user, an affiliation of the user, a right to create a document template, and a right to input data. ) Is stored.
[0033]
The user determination unit 332 makes a determination on the processing authority of the user based on the user management information stored in the user management information storage unit 402. The tag storage unit 404 classifies and stores the tags for each tag template. The document template storage unit 406 stores a document template. The document template stored in the document template storage unit 406 is converted into a web display format by the data conversion unit 336, and is provided to the general user by the general user interface unit 312.
[0034]
The structured document file storage unit 408 stores a structured document file. The general user inputs predetermined data based on the document template stored in the document template storage unit 406, and stores the data in the structured document file storage unit 408 as a structured document file. The structured document file stored in the structured document file storage unit 408 includes various types of input data, information on their data structures, and information on the display layout of the file. That is, the structured document file storage unit 408 structures and stores data in file units.
[0035]
On the other hand, the input data storage unit 410 stores data input by a general user in a structured manner. That is, the data conversion unit 336 reads data included in the structured document file defined in the XML format or the like stored in the structured document file storage unit 408, its structure, and information such as the user who has input the data. Then, various data are extracted from the structured document file and stored in the input data storage unit 410 in a predetermined format.
[0036]
FIG. 4 shows a functional block diagram of the inside of the document template creating section 360. The creating unit 362 creates a document template. The tag search unit 364 searches the tag storage unit 404 for a desired tag when creating a document template. When the creating unit 362 creates a new document template based on an existing document template, the document template selecting unit 368 selects a document template to be the base from the document template storage unit 406.
[0037]
The tag edit processing unit 370 creates a new tag by defining a new tag or editing an existing tag. The tag registration unit 374 registers the tags created by the tag editing unit 370 in the tag storage unit 404 for each tag template. The hierarchical structure setting unit 372 defines a hierarchical structure of tags included in the document template. It is not necessary to define the hierarchical structure of the tags included in the document template. The document template registration unit 366 registers the created document template in the document template storage unit 406. The registered document template is converted into a web display format and published.
[0038]
FIG. 5 shows a functional block diagram of the inside of the data acquisition unit 340. The document template selection unit 346 selects a document template from which the general user should input data from the document template storage unit 406. The data input unit 342 receives data input by a general user.
[0039]
Each tag in the document template has a data type when receiving data input. For example, there are tags for inputting a date and tags for inputting an amount, and there are various types. The data type checking unit 344 checks the type of data input by the user, and takes action to prevent incorrect data input. When data is input, the structured document file registration unit 348 registers the data in the structured document file storage unit 408 as a structured document file.
[0040]
Next, the process of creating a document template that defines the layout of a business daily report within a company will be specifically described from the viewpoint of a user interface. When the document template creator instructs the user interface processing unit 310 to create a document template, various screens shown in FIG. 6 and subsequent figures are displayed to the document template creator.
[0041]
FIG. 6 shows a document template creation screen 450 displayed when a document template creator creates a document template. A document template layout area 452 indicates a display layout of the document template being created. In the tag selection area 456, a tag to be imported into the document template being created is selected. When the tag creation button 458 is pressed, a tag editing screen 500 for creating a new tag is displayed. When the tag edit button 460 is pressed, a tag edit screen 500 is displayed to edit an existing tag. The tag editing screen 500 will be described later in detail.
[0042]
A tag template can be selected by a tag template selection button 462. In the figure, a tag template named “standard” is selected. The tag selection area 464 shows a list of tags classified into the tag template selected by the tag template selection button 462. When the setting button 466 is pressed, the tag selected in the tag selection area 464 is taken into the designated position in the document template layout area 452. The data input method of each tag displayed in the tag selection area 464 is various, such as a selection type and an entry type, and is not necessarily the same. Here, the entry type input icon 468 indicates that an entry type tag has been captured. On the other hand, the selection formula input icon 470 indicates that a selection formula tag has been captured.
[0043]
FIG. 7 shows a tag editing screen 500 displayed when the tag creation button 458 or the tag edit button 460 is pressed on the document template creation screen 450. On the tag editing screen 500, creation of a new tag and editing of an existing tag are performed. An input method setting area 506 sets the data input format of the tag. The data input format of the tag is determined by either the one-line input selection button 502 or the free description selection button 504. When the one-line input selection button 502 is selected, the tag has a format for inputting data of only one line. When the free description selection button 504 is selected, the tag has a free description input format.
[0044]
When the input list setting area 508 is checked while the one-line input selection button 502 is selected, the tag is a list selection type. At this time, when the input list edit button 510 is pressed, a screen for setting the list candidates is displayed (not shown).
[0045]
A tag template to which the tag belongs is set by a tag template selection button 512. Further, a tag template to which a tag belongs can be newly defined by a tag template definition button 514. In the tag name setting area 516, a tag name is set. In the caption setting area 518, a caption of the tag is set. This caption is displayed in the tag selection area 464. In the description entry area 520, a description of the tag is set.
[0046]
FIG. 8 shows a tag hierarchical structure setting screen 550 for creating a hierarchical structure of tags captured in the document template. The tag hierarchical structure setting area 552 indicates the hierarchical structure of the tag. The document template creator designs the hierarchical structure of the tags in the tag hierarchical structure setting area 552. In addition, a new tag can be added to combine these tags. When the OK button 554 is pressed, the hierarchical structure of the tag designed in the tag hierarchical structure setting area 552 is activated.
[0047]
When the document template registration unit 366 registers the document template in the document template storage unit 406, the document template is converted into a web display format and provided to general users.
[0048]
FIG. 9 shows a document template display screen 600 for a general user to input data to a document template created on each screen of FIGS. 6 to 8. The document template display area 602 is a document template for creating a business daily report. The general user inputs data to each item of the document template display area 602. When the mouse cursor is moved to a predetermined tag, the description of the tag set in the description entry area 520 of FIG. When the data input is completed, the structured document file including the input data is stored in the structured document file storage unit 408. Each input data in the structured document file is stored in a hierarchical structure according to the tag hierarchical structure set on the tag hierarchical structure setting screen 550.
[0049]
Next, a processing flow will be described.
[0050]
FIG. 10 shows a flowchart in the process of creating a document template. When creating a document template, the document template creator may create a completely new document template, or may create a new document template based on an existing document template. If the document template creator is to use the existing document template as a base (Y in S10), the desired document template is loaded from the document template storage unit 406 by the document template selection unit 368 (S12).
[0051]
When the document template creator creates a new tag on the tag editing screen 500 (Y in S14), a tag creation process is performed (S16). The newly created tags are classified and registered in the tag storage unit 404 for each tag template (S18). These tags stored in the tag storage unit 404 are acquired and tags are set, and the layout of the document template is determined (S20).
[0052]
When the tags included in the document template are hierarchically structured (Y in S22), the hierarchical structure setting unit 372 performs a hierarchical structure creation process of the tags (S24). The document template thus created, including the hierarchical structure of the tags, is registered in the document template storage unit 406 (S26), and the document template creation processing ends.
[0053]
FIG. 11 is a flowchart showing a process in which a general user inputs data according to a tag of a document template and registers the data. The general user selects a document template to which data is to be input from the document templates displayed in the web display format (S30). The general user inputs data in a predetermined format for each tag item of a predetermined document template (S32). When the data input is completed (Y in S34), the data is registered in the structured document file storage unit 408 as a structured document file (S36). The input data is extracted in a predetermined format according to the hierarchical structure of the tag of the document template, stored in the input data storage unit 410 (S38), and the process ends.
[0054]
As described above, in the embodiment, tags for a document template creator to create a document template are classified in advance by the tag template. Therefore, a desired tag can be efficiently selected according to the purpose of creating the document template. Further, the display format of the document template and the definition of the hierarchical structure of the tags can all be performed on a GUI (Graphical User Interface) basis. Therefore, there is no burden on the document template creator to acquire expertise in a meta-language such as XML.
[0055]
Further, when creating a document template, the document template creator can also create a new desired tag and register it on a GUI basis. As a result, as the structured document file management device is used, useful tags corresponding to the purpose of use are accumulated. Therefore, a desired document template can be created more efficiently.
[0056]
The present invention has been described based on the embodiments. It should be understood by those skilled in the art that the embodiments are exemplifications, and that various modifications can be made to the combination of each component and each processing process, and that such modifications are also within the scope of the present invention. .
[0057]
As such a modification, the tags may be hierarchically structured from the beginning and stored in the tag storage unit 404. The tags incorporated in the document template may be automatically hierarchized based on the hierarchical structure information in the tag storage unit 404. This reduces the burden of defining a similar hierarchical structure each time a document template is created. Further, not limited to the data input tag, for example, a predetermined software component such as a word search button may be selected and taken into the document template. Further, by combining and grouping a plurality of tags, the tags may be collectively taken as one unit and taken into the document template.
[0058]
Further, the structured document file management device may have a function of acquiring a desired tag via a network. By incorporating tags created by others into the document template, more diverse tags can be used. Further, when creating a document template, the apparatus may have a function of defining only a tag and its hierarchical structure without defining a display layout. The display layout may be separately defined. Thereby, a plurality of display layouts can be defined even with the same data structure. Alternatively, a document template may be created by deciding a display layout in advance using word processing software or the like, fetching the display layout, and embedding a desired tag.
[0059]
【The invention's effect】
According to the present invention, a structured document file can be effectively managed.
[Brief description of the drawings]
FIG. 1 is a schematic diagram relating to creation of a document template in the present embodiment.
FIG. 2 is a hardware configuration diagram of a structured document file management device according to the present embodiment.
FIG. 3 is a diagram showing functional blocks of a structured document file management device.
FIG. 4 is a diagram showing functional blocks inside a document template creation unit.
FIG. 5 is a diagram showing functional blocks inside a data acquisition unit.
FIG. 6 is a diagram illustrating an example of a document template creation screen.
FIG. 7 is a diagram illustrating an example of a tag editing screen.
FIG. 8 is a diagram showing an example of a tag hierarchical structure setting screen.
FIG. 9 is a diagram illustrating an example of a document template display screen for a general user.
FIG. 10 is a flowchart in a process of creating a document template.
FIG. 11 is a flowchart in a process of inputting data via a document template.
[Explanation of symbols]
Reference Signs List 10 structured document file management device, 310 user interface processing unit, 312 general user user interface processing unit, 314 document template creator user interface processing unit, 330 data processing unit, 340 data acquisition unit, 348 structured document file registration Section, 360 document template creation section, 364 tag search section, 366 document template registration section, 370 tag editing processing section, 372 hierarchical structure setting section, 374 tag registration section, 400 data storage section, 404 tag storage section, 406 document template storage Unit, 408 structured document file storage unit, 410 input data storage unit.

Claims (6)

An input form display unit for displaying an input form including an item for which a data entry person should input data on a screen,
Through the items included in the input form, a data acquisition unit that acquires data input from the data input person,
A data storage unit for storing the obtained data,
Including
Further, in the step of generating the input form, which is processed prior to the display,
A tag storage unit that classifies a plurality of tags referred to when displaying an input form as attribute information of the item that receives data input from the data input user according to a use purpose of the input form, and stores the tag as a library When,
A tag acquisition unit that acquires a tag specified by a form creator from among the plurality of tags included in the library,
Based on an instruction from the form creator, a template creating unit that arranges the obtained tags to generate a template of the input form,
A structured document file management device, comprising: The template creation unit creates a template by hierarchically associating tags included in the template based on an instruction from the form creator,
The structured document file management device according to claim 1, wherein the data storage unit stores the data acquired by the data acquisition unit based on tag association information included in the template. A tag creation unit that acquires a newly created tag according to the instruction of the form creator,
Further comprising
3. The structured document file management device according to claim 1, wherein the tag storage unit classifies the acquired tags according to a use purpose of the input form, and holds the acquired tags as a library. 4. The tag creation unit further has a function of acquiring a tag selected and edited by an instruction of the form creator, from a plurality of tags included in the library,
4. The structured document file management device according to claim 3, wherein the tag storage unit classifies the obtained tags according to a use purpose of the input form and holds the tags as a library. 5. From the data input person, as an item of the input form that accepts data input, a tag including attribute information referred to when displaying the input form, from a library that is classified and held according to the purpose of use of the input form, A tag acquisition step for acquiring a tag specified by the form creator;
Based on an instruction from the form creator, a template creating step of arranging the obtained tag and generating a template of the input form,
A structured document file management method comprising: A function to display an input form including items for which the data entry person should input data on the screen,
Through the items included in the input form, a function to obtain data input from the data input person,
A function of storing the obtained data;
Including
Further, in the step of generating the input form, which is processed prior to the display,
A function of classifying a plurality of tags referred to when displaying an input form according to the purpose of use of the input form as attribute information of the item that receives data input from the data input person, and holding the library as a library,
A function of acquiring a tag specified by a form creator from among the plurality of tags included in the library,
A function of arranging the obtained tags and generating a template of the input form based on an instruction from the form creator;
A structured document file management program characterized by causing a computer to perform the functions described above.

Images