JP2005339387A - Document preparation support method and document preparation support program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document preparation support method and a document preparation support program, for easily acquiring necessary information according to the kind of a document to be prepared to efficiently prepare the document. <P>SOLUTION: A document preparation support server 20 transmits a template document embedded with a section identifier 715 to a user terminal so as to display it on a first screen 710 of a display screen 700 displayed on a user terminal. The document preparation support server 20 acquires the section identifier 715 displayed on the first screen 710 of the user terminal, and embedded in the template document during editing work by a user. The document preparation support server 20 performs transmission to display related information associated to the section identifier 715 on a second screen 720 of the user terminal. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a document creation support method and a document creation support program for supporting document creation.

Conventionally, when creating a standard document, a template of the document may be used. A large number of devices for creating such documents have been disclosed (for example, see Patent Document 1). This Patent Document 1 describes an apparatus that creates a document by selecting and inputting a template using voice recognition.
JP 2001-10162 A (page 4-10)

  However, even when using a template, specialized knowledge may be required when creating a document. In this case, the user often cannot easily create a document. Even when a template is used, it may be easier to create a document by creating a document with reference to a description example. In such a case, the user refers to various books or searches for information via the Internet in order to obtain necessary information. However, it is not always possible to quickly find an information source from which necessary information can be obtained. Further, when creating a plurality of different types of documents, it is necessary to collect information necessary for creating each document. For this reason, collection of information necessary for document creation may be a heavy load.

  The present invention has been made to solve the above-described problems, and its purpose is to easily acquire necessary information according to the type of document to be created and to efficiently create a document. To provide a creation support method and a document creation support program.

  According to the present invention, the management computer uses the support information storage means that records the section identifier and the support information in association with each other, and the management computer connectable to the user terminal. The template document in which the section identifier is embedded is transmitted to the user terminal and displayed on the first screen of the user terminal, and is embedded in the template document being edited by the user. An identifier is acquired, and support information associated with the section identifier is transmitted for display on the second screen of the user terminal. As a result, it is possible to identify a section that is displayed on the first screen of the user terminal and is working, and to display support information corresponding to the section on the second screen. Therefore, it is possible to work while confirming the support information of the section displayed on the first screen and being worked on the second screen.

  Furthermore, according to the present invention, the management computer acquires user attributes and selects support information to be displayed on the second screen of the user terminal based on the user attributes. Thereby, the support information according to the user attribute can be displayed on the second screen of the user terminal.

  Further, according to the present invention, the user attribute is an attribute of a group to which the user belongs or a level of proficiency of the user. Thereby, the support information according to the attribute of the group to which the user belongs and the proficiency level of the user can be displayed on the second screen of the user terminal.

  According to the present invention, it is possible to easily acquire necessary information according to the type of document to be created and efficiently create a document.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, a description will be given of a document creation support method and a document creation support program for easily acquiring necessary information according to the type of document to be created and efficiently creating a document. Here, a case where a user provides a document creation support service that supports creation of a disclosure document such as a securities report will be described. In the present embodiment, it is assumed that when the creation of a disclosure document is completed, an in-house approval authority performs approval, and an external auditor (external auditor) performs an audit. Disclosure documents that have been audited by an external auditor are made public via the Internet.

  As shown in FIG. 1, the document creation support server 20 can be connected to the user terminal 30 via the Internet 40. Here, it is assumed that a disclosure document creator, an authorized authority, and an external auditor are used as users.

  The user terminal 30 is a computer terminal used by a user, and has a function of transmitting data via a network, a function of displaying received data, and the like. The user terminal 30 includes control means (CPU) and storage means (RAM, ROM, etc.) not shown, input means such as a keyboard and mouse, output means such as a display, communication means such as a modem, and the like. In the present embodiment, a disclosure document creator, an approval authority, and an external auditor each access the document creation support server 20 using the user terminal 30 to perform disclosure document creation, internal approval, and external audit. Do each.

  The document creation support server 20 performs various data management and various data processing for supporting creation of a disclosure document. The document creation support server 20 includes a management computer 21.

  The management computer 21 performs data transmission / reception with the user terminal 30 and various data processing. The management computer 21 includes a control unit (CPU), a storage unit (RAM, ROM, etc.), an input unit, an output unit, a communication unit, and the like (not shown), and performs processing described later. By executing the document creation support program for that purpose, the management computer 21 functions as a template transmission unit, a section identifier acquisition unit, a support information transmission unit and the like described in the claims.

  The template transmission means transmits the template document in which the section identifier is embedded to the user terminal 30 for display on the first screen 710 (see FIG. 10) of the user terminal 30. The section identifier acquisition means acquires a section identifier displayed on the first screen 710 of the user terminal 30 and embedded in the template document being edited. The support information transmitting means transmits the support information (related information) associated with the section identifier for display on the second screen 720 (see FIG. 10) of the user terminal 30.

  The management computer 21 includes a user data storage unit 22, a template data storage unit 23, a related document data storage unit 24 as support information storage means, a created document data storage unit 25, and an access history data storage unit 26. It is connected.

