Program, information processing device, and method

The program for managing meeting data on a computer improves meeting effectiveness by structuring and storing participant inputs to align actions with meeting purposes, addressing divergent discussions.

JP2025107039APending Publication Date: 2025-07-17弁護士ドットコム株式会社
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024000751
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-01-05
Publication Date
2025-07-17

AI Technical Summary

Technical Problem

Existing meeting systems fail to effectively enhance the achievement of meeting purposes when discussions diverge, leading to unclear actions and missed objectives.

Method used

A program for a computer that notifies participants of predetermined inputs at set times, receives user inputs, and stores them in a storage unit to manage meeting minutes and associated data, including user tables, minutes tables, issue tables, document tables, confirmation tables, and reaction tables.

Benefits of technology

Enhances the likelihood of achieving meeting objectives by structuring and storing meeting data to ensure clear actions and outcomes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025107039000001_ABST
    Figure 2025107039000001_ABST
Patent Text Reader

Abstract

To provide a technology for enabling a higher possibility of achieving an object of a meeting to be obtained.SOLUTION: A program for causing a computer including a processor to operate, causes the processor to execute the steps of: when a predetermined timing arrives based on a time set for a meeting, issuing a notice for prompting a user who is a participant of the meeting to perform predetermined input in line with an object of the meeting; accepting the predetermined input in line with the object of the meeting from the user; and causing a storage unit to store a content of the accepted input.SELECTED DRAWING: Figure 23
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a program, an information processing apparatus, and a method.

Background Art

[0002] It can be said that a meeting is held for some purpose. For example, in order to promote a project in a business company or the like, among members, the progress, information sharing, task assignment, etc. may be carried out. Patent Document 1 discloses a technique for capitalizing on the content of a meeting and streamlining the operation of the meeting.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] On the other hand, if an event such as the discussion in the meeting remaining divergent occurs, the participants in the meeting may not be able to imagine a specific action and the purpose of the meeting may not be achieved. The present disclosure is to provide a technique that can further enhance the possibility of achieving the purpose of a meeting.

Means for Solving the Problems

[0005] According to one embodiment, there is provided a program for operating a computer including a processor. The program causes the processor to perform a step of notifying a user of a participant in the meeting with a notification for prompting a predetermined input in accordance with the purpose of the meeting when a predetermined timing arrives based on the time set for the meeting, a step of receiving a predetermined input in accordance with the purpose of the meeting from the user, and a step of storing the content of the received input in a storage unit.

Advantages of the Invention

[0006] According to the present disclosure, the possibility of achieving the purpose of the meeting can be further enhanced.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Embodiments for Carrying Out the Invention

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, the same reference numerals are assigned to common components, and repeated descriptions will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure. Further, each drawing is a schematic diagram and is not necessarily drawn precisely.

[0009] <First Embodiment> The first embodiment will be described. <Configuration of System 1> System 1 in the present disclosure is an information processing system for providing a minutes management service for storing and managing minutes that record the content and decisions discussed in a meeting. System 1 includes an information processing device of server 10, a first user terminal 20, a second user terminal 30, and an online meeting system 40, which are connected via network N. FIG. 1 is a block diagram showing the functional configuration of System 1. FIG. 2 is a block diagram showing the functional configuration of server 10. FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30.

[0010] Each information processing device is configured by a computer including an arithmetic unit and a storage unit. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, the second user terminal 30, and the online conferencing system 40, descriptions overlapping with the basic hardware configuration of the computer and the basic functional configuration of the computer described later will be omitted.

[0011] <Configuration of Server 10> The server 10 is an information processing device that provides a minutes management service. The server 10 includes a storage unit 101 and a control unit 104.

[0012] <Configuration of the Storage Unit 101 of Server 10> The storage unit 101 of the server 10 includes an application program 1011, a user table 1012, a minutes table 1013, a topic table 1014, a document table 1015, a confirmation table 1021, and a reaction table 1022.

[0013] The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit. The application program 1011 includes applications such as a web browser application.

[0014] The user table 1012 is a table that stores and manages information of member users (hereinafter referred to as users) who use the service. By registering for use of the service, the information of the user is stored in a new record in the user table 1012. Thereby, the user can use the service according to the present disclosure. The user table 1012 is a table having columns of user ID, user name, and evaluation data with the user ID as the primary key. FIG. 5 is a diagram showing the data structure of the user table 1012.

[0015] The user ID is an item that stores user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user. The user name is an item that stores the user's name. The user name may be set to any string such as a nickname instead of the actual name. The evaluation data is an item that stores evaluation information such as personnel assessment of the user specified by the user identification information. The evaluation information includes strings indicating ranks such as A, B, C, scores such as 80 points and 70 points, and numerical values.

[0016] The minutes table 1013 is a table for storing and managing information related to minutes (minutes information). The minutes table 1013 is a table having columns for a minutes ID, a meeting name, a meeting ID, a holding date and time, a holding place, and a participant ID, with the minutes ID as the primary key. Figure 6 is a diagram showing the data structure of the minutes table 1013.

[0017] The minutes ID is an item that stores minutes identification information for identifying minutes. The minutes identification information is an item for which a unique value is set for each minutes information. The meeting name is an item that stores the name of the meeting. Any string can be set as the meeting name. For example, the meeting name includes a string for identifying meetings such as board meetings and general shareholders' meetings. The meeting ID is an item that stores meeting identification information for identifying a meeting. The holding date and time is an item that stores information related to the holding period, including the start date and time and the end date and time of the meeting. The holding place is an item that stores the place where the meeting specified by the meeting identification information is held. For example, the meeting room name and number are stored in the holding place. Also, in the case of an online meeting, etc., a string such as a URL for identifying a virtual meeting room called the room where the online meeting, etc. is held is stored in the holding place. The Participant ID is an item that stores user identification information for identifying participants who have participated in a meeting. The Participant ID stores user identification information related to one or more participants.

[0018] The Issue Table 1014 is a table for storing and managing information related to issues (issue information). The Issue Table 1014 is a table having columns for an issue ID, issue content, and access authority, with the issue ID as the primary key. Figure 7 is a diagram showing the data structure of the Issue Table 1014.

[0019] The Issue ID is an item that stores issue identification information for identifying an issue. The issue identification information is an item for which a unique value is set for each piece of issue information. The Issue Content is an item that stores a string for explaining the content of an issue. Specifically, the issue content includes strings for specifying issues such as "Product Development", "Product Design", "Marketing", etc. The Access Authority is an item that stores information related to the authority for viewing, referring to, etc. an issue specified by the issue identification information. The Access Authority includes user identification information for identifying users who can view, refer to, etc. an issue. The Access Authority includes group information for identifying the department, organization, company, etc. to which a user who can view, refer to, etc. an issue belongs. The group information stores a string for identifying a group such as a company name, department name, organization name, etc. The Access Authority includes information related to the position of a user who can view, refer to, etc. an issue (position information). The position information stores a string for identifying positions such as section chief, department head, office head, officer, executive officer, director, etc.

[0020] The Document Table 1015 is a table for storing and managing information related to documents (document information). The Document Table 1015 is a table having columns for a document ID, minutes ID, issue ID, heading text, document data, access authority, start date and time, and end date and time, with the document ID as the primary key. FIG. 8 is a diagram showing the data structure of the document table 1015.

[0021] The document ID is an item for storing document identification information for identifying a document. The document identification information is an item for which a unique value is set for each document information. The minutes ID is an item for storing the minutes identification information of the minutes associated with the document specified by the document identification information. The topic ID is an item for storing the topic identification information of the topic associated with the document specified by the document identification information. A plurality of topic IDs may be associated and stored for one document information. The heading text is an item for storing the title (caption) of the document. The document data is an item for storing text information related to the body of the document. Specifically, the document data stores information such as the discussed content and decisions regarding a specific topic in the meeting. The document data includes document data in any data format such as PDF (Portable Document Format), Word, XML (Extensible Markup Language). The access right is an item for storing information regarding the right to view, refer to, etc. the document specified by the document identification information. Since it is the same as the access right item in the topic table 1014, the description is omitted. In the present disclosure, it is possible to independently set the access right for each topic and the access right for each document. Note that the access right can be set for at least either each topic or each document. The start date and time is an item for storing the start date and time when the discussion on the topic started in the meeting. The end date and time is an item for storing the end date and time when the discussion on the topic ended in the meeting.

[0022] The confirmation table 1021 is a table for storing and managing information (confirmation information) indicating that the document information has been confirmed by a predetermined user. The confirmation table 1021 is a table having columns for document ID, confirmor ID, and confirmation date and time. Figure 9 is a diagram showing the data structure of the confirmation table 1021.

[0023] The document ID is an item for storing document identification information. The confirmor ID is an item for storing user identification information for identifying the confirmor. The confirmation date and time is an item for storing the date and time when the document information was confirmed by the confirmor.

[0024] The reaction table 1022 is a table for storing and managing information related to reactions (reaction information). The reaction table 1022 is a table having columns for document ID, issue ID, reaction data, user ID, and reaction date and time. Figure 10 is a diagram showing the data structure of the reaction table 1022.

[0025] The document ID is an item for storing document identification information. The issue ID is an item for storing issue identification information. The reaction data is an item for storing evaluation information given by the user to the document information. The evaluation information includes information such as "like", a rating evaluation from 1 to 5 levels, icon identification information (stamp) for identifying an icon indicating the user's sentiment towards the document information, and a character string indicating the user's sentiment towards the document information. By associating reaction data with the document information, the user's intention and opinion regarding the document information can be expressed. The user ID is an item for storing user identification information. The reaction date and time is an item for storing the date and time when the user reacted to the document.

[0026] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a creation unit 1042, and a browsing unit 1043. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0027] The user registration control unit 1041 performs a process of storing information of a user who wishes to use the service according to the present disclosure in the user table 1012. The information stored in the user table 1012 is such that the user opens a web page or the like operated by the service provider from an arbitrary information processing terminal, inputs information into a predetermined input form, and transmits it to the server 10. The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. As a result, the user stored in the user table 1012 can use the service. Prior to the registration of user information by the user registration control unit 1041 in the user table 1012, the service provider may perform a predetermined review to restrict the use of the service by the user. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or the user registration control unit 1041 may automatically set any character string or number.

[0028] The creation unit 1042 executes a minutes creation process. Details will be described later.

[0029] The browsing unit 1043 executes a list display process, a minutes browsing process, and a topic browsing process. Details will be described later.

[0030] <Configuration of the First User Terminal 20> The first user terminal 20 is an information processing device operated by a user who uses the service. The first user terminal 20 may be, for example, a mobile terminal such as a smartphone or a tablet, or a stationary PC (Personal Computer) or a laptop PC. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type terminal. The first user terminal 20 includes a storage unit 201, a control unit 204, an input device 206, and an output device 208.

[0031] <Configuration of the storage unit 201 of the first user terminal 20> The storage unit 201 of the first user terminal 20 includes a first user ID 2011 and an application program 2012.

[0032] The first user ID 2011 is the account ID of the first user. The first user transmits the first user ID 2011 from the first user terminal 20 to the server 10. The server 10 identifies the first user based on the first user ID 2011 and provides the service according to the present disclosure to the first user. Note that the first user ID 2011 includes information such as a session ID temporarily assigned by the server 10 for identifying the first user who is using the first user terminal 20.

[0033] The application program 2012 may be pre-stored in the storage unit 201, or may be configured to be downloaded from a web server or the like operated by a service provider via a communication IF. The application program 2012 includes an application such as a web browser application. The application program 2012 includes an interpreter-type programming language such as JavaScript (registered trademark) that is executed on the web browser application stored in the first user terminal 20.

[0034] <Configuration of the control unit 204 of the first user terminal 20> The control unit 204 of the first user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing the application program 2012 stored in the storage unit 201.

[0035] <Configuration of the input device 206 of the first user terminal 20> The input device 206 of the first user terminal 20 includes a camera 2061, a microphone 2062, a position information sensor 2063, a motion sensor 2064, and a touch device 2065.

[0036] <Configuration of the output device 208 of the first user terminal 20> The output device 208 of the first user terminal 20 includes a display 2081 and a speaker 2082.

[0037] <Configuration of the second user terminal 30> The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a mobile terminal such as a smartphone or a tablet, or a stationary PC (Personal Computer) or a laptop PC. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type terminal. The second user terminal 30 includes a storage unit 301, a control unit 304, an input device 306, and an output device 308.

[0038] <Configuration of the storage unit 301 of the second user terminal 30> The storage unit 301 of the second user terminal 30 includes a second user ID 3011 and an application program 3012.

[0039] The second user ID 3011 is the account ID of the second user. The second user transmits the second user ID 3011 from the second user terminal 30 to the server 10. The server 10 identifies the second user based on the second user ID 3011 and provides the service according to the present disclosure to the second user. Note that the second user ID 3011 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the second user terminal 30.

[0040] The application program 3012 may be stored in advance in the storage unit 301, or may be configured to be downloaded from a web server or the like operated by a service provider via a communication IF. The application program 3012 includes applications such as a web browser application. The application program 3012 includes an interpreter-type programming language such as JavaScript (registered trademark) that is executed on a web browser application stored in the second user terminal 30.

[0041] <Configuration of the control unit 304 of the second user terminal 30> The control unit 304 of the second user terminal 30 includes an input control unit 3041 and an output control unit 3042. The control unit 304 realizes each functional unit by executing the application program 3012 stored in the storage unit 301.

[0042] <Configuration of the input device 306 of the second user terminal 30> The input device 306 of the second user terminal 30 includes a camera 3061, a microphone 3062, a position information sensor 3063, a motion sensor 3064, and a touch device 3065.

[0043] <Configuration of the output device 308 of the second user terminal 30> The output device 308 of the second user terminal 30 includes a display 3081 and a speaker 3082.

[0044] <Configuration of Online Meeting System 40> The online meeting system 40 is an information processing device that provides an online meeting service that allows multiple users to participate. The online meeting system 40 may be an information processing service operated and provided by a business operator different from the business operator that provides the minutes management service according to the present disclosure. For example, the online meeting system 40 may be an online meeting service such as Zoom, Teams, Google Meet, etc.