As shown in FIG. 2, user data 220 is recorded in the user data storage unit 22 for each user. The user data 220 is recorded by registration of users who can use the document creation support server 20. The user data 220 includes data related to a user identifier, a password, an affiliated company, an affiliated department, and a level.

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

In the affiliated company data area, data relating to identification information of the affiliated company for specifying the affiliated company of the user is recorded.
In the belonging department data area, data relating to identification information of the belonging department for specifying the department to which the user belongs is recorded.

In the level data area, data relating to the level of proficiency of the user is recorded. In the present embodiment, the level of proficiency is distinguished in three stages: “Beginner”, “Intermediate”, and “Advanced”.
As shown in FIG. 3, the template data storage unit 23 stores template data 230 for each section of each document type. This template data 230 is recorded when a template document is prepared prior to provision of the document creation support service. The template data 230 includes data related to the document type and the template document.

  Data relating to the document type is recorded in the document type data area. In the present embodiment, “securities report”, “half-year report”, “business report”, and the like are recorded as document types.

  In the template document data area, data relating to a template document (template document) corresponding to the document type is recorded. This template document data is composed of a plurality of sections, and data relating to section identifiers is embedded in each section. The section identifier is an identifier for specifying a section in the disclosure document. Here, the section is a unit obtained by dividing the disclosure document according to the description content.

  In the related document data storage unit 24, as shown in FIG. 4, related document data 240 is recorded for each related document as support information prepared corresponding to the document type and the section identifier. In the present embodiment, one or a plurality of related documents are prepared in correspondence with the document type and the section identifier. The related document data 240 is recorded when a related document is prepared prior to provision of the document creation support service. The related document data 240 includes data related to the document type, section identifier, company attribute, level, and related documents.

Data relating to the document type is recorded in the document type data area.
In the section identifier data area, data relating to an identifier for specifying a section in the document is recorded.

  In the company attribute data area, data relating to a company attribute that provides a related document is recorded. Here, the settlement method of “consolidated settlement company” and “single settlement company” is recorded as the company attribute. Here, when the related document in the related document data 240 targets a plurality of company attributes, data related to all target company attributes is recorded in this company attribute data area.

In the level data area, data relating to the level of proficiency of the user who provides the related document is recorded. In the present embodiment, the level of proficiency is distinguished in three stages: “Beginner”, “Intermediate”, and “Advanced”. This level corresponds to the level that is the target of the related document in the related document data 240. For example, for the “beginner” level, disclosure document creation support information for a creator who is not very familiar with creating the disclosure document is prepared as a related document. On the other hand, for the “advanced” level, disclosure document creation support information for creators who have mastered the creation of disclosure documents is prepared as related documents. Here, when a plurality of levels of users are targeted, data relating to all the plurality of targeted levels is recorded in the level data area.

  In the related document data area, data related to a related document provided to the user is recorded as support information for creating a disclosure document. As described above, related documents corresponding to document types and section identifiers, and different related documents are prepared according to company attributes and levels. That is, in this embodiment, the attribute of the group to which the user belongs (company attribute) and the level of proficiency of the user are recorded as the user attribute, and a related document corresponding to the company attribute and level is provided. In the present embodiment, the related document includes information about a description example, a description example, a law, a description thereof, and the like.

Here, the relationship between the template data 230 and the related document data 240 will be described with reference to FIG. Here, the document type is “securities report”.
As shown in FIG. 7, the securities report 50 is composed of a plurality of sections, and a template corresponding to each section is prepared. This template corresponds to the template document of the template data 230. A section identifier is embedded in this template document.

  For each template, a related document for supporting creation of a disclosure document is prepared. A plurality of related documents are prepared as necessary in correspondence with company attributes and user levels.

  For example, regarding the section identifier “section 1” of the document type “securities report”, different related documents are used for the company attributes “single settlement company” and “consolidated settlement company”, and the levels are distinguished. If not, two related documents are prepared. That is, two pieces of related document data 240 of document type “securities report” and section identifier “section 1” are recorded. In one of the related document data 240, “single settlement company” is recorded as a company attribute, and “beginning”, “intermediate”, and “advanced” are recorded as levels. In another related document data 240, “consolidated settlement company” is recorded as a company attribute, and “beginning”, “intermediate”, and “advanced” are recorded as levels.

  In the created document data storage unit 25, as shown in FIG. 5, created document data 250 is recorded for each section in the disclosure document (created document). The created document data 250 is recorded when a disclosure document is created using this system. In this embodiment, when a created disclosure identifier is assigned and a newly created disclosure document is created, the created document data 250 for each section included in the disclosure document is recorded. The created document data 250 includes data relating to a created document identifier, document type, section identifier, company identifier, creator identifier, approval authority identifier, external auditor identifier, approval status, and content.

In the created document identifier data area, data relating to an identifier for specifying the created document is recorded.
Data relating to the document type of the created document is recorded in the document type data area.

In the section identifier data area, data relating to a section identifier for specifying each section of the created document is recorded.
In the company identifier data area, data relating to a company identifier for specifying the company to which the user belongs is recorded.

In the creator identifier data area, data relating to the creator identifier for specifying the creator of the created document is recorded.
In the approval authority identifier data area, data related to the approval authority identifier for identifying the approval authority for the created document is recorded.

In the external auditor identifier data area, data relating to an external auditor identifier for specifying a person who performs an external audit for the created document is recorded.
In the approval status data area, data related to the approval status of the created document is recorded. Specifically, “0” before creation by the creator is completed, “1” when creation by the creator is completed, “2” when approved by the approval authority, and approval by the external auditor “3” is recorded, and “9” is recorded when the external audit result is unapproved. Thus, in this embodiment, this approval status indicates the progress status.

  Content data of the created document is recorded in the content data area. That is, data relating to a template document (template document) or data relating to a document obtained by editing a template document (template document) is recorded.

  In this embodiment, when a new disclosure document is created, the created document data 250 is recorded for all sections in the disclosure document. Here, a case where a new disclosure document is created will be described.

  When creating a new disclosure document, first, a user (authorization setting person) who has the setting authority of the creator, approval authority, and external auditor accesses the document creation support server 20 using the user identifier and password. . Then, the authority setter selects a document type and makes a request for creating a new disclosure document. The management computer 21 of the document creation support server 20 extracts the template data 230 from the template data storage unit 23 based on the selected document type. Here, when the disclosure document of the selected document type is composed of a plurality of sections, a plurality of template data 230 corresponding to the sections are extracted. Then, based on the extracted template data 230, the document creation support server 20 transmits data for displaying the template documents side by side according to the section identifier to the user terminal 30. As a result, the template documents of the selected document type are arranged and displayed on the user terminal 30 according to the section identifier.

  The management computer 21 further requests input of a created document identifier. In response to this, the authority setting person inputs the created document identifier using the user terminal 30. Using this created document identifier, the management computer 21 records the created document data 250 corresponding to each section in the disclosure document of the selected document type in the created document data storage unit 25.

  Here, the created document identifier input by the user is recorded in the created document identifier data area of each created document data 250. In the section identifier data area, a section identifier embedded in the template document of the extracted template data 230 is recorded. The selected document type is recorded in the document type data area. In the company identifier data area, the company to which the user belongs extracted from the user data storage unit 22 based on the user identifier is recorded. “0” is recorded as the approval status. Further, a template document extracted from the template data storage unit 23 based on the created document identifier and the section identifier is recorded in the content data area.

  The document creation support server 20 further requests input of a creator identifier, an approval authority identifier, and an external auditor identifier for each section. In response to this, the authority setter uses the user terminal 30 to input the creator identifier, the authorized authority identifier, and the external auditor identifier for each section. Based on the data input here, the document creation support server 20 records the creator identifier, the approval authority identifier, and the external auditor identifier in the created document data 250 specified by the created document identifier and the section identifier. .

  In the access history data storage unit 26, as shown in FIG. 6, access history data 260 is recorded for each access to a disclosure document before publication. The access history data 260 includes data relating to a document identifier, an accessor identifier, and access time.