[0045] <Operation of System 1> Hereinafter, each process of System 1 will be described. FIG. 11 is a flowchart showing the operation of the minutes creation process. FIG. 12 is a flowchart showing the operation of the minutes viewing process. FIG. 13 is a flowchart showing the operation of the topic viewing process. FIG. 14 is a flowchart showing the operation of the meeting process. FIG. 15 is an example screen showing the operation of the minutes creation process. FIG. 16 is an example screen showing the operation of the document creation process. FIG. 17 is an example screen showing the operation of the topic creation process. FIG. 18 is an example screen showing the operation of the minutes viewing process. FIG. 19 is a first example screen showing the operation of the topic viewing process. FIG. 20 is a second example screen showing the operation of the topic viewing process. FIG. 21 is an example screen showing the operation of the meeting process.

[0046] <Minutes Creation Process> The minutes creation process is a process for a user (such as a meeting organizer, secretary, etc.) who creates minutes in a meeting to create minutes. In the present disclosure, the minutes creation process by the first user will be described as an example. Note that the user who executes the minutes creation process is not limited to the first user, and any user may execute it. In the present disclosure, the case where the minutes creation process is executed after the execution of the meeting process described below will be mainly described, but it is not limited thereto. For example, it may be configured such that the minutes creation process is executed in real time in parallel with the meeting process. Further, the minutes creation process does not necessarily have to be executed manually, and it may be configured to be automatically executed in accordance with the meeting process described below.

[0047] <Overview of Minutes Creation Process> The minutes creation process is a series of processes that create minutes information, create document information, create topic information, set access rights for each topic information, and store the document information in association with the minutes information and the topic information.

[0048] <Details of Minutes Creation Process> The details of the minutes creation process will be described below.

[0049] In step S101, the creation unit 1042 of the server 10 executes a minutes storage step of storing minutes information regarding the minutes of the meeting. Specifically, the first user operates the input device 206 of the first user terminal 20 to input the URL of a page (minutes creation page) for executing the minutes creation process into a web browser or the like, and opens the minutes creation page. The control unit 204 of the first user terminal 20 transmits a request for opening the minutes creation page to the server 10. The control unit 104 of the server 10 generates the minutes creation page based on the received request and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received minutes creation page on the display 2081 of the first user terminal 20.

[0050] FIG. 15 is an example of a screen showing the operation of the minutes creation process. The minutes creation page includes a minutes creation screen D10. The minutes creation screen D10 includes input fields for the meeting name D101, meeting ID D102, holding date and time D103, holding place D104, participant ID D105, and a minutes creation button D11.

[0051] The first user operates the input device 206 of the first user terminal 20 to input a character string related to the name of the meeting into the input field for the meeting name D101. For example, a character string such as the meeting name, title, etc. of the meeting is input into the meeting name D101.

[0052] The first user operates the input device 206 of the first user terminal 20 to input a numerical value or a character string related to the meeting identification information for identifying the meeting into the meeting ID D102. In the meeting ID D102, unique numerical values, character strings, etc. assigned to each held meeting in a meeting operation service, etc. operated and provided by an operator different from the operator providing the minutes management service according to the present disclosure are stored. The meeting ID D102 may store a character string such as a URL for specifying the meeting. Specifically, when the meeting is provided by the online meeting system 40, a character string such as a URL assigned to a virtual meeting room called a room can be used as the meeting identification information.

[0053] The first user operates the input device 206 of the first user terminal 20 to input information regarding the holding period, including the start date and time and the end date and time of the meeting, into the holding date and time D103. Note that only the date information on which the meeting was held may be input into the holding date and time D103.

[0054] The first user operates the input device 206 of the first user terminal 20 to input a character string for specifying the meeting venue, such as the meeting room name, meeting room number, etc., into the meeting venue D104. Note that when the meeting is provided by the online meeting system 40, a character string such as a URL assigned to a virtual meeting room called a room may be input into the meeting venue D104.

[0055] The first user operates the input device 206 of the first user terminal 20 to input the user identification information of the users participating in the meeting into the participant IDD 105. The user identification information includes the user name and the user ID. When a plurality of users participate in the meeting, a plurality of user identification information is input into the participant IDD 105.

[0056] The first user operates the input device 206 of the first user terminal 20 to press the minutes creation button D11. Thereby, the control unit 204 of the first user terminal 20 sends a request for creating minutes, including the meeting name D101, the meeting ID D102, the holding date and time D103, the holding location D104, the input values input into the participant IDD 105, and the first user ID 2011, to the server 10. The creation unit 1042 of the server 10 receives and accepts the request. The creation unit 1042 of the server 10 stores the received meeting name D101, meeting ID D102, holding date and time D103, holding location D104, and participant IDD 105 in the meeting name, meeting ID, holding date and time, holding location, and participant ID items of a new record in the minutes table 1013, and newly assigns a serial number (increments) to the minutes ID. Thereby, minutes information regarding the minutes of the meeting is stored in the minutes table 1013.

[0057] In the present disclosure, the first user is disclosed as an example of a configuration in which the meeting name D101, the meeting ID D102, the holding date and time D103, the holding location D104, and the participant IDD 105 are input by operating the input device 206 of the first user terminal 20. However, it may be configured to be automatically input by analyzing information stored in the online meeting system 40 in which information regarding the held meeting is stored, or information stored in a calendar service provided by other operators. In this case, it may be configured that the minutes information is stored in the minutes table 1013 at any timing such as before the meeting is held, during the meeting, before the meeting ends, at the start of the meeting, and at the end of the meeting. Thereby, the minutes information of a specific meeting is stored in the minutes table 1013 without the user executing an explicit minutes creation process.

[0058] The creation unit 1042 of the server 10 generates a document creation page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received document creation page on the display 2081 of the first user terminal 20.

[0059] In step S102, the creation unit 1042 of the server 10 executes a document storage step of associating and storing a plurality of document information related to each of a plurality of topics discussed in the meeting with the minutes information stored in the minutes storage step.

[0060] FIG. 16 is an example of a screen showing the operation of the document creation process. The document creation page includes a document creation screen D20. The document creation screen D20 includes document information input fields D201, D202, D203 ···, topic buttons D211, D212, D213, and a document creation button D25. The document information input fields D201, D202, D203 each include input fields for a heading text D2011, D2021, D2031, document data D2012, D2022, D2032, access authority D2013, D2023, D2033, start date and time D2014, D2024, D2034, and end date and time D2015, D2025, D2035.

[0061] The first user operates the input device 206 of the first user terminal 20 to input character strings related to the title and heading of the document into the heading texts D2011, D2021, D2031. For example, character strings related to titles indicating a plurality of topics discussed in the meeting, such as "Regarding the next year's budget review", "Regarding the product development plan", and "Regarding the marketing plan", are input into the heading texts D2011, D2021, D2031.

[0062] The first user operates the input device 206 of the first user terminal 20 to input strings such as the content discussed and decisions made into the document data D2012, D2022, and D2032. Note that the document data D2012, D2022, and D2032 may be input fields that can accept any document file such as PDF, Word, or XML.

[0063] The first user operates the input device 206 of the first user terminal 20 to input information defining the access rights to the document data into the access rights D2013, D2023, and D2033. For example, the access rights D2013, D2023, and D2033 may include user identification information for identifying users who can view and refer to the document data, strings for identifying groups such as company names, department names, and organization names, and information related to job positions (job position information). Note that the input for the access rights D2013, D2023, and D2033 may be omitted. In the present disclosure, the access rights to the document information may be determined according to the access rights to the topic information associated with the document information. Specifically, the access rights to the document information may be the access rights to the topic information associated with the document information. When a plurality of topic information is associated with the document information, the access rights based on the logical product or logical sum of the access rights of all the topic information may be used as the access rights to the document information. For example, when one piece of document information is associated with Topic A and Topic B, and the access rights for Topic A are set as "Legal Department" and the access rights for Topic B are set as "Above Department Head", the access rights for the one piece of document information may be set as "Legal Department" AND "Above Department Head" (logical product). Similarly, it may be set as "Legal Department" OR "Above Department Head" (logical sum). In addition, as access rights, it may be set that the organizers and participants of the meeting automatically have access rights to the document information.

[0064] The first user operates the input device 206 of the first user terminal 20 to input the start times D2014, D2024, D2034 and the end times D2015, D2025, D2035 of each topic input in the document information input fields D201, D202, D203 in the meeting respectively.

[0065] In the present disclosure, the first user is disclosed as an example of a configuration in which the first user operates the input device 206 of the first user terminal 20 to input into each input field included in the document information input fields D201, D202, D203, but the present disclosure is not limited thereto. For example, when the meeting is held in the online meeting system 40, it may be configured to automatically input into each input field included in the document information input fields D201, D202, D203 by analyzing voice data, video data, etc. emitted by participants in the meeting held in the online meeting system 40. The creation unit 1042 of the server 10 identifies a plurality of topics included in the voice data by analyzing the voice data. The creation unit 1042 of the server 10 may input each of the plurality of text data obtained by transcribing the voice data for each topic into the document data D2012, D2022, D2032. Note that for the transcription of text data, learning models such as a machine learning model, a deep learning model, and an artificial intelligence model that take voice data as input data and output transcribed text can be used. The creation unit 1042 of the server 10 may automatically extract the titles from the document data D2012, D2022, D2032 and input them into the heading texts D2011, D2021, D2031. For example, the important words in the document data D2012, D2022, D2032 may be input into the heading texts D2011, D2021, D2031. The creation unit 1042 of the server 10 may estimate the access authority by analyzing the content of the voice data and video data, and input the access authorities D2013, D2023, and D2033. For example, a learning model such as a machine learning model, a deep learning model, or an artificial intelligence model that outputs the access authority using the voice data and video data as input data may be used to estimate the input values for the access authorities D2013, D2023, and D2033. The creation unit 1042 of the server 10 may input the start date and time and end date and time of the voice data and video data for each identified topic into the start date and time D2014, D2024, D2034 and the end date and time D2015, D2025, D2035, respectively.

[0066] In step S102, the document storage step includes associating the first document information with the first minutes of the first meeting and associating the second document information with the second minutes of the second meeting. Specifically, the first user operates the input device 206 of the first user terminal 20 to press the document creation button D25. Thereby, the control unit 204 of the first user terminal 20 transmits a request for creating minutes, including the input values entered in the document information input fields D201, D202, D203 and the first user ID 2011, to the server 10. The creation unit 1042 of the server 10 receives and accepts the request. The creation unit 1042 of the server 10 stores the heading text D2011, D2021, D2031, document data D2012, D2022, D2032, access authority D2013, D2023, D2033, start date and time D2014, D2024, D2034, end date and time D2015, D2025, D2035, and the topic ID numbered in step S101 included in the received document information input fields D201, D202, D203 into the heading text, document data, access authority, start date and time, end date and time, and topic ID items of a new record in the document table 1015, and newly assigns (increments) a document ID. Thereby, the document information regarding each topic discussed in the meeting is stored in the document table 1015 in association with the minutes information. In the present disclosure, one document information is stored in association with one minutes of meeting. That is, the first document information is stored in association with the first minutes of meeting regarding the first meeting, and is not associated with the second minutes of meeting regarding the second meeting different from the first meeting. Similarly, the second document information is stored in association with the second minutes of meeting regarding the second meeting, and is not associated with the first minutes of meeting regarding the first meeting different from the second meeting.

[0067] In step S102, the document storage step executes a step of storing, in real time during the holding of the meeting, text information regarding the speech content of the participants as document information in the online meeting system. Specifically, when the meeting is held in the online meeting system 40, the creation unit 1042 of the server 10 may identify text data regarding the speech content of the participants, which is obtained by transcribing the voice data spoken by the participants during the holding of the meeting, by analyzing the voice data in real time during the holding of the meeting. Further, the text data may be stored in the item of the document data in the document table 1015 without waiting for the end of the meeting during the holding of the meeting. Thereby, during the holding of the meeting without waiting for the end of the meeting, the meeting participants can visually confirm and share the content discussed in the meeting as text information. Specifically, during the execution period of the meeting process described later, the document creation process may be executed.

[0068] The first user can press the topic buttons D211, D212, D213 by operating the input device 206 of the first user terminal 20. When the topic buttons D211, D212, D213 are pressed, a request is sent to the server 10 to display a topic creation page for selecting and editing topic information associated with the document information input fields D201, D202, D203 corresponding to the respective topic buttons. Specifically, when the first user operates the input device 206 of the first user terminal 20 to press the topic buttons D211, D212, D213, document IDs corresponding to the document information input fields D201, D202, D203 corresponding to the pressed topic buttons D211, D212, D213 are selected and sent to the server 10. The server 10 receives and accepts the document IDs to be associated in the topic creation process described later. The creation unit 1042 of the server 10 generates a topic creation page and sends it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received topic creation page on the display 2081 of the first user terminal 20.

[0069] In step S103, the creation unit 1042 of the server 10 executes a topic storage step of associating and storing a plurality of document information stored in the document storage step with the topic information regarding the topic.

[0070] FIG. 17 is an example of a screen showing the operation of the topic creation process. The topic creation page includes a topic creation screen D30. The topic creation screen D30 includes topic information input fields D301, D302, D303 ···, a topic addition button D35, a topic selection button D36, and a topic save button D37. The topic information input fields D301, D302, D303 each include input fields for topic content D3011, D3021, D3031, access rights D3012, D3022, D3032, and save buttons D3013, D3023, D3033.

[0071] The first user can add the topic information input fields D301, D302, D303 for inputting new topic information by operating the input device 206 of the first user terminal 20 to press the topic addition button D35. The first user can input a character string for explaining the content of the topic into the topic content D3011, D3021, D3031 by operating the input device 206 of the first user terminal 20. The first user inputs information for defining the access authority to the issue information into the access authorities D3012, D3022, and D3032 by operating the input device 206 of the first user terminal 20. For example, the access authorities D3012, D3022, and D3032 are input with user identification information for identifying users who can view and refer to document data associated with the issue information, a character string for identifying a group such as a company name, department name, and organization name, information regarding a position (position information), and the like. The first user presses the save buttons D3013, D3023, and D3033 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits the issue information input in the issue information input fields D301, D302, and D303 to the server 10. The creation unit 1042 of the server 10 stores the issue contents D3011, D3021, D3031 and the access authorities D3012, D3022, D3032 included in the received issue information in the issue content and access authority items of a new record in the issue table 1014, and newly assigns a serial number (increments) to the issue ID. Thereby, the issue information regarding the issue is stored in the issue table 1014. Note that the issue information may be configured such that only an administrator user having a predetermined authority can create and edit it. For example, the administrator user may be configured to be able to create and edit the issue information stored in the issue table 1014 of the server 10 by accessing an issue editing page or the like provided by the server 10.