In the document identifier data area, data relating to a created document identifier for specifying a created document permitted to be browsed is recorded.
In the accessor identifier data area, data relating to a user identifier for identifying a user who is permitted to view a disclosure document before publication is recorded.

In the access time data area, data related to the accessed time is recorded.
A processing procedure for supporting creation of a disclosure document in the system configured as described above will be described with reference to FIGS. Here, the disclosure document creation process (FIG. 8), the approval process by the approval authority (FIG. 9), and the audit process by the external auditor will be described separately. First, a disclosure document creation process will be described with reference to FIG.

(Disclosure document creation process)
The creator of each section of the disclosure document uses the user terminal 30 to input the created document identifier, the user identifier, and the password, and requests the document creation support server 20 to access the document creation screen. As a result, the user terminal 30 sends access request data including the created document identifier, the user identifier, and the password to the document creation support server 20 to make an access request to the document creation screen (step S1-1).

  The management computer 21 of the document creation support server 20 that has received the access request data performs user authentication (step S1-2), and then determines whether or not there is browsing authority (step S1-3). Here, the management computer 21 first extracts the created document data 250 from the created document data storage unit 25 based on the created document identifier in the access request data. If the created document is composed of a plurality of sections, a plurality of created document data 250 corresponding to the sections are extracted. In the present embodiment, a user registered as a creator or an authorized person can access the document creation screen for any section of the created document. Specifically, the management computer 21 collates the creator identifier and approval authority identifier in the extracted created document data 250 with the user identifier in the access request data. Here, when the user identifier in the access request data exists in the extracted creator identifier and approval authority identifier, the user who made the access request has the viewing authority. If there is no viewing authority (NO in step S1-3), the management computer 21 notifies the user terminal 30 that the browsing is refused (step S1-4), and the process is terminated.

If there is a viewing authority (YES in step S1-3), the management computer 21 provides a created document (step S1-5). Specifically, the management computer 21 first extracts the created document data 250 from the created document data storage unit 25 based on the created document identifier. Then, the contents are arranged according to the section identifier. Then, the management computer 21 transmits the created document data in which the contents are arranged in this way to the user terminal 30.

  The user terminal 30 that has received the created document data displays the created document on the user terminal 30 based on the created document data (step S1-6). In the present embodiment, the created document is displayed on the first screen 710 of the display screen 700 shown in FIG.

  As shown in FIG. 10, in the first screen 710, the created documents of each section of the created document are displayed side by side according to the section identifier. Here, a document titled “1. About consolidated financial statements and methods of preparing financial statements” is displayed as the first section, and a document titled “2 About audit certification” is displayed as the second section. Similarly, the documents after the third section are displayed. Each section has a section identifier 715 embedded therein. On the first screen 710, a document can be created in the same manner as when creating a document using document creation software.

  Here, when the user moves the cursor for inputting a document on the first screen 710, the user terminal 30 specifies the section identifier 715 embedded in the data corresponding to the section area where the cursor is located. The data including the section identifier, the created document identifier, and the user identifier is transmitted to the document creation support server 20 (step S1-7).

  Receiving this data, the management computer 21 of the document creation support server 20 determines creation authority based on the received created document identifier, section identifier, and user identifier (step S1-8). Specifically, the management computer 21 first extracts the creator identifier from the created document data storage unit 25 based on the created document identifier and the section identifier. Then, the extracted creator identifier is collated with the user identifier in the received data. Here, when the user identifier in the received data exists in the extracted creator identifier, the user has the creation authority. If there is no creation authority (NO in step S1-8), the management computer 21 notifies the user terminal 30 that the creation is rejected (step S1-4), and the process ends. In this case, when the user moves the cursor to another section, the user terminal 30 performs the process of step S1-7 again on the section to which the cursor is moved.

  If there is a creation authority (YES in step S1-8), the management computer 21 first extracts a related document (step S1-9). Specifically, data related to the related document is extracted from the related document data storage unit 24 based on the selected document type and section identifier, the company attribute of the company to which the creator belongs, and the level of the creator. . Here, the company attribute is extracted from a company attribute data storage unit (not shown) based on the affiliated company. The company attribute data storage unit records the company and the company attribute in association with each other. And the management computer 21 transmits the data regarding the extracted related document to the user terminal 30 (step S1-10).

  Receiving this, the user terminal 30 displays the related document on the user terminal 30 based on the data related to the related document (step S1-11). In the present embodiment, the related document is displayed on the second screen 720 of the display screen 700 shown in FIG.

  Thus, since the related document is displayed based on the data related to the related document extracted as described above, the related document displayed corresponding to the document type and the section identifier is the company attribute and the level of the creator. The one corresponding to is displayed. Therefore, for example, when the level of the creator is advanced, a related document for advanced users is displayed, and when the creator level is beginner, related documents for beginners are displayed.

  The creator creates a disclosure document on the first screen 710 while referring to the related document displayed on the second screen 720 (step S1-12). When the creation of the disclosure document is completed, the creator inputs to the user terminal 30 the completion of the created document. Thereby, the user terminal 30 notifies the document creation support server 20 of the completion of the creation of the disclosure document (step S1-13).

  When receiving this, the management computer 21 of the document creation support server 20 records the created document (step S1-14). Specifically, the management computer 21 records the content data of the created document in the content data area of the created document data 250 specified by the created document identifier and the section identifier in the created document data storage unit 25. Then, “1” is recorded as the approval status. Then, the management computer 21 sends an approval request e-mail to the approval authority for the section for which the creation has been completed. Specifically, the management computer 21 first extracts the approval authority identifier from the created document data storage unit 25 based on the created document identifier and the section identifier. Then, an e-mail in which the created document identifier and the section identifier and the request for approval is requested is transmitted to the e-mail address of the approval authority specified by the approval authority identifier.

  In the case where the creation is to be saved in a situation where the creation has not been completed, the creator inputs a request for saving the created document. In this case, the document creation support server 20 records the content data of the created document at that time in the content data area of the created document data 250. In this case, the approval status is not updated.