[0072] The first user presses the issue selection button D36 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 displays an issue selection dialog for selecting issue information on the display 2081 of the first user terminal 20. Specifically, the control unit 204 of the first user terminal 20 sends a request to the server 10 to obtain a topic. The creation unit 1042 of the server 10 retrieves a plurality of topic information including a topic ID, topic content, and access authority by searching the topic table 1014. The creation unit 1042 of the server 10 sends the retrieved topic information to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received topic information in a selectable manner in a topic selection dialog. The first user selects predetermined topic information from the topic information listed in the topic selection dialog by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 inputs the topic content and access authority included in the selected topic information into the topic content D3011, D3021, D3031 and access authority D3012, D3022, D3032 in the topic information input fields D301, D302, D303. In this case, the first user may also be configured to edit the content of the topic content D3011, D3021, D3031 and access authority D3012, D3022, D3032 by operating the input device 206 of the first user terminal 20, and update (overwrite) the topic content and access authority information in the topic table 1014 by pressing the save buttons D3013, D3023, D3033. Note that the control unit 204 of the first user terminal 20 may display the save buttons D3013, D3023, D3033 on the display 2081 of the first user terminal 20 in a non-selectable manner. That is, the first user may be considered unable to edit the topic information stored in the topic table 1014 of the server 10.

[0073] In step S103, the topic storage step includes a step of associating and storing the first document information associated with the first minutes and the second document information associated with the second minutes different from the first minutes with one topic information. The first user presses the topic save button D37 by operating the input device 206 of the first user terminal 20. As a result, the control unit 204 of the first user terminal 20 sends a request including the topic ID of the topic information input in the topic information input fields D301, D302, and D303 to the server 10. The creation unit 1042 of the server 10 receives and accepts the request. The creation unit 1042 of the server 10 searches for the document ID in the document table 1015 based on the document ID selected in step S102 and stores the received topic ID in the topic ID item of the record specified thereby. As a result, the topic information is stored in association with the document information selected in step S102. In the present disclosure, a plurality of topic information can be stored in association with one document information. Further, for one topic information, document information associated with minutes information in a plurality of different meetings can be associated. As a result, the common discussion content discussed across a plurality of meetings can be efficiently managed in association with a predetermined piece of topic information.

[0074] In step S103, the creation unit 1042 of the server 10 executes a meeting storage step of associating and storing, in one piece of topic information stored in the topic storage step, first meeting identification information for identifying the first meeting and second meeting identification information for identifying the second meeting. Specifically, the topic ID is stored in association with the document ID in the document table 1015. The document ID is stored in association with the minutes ID in the document table 1015. The minutes ID is stored in association with the meeting ID in the minutes table 1013. As a result, the topic information specified by the topic ID is stored in association with the meeting ID of one or a plurality of meetings in which the topic was discussed. As a result, the user can easily grasp in which meetings the topic information includes the discussion content.

[0075] In step S104, the creation unit 1042 of the server 10 executes an issue setting step of setting access authority information for the predetermined issue information stored in the issue storage step. Specifically, the first user can edit the contents of the access authorities D3012, D3022, and D3032 by operating the input device 206 of the first user terminal 20, and update the access authority information of the issue information stored in the issue table 1014 by pressing the save buttons D3013, D3023, and D3033. Note that the setting of the access authority for an issue may be configured such that only an administrator user having a predetermined authority can create and edit it. For example, the administrator user may access an issue editing page or the like provided by the server 10, and may be configured to be able to create and edit the access authority information for each piece of issue information stored in the issue table 1014 of the server 10.

[0076] In step S104, the issue setting step includes a step of issuing a notification prompting the setting of access authority information when the predetermined document information associated with the predetermined issue information includes personal information. Specifically, when the document information selected in step S102 includes at least one or more pieces of personal information such as a person's name, personal number, personal identification information, and restricted access data, the control unit 204 of the first user terminal 20 may display a notification prompting the setting of the access authority information of the issue information on the display 2081 of the first user terminal 20. When a predetermined personal information label, restricted access data label, etc. are set at the location where a person's name, personal number, personal identification information, restricted access data, etc. are described in the document information, the control unit 204 of the first user terminal 20 may identify the label and display a notification prompting the setting of the access authority information of the issue information on the display 2081 of the first user terminal 20. The first user may edit the access rights D3012, D3022, and D3032 of the topic information associated with the document information by operating the input device 206 of the first user terminal 20. Further, the first user may associate the document information with the topic information for which a predetermined access right is set by operating the input device 206 of the first user terminal 20. In addition, the first user may exclude personal information from the document information by operating the input device 206 of the first user terminal 20 to delete the portions including personal information from the document information. Although the configuration for setting the access rights of the topic information is adopted in the present disclosure, a configuration for executing a notification for prompting the setting of the access right information for the document information defined in the document table 1015 may also be adopted. For example, the first user may directly set the access right information of the document information selected in step S102 in the document table 1015 by operating the input device 206 of the first user terminal 20.

[0077] In step S104, when the predetermined document information associated with the predetermined topic information includes personal information, the topic setting step executes a step of setting predetermined access right information for the predetermined topic information. Specifically, when the document information selected in step S102 includes at least one or more pieces of personal information such as a person's name, personal number, personal identification information, and restricted-provided data, the creation unit 1042 of the server 10 may set the access right of the topic information specified based on the topic ID associated in the document table 1015 to a predetermined access right. When predetermined personal information labels, restricted-provided data labels, etc. are set at the locations where a person's name, personal number, personal identification information, restricted-provided data, etc. are described in the document information, the creation unit 1042 of the server 10 may identify the labels and set the access right of the topic information specified based on the topic ID associated in the document table 1015 to a predetermined access right. For example, when personal information or the like is included in the document information, the creation unit 1042 of the server 10 may automatically set the access authority of the issue information associated with the document information to information identifying users who can view personal information such as "only users belonging to the Personnel Department" or "only those at or above the department head level". As a result, a predetermined access authority is automatically set for issues including highly confidential information such as personal information in the document information. It is possible to avoid omitting the setting of access authority for issues including highly confidential information or forgetting to set the access authority. Although the configuration for setting the access authority of the issue information is adopted in the present disclosure, it may also be configured to automatically set the access authority information for the document information defined in the document table 1015. For example, the creation unit 1042 of the server 10 may be configured to automatically set the access authority information of the document information selected in step S102 in the document table 1015.

[0078] In step S104, the issue setting step executes a step of setting predetermined access authority information for predetermined issue information based on the access authority information of other document information referred to or cited by the predetermined document information associated with the predetermined issue information. Specifically, when the document information selected in step S102 by the creation unit 1042 of the server 10 refers to or cites other document information, the access authority of the issue information associated with the selected document information may be set to the access authority of the issue information associated with the other document information. For example, the creation unit 1042 of the server 10 may associate and store, as the issue information associated with the selected document information, the issue information associated with other document information referred to or cited by the document information. As a result, the access authorities of the selected document information and other document information referred to or cited by the document information are the same. Although the configuration for setting the access authority of the issue information is adopted in the present disclosure, it may also be configured to set the access authority information for the document information defined in the document table 1015 to the access authority information of other document information referred to or cited by the document information. Accordingly, a predetermined access right is automatically set for an issue including document information that refers to or quotes highly confidential information such as personal information. It is possible to avoid omitting the setting of the access right for an issue including highly confidential information or forgetting to set the access right.

[0079] <List display process> The list display process is a process of displaying a list of minutes information, issue information, and recommended issue information recommended for the user that are viewable by the user. In the present disclosure, the list display process by the first user will be described as an example. Note that the user who executes the list display process is not limited to the first user, and any user may execute it.

[0080] <Outline of list display process> The list display process is a series of processes of accessing a list display page, acquiring minutes information, acquiring issue information, acquiring recommended issue information, and presenting the acquired minutes information and issue information to the user.

[0081] <Details of list display process> The details of the list display process will be described below.

[0082] Specifically, the first user operates the input device 206 of the first user terminal 20, executes a browser application or the like, and opens a list display page by inputting a URL or the like of a web page (list display page) for executing the list display process. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for opening the list display page to the server 10.

[0083] FIG. 18 is an example screen of a list display screen in the list display process. A list display page is displayed on the display 2081 of the first user terminal 20. The list display page includes a list display screen D40. The list display screen D40 includes a minutes list D41, an issue list D42, and a recommended issue list D43. The minutes list D41 includes minutes D411 and D412. The minutes D411 and D412 include the holding date and time D4111, D4121, the meeting name D4112, D4122, and the minutes display buttons D4113, D4123. The topic list D42 includes topics D421 and D422. The topics D421 and D422 include the final update date and time D4211, D4221, the topic content D4212, D4222, and the topic display buttons D4213, D4223. The recommended topic list D43 includes topics D431 and D432. The topics D431 and D432 include the final update date and time D4311, D4321, the topic content D4312, D4322, and the topic display buttons D4313, D4323.

[0084] When the browsing unit 1043 of the server 10 receives a request, it searches the participant ID item of the minutes table based on the first user ID 2011, and obtains the minutes ID, the meeting name, and the holding date and time. Based on the obtained meeting name and holding date and time, the browsing unit 1043 of the server 10 generates the display contents of the meeting name D4112, D4122, the holding date and time D4111, D4121 in the minutes list D41. As a result, the minutes information of the meetings hosted or participated in by the first user is displayed in a list.

[0085] When the browsing unit 1043 of the server 10 receives a request, it searches the access authority item of the topic table 1014 based on the first user ID 2011, and obtains the topic ID and the topic content included in the topic information accessible to the first user. The browsing unit 1043 of the server 10 searches the topic ID of the document table 1015 based on the obtained topic ID, and obtains the latest start date and time or end date and time (final update date and time) among the document information associated with the topic ID. Based on the obtained topic content and final update date and time, the browsing unit 1043 of the server 10 generates the display contents of the topic content D4212, D4222, the final update date and time D4211, D4221 in the topic list D42. As a result, the topic information accessible to the first user is displayed in a list.

[0086] The viewing section 1043 of server 10 executes a sharing step of presenting, to other users based on evaluation information, the issue information stored in association with the evaluation information in the evaluation storage step. Specifically, when the viewing section 1043 of server 10 receives a request, it searches for the access right item in the issue table 1014 based on the first user ID 2011, and obtains the issue ID and issue content included in the issue information accessible to the first user. The viewing section 1043 of server 10 searches for the issue ID in the document table 1015 based on the obtained issue ID, and obtains the document ID. The viewing section 1043 of server 10 searches for the document ID in the reaction table based on the obtained document ID, and obtains reaction data, user ID, and reaction date and time. The viewing section 1043 of server 10 identifies, as recommended issue information (recommended issue information), a predetermined number of issue information from among a plurality of issue information based on the reaction information associated with the issue information. For example, the viewing section 1043 of server 10 may use, as the recommended issue information, one or a plurality of issue information among the plurality of issue information whose number of pieces of reaction information associated with the issue information is equal to or more than a predetermined number, or a predetermined number of issue information in descending order of the number of pieces of reaction information associated with the issue information. Thereby, the issue information evaluated by various users can be presented to the first user as the recommended issue information. The viewing section 1043 of server 10 generates the display contents of the issue contents D4312, D4322, the final update date and time D4311, and D4321 in the recommended issue list D43 based on the issue contents and the update date and time included in the obtained recommended issue information. Thereby, it is possible to present, to the first user, recommended issue information based on the reaction information. Specifically, it is possible to recommend issues with good reputations from other users.

[0087] The sharing step includes a step of calculating an evaluation index value of the issue information stored in association with the evaluation information in the evaluation storage step based on the evaluation information, and a step of presenting the issue information to other users based on the calculated evaluation index value. Specifically, the browsing unit 1043 of the server 10 calculates an evaluation index value (score) for each piece of issue information based on the reaction information associated with the issue information among a plurality of pieces of issue information. For example, a predetermined point may be assigned to each of the plurality of reaction data, and the sum of the points assigned to the reaction data associated with the issue information for each piece of issue information may be used as the evaluation index value of the issue information. For example, when the reaction data is a rating evaluation such as from 1 to 5 levels, points from 1 to 5 are assigned for each level of the rating evaluation. When the reaction data is a stamp, points from 1 to 5 are assigned for each stamp. When the reaction data is information such as a character string, index values such as a positive degree and a negative degree are calculated according to the content of the character string or the like, and the index values can be pointed as points and assigned to the character string or the like. For example, when the points of the reaction information associated with each piece of document information associated with the issue information in the browsing unit 1043 of the server 10 are "3, 2, 8, 4", the evaluation index value of the issue information is calculated as "17", which is the sum of "3, 2, 8, 4". The browsing unit 1043 of the server 10 may use, as recommended issue information, one or more pieces of issue information among the plurality of pieces of issue information whose evaluation index value is equal to or greater than a predetermined value, or a predetermined number of pieces of issue information in descending order of the evaluation index value of the issue information. Thereby, according to the content of the reaction data evaluated by various users for each piece of issue information and according to the evaluation index value, issue information suitable for the first user can be recommended.