(Approval process by approval authority)
Next, the approval process by the approval authority will be described with reference to FIG. Here, an approval process by an in-house approval authority will be described.

  When the approval request e-mail is received, the approval authority uses the user terminal 30 to input the created document identifier, the user identifier, and the password, and makes an access request to the document creation support server 20. As a result, the user terminal 30 transmits access request data including the created document identifier, the user identifier, and the password to the document creation support server 20 as shown in FIG. 9 (step S2-1).

  The management computer 21 of the document creation support server 20 performs user authentication by comparing the user identifier and password in the received access request data with the user identifier and password in the user data storage unit 22 (step S2-2). ).

When the user is authenticated, the management computer 21 checks the viewing authority of the user (step S2-3). Specifically, the management computer 21 first extracts the created document data 250 from the created document data storage unit 25 based on the created document identifier in the access request data. Here, when the created document is composed of a plurality of sections, a plurality of created document data 250 corresponding to the sections are extracted. Next, the management computer 21 extracts the approval status in the extracted created document data 250. When the extracted document data 250 includes an approval status “1”, the created document is subject to approval by an approval authority. In this case, a user registered as a creator or an authorized authority can access any section of the created document. Specifically, the management computer 21 collates the creator identifier and approval authority identifier in the extracted created document data 250 with the user identifier in the access request data. Here, when the user identifier in the access request data exists in the extracted creator identifier and approval authority identifier, it is assumed that the user who made the access request has the viewing authority. If there is no viewing authority (NO in step S2-3), the management computer 21 notifies the user terminal 30 that browsing is refused (step S2-4), and the process is terminated.

  If there is a viewing authority (YES in step S2-3), the management computer 21 provides the created document to the user terminal 30 (step S2-5). Specifically, the management computer 21 first extracts the created document data 250 from the created document data storage unit 25 based on the created document identifier. Then, the contents are arranged according to the section identifier. Then, the management computer 21 transmits the created document data in which the contents are arranged in this way to the user terminal 30.

Then, the management computer 21 records the access history data 260 in the access history data storage unit 26 (step S2-6).
The user terminal 30 that has received the created document data displays the created document on the user terminal 30 based on the created document data (step S2-7). Specifically, the contents of the created document specified by the created document identifier are arranged and displayed based on the section identifier. Here, only the section whose approval status is “1” can be input by the approval authority for the section.

  The approval authority confirms the section for which he / she has the approval authority and determines whether or not the approval is permitted (step S2-8). If approval is possible (YES in step S2-8), the approval authority specifies the section and performs approval input on the user terminal 30. Thereby, the user terminal 30 transmits approval data including the created document identifier, the section identifier, the approval flag, and the user identifier of the approval authority to the document creation support server 20 (step S2-9).

  The management computer 21 of the document creation support server 20 that has received the approval data determines whether or not the user who has made the approval has approval authority (step S2-10). Specifically, the management computer 21 first extracts the authorization authority identifier from the created document data storage unit 25 based on the created document identifier and the section identifier. Then, the extracted approval authority identifier and the user identifier in the approval data are collated. Here, when the user identifier in the approval data is present in the extracted approval authority identifier, it is assumed that the user who performed the approval has the approval authority. Here, when there is no approval authority (in the case of NO in step S2-10), the management computer 21 notifies the user terminal 30 that the approval is rejected (step S2-4), and the process ends.

  If there is an approval authority (YES in step S2-10), if the approval flag is “approval”, the management computer 21 records “2” as the approval status (step S2-11). Specifically, the management computer 21 specifies the created document data 250 by the created document identifier and the section identifier in the created document data storage unit 25 and records “2” as the approval status of the created document data 250.

  If the approval flag is “non-approved”, the management computer 21 records “0” as the approval status. Then, the created document identifier and the section identifier are specified, the fact that the section is not approved is notified to the creator of the section by e-mail, and the process ends. In this case, the creator recreates the document for that section.

(Audit processing by an external auditor)
Next, audit processing by an external auditor will be described. In the present embodiment, disclosure documents approved by an approval authority for all sections are subject to auditing by an external auditor.

  In the present embodiment, the flow of the audit process by the external auditor is the same as that of the approval process by the approval authority. For this reason, it demonstrates using FIG. 9 similarly to said case. Here, the description of the same process as the approval process by the approval authority is omitted.

  When the approval status for all sections in the disclosure document becomes “2”, the management computer 21 of the document creation support server 20 sends an e-mail for requesting an external auditor for each section to perform an external audit. Send. Specifically, the management computer 21 first extracts the external auditor identifier from the created document data storage unit 25 based on the created document identifier. Then, the management computer 21 transmits an e-mail in which the created document identifier and the section identifier and the request for external audit are requested to the e-mail address of the external auditor specified by the external auditor identifier.

  When the external audit request e-mail is received, the external auditor uses the user terminal 30 to input the created document identifier, the user identifier, and the password, and makes an access request to the document creation support server 20. Accordingly, the user terminal 30 transmits access request data including the created document identifier, the user identifier, and the password to the document creation support server 20 (step S2-1). The management computer 21 of the document creation support server 20 performs user authentication by comparing the user identifier and password received from the user terminal 30 with the user identifier and password of the user data storage unit 22 (step S2-2). ).

  When the user is authenticated, the management computer 21 checks the viewing authority of the user (step S2-3). Here, when there is no approval status “0” or “1” in the created document data 250 extracted based on the created document identifier, the external auditor can browse the disclosure document. In this case, a user registered as a creator, an authorized authority, or an external auditor can view any section of the created document.

  Specifically, the management computer 21 extracts the creator identifier, the approval authority identifier, and the external auditor identifier in the extracted created document data 250. Then, the creator identifier and approval authority identifier extracted are compared with the user identifier in the access request data. Here, when the user identifier in the access request data exists in the extracted creator identifier, approval authority identifier, and external auditor identifier, the user who made the access request has the viewing authority. . If there is no viewing authority (NO in step S2-3), the management computer 21 notifies the user terminal 30 that browsing is refused (step S2-4), and the process is terminated.

  If there is a viewing authority (YES in step S2-3), the management computer 21 provides the created document to the user terminal 30 (step S2-5). Then, the management computer 21 records the access history data 260 in the access history data storage unit 26 (step S2-6).

  The user terminal 30 that has received the created document data displays the created document on the user terminal 30 based on the created document data (step S2-7). Specifically, the contents of the created document specified by the created document identifier are arranged and displayed based on the section identifier.