[0088] The sharing step includes a step of calculating the evaluation index value of the issue information such that the influence based on the evaluation information based on the input operation performed at the input timing included in the period during which the issue information was being discussed is greater than the evaluation information based on the input operation performed at the input timing included in the period during which the issue information was not being discussed. Specifically, the browsing unit 1043 of the server 10 searches for the issue ID in the document table 1015 based on the acquired issue ID, and acquires the document ID, start date and time, and end date and time. The browsing unit 1043 of the server 10 searches for the document ID in the reaction table based on the acquired document ID, and acquires the reaction data, user ID, and reaction date and time. When calculating the evaluation index value, the browsing unit 1043 of the server 10 may evaluate the points of the reaction data in which the reaction date and time of the reaction information is included during the period when the issue was being discussed from the start date and time to the end date and time of the document information associated with the reaction information, as being larger than the points of the reaction data in which the reaction date and time is not included during the period when the issue was being discussed from the start date and time to the end date and time of the document information associated with the reaction information. For example, consider the case where the points of the reaction information associated with each document information associated with the issue information are "3, 2, 8, 4". Among these, when the reaction date and time of the reaction information with points "3, 8" is included in the period from the start date and time to the end date and time of the document information associated with the reaction information, the points are set to double, "6, 16". The browsing unit 1043 of the server 10 calculates the evaluation index value of the issue information as "28", which is the sum of "6, 2, 16, 4".

[0089] The browsing unit 1043 of the server 10 transmits the list display screen D40 based on the generated display content to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received list display screen D40 on the display 2081 of the first user terminal 20.

[0090] The first user can execute the minutes viewing process described later based on the minutes information (minutes ID) corresponding to the pressed minutes display buttons D4113 and D4123 by operating the input device 206 of the first user terminal 20 to press the minutes display buttons D4113 and D4123 in the minutes list D41.

[0091] The first user can execute the issue browsing process described later based on the issue information (issue ID) corresponding to the pressed issue display buttons D4213 and D4223 by operating the input device 206 of the first user terminal 20 to press the issue display buttons D4213 and D4223 in the issue list D42. The first user can execute the issue browsing process described later based on the issue information (issue ID) corresponding to the pressed issue display buttons D4313 and D4323 by operating the input device 206 of the first user terminal 20 to press the issue display buttons D4313 and D4323 in the recommended issue list D43.

[0092] <Proceedings browsing process> The proceedings browsing process is a process for a user to view the content of the proceedings. In the present disclosure, the proceedings browsing process by the first user will be described as an example. Note that the user who executes the proceedings browsing process is not limited to the first user, and any user may execute it.

[0093] <Outline of proceedings browsing process> The proceedings browsing process is a series of processes that accesses a proceedings browsing page, obtains proceedings information, obtains document information associated with the proceedings information, and displays the proceedings to the user.

[0094] <Details of proceedings browsing process> The details of the proceedings browsing process will be described below.

[0095] In step S301, the browsing unit 1043 of the server 10 executes an access reception step of receiving an access request from the user for predetermined document information stored in association with predetermined issue information in the issue storage step. The access reception step executes a step of receiving access requests for each of a plurality of pieces of document information. Specifically, the first user operates the input device 206 of the first user terminal 20 to input the URL of a page (minutes viewing page) for executing minutes viewing processing in a web browser or the like, and opens the minutes viewing page. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for opening the minutes viewing page to the server 10. Note that the URL includes a character string of the minutes ID for specifying the minutes to be the target of the minutes viewing processing. The minutes ID may be directly included in the URL, or may be a string converted into a different string by a predetermined encryption process or the like, or any other character string that can specify the minutes ID based on a table (not shown) or the like. The viewing unit 1043 of the server 10 receives and accepts the request received from the first user terminal 20 as a request for a plurality of document information items stored in association with the minutes information. Note that the first user may be configured to receive a message in which a URL including the minutes ID of a meeting hosted or participated in by the first user is described after the end of the online meeting in the meeting processing described later. In this case, the first user can specify the URL related to the minutes viewing processing based on the received message. Further, the first user may specify the URL related to the minutes viewing processing by selecting the minutes display buttons D4113 and D4123 related to the minutes ID of the minutes information to be viewed from the list display screen D40 in which the minutes IDs of the meetings hosted or participated in by the user himself / herself are listed.

[0096] In step S302, the viewing unit 1043 of the server 10 specifies the minutes ID based on the received request. The viewing unit 1043 of the server 10 searches the minutes ID item of the minutes table 1013 based on the specified minutes ID, and acquires the meeting name, meeting ID, holding date and time, holding place, and participant ID.

[0097] In step S303, the browsing unit 1043 of the server 10 searches for the minutes ID in the document table 1015 based on the specified minutes ID, and acquires the items of the topic ID, the heading text, the document data, and the access authority. The browsing unit 1043 of the server 10 searches the topic table 1014 based on the acquired topic ID, and acquires the topic content and the access authority.

[0098] In step S303, the browsing unit 1043 of the server 10 executes an access determination step of determining whether to permit access to the access request received in the access reception step based on the access authority information set in the topic setting step. The access determination step executes a step of determining whether to permit access to each of a plurality of document information. Specifically, the browsing unit 1043 of the server 10 specifies the access authority for each document information based on the access authority acquired from the document table 1015 and the access authority acquired from the topic table 1014. For example, when the access authority for the document information is not set, the access authority for the topic information may be used as the access authority for the document information. Also, when the access authority for the document information is set, the access authority for the document information may be specified by ignoring the access authority for the topic information. Further, the logical product or logical sum of the access authority for the document information and the access authority for the topic information may be used as the access authority for the document information.

[0099] The browsing unit 1043 of the server 10 compares the access authority specified for the document information with the information of the first user (first user information) specified based on the first user ID 2011, and determines whether the first user has the access authority for the document information. Specifically, the viewing unit 1043 of the server 10 searches the user ID item in the user table 1012 based on the first user ID 2011, and obtains the user name, as well as other affiliated organizations, departments, position information, etc. (not shown). If the first user ID 2011, user name, affiliated organization, department, office information, etc. of the first user are not included in the access authority, the heading text and document data items are excluded from the document information.

[0100] In step S304, the viewing unit 1043 of the server 10 executes a minutes presentation step of simultaneously presenting a plurality of document information items stored in association with predetermined minutes information in the document storage step. Specifically, the viewing unit 1043 of the server 10 transmits the obtained minutes information, document information, and topic information to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received minutes information, document information, and topic information on the display 2081 of the first user terminal 20. The control unit 204 of the first user terminal 20 simultaneously presents a plurality of document information items D511, D512, D513 stored in association with the minutes ID of the selected minutes information on the minutes viewing screen D50.

[0101] FIG. 19 is a first screen example showing the operation of the minutes viewing process. The minutes viewing page includes the minutes viewing screen D50. The minutes viewing screen D50 includes the meeting name D501, meeting ID D502, holding date and time D503, holding place D504, participant names D505, document information D511, D512, D513 ···, approval buttons D521, D522, D523. The document information D511 includes the topic content D5111, heading text D5112, document data D5113, start date and time D5114, and end date and time D5115. The document information D512 includes the topic content D5121, start date and time D5124, and end date and time D5125. In the present disclosure, it is assumed that the first user does not have access authority to the document information D512. Document information D513 includes issue content D5131, heading text D5132, document data D5133, start date and time D5134, and end date and time D5135.

[0102] The minutes presentation step is to present the content of one or more document information items that are permitted to be accessed in the access determination step among a plurality of document information items, and not to present the content of one or more document information items that are not permitted to be accessed in the access determination step, and execute the step. The control unit 204 of the first user terminal 20 displays the document information D511 and D513 to which the first user has access rights on the display 2081 of the first user terminal 20, and for the document information D512 to which the first user does not have access rights, excludes information related to the content of the document information, such as the heading text and document data items, and displays it on the display 2081 of the first user terminal 20. Note that the document information D512 may not be configured to be displayed on the minutes viewing screen D50.

[0103] In step S304, the minutes presentation step includes the step of presenting the headings or summaries of one or more document information items that are not permitted to be accessed in the access determination step, and not presenting the content. Specifically, the control unit 204 of the first user terminal 20 displays, on the display 2081 of the first user terminal 20, not the document data but the heading text or a string related to the summary in the document data for the document information D512 to which the first user does not have access rights. Note that the summary of the document data may be specified using a learning model such as a machine learning model, a deep learning model, or an artificial intelligence model that uses audio data and document data as input data and outputs the summary of the document data. Thereby, the user can grasp the summary of the document information without checking the detailed content of the document information for which the user does not have access rights.

[0104] In step S304, the minutes presentation step includes a step of presenting information indicating the amount of information of one or more document information that was not permitted to be accessed in the access determination step, and not presenting the content. Specifically, for the document information D512 for which the first user does not have access authority, the control unit 204 of the first user terminal 20 does not display the document data, and when the first user has access authority, blank characters or a blank area are displayed on the display 2081 of the first user terminal 20 in the area where the document data should be displayed. In addition to the number of characters of the document data, a numerical value, characters, etc. indicating the amount of information of the document information may be displayed on the display 2081 of the first user terminal 20. Thereby, the user can grasp the amount of information such as the amount of text of the document information without confirming the content of the detailed document information for the document information for which the user does not have access authority.

[0105] In step S304, the minutes presentation step executes a step of presenting, in association with one or more document information that was not permitted to be accessed in the access determination step, information identifying a user who can access the one or more document information. Specifically, for the document information D512 for which the first user does not have access authority, the control unit 204 of the first user terminal 20 does not display the document data, and displays on the display 2081 of the first user terminal 20 information identifying a user who can access the document information D512. For example, information such as "User A can view", "The Personnel Department can view", "Those above the department head level can view" may be displayed on the display 2081 of the first user terminal 20. The information displayed on the display 2081 of the first user terminal 20 may include information indicating the authority level of the viewable users such as "Those above the department head level can view". Note that the control unit 204 of the first user terminal 20 can identify the information by analyzing the access authority set for the document information.

[0106] In step S304, the browsing unit 1043 of the server 10 executes an approval reception step of receiving an input operation from the user for each of the plurality of document information stored in the document storage step. Specifically, the first user can press the approval buttons D521 and D523 corresponding to the document information D511 and D512 by operating the input device 206 of the first user terminal 20. Note that the approval button D522 corresponding to the document information D512 for which the first user does not have access permission in the present disclosure is displayed in a non-pressable manner. When the first user presses the approval buttons D521 and D523 by operating the input device 206 of the first user terminal 20, the control unit 204 of the first user terminal 20 transmits an approval request including the document IDs of the document information D511 and D513 corresponding to the approval buttons D521 and D523 and the first user ID 2011 to the server 10. When the browsing unit 1043 of the server 10 receives the approval request, it receives and accepts the approval request regarding the approval of the document information D511 and D513.

[0107] In step S304, the browsing unit 1043 of the server 10 executes an approval storage step of associating and storing information indicating that the document information has been approved by the user with each of the plurality of document information according to the input operation received in the approval reception step. Specifically, the browsing unit 1043 of the server 10 stores the received document ID, the first user ID 2011, and the current date and time in the document ID, verifier ID, and verification date and time items of the confirmation table 1021, respectively. Thereby, the user can independently approve the discussion content for each piece of document information included in the minutes.

[0108] <Agenda Browsing Process> The agenda browsing process is a process for the user to browse the documents included in the agenda. In the present disclosure, the issue browsing process by the first user will be described as an example. Note that the user who executes the issue browsing process is not limited to the first user, and any user may execute it.

[0109] <Overview of Issue Browsing Process> The issue browsing process is a series of processes that accesses an issue browsing page, obtains issue information, obtains document information associated with the issue information, and displays the issue to the user.

[0110] <Details of Issue Browsing Process> The details of the issue browsing process will be described below.

[0111] In step S501, the browsing unit 1043 of the server 10 executes an access reception step of receiving an access request from the user for predetermined document information stored in association with predetermined issue information in the issue storage step. The access reception step executes a step of receiving an access request for each of a plurality of pieces of document information. Specifically, the first user operates the input device 206 of the first user terminal 20 to input the URL of a page (issue browsing page) for executing the issue browsing process into a web browser or the like, and opens the issue browsing page. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for opening the issue browsing page to the server 10. Note that the URL includes a character string of an issue ID for specifying the issue to be the target of the issue browsing process. The issue ID may be directly included in the URL, or may be a character string converted into a different character string by a predetermined encryption process or the like, or any other character string that can specify the issue ID based on a table (not shown) or the like. The browsing unit 1043 of the server 10 receives and accepts the request received from the first user terminal 20 as a request for a plurality of pieces of document information stored in association with the issue information. In addition, the first user may be configured to receive a message containing a URL with the topic ID of the meeting hosted or participated in by the first user after the online meeting ends in the meeting process described below. In this case, the first user can identify the URL for the topic viewing process based on the received message. Alternatively, the first user may identify the URL for the topic viewing process by selecting the topic display buttons D4213 and D4223 related to the topic ID of the topic information to be viewed from the list display screen D40 on which the topic IDs are listed.

[0112] In step S502, the viewing unit 1043 of the server 10 identifies the topic ID based on the received request. The viewing unit 1043 of the server 10 searches the topic ID item of the topic table 1014 based on the identified topic ID and obtains the topic content and access authority. The viewing unit 1043 of the server 10 compares the obtained access authority with the information of the first user (first user information) identified based on the first user ID 2011 to determine whether the first user has the access authority to the topic information. Specifically, the viewing unit 1043 of the server 10 searches the user ID item of the user table 1012 based on the first user ID 2011 and obtains the user name and other information such as the affiliated organization, department, and position information (not shown). If the first user ID 2011, user name, affiliated organization, department, and position information of the first user are not included in the access authority, access to the topic information by the first user is denied and the topic viewing process ends. In this case, a message containing information indicating that the first user does not have the access authority to the topic information may be presented to the first user. If the first user ID 2011, user name, affiliated organization, department, and position information of the first user are included in the access authority, the process proceeds to step S503.

[0113] In step S503, the viewing unit 1043 of the server 10 obtains and accepts the topic ID, topic content, and access authority from the topic table 1014.

[0114] In step S504, the browsing unit 1043 of the server 10 searches for the topic ID in the document table 1015 based on the identified topic ID, and acquires the items of the minutes ID, the heading text, the document data, and the access authority.

[0115] In step S505, the browsing unit 1043 of the server 10 executes a topic presentation step of simultaneously presenting a plurality of document information items stored in association with predetermined topic information in the topic storage step. Specifically, the browsing unit 1043 of the server 10 transmits the acquired topic information and document information to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received topic information and document information on the display 2081 of the first user terminal 20. The control unit 204 of the first user terminal 20 simultaneously presents a plurality of document information items D611, D612, and D613 stored in association with the topic ID of the selected topic information on the topic browsing screen D60.