The external auditor determines whether or not the section for which he / she has external audit authority can be approved for each section (step S2-8). If approval is possible (YES in step S2-8), the external auditor specifies a section and inputs approval in the user terminal 30. As a result, the user terminal 30 transmits external audit data including the created document identifier, section identifier, external audit approval flag, and external auditor user identifier to the document creation support server 20 (step S2-9).

  The management computer 21 of the document creation support server 20 that has received the external audit data determines whether or not there is an external audit authority (step S2-10). Specifically, the management computer 21 first extracts an external audit authority identifier from the created document data storage unit 25 based on the created document identifier and the section identifier. Then, the extracted external audit authority identifier is collated with the user identifier in the external audit data. Here, when the user identifier in the external audit data is present in the extracted external auditor identifier, the user (external auditor) who performed the external audit has the external audit authority. Here, when there is no external audit authority (NO in step S2-10), the management computer 21 notifies the user terminal 30 that acceptance of external audit is rejected (step S2-4), and the process is performed. finish.

  If there is external audit authority (YES in step S2-10), if the approval flag by external audit is “approved”, the management computer 21 records “3” as the approval status (step S2-11). . Specifically, the management computer 21 specifies the created document data 250 by the created document identifier and the section identifier in the created document data storage unit 25 and records “3” as the approval status of the created document data 250. Then, the created document identifier and section identifier are specified, and notification that the external audit result is approval is sent by e-mail to the creator and approval authority for the section and other registered users for notification. Then, the process ends.

  If the approval flag by the external audit is “non-approved”, the management computer 21 records “9” as the approval status. Then, by identifying the created document identifier and section identifier, the fact that the external audit result is unapproved is notified by e-mail to the creator and approval authority for the section and other registered users for notification. Notify and finish the process. In this case, the creator and the approval authority re-create and approve the document for the section, and undergo external audit again by the external auditor. When the document is updated for re-creation, the management computer 21 records “0” as the approval status.

As described above, according to the present embodiment, the following effects can be obtained.
In the above embodiment, the management computer 21 sends a template document in which the section identifier 715 is embedded to the user terminal 30 for display on the first screen 710 of the display screen 700 displayed on the user terminal 30. Send. Then, the management computer 21 acquires the section identifier 715 that is displayed on the first screen 710 of the user terminal 30 and embedded in the template document being edited by the user. Then, the management computer 21 transmits support information (related information) associated with the section identifier 715 for display on the second screen 720 of the user terminal 30.

  For this reason, it is possible to identify a section that is displayed on the first screen 710 of the user terminal 30 and is working, and to display support information corresponding to the section on the second screen 720. Therefore, the user can work while checking the support information of the section being displayed and displayed on the first screen 710 on the second screen 720.

  In the above embodiment, the related document is recorded in the related document data storage unit 24 in association with the company attribute and the level. Then, the management computer 21 extracts a related document from the related document data storage unit 24 based on the company attribute of the company to which the user belongs and the level of the user acquired based on the user identifier. It is displayed on the second screen 720.

  For this reason, it is possible to display the support information corresponding to the company attribute of the company to which the user belongs and the level of the user on the second screen 720 of the user terminal 30. Therefore, the user can refer to the support information corresponding to the company attribute of the company to which the user belongs, and can refer to the support information according to his / her level, and can efficiently create a document.

  In the above embodiment, when creating a disclosure document composed of a plurality of sections, a document in which contents are arranged according to the section identifier embedded in the template document is displayed on the first screen 710. Therefore, the user can view the entire disclosure document composed of a plurality of sections.

  In the above embodiment, a template document is used for a section newly created by the creator. For this reason, it is easy to create a document, and it is possible to prevent omission of necessary items.

  In the above embodiment, all sections of the disclosure document are displayed on the first screen 710, and the related document for the section being worked on is displayed on the second screen 720. Therefore, the creator can browse the entire disclosure document, and can efficiently obtain appropriate support information for the section being worked on.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, related documents are recorded in the related document data storage unit 24 in association with company attributes and levels. Then, the management computer 21 extracts the related document from the related document data storage unit 24 based on the company attribute of the company to which the user belongs and the level of the user acquired based on the user identifier. Based on the support information (related documents) based on. The user attribute used for selecting the support information to be displayed on the second screen 720 is not limited to this. When a plurality of support information (related documents) to be provided for each section is prepared, each related document is selected. Any user attribute may be used as long as the user attribute is used.

  In the above embodiment, the case of creating a disclosure document has been described, but the document to be created is not limited to this. Any document can be used as long as it is a document composed of a plurality of sections and can be created by using a template document and providing support information for each section. .

  In the above embodiment, the first screen 710 and the second screen 720 are provided on the display screen 700 displayed on the user terminal 30. Instead, using a user terminal having a plurality of displays, the first screen 710 may be displayed on one display and the second screen 720 may be displayed on another display.

  In the above embodiment, when the cursor is moved on the first screen 710, the user terminal 30 transmits the section identifier to the document creation support server 20. Instead, when the cursor is moved to a different section area on the first screen 710, the user terminal 30 may transmit the section identifier to the document creation support server 20. In this case, the user terminal 30 stores the section identifier of the section where the cursor is located. When the cursor is moved, the section identifier of the section to which the cursor is moved is acquired and compared with the stored section identifier. The section identifier is transmitted to the document creation support server 20 only when the section identifier of the destination section is different from the stored section identifier. As a result, the section identifier can be transmitted only when the input operation is started for a different section. Therefore, the communication load can be reduced.

  ○ In the above embodiment, related documents are prepared according to the level of proficiency of users and company attributes, and related documents are selected using these as keys. However, users who use them as keys when selecting related documents The attributes are not limited to these. For example, related documents may be prepared according to expertise, user position, role, position, etc., and related documents may be selected using these as keys.

  In the above embodiment, when creating a document on the first screen 710, the related document is displayed on the second screen 720 so that the user can refer to it. In addition, the contents of the second screen 720 may be incorporated into the document being created on the first screen 710. For example, on the second screen 720, a capture button for capturing on the first screen 710 is prepared. When this import button is clicked, the portion associated with the capture button is captured at the cursor position on the first screen 710. Specifically, the related document data recorded in the related document data storage unit 24 is extracted and imported to the document data displayed on the first screen 710. Thereby, a document can be created more efficiently.

  In the above embodiment, the related document corresponding to the document type and section of the document being created on the first screen 710 is displayed on the second screen 720. In addition, spell checking may be performed according to the document type and section. For example, data (for example, dictionary data) for performing spell check is recorded as a related document in association with the document type and section identifier. Then, the document type and section identifier of the document being created are acquired, the spell check data is extracted, and the spell check of the document being created is performed using this data. As a result, a more accurate document can be created more efficiently.