[0116] FIG. 20 is a second screen example showing the operation of the topic browsing process. The topic browsing page includes the topic browsing screen D60. The topic browsing screen D60 includes the topic content D601, the document information D611, D612, D613 ···, and the reaction button D62. The document information D611, D612, and D613 includes the heading text D6112, D6122, D6132, the document data D6113, D6123, D6133, the start date and time D6114, D6124, D6134, the end date and time D6115, D6125, D6135.

[0117] In step S505, the browsing unit 1043 of the server 10 executes an evaluation reception step of receiving an input operation from the user with respect to the predetermined topic information stored in the topic storage step. The browsing unit 1043 of the server 10 executes an evaluation storage step of associating and storing evaluation information regarding the evaluation by the user with the predetermined topic information according to the input operation received in the evaluation reception step. Specifically, the first user operates the input device 206 of the first user terminal 20 to press the reaction button D62 displayed on the issue browsing screen D60 (reaction operation). Thereby, the first user can indicate his / her own emotions, intentions, opinions, etc. regarding the issue. The control unit 204 of the first user terminal 20 transmits the issue ID, reaction data corresponding to the reaction button D62 pressed by the first user, the first user ID 2011, and the transmission date and time (referred to as the reaction date and time) to the server 10. The browsing unit 1043 of the server 10 stores the received issue ID, reaction data, first user ID 2011, and transmission date and time in the items of issue ID, reaction data, user ID, and reaction date and time in the reaction table 1022. Thereby, the reaction operation by the first user is stored in association with the issue information. In the present disclosure, a configuration in which reactions can be performed by the reaction button D62 for each issue is disclosed as an example. However, a configuration in which reaction buttons are provided for each of the document information D611, D612, D613, and reaction operations can be received for each document information may also be adopted.

[0118] In step S505, the browsing unit 1043 of the server 10 executes a user evaluation step of evaluating the user or the user who evaluates the user regarding the issue based on the input operation received in the evaluation reception step. Specifically, the browsing unit 1043 of the server 10 acquires the document ID, issue ID, reaction data, and user ID stored in the reaction table 1022. The browsing unit 1043 of the server 10 specifies the user (presenter) who presents the content related to the document information and issue information based on the acquired document ID and issue ID by referring to a table (not shown) or the like. Note that, instead of the presenter, the user who is in charge of the work related to the issue information may be specified by referring to a table (not shown) or the like. For example, the user (user in charge of the work) such as the person in charge, the main person in charge, or the person in charge of the work content mentioned in the document information and issue information is specified. The viewing section 1043 of server 10 calculates the evaluation index value of the user regarding the issue based on the acquired reaction data. For example, the number of reactions may be used as the evaluation index value. Alternatively, a predetermined point may be assigned to each of the plurality of reaction data, and the sum of the points assigned to the reaction data for each user may be used as the evaluation index value of the user. The viewing section 1043 of server 10 stores the calculated evaluation index value in the evaluation data item of the record specified by searching the user ID item of user table 1012 based on the user ID of the user to be calculated. Thereby, reaction data can be used for evaluations such as personnel assessment of users. Note that the evaluation of the user who executed the reaction operation rather than the user regarding the issue may be performed based on the reaction data. For example, for a user who actively performs reaction operations on various issues, documents, etc., the reaction data may be used as the evaluation index value of the user.

[0119] In step S505, the viewing section 1043 of server 10 executes a visualization step of presenting a co-occurrence network diagram based on the co-occurrence relationship between the document information and the minutes information associated with the issue information of the issue information stored in the issue storage step. Specifically, the viewing section 1043 of server 10 can draw the relationship between a plurality of issue information as a co-occurrence network by connecting a plurality of issue information having document information commonly associated therewith with links, using the plurality of issue information as each vertex (node). Similarly, the viewing section 1043 of server 10 can draw the relationship between a plurality of issue information as a co-occurrence network by connecting a plurality of issue information having minutes information commonly associated therewith with links, using the plurality of issue information as each vertex (node). The viewing section 1043 of server 10 can display and present the co-occurrence network on the issue viewing screen D60.

[0120] <Meeting Processing> The meeting process is a process for conducting an online meeting that allows multiple users to participate. In an online meeting, a user participating in the meeting can perform a reaction operation to express their intention and opinion regarding the content being discussed. In the present disclosure, the meeting process by the second user will be described as an example. Note that the user who executes the meeting process is not limited to the second user, and any user may execute it.

[0121] <Overview of Meeting Process> The meeting process is a series of processes in which the organizer sets up the online meeting, invites users to the online meeting, holds the online meeting, receives reaction operations from the users involved in the participants, and ends the online meeting.

[0122] <Details of Meeting Process> The details of the meeting process will be described below.

[0123] In step S701, the second user performs the setup for holding an online meeting by operating the input device 306 of the second user terminal 30. Specifically, the second user operates the input device 306 of the second user terminal 30 to input the URL of a page (meeting holding page) for executing the meeting process into a web browser or the like, and opens the meeting holding page. The control unit 304 of the second user terminal 30 transmits a request for opening the meeting holding page to the online meeting system 40. The online meeting system 40 generates the meeting holding page based on the received request and transmits it to the second user terminal 30. The control unit 304 of the second user terminal 30 displays the received meeting holding page on the display 3081 of the second user terminal 30. The second user operates the input device 306 of the second user terminal 30 to input into the input fields such as the title of the online meeting, the description of the meeting content, the start date and time, the end date and time, and the participants provided on the meeting holding page, and transmits the input to the online meeting system 40. The online meeting system 40 stores the received meeting information including the title of the online meeting, the description of the meeting content, the start date and time, the end date and time, and the participants in the storage unit. Note that, in the input field for participants and the like, the email address and the like of the user related to the participant may be input. In the present disclosure, as an example, it is assumed that the users related to the first user and the second user as participants are stored in the storage unit.

[0124] In step S702, the online meeting system 40 transmits a message for inviting the participants stored in step S701 to the online meeting by mail or the like. Specifically, the message includes a character string such as a URL assigned to a virtual meeting room called a room, and meeting information regarding the title, description, start date and time, and end date and time.

[0125] In step S703, at the start date and time of the online meeting, the user related to the participant operates his / her own information processing terminal, launches an application such as a web browser, and selects the URL described in the message received by mail or the like. Specifically, in the present disclosure, the second user operates the input device 306 of the second user terminal 30 to select a URL or the like assigned to the virtual meeting room, and enters the virtual meeting room related to the online meeting room. In addition to the first user, the users invited to the online meeting in step S702 can enter the virtual meeting room. The control unit 304 of the second user terminal 30 displays the meeting screen D70 on the display 3081 of the second user terminal 30.

[0126] FIG. 21 is an example of a screen showing the operation of the meeting process. The conference screen D70 includes participant images D701, D702, D703, ··· that display the videos of multiple participants participating in the online conference, and reaction buttons D711.

[0127] In the present disclosure, as an example, a case where the minutes creation process is executed along with the start of an online conference will be described. Specifically, the online conference system 40 transmits the title of the conference, the URL of the virtual conference room, the start date and time, and the end date and time input in step S701 to the server 10. The creation unit 1042 of the server 10 executes step S101 of the minutes creation process. The creation unit 1042 of the server 10 stores the received title in the item of the meeting name in the new record of the minutes table 1013. The creation unit 1042 of the server 10 stores the received URL in at least one of the meeting ID and the venue of the new record in the minutes table 1013. The creation unit 1042 of the server 10 stores the received start date and time and end date and time in the item of the holding date and time of the new record in the minutes table 1013. Thereby, the user can automatically create minutes information based on the conference information input in step S701 without executing the minutes creation process.

[0128] The online conference system 40 transmits voice data, video data, etc. emitted by participants in the online conference to the server 10. The creation unit 1042 of the server 10 may be configured to automatically input into each input field included in the document information input fields D201, D202, D203 by analyzing the voice data, video data, etc. The creation unit 1042 of the server 10 identifies a plurality of topics included in the voice data by analyzing the voice data. The creation unit 1042 of the server 10 inputs the text data obtained by transcribing the voice data for each topic into the document data D2012, D2022, D2032, respectively. Details have been described in step S102 of the minutes creation, so the description will be omitted.

[0129] In step S704, the evaluation reception step executes a step of receiving an input operation of evaluation information by a user for an online meeting system during the holding of a meeting. Specifically, the second user operates the input device 306 of the second user terminal 30 to press a reaction button D711 displayed on the meeting screen D70 (reaction operation). Thereby, the second user can show his / her own feelings, intentions, opinions, etc. regarding the topic being discussed in the online meeting. The control unit 304 of the second user terminal 30 transmits reaction data corresponding to the reaction button D711 pressed by the second user, the second user ID 3011, and the transmission date and time (referred to as the reaction date and time) to the online meeting system 40. Specifically, the reaction data includes evaluation information regarding information such as a like, a rating evaluation from 1 to 5 levels, icon specification information (stamp) for specifying an icon indicating the user's feelings towards the user's document information, and a character string indicating the user's feelings towards the user's document information. The online meeting system 40 displays the received reaction data on the meeting screen D70, thereby displaying and presenting the reaction shown by a specific participant in a manner that can be referred to by other participants.

[0130] The online meeting system 40 transmits the second user ID 3011, the reaction data, and the reaction date and time received from the second user terminal 30 to the server 10. The creation unit 1042 of the server 10 receives and accepts the second user ID 3011, the reaction data (evaluation information), and the reaction date and time.

[0131] In step S704, the evaluation reception step executes a step of specifying predetermined topic information according to the input timing of the input operation received from the user, and a step of receiving an input operation for the specified predetermined topic information. The evaluation storage step executes a step of associating and storing the user identification information for identifying the user who has performed the input operation of the evaluation information in the online meeting system with the evaluation information for the predetermined topic information. The evaluation reception step executes a step of specifying issue information based on the text information in the document storage step, and a step of specifying predetermined issue information by comparing the speech period of the speech content regarding the text information with the input timing. Specifically, the creation unit 1042 of the server 10 specifies document information corresponding to the topic being discussed at the reaction date and time (the timing of the reaction) based on the reaction date and time. Specifically, the creation unit 1042 of the server 10 searches for the start date and time and the end date and time in the document table 1015, and specifies and acquires document information including the reaction date and time within the period from the start date and time to the end date and time (the speech section of the voice data and video data corresponding to the document information). The creation unit 1042 of the server 10 stores the document ID, reaction data, second user ID 3011, and reaction date and time of the acquired document information in the items of document ID, reaction data, user ID, and reaction date and time in the reaction table 1022. Thereby, the reaction data is stored in association with the user ID of the user who performed the reaction operation and the document ID regarding the topic that was the target of the reaction operation.

[0132] Note that the second user can associate a predetermined issue with the document information by operating the input device 306 of the second user terminal 30 and executing step S103 of the minutes creation process during the meeting. Specifically, in the document table 1015, the issue ID is stored in association with the document ID. Note that the issue information to be associated with the document information may be configured such that the issue ID is automatically specified based on the content of the document information without any operation by the user and is associated with the document information. In this case, when a reaction operation is performed by the second user, based on the document information for which the reaction operation was performed, the creation unit 1042 of the server 10 can identify the topic information associated with the document information as the topic information for which the reaction operation was performed. Also, the creation unit 1042 of the server 10 can consider that a reaction operation has been executed on the topic information. Then, based on the document ID in the reaction table 1022, the user ID, and the topic ID associated with the document ID in the document table 1015, the reaction data includes the topic information, the second user ID 3011 that performed the reaction operation in the online meeting system, and is stored in the storage unit 101 of the server 10 with the reaction data associated therewith.

[0133] <Meeting processing (modification example)> In the present disclosure, as an example of meeting processing, meeting processing related to an online meeting implemented by a plurality of users participating in a virtual meeting room or the like has been described as an example, but it is not limited thereto. For example, it is also applicable to a meeting held by a plurality of participants in an actual meeting room or the like. In that case, instead of the online meeting system, the participants in the meeting place a smart phone or other information processing terminal on which application software for realizing the meeting system is pre-installed at a predetermined location in the meeting room, such as on top of the meeting machine. The information processing terminal can collect the speech content of the meeting participants via an input device such as a microphone. Steps S701 and S702 of the meeting processing can be omitted. In step S703 of the meeting processing, the meeting system may be configured such that minutes creation processing is executed based on the collected voice. Specifically, it may be configured to store the document data transcribed based on the collected voice data in the document table 1015. The meeting system may be configured to identify the user who spoke the document information, together with the document information of the speech content, by comparing the collected voice with a voice pattern or the like registered in advance for each user. The conference system may be configured to receive an input operation of evaluation information via the information processing terminals respectively owned by the users participating in the conference. Thereby, even in a conference that is not an online conference, a reaction operation from the user can be received in the same manner as in step S704 of the conference process. Note that the document data may be configured to be written in real time and stored in the document table 1015. Thereby, the conference system can receive reactions for each topic during the conference.

[0134] <Basic Hardware Configuration of Computer> FIG. 22 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 includes at least a processor 901, a main memory device 902, an auxiliary storage device 903, and a communication IF 991 (Interface). These are electrically connected to each other by a communication bus 921.

[0135] The processor 901 is hardware for executing an instruction set described in a program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0136] The main memory device 902 is for temporarily storing a program and data processed by the program and the like. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0137] The auxiliary storage device 903 is a storage device for storing data and programs. For example, it is a flash memory, an HDD (Hard Disc Drive), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like.

[0138] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard. The network is composed of various mobile communication systems constructed by the Internet, LAN, wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (such as Wi-Fi (registered trademark)) that can be connected to the Internet by a predetermined access point. When connecting wirelessly, communication protocols such as Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. are included. When connecting by wire, the network also includes those directly connected by a USB (Universal Serial Bus) cable, etc.

[0139] Note that all or part of each hardware configuration can be distributed and provided in a plurality of computers 90, and the computers 90 can be virtually realized by connecting them to each other via a network. In this way, the computer 90 is a concept that includes not only a single housing and the computer 90 housed in a case, but also a virtualized computer system.

[0140] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration (Figure 22) of the computer 90 will be described. The computer includes at least functional units of a control unit, a storage unit, and a communication unit.

[0141] Note that the functional units included in the computer 90 can also be realized by distributing all or part of each functional unit to a plurality of computers 90 interconnected by a network. The computer 90 is a concept that includes not only a single computer 90, but also a virtualized computer system.

[0142] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903 and expanding them in the main storage device 902, and executing processing according to the programs. The control unit can realize functional units that perform various information processes according to the types of programs. As a result, the computer is realized as an information processing device that performs information processing.

[0143] The storage unit is realized by the main storage device 902 and the auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Also, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute addition, update, and deletion processing of the data stored in the storage unit according to various programs.

[0144] The database refers to a relational database and is for managing a table in a tabular form structurally defined by rows and columns, and a data set called a master, in association with each other. In a database, a table is called a table, a master, a column of a table is called a column, and a row of a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Normally, a column serving as a primary key for uniquely identifying a record is set for each table and each master, but setting a primary key for a column is not essential. The control unit can cause the processor 901 to add, delete, and update records in a specific table and master stored in the storage unit according to various programs. Also, by storing data, various programs, and various databases in the storage unit, the information processing device and information processing system according to the present disclosure can be regarded as being manufactured.

[0145] Note that the database and master in the present disclosure may include any data structure (such as a list, dictionary, associative array, object, etc.) in which information is structurally defined. The data structure shall also include data that can be regarded as a data structure by combining data with functions, classes, methods, etc. described in any programming language.

[0146] The communication unit is realized by the communication IF991. The communication unit realizes the function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Also, the communication unit can transmit the information output from the control unit to other computers 90.

[0147] <Second Embodiment> Next, the second embodiment will be described. The same reference numerals will be used for the same configurations as in the first embodiment, and the description will not be repeated.

[0148] In the second embodiment, a technique for assisting in continuously conducting various discussions in a meeting with each issue as a unit will be described as follows. (1) Improving the quality of meeting minutes and issues (events for promoting the closing of a meeting) (2) It is common for multiple issues to be discussed in one meeting. By facilitating the setting of access rights for each issue, discussions can be further promoted (setting access rights for meeting minutes and issues) (3) By making it even easier to extract the subject of discussion as an issue as a result of the discussion, the discussion can be promoted (extracting new issues from existing meeting minutes and issues) (4) Making various contents such as text generated by a meeting and video data of the meeting easier to use or refer to (dividing the video data of the meeting and assigning it to issues)

[0149] More specifically, in the second embodiment, the following will be described. (1) Closing event: In a meeting, set up a completion event for the minutes and agenda. This promotes a change in the user's behavior to achieve consensus on the decisions made in the meeting, clarify ToDos, and confirm the sharing permissions for the minutes and agenda. Specifically, a certain time before the end of the meeting (for example, 5 minutes before the meeting ends), in order to prompt the user to input for closing the meeting, perform processing such as making the button prominent to prompt the user to summarize the meeting and organize the ToDos. (2) Confirmation and change of access rights settings in the list of minutes and agenda, and suggestions for access rights settings of minutes and agenda: For the minutes and agenda, set the user's access rights to facilitate the setting of those access rights. This allows meeting participants to refer to the minutes and agenda more appropriately and enables the discussion among meeting participants to proceed more smoothly. Specifically, display the list of agendas, and while selecting an agenda, enable easy setting of access rights for each agenda item. Also, when an arbitrary keyword such as "personnel" is set in the title of the agenda, display a message to suggest to the user whether to automatically change the access rights of the agenda to those with access restrictions or to change them. (3) Creation of new agendas by extracting agendas from minutes and agendas: Facilitate the extraction of new agendas from the content (text, etc.) generated by the user as a result of the meeting. Specifically, select an editable unit (such as a text box) included in the minutes and agenda, display a menu such as "Create as a new agenda", and create a new agenda according to the user's operation. (4) Splitting of meeting videos and meeting audio for each agenda: Enable the splitting of the meeting video data for each agenda.

[0150] FIG. 23 is a diagram showing the flow of processing for generating a closing event for summarizing the meeting in accordance with the expiration of the meeting time.

[0151] In step S2311, the server 10 detects that a predetermined timing before the end of the meeting time has arrived within the time set for the meeting.

[0152] For example, the server 10 accepts access from the first user terminal 20 via a browser or the like, and provides an operation screen for using the minutes management service to the first user terminal 20. The server 10 detects that the time point, for example, 5 minutes before the time when the time set for the meeting ends has arrived, and transmits information for displaying the operation screen to the display 2081 of the first user terminal 20 to the first user terminal 20.

[0153] In step S2321, the first user terminal 20 highlights an operation member for starting a closing event.

[0154] The first user terminal 20 prompts the user to transition to a screen for summarizing the meeting and inputting tasks by, for example, making an operation button for starting a closing event prominent on the operation screen.

[0155] In step S2323, the first user terminal 20 displays a screen for receiving a predetermined input from the user according to the user's operation on the operation member along the purpose of the meeting.

[0156] The first user terminal 20 displays a screen for receiving the above-mentioned predetermined input by, for example, expression methods such as an overlay, a pop-up, and a slide.

[0157] In step S2325, the first user terminal 20 receives a predetermined input from the user along the purpose of the meeting on the closing event screen.

[0158] The first user terminal 20 receives the following inputs as predetermined inputs along the purpose of the meeting. · Input related to the content of the agenda, such as decisions, summaries, etc. for each agenda item of the meeting · Setting of access rights for each agenda item of the meeting · The progress stage (status) of the discussion, such as whether to continue discussing the agenda item of the meeting ("In Discussion"), end the discussion ("Closed"), put the discussion on hold ("Pending"), or not put the discussion on hold but not yet started ("Not Started") · Setting of the ID of other agenda items related to the agenda item of the meeting As described above, the server 10 manages information on the progress stage of the discussion for each agenda item in the agenda table 1014.

[0159] In step S2315, the server 10 stores the content of the input received from the user in the document table 1015 and the agenda table 1014 in association with the meeting document and the agenda item of the meeting.

[0160] FIG. 24 is a diagram showing an example of a screen for displaying the meeting schedule and the agenda items associated with the meeting and receiving input such as the results of the meeting.

[0161] The agenda display screen 2401 is an area for displaying a list of agenda items related to the meeting.

[0162] The agenda display screen 2401 is an area that receives an operation to save as a document associated with the meeting by receiving input such as text from the user and uploading a file in addition to the agenda items associated with the meeting.

[0163] The meeting display screen 2402 is a screen for displaying each meeting.

[0164] The meeting display screen 2402 displays each meeting set for the user, for example, arranged in chronological order, by displaying the result of reading each schedule set in the user's calendar tool.

[0165] The supplementary display screen 2403 is an area for displaying various types of information associated with the meeting.

[0166] The meeting information 2411 is an area for displaying the information of the meeting designated for the user.

[0167] As the meeting information, the meeting information 2411 displays, as shown in the figure, the name of the meeting, the time zone in which the meeting is set, the remaining time of the meeting compared with the current time, etc.

[0168] The closing event button 2412 is an operation member for receiving an input from the user for organizing the content of the meeting.

[0169] The closing event button 2412 is an operation member for displaying a screen for making an input (such as summarization) in accordance with the purpose of the meeting by means of a slide, a pop-up, etc., in response to the user's operation on the button.

[0170] The access authority 2413 is an area for displaying the access authority of the document associated with the meeting.

[0171] The topic addition button 2414 is an operation member for receiving an input operation from the user for adding a topic associated with the meeting.

[0172] The topic addition button 2414 is an operation member for displaying an input field for receiving an input of a new topic so as to follow the topics 2415 and 2416, in response to the user's operation on the button.

[0173] The topic 2415 is an area for displaying the information of the topic associated with the meeting.

[0174] In the illustrated example, the topic 2415 is displayed as "private" and includes information indicating that the access authority of the topic is limited to some users.

[0175] The topic 2416 is an area for displaying the information of the topic associated with the meeting.

[0176] Issue 2416 is displayed as "public" in the illustrated example, and includes information indicating that the access right to the issue is not restricted, for example, the viewing right to the issue is set for the participants of the meeting.

[0177] Issue 2416 is displayed in a different manner (highlighting the frame) from Issue 2415 which is another issue, indicating that the user is in the process of editing.

[0178] Meeting 2421 is an area for displaying the content of each meeting assigned to the user.

[0179] Meeting 2421 is displayed as "ended" in the illustrated example, and includes a display indicating that the end time of the meeting has passed at the current time.

[0180] Meeting 2422 is an area for displaying the content of each meeting assigned to the user.

[0181] Similar to Meeting 2421, Meeting 2422 is displayed as "ended" in the illustrated example, and includes a display indicating that the end time of the meeting has passed at the current time.

[0182] Meeting 2423 is an area for displaying the content of each meeting assigned to the user.

[0183] Meeting 2423 is displayed as "in progress" in the illustrated example, and includes a display indicating that it is a meeting that the user should participate in at the current time.

[0184] Meeting 2423 is displayed in a different manner (for example, in an emphasized manner such as making the frame prominent) from Meeting 2421, Meeting 2422, and Meeting 2424, indicating that the said Meeting 2423 is in progress.

[0185] Meeting 2424 is an area for displaying the content of each meeting assigned to the user.

[0186] In the illustrated example, meeting 2424 includes a display indicating that it is still in a state before the meeting is held at the current time.

[0187] Meeting type 2431 is an area for displaying information related to the nature and content of the meeting, such as the attributes of the meeting and the type of the meeting.

[0188] Meeting type 2431 displays, as information related to the nature and content of the meeting, for example, the results of receiving the following specifications from the user. · Meeting for decision-making · Meeting for regular reporting · Meeting for the respective department's work

[0189] Meeting name 2432 is an area for displaying the name set for the meeting.

[0190] Related topic 2433 is an area for displaying topics set as related to the meeting, separate from the topics discussed in the set meeting.

[0191] Related topic 2433 may also be an operation area for receiving an input operation for designating other topics associated with the meeting.

[0192] Tag 2434 is an area for displaying any tags set by the user.

[0193] Tag 2434 may also be an operation area for receiving an input operation for designating tags associated with the meeting.

[0194] Figure 25 is a diagram showing an example of a screen of a process for emphasizing a button as a notification for starting a closing event before the end of the meeting time.

[0195] The closing event button 2412 is made prominent by, for example, emphasizing its border line as compared to the situation in Fig. 24, and thus emphasizes and displays the existence of the closing event button 2412 to the user.

[0196] The closing event button 2412 thus serves to notify the user and prompt an input in line with the purpose of the meeting.

[0197] The meeting information 2411 displays the information on the remaining time of the meeting as described above. In the example of Fig. 25, it shows a situation where the remaining time of the meeting is a certain time before the end of the meeting (for example, 5 minutes before the end of the meeting).

[0198] Fig. 26 is a diagram showing an example of a screen for receiving an input such as a summary of the meeting from the user in a closing event. For example, when the user performs an input operation on the closing event button 2412, the server 10 presents the user with the closing event input screen 2404 shown in Fig. 26.

[0199] The closing event input screen 2404 is a screen for receiving an input from the user in line with the purpose of the meeting in a closing event.

[0200] The supplementary information input screen 2405 is a screen for receiving a specification of various types of information associated with the meeting from the user in a closing event.

[0201] The meeting information 2441 is an area for displaying the information on the meeting specified by the user.

[0202] The situation 2442 is an area for displaying the situation of the meeting.

[0203] The situation 2442 displays, for example, the following as the situation of the meeting. · Before start (before the time of the meeting) · In progress (within the time set for the meeting) · During the closing event (when accepting an operation from the user to start the closing event) · End (after the meeting has ended)

[0204] Access authority 2443 is an area for setting access rights to view or edit topics, documents (minutes), etc. associated with a meeting.

[0205] Access authority 2443 displays users with access rights by showing icons of users with access rights. Also, in response to a user's input operation to access authority 2443, a screen for setting access rights may be displayed.

[0206] Discussion status 2444 is an area for accepting the specification of the progress of discussions carried out in a meeting.

[0207] Discussion status 2444 displays, for example, the following as the discussion status. · In progress · Ended · Not started

[0208] Discussion type 2445 is an area for accepting the setting of the type of discussion carried out in a meeting.

[0209] Discussion type 2445 accepts the following specifications as the types of discussions set in a meeting. · Sharing (sharing reporting items, etc. with meeting participants) · Resolution (resolving issues such as operation methods, transactions, and procedures related to budget execution) · Idea generation (for the purpose of brainstorming, etc.)

[0210] Task setting 2446 is an area for setting tasks for each person in charge as a result of a meeting.

[0211] Task setting 2446 accepts the following inputs as task settings. · Content of the task · Person in charge of the task · Deadline of the task

[0212] Server 10 may be configured such that, in task setting 2446, the person in charge of the task can be limited to the following users only. · Users with access rights set for information on documents related to the meeting · Users with access rights set for information on topics related to the meeting · Users participating in the meeting For example, in task setting 2446, when a user sets the person in charge of the task, by presenting the candidates limited to the above users, the person in charge of the task can be set more easily than when presenting candidates without such limitations.

[0213] Summary setting 2447 is an area for inputting summaries such as conclusions, summaries, and next actions obtained from discussions in the meeting.

[0214] Meeting setting button 2451 is an area for receiving an operation to associate another meeting with the meeting related to the closing event.

[0215] Meeting setting button 2451 may receive an operation to associate the meeting while displaying another meeting that is a candidate for association in the vicinity. Here, another meeting that is a candidate for association may be as follows. · Another meeting with the same or similar meeting name · Another meeting with a certain degree of overlap in meeting participants

[0216] Topic setting button 2452 is an area for receiving an operation from the user to associate a topic with the meeting related to the closing event.

[0217] The issue setting button 2452 may also accept an operation to associate an issue while displaying candidate issues to be associated in the vicinity. Here, the candidate issues to be associated may be as follows. · Refer to the information of the participants in each meeting, and an issue associated with another meeting where the participants of the meeting overlap to a certain extent