1 is a schematic diagram of a system according to an embodiment of the present invention. Explanatory drawing of the data memorize | stored in the user data storage part. Explanatory drawing of the data memorize | stored in the template data storage part. Explanatory drawing of the data memorize | stored in the related document data storage part. Explanatory drawing of the data memorize | stored in the created document data storage part. Explanatory drawing of the data memorize | stored in the access history data storage part. Explanatory drawing regarding template data and related document data. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing regarding the display of the document creation screen in a user terminal.

Explanation of symbols

  20 ... Document creation support server, 21 ... Management computer, 30 ... User terminal, 710 ... First screen, 715 ... Section identifier, 720 ... Second screen.

Claims (6)

A method for supporting creation of a document using support information storage means that records a section identifier and support information in association with each other, and a management computer that can be connected to a user terminal,
The management computer is
Transmitting a template document with an embedded section identifier to the user terminal for display on the first screen of the user terminal;
Obtaining a section identifier displayed on the first screen of the user terminal and embedded in the template document being edited by the user;
Transmitting the support information associated with the section identifier for display on the second screen of the user terminal. The management computer is
The document creation support according to claim 1, further comprising: obtaining user attributes and selecting support information to be displayed on the second screen of the user terminal based on the user attributes. Method.   The document creation support method according to claim 2, wherein the user attribute is an attribute of a group to which the user belongs or a level of proficiency of the user. A document creation support program for supporting creation of a document using support information storage means that records the section identifier and support information in association with each other, and a management computer that can be connected to a user terminal,
The management computer,
A template transmission means for transmitting a template document with an embedded section identifier to the user terminal for display on the first screen of the user terminal;
Section identifier acquisition means for acquiring a section identifier displayed on the first screen of the user terminal and embedded in the template document being edited by the user;
A document creation support program that functions as support information transmission means for transmitting support information associated with the section identifier for display on the second screen of the user terminal. The management computer further
5. The document creation support program according to claim 4, wherein the document creation support program functions as means for selecting support information to be displayed on the second screen of the user terminal based on the user attribute. .   The document creation support program according to claim 5, wherein the user attribute is an attribute of a group to which the user belongs or a level of proficiency of the user.

Images