[0218] The tag setting button 2453 is an area for accepting from the user the setting of an arbitrary tag for the meeting related to the closing event.

[0219] The tag setting button 2453 may also accept an operation to associate a tag while displaying candidate tags to be associated in the vicinity. Here, the candidate tags to be associated may be as follows. · Refer to the information of the participants in each meeting, and a tag associated with another meeting where the participants of the meeting overlap to a certain extent

[0220] FIG. 27 is a diagram showing an example of a screen that emphasizes input items such as a summary of a meeting on the closing event screen. The server 10 detects that a certain time before the end of the meeting time (for example, 5 minutes before) arrives, and displays a prompt for the user to input in accordance with the purpose of the meeting as follows.

[0221] The situation 2442 indicates that it is in the state of the closing event as compared with the situation in FIG. 26.

[0222] The access authority 2443 is made prominent by, for example, emphasizing the frame line as compared with the situation in FIG. 26, and prompts the user to set the access authority for documents (minutes) associated with the meeting.

[0223] The discussion status 2444 is made prominent by, for example, emphasizing the frame line as compared with the situation in FIG. 26, and prompts the user to check the progress of the discussion and make appropriate changes.

[0224] The task setting 2446, as compared with the situation in FIG. 26, has an expression that makes it stand out, such as by emphasizing the frame line, and prompts the user to input the tasks that have arisen as a result of the discussion.

[0225] The summary setting 2447, as compared with the situation in FIG. 26, has an expression that makes it stand out, such as by emphasizing the frame line, and prompts the user to input the summary of the discussion and the like.

[0226] FIG. 28 is a diagram showing an example of a screen that displays a list of topics associated with the minutes of a meeting.

[0227] The topic list screen 2801 is a screen for displaying a list of topics based on a document associated with the minutes and accepting the setting of access rights.

[0228] The minutes name 2811 is an area for displaying the name of the meeting associated with the minutes.

[0229] The batch setting section 2812 is an area for accepting an operation of collectively setting the respective access rights of the participants in the meeting associated with the minutes for a plurality of topics based on the document associated with the minutes.

[0230] The topic 2813 is an area for displaying information on individual topics.

[0231] The topic 2813 displays the following as information on individual topics. · The name of the topic · The viewing setting of the topic (public: can be viewed without restrictions within the company, etc., limited: there are restrictions on the range of members who can view, workplace: can be viewed by an arbitrarily set group) · Whether the topic can be updated (only viewable or editable) · Information on users who have access rights to the topic (user profile, number of people, etc.)

[0232] Issue 2814 is an area for displaying information on individual issues.

[0233] Issue 2815 is an area for displaying information on individual issues.

[0234] The permission setting section 2816 is an area for receiving an operation to add access permissions for a specified minutes or issue.

[0235] In the illustrated example, since the minutes are specified by the user, the permission setting section 2816 is receiving an operation to add access permissions to the minutes.

[0236] The editable user list 2817 is an area for displaying a list of users who can edit a specified minutes or issue.

[0237] In the illustrated example, since the minutes are specified by the user, the editable user list 2817 is displaying a list of users who can edit the name, access permissions, etc. of the minutes. Also, the editable user list 2817 distinguishes and displays participants in the meeting associated with the minutes and those who are not.

[0238] The accessible user list 2818 is an area for displaying a list of users who can view a specified minutes or issue.

[0239] In the illustrated example, since the minutes are specified by the user, the accessible user list 2818 is displaying a list of users who can view the minutes.

[0240] Figure 29 is a diagram showing an example of receiving from a user the setting of access permissions for a specific issue.

[0241] Issue 2814, compared with the situation in FIG. 28, uses an expression that makes it stand out, such as by emphasizing the frame line, making it easy for the user to recognize that it is an issue for which access rights are to be set.

[0242] In the illustrated example, since an issue has been specified for the user, the permission setting unit 2816 accepts an operation to add access rights to the issue.

[0243] In the illustrated example, since an issue has been specified for the user, the editable user list 2817 displays a list of users who can edit the issue.

[0244] In the illustrated example, since an issue has been specified for the user, the accessible user list 2818 displays a list of users who can view the issue.

[0245] FIG. 30 is a diagram showing an example of a screen that displays issues that a user can view based on access rights set for each issue.

[0246] The permission list screen 3001 for each issue is a screen for displaying a list of access rights set for each issue.

[0247] The permission list screen 3001 for each issue displays a list of issues for which access rights are set for each target for which rights are set. Examples of targets for which rights are set are as follows. · Meeting participants · Specific groups (such as departments) · Specific users

[0248] The issue list 3021 for meeting participants is an area that displays a list of issues for which access rights are set for meeting participants.

[0249] The issue list 3021 for meeting participants displays a list of issues for which access rights are set for specific meeting participants, for example, in the following order. · Meeting time series · Number of reactions to topics (e.g., in descending order of the number of reactions) · Number of views of topics

[0250] The topic list 3022 of the Personnel Department is an area that displays a list of topics for which access rights are set for the Personnel Department.

[0251] The topic list 3022 of the Personnel Department displays a list of topics for which access rights are set for a specific group of users, for example, users in the Personnel Department, in the following order, for example. · Meeting time series · Number of reactions to topics (e.g., in descending order of the number of reactions) · Number of views of topics

[0252] Figure 31 is a diagram showing the flow of a process for creating a new topic based on arbitrary content such as text selected by the user.

[0253] In step S3111, the server 10 presents a screen for editing a document or topic associated with the minutes of a meeting to the user.

[0254] In step S3121, the first user terminal 20 accepts an operation for editing a document or topic.

[0255] In step S3123, the first user terminal 20 displays a menu in response to an operation of selecting content such as text included in the document or topic.

[0256] When the first user terminal 20 accepts an operation from the user to specify a range such as text or an image included in a document or topic, for example, the first user terminal 20 displays a menu. In the menu, the first user terminal 20 displays an operation area for accepting an operation of "creating a new topic".

[0257] In step S3125, the first user terminal 20 receives from the user an input operation for creating a new topic based on the selected content.

[0258] In step S3115, the server 10 creates a new topic based on the content of the input received from the user and updates the database.

[0259] The server 10 generates a topic ID in response to the operation of creating a new topic, and updates the topic table 1014 with the content such as the text selected by the user as the topic content.

[0260] The server 10 may set the access rights for the new topic as follows. · Set the access rights in the topic table 1014 so as to inherit the access rights of the document or topic that was the source for creating the new topic · Assume that only the creator of the new topic is the user with access rights to the topic, and furthermore, display prompting for changing the access rights to the user having the access rights. · Set the access rights for the new topic in a form where there is no particular viewing restriction within the organization.

[0261] The server 10 updates the document table 1015 by inheriting the minutes ID, document ID, etc. associated with the document or topic that was the source for creating the new topic and associating the newly generated minutes ID.

[0262] FIG. 32 is a diagram showing an example of a screen of a process for creating a new topic based on arbitrary content selected by the user.

[0263] The screen 3201 is a screen for displaying the content of the topic.

[0264] The user's selection range 3211 is a selection range selected by the user through an operation of specifying a range or the like for the content such as text included in the issue. As shown in the figure, in the user's selection range 3211, the text is underlined, indicating that it is the range selected by the user.

[0265] The menu 3212 is an area that displays operations possible for the content included in the selection range.

[0266] In the example shown in the figure, in the menu 3212, the following operations are accepted for the content specified by the user. · Deletion: Delete the selected content from the issue · Duplication: Duplicate the selected content within the issue · Creation of a new issue: Generate a new issue based on the selected content

[0267] In the example shown in the figure, the server 10 displays the menu 3212 in the vicinity of the user's selection range 3211, and the user selects "Creation of a new issue" in the menu 3212.

[0268] Figure 33 is a diagram showing the flow of a process of splitting the video data of a meeting and associating the video data with each issue.

[0269] In step S3311, the server 10 presents a screen for editing the video data of the meeting to the user.

[0270] In step S3321, the first user terminal 20 accepts an operation of splitting the video data of the meeting in time series.

[0271] In step S3323, the first user terminal 20 accepts an operation of associating the split video data of the meeting with the issue.

[0272] For example, the first user terminal 20 receives, from the user, an operation of associating topics with each of the divided video data of the meeting.

[0273] In step S3325, the first user terminal 20 receives an operation of setting access rights to the divided video data of the meeting.

[0274] In step S3315, the server 10 updates the database by associating topics with the divided video data based on the content of the input received from the user. The functions realized by the components described in this specification may be implemented in circuitry or processing circuitry including a general-purpose processor, a specific-purpose processor, an integrated circuit, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the described functions. The processor includes transistors and other circuits and is regarded as circuitry or processing circuitry. The processor may be a programmed processor that executes a program stored in a memory. In this specification, circuitry, unit, and means are hardware programmed to realize the described functions or hardware that executes the functions. The hardware may be any hardware disclosed in this specification or any hardware known as being programmed or executing to realize the described functions. When the hardware is a processor regarded as the type of circuitry, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or the processor.

[0275] <Appendix> The matters described in each of the above embodiments are appended below.

[0276] (First Embodiment) (Appendix 1) A minutes management program for causing a computer including a processor and a storage unit to manage minutes of a meeting, wherein the processor executes: a minutes storage step (S101) of storing minutes information regarding the minutes of the meeting; a document storage step (S102) of storing a plurality of document information related to each of a plurality of topics discussed in the meeting in association with the minutes information stored in the minutes storage step; and a topic storage step (S103) of storing the plurality of document information stored in the document storage step in association with topic information regarding the topic. The document storage step (S102) includes a step of associating first document information with first minutes regarding a first meeting and a step of associating second document information with second minutes regarding a second meeting. The topic storage step (S103) includes a step of storing, in association with one topic information, the first document information associated with the first minutes and the second document information associated with second minutes different from the first minutes. Thereby, when discussions are made across a plurality of meetings regarding a predetermined topic, a plurality of document information in which the discussion content is described can be stored in association with the predetermined topic information. Thereby, common discussion content discussed across a plurality of meetings can be efficiently managed in association with predetermined topic information. For example, when discussions are made across a plurality of meetings regarding a specific topic, the discussion content and the like regarding the topic can be tracked and confirmed for each topic.

[0277] (Appendix 2) The minutes management program described in Appendix 1 executes an issue setting step (S104) in which the processor sets access authority information for predetermined issue information stored in the issue storage step, an access reception step (S301, S501) in which the program receives an access request from the user for predetermined document information stored in association with the predetermined issue information in the issue storage step, and an access determination step (S303, S502) in which the program determines whether to permit access to the access request received in the access reception step based on the access authority information set in the issue setting step. As a result, it is possible to independently set access authority for each issue regarding an issue discussed across a plurality of meetings with respect to a predetermined topic. Without setting access authority for individual documents, it is possible to efficiently set access authority in units of issues.

[0278] (Appendix 3) The issue setting step (S104) of the minutes management program described in Appendix 2 includes a step of issuing a notice prompting the setting of access authority information when the predetermined document information associated with the predetermined issue information includes personal information. As a result, the user can check an issue including information with high confidentiality such as personal information, and can set access authority as necessary.

[0279] (Appendix 4) Personal information is at least one or more of a person's name, personal number, personal identification information, and restricted access data in the minutes management program described in Appendix 3. As a result, the user can check an issue including information with high confidentiality such as a person's name, personal number, personal identification information, and restricted access data, and can set access authority as necessary.

[0280] (Appendix 5) The issue setting step (S104) is the step of setting predetermined access authority information for predetermined issue information when predetermined document information associated with the predetermined issue information includes personal information, as described in Appendix 2 of the minutes management program. Thereby, predetermined access authority is automatically set for an issue including document information with high confidentiality such as personal information. It is possible to omit the setting of access authority for an issue including highly confidential information or avoid forgetting to set the access authority.

[0281] (Appendix 6) The issue setting step (S104) is the step of setting predetermined access authority information for predetermined issue information based on the access authority information of other document information referred to or cited by the predetermined document information associated with the predetermined issue information, as described in Appendix 2 of the minutes management program. Thereby, predetermined access authority is automatically set for an issue including document information that refers to or cites document information with high confidentiality such as personal information. It is possible to omit the setting of access authority for an issue including highly confidential information or avoid forgetting to set the access authority.

[0282] (Appendix 7) The processor executes an issue presentation step (S505) of simultaneously presenting a plurality of document information stored in association with predetermined issue information in the issue storage step, as described in Appendix 1 of the minutes management program. Thereby, the user can check at once the discussion contents discussed across a plurality of meetings for each issue of a plurality of topics discussed in a meeting, rather than for each meeting.

[0283] (Appendix 8) The processor executes a minutes presentation step (S304) of simultaneously presenting a plurality of document information items stored in association with predetermined minutes information in a document storage step. The access reception step (S301) is a step of receiving an access request for each of the plurality of document information items. The access determination step (S303) is a step of determining whether to permit access to each of the plurality of document information items. The minutes presentation step (S304) presents the contents of one or more document information items permitted to be accessed in the access determination step among the plurality of document information items, and does not present the contents of one or more document information items not permitted to be accessed in the access determination step. This is the minutes management program described in Supplementary Note 2. Accordingly, the access authority for each of the plurality of document information items included in the minutes information regarding a predetermined meeting is set according to the access authority information for the topic information associated with each of the plurality of document information items. The user can omit setting the access authority for each document information item included in the minutes information or avoid forgetting to set the access authority.

[0284] (Supplementary Note 9) The minutes presentation step (S304) of the minutes management program described in Supplementary Note 8 includes a step of presenting the headings or outlines of one or more document information items not permitted to be accessed in the access determination step and not presenting the contents. Accordingly, the user can grasp the outline of the document information without checking the contents of the detailed document information for the document information without access authority.

[0285] (Supplementary Note 10) The minutes presentation step (S304) of the minutes management program described in Supplementary Note 8 includes a step of presenting information indicating the amount of information of one or more document information items not permitted to be accessed in the access determination step and not presenting the contents. As a result, the user can grasp the amount of information such as the number of characters in the document information without checking the details of the document information for which they do not have access rights.

[0286] (Appendix 11) The minutes presentation step (S304) is a step of presenting, in association with one or more pieces of document information that were not permitted to be accessed in the access determination step, information identifying a user who can access the one or more pieces of document information, as described in Appendix 8 of the minutes management program. As a result, the user can confirm who can access the document information for which they do not have access rights. For example, the user can inquire about the content of the document information to the user who can access it. Note that the information for identifying an accessible user includes information indicating that a person with a predetermined position or higher (e.g., department head or higher) can access, information indicating that a person who is a participant in the meeting related to the predetermined minutes can access, and the like.

[0287] (Appendix 12) A meeting storage step (S103) in which the processor stores, in association with one piece of issue information stored in the issue storage step, first meeting identification information for identifying a first meeting and second meeting identification information for identifying a second meeting, as described in Appendix 1 of the minutes management program. As a result, the user can easily grasp in which meetings the issue information was discussed.

[0288] (Appendix 13) An approval reception step (S304) in which the processor receives an input operation from the user for each of a plurality of pieces of document information stored in the document storage step, and an approval storage step (S304) in which, in response to the input operation received in the approval reception step, information indicating that the document information has been approved by the user is stored in association with each of the plurality of pieces of document information, as described in Appendix 8 of the minutes management program. As a result, the user can approve the discussion content for each document information included in the minutes of the meeting.

[0289] (Appendix 14) An evaluation reception step (S505) in which a processor receives an input operation from a user for predetermined issue information stored in the issue storage step, and an evaluation storage step (S505) in which evaluation information regarding the evaluation by the user is associated with and stored in the predetermined issue information in response to the input operation received in the evaluation reception step. The minutes management program described in Appendix 1. As a result, it is possible to grasp based on the evaluation information which issues the user's interests and concerns are concentrated on. It is possible to grasp the degree of the user's interests and concerns in units of issues, rather than in units of meetings.

[0290] (Appendix 15) The evaluation reception step (S704) is a step of receiving an input operation of evaluation information from the user for the conference system during the holding of the meeting. The minutes management program described in Appendix 14. As a result, the user can associate and store reactions such as reactions made in online meeting services such as Zoom, Teams, and Google Meet as evaluation information with respect to the issue.

[0291] (Appendix 16) The evaluation storage step (S704) is a step of associating and storing user identification information for identifying the user who has performed the input operation of the evaluation information in the conference system and the evaluation information with respect to the predetermined issue information. The minutes management program described in Appendix 15. As a result, it is possible to identify the user who has performed the input operation for each piece of evaluation information as to who has performed the input operation of the evaluation information.

[0292] (Appendix 17) The evaluation reception step (S704) executes a step of specifying predetermined issue information according to the input timing of an input operation received from a user, and a step of receiving an input operation for the specified predetermined issue information. The minutes management program described in Appendix 15. As a result, when the user makes a reaction such as a reaction in an online meeting service, the issue is automatically specified according to the timing of the reaction, and the evaluation information can be stored in association with the issue. Without performing a selection operation or the like on the issue information, the user can store the reaction to the issue information as evaluation information.

[0293] (Appendix 18) The document storage step (S102) is a step of storing text information regarding the speech content of participants in a meeting system as document information in real time during the holding of the meeting. The evaluation reception step (S704) executes a step of specifying issue information based on the text information in the document storage step, and a step of specifying predetermined issue information by comparing the speech period and the input timing of the speech content regarding the text information. The minutes management program described in Appendix 17. As a result, the speech content during the online meeting is automatically transcribed as text information and stored as document information. Issues are automatically specified based on the text information, and for the issues

[0294] (Appendix 19) The processor executes a sharing step of presenting the issue information stored in association with the evaluation information in the evaluation storage step to other users based on the evaluation information. The minutes management program described in Appendix 14. As a result, for issues with active evaluations such as reactions, recommendations (recommendations) etc. can be made to other users. For example, a good issue with an active discussion can be shared with other members within the company. Other members can check the content of the good issue and also grasp the meeting etc. where the issue was discussed.

[0295] (Appendix 20) The sharing step includes: a step of calculating an evaluation index value of issue information stored in association with evaluation information in the evaluation and storage step based on the evaluation information; and a step of presenting the issue information to other users based on the calculated evaluation index value. The minutes management program described in Appendix 19 Accordingly, it is possible to identify an issue for making a recommendation or the like to other users based on the evaluation index value calculated according to an evaluation such as a reaction. Also, it is possible to score the usefulness or the like of the issue itself by the evaluation index value.

[0296] (Appendix 21) The sharing step includes a step of calculating an evaluation index value of issue information such that an influence based on evaluation information based on an input operation performed at an input timing included in a period during which the issue information was being discussed is greater than an influence based on evaluation information based on an input operation performed at an input timing included in a period during which the issue information was not being discussed. The minutes management program described in Appendix 20 When calculating the evaluation index value of an issue, by making the influence of the reaction by a user participating in the meeting greater than the influence of the reaction by a user who did not participate in the meeting and later checked the content, it is possible to encourage active participation in the meeting. Also, it is possible to evaluate more highly an issue that received a reaction by a reaction in the meeting.

[0297] (Appendix 22) The processor executes a user evaluation step (S505) of evaluating a user or a user who evaluates a user related to an issue based on an input operation received in the evaluation reception step. The minutes management program described in Appendix 14 Accordingly, it is possible to positively evaluate a user who actively makes a reaction or the like in the meeting as a user who actively participates in the meeting.

[0298] (Appendix 23) The recording management program according to Supplementary Note 1, wherein the processor executes a visualization step (S505) of presenting a co-occurrence network diagram based on the co-occurrence relationship of document information or minutes information associated with the issue information stored in the issue memory step for the issue information stored in the issue memory step. Thereby, the relationship between issues can be visually overviewed based on the co-occurrence network diagram. Other issues highly relevant to a specific issue can be referred to and confirmed.

[0299] (Supplementary Note 24) An information processing apparatus including a processor and a memory unit, wherein the processor executes a minutes recording step (S101) of storing minutes information regarding the minutes of a meeting, a document storage step (S102) of storing a plurality of document information related to each of a plurality of topics discussed in the meeting in association with the minutes information stored in the minutes recording step, and an issue storage step (S103) of storing the plurality of document information stored in the document storage step in association with issue information regarding an issue, and the document storage step (S102) includes a step of associating first document information with a first minutes for a first meeting and a step of associating second document information with a second minutes for a second meeting, and the issue storage step (S103) includes a step of storing, in association with one issue information, the first document information associated with the first minutes and the second document information associated with a second minutes different from the first minutes. Thereby, when discussions span multiple meetings regarding a predetermined topic, a plurality of document information containing the discussion content can be stored in association with the predetermined issue information. Thereby, the common discussion content spanning multiple meetings can be efficiently managed in association with the predetermined issue information. For example, when discussions span multiple meetings regarding a specific issue, the discussion content for the issue can be tracked and confirmed for each issue.

[0300] (Supplementary Note 25) A method for manufacturing an information processing system including an information processing apparatus having a processor and a storage unit, the method including the step of providing, to the information processing apparatus, the minutes management program according to any one of Appendices 1 to 23. Accordingly, when discussions span multiple meetings regarding a predetermined topic, a plurality of document information in which the discussion content is described can be stored in association with the predetermined topic information. Accordingly, common discussion content spanning multiple meetings can be efficiently managed in association with the predetermined topic information. For example, when discussions span multiple meetings regarding a specific topic, the content of discussions regarding the topic can be tracked and confirmed for each topic.

[0301] (Appendix 26) An information processing method executed by a computer having a processor and a storage unit, the computer executing a minutes storage step (S101) of storing minutes information regarding the minutes of a meeting, a document storage step (S102) of storing a plurality of document information related to each of a plurality of topics discussed in the meeting in association with the minutes information stored in the minutes storage step, and a topic storage step (S103) of storing the plurality of document information stored in the document storage step in association with topic information regarding the topic. The document storage step (S102) includes a step of associating first document information with a first minutes regarding a first meeting and a step of associating second document information with a second minutes regarding a second meeting. The topic storage step (S103) includes a step of storing the first document information associated with the first minutes and the second document information associated with a second minutes different from the first minutes in association with one topic information. Accordingly, when discussions span multiple meetings regarding a predetermined topic, a plurality of document information in which the discussion content is described can be stored in association with the predetermined topic information. Accordingly, common discussion content spanning multiple meetings can be efficiently managed in association with the predetermined topic information. For example, when discussions on a specific topic span multiple meetings, it is possible to track and confirm the content of the discussions on that topic for each topic.

[0302] (Second Embodiment) (Appendix 1) A program for operating a computer equipped with a processor, the program causing the processor to, based on the time set for a meeting, when a predetermined timing arrives (S2311), notify the user of the participants in the meeting with a notification for prompting a predetermined input along the purpose of the meeting (S2321), receive a predetermined input along the purpose of the meeting from the user (S2323, S2325), and store the content of the received input in a storage unit (S2315).

[0303] (Appendix 2) At the time set for the meeting, an operation member for starting a predetermined input along the purpose of the meeting is presented to the user, and when the predetermined timing arrives, the operation member is highlighted and displayed (S2321, Figure 25). In the receiving step, in response to the user's input operation on the operation member, a screen (2404, Figure 26) for receiving a predetermined input along the purpose of the meeting is presented to the user. The program according to Appendix 1.

[0304] (Appendix 3) In the receiving step, as a predetermined input along the purpose of the meeting, Inputs related to the content of the topic, such as decisions, summaries, etc. for each topic of the meeting (2447), Setting of access rights for each topic of the meeting (2443), The status of the discussion, such as whether to continue discussing the topic of the meeting or end the discussion (2444), Setting of other topics related to the topic of the meeting (2452), The program according to Appendix 1, which receives at least any one of the above inputs.

[0305] (Appendix 4) A program described in Appendix 3, which is configured to store in the memory unit by associating information about a meeting, information about a document related to the meeting, and information about an agenda related to the meeting (1015, 1013, 1014).

[0306] (Appendix 5) In the receiving step, as a predetermined input along the purpose of the meeting, Receive at least one of the content of a task that can be assigned to a participant in the meeting, the person in charge of the task, and the due date of the task (2446), a program described in any one of Appendices 2 to 4.

[0307] (Appendix 6) In the memory unit, it is configured to store in association with information about a meeting, information about a document related to the meeting, and information about an agenda related to the meeting (1015, 1013, 1014). When receiving an input from the person in charge of a task in the receiving step, perform a process of limiting the person in charge of the task to a user with access authority set to the information about the document related to the meeting or the information about the agenda related to the meeting. A program described in Appendix 5.

[0308] (Appendix 7) A method for operating a computer equipped with a processor. The method includes steps for the processor to send a notification to prompt a predetermined input along the purpose of the meeting to a user of a participant in the meeting when a predetermined timing arrives based on the time set for the meeting, receive a predetermined input along the purpose of the meeting from the user, and store the content of the received input in the memory unit.

[0309] (Appendix 8) An information processing apparatus including a processor, wherein the processor performs the steps of: notifying a user who is a participant in a meeting to prompt a predetermined input in accordance with the purpose of the meeting when a predetermined timing arrives based on the time set for the meeting; receiving a predetermined input in accordance with the purpose of the meeting from the user; and storing the content of the received input in a storage unit.

Explanation of Signs

[0310] 1 System, 10 Server, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 First User Terminal, 201 Storage Unit, 204 Control Unit, 206 Input Device, 208 Output Device, 30 Second User Terminal, 301 Storage Unit, 304 Control Unit, 306 Input Device, 308 Output Device, 40 Online Meeting System, 401 Storage Unit, 404 Control Unit, 406 Input Device, 408 Output Device

Claims

1. A program for operating a computer comprising a processor, the program causing the processor to: based on the time set for a meeting, when a predetermined timing arrives, notify a user who is a participant in the meeting to prompt a predetermined input in line with the purpose of the meeting; receive a predetermined input in line with the purpose of the meeting from the user; store the content of the received input in a storage unit. A program that causes the above steps to be executed.

2. At the time set for the meeting, an operation member for starting a predetermined input in line with the purpose of the meeting is presented to the user, when the predetermined timing arrives, the operation member is highlighted and displayed, In the receiving step, a screen for receiving a predetermined input in line with the purpose of the meeting is presented to the user in response to an input operation of the user on the operation member. The program according to claim 1.

3. In the receiving step, as a predetermined input in line with the purpose of the meeting, inputs related to the content of the topic, such as decisions and summaries for each topic of the meeting; setting of access rights for each topic of the meeting; the status of the discussion, such as whether to continue discussing the topic of the meeting or end the discussion; setting of other topics related to the topic of the meeting, The program according to claim 1, which receives at least any one of the above inputs.

4. In the storage unit, the meeting information, the information of documents related to the meeting, and the information of topics related to the meeting are configured to be stored in association with each other. The program according to claim 3.

5. In the receiving step, as a predetermined input in line with the purpose of the meeting, The program according to claim 2, which receives at least any one of the input of the content of the task that can be assigned to the participants in the meeting, the person in charge of the task, and the due date of the task.

6. In the storage unit, the meeting information, the information of documents related to the meeting, and the information of topics related to the meeting are configured to be stored in association with each other, In the receiving step, when receiving the input of the person in charge of the task, a process is performed to limit the person in charge of the task to a user who has access rights to the information of the document related to the meeting or the information of the topic related to the meeting. The program according to claim 5.

7. A method for operating a computer comprising a processor, the method comprising the steps of: when a predetermined timing arrives based on a time set for a meeting, the processor notifying a user of a participant in the meeting with a notification for prompting a predetermined input in line with the purpose of the meeting; receiving a predetermined input in line with the purpose of the meeting from the user; storing the content of the received input in a storage unit.

8. An information processing apparatus comprising a processor, the processor performing the steps of: when a predetermined timing arrives based on a time set for a meeting, notifying a user of a participant in the meeting with a notification for prompting a predetermined input in line with the purpose of the meeting; receiving a predetermined input in line with the purpose of the meeting from the user; storing the content of the received input in a storage unit. ​ ​

Citation Information

Patent Citations

  • Conference support system and conference support program

    JP2019061594A