JP2017134734A - Information processing device, information storage method, program, and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing device capable of storing materials used in a meeting and information related to the meeting.SOLUTION: An information processing device for managing a meeting to be performed between a plurality of terminal apparatuses comprises: information generation means for, from a storage type information storage part for storing storage type information in which a rule for storing materials used in a meeting and information related to the meeting for each storage type under different conditions is set, reading the storage type information of the selected storage type, and for generating information related to the meeting based on the read storage type information; and storage means for storing the materials used in the meeting and the generated information related to the meeting in an output destination set in the read storage type information.SELECTED DRAWING: Figure 12

Description

  The present invention relates to an information processing apparatus, an information storage method, a program, and an information processing system.

  In a paperless (electronic) conference system, materials used in a meeting or the like are digitized, and the materials are displayed on a client terminal such as a tablet terminal or a notebook PC at hand of a participant. In the conventional electronic conference system, an efficient conference is performed by synchronizing the display of the participant's client terminal with the display page of the document of the speaker's client terminal or a memo.

  For the purpose of convenience of using conference materials, for example, for storing and referencing conference materials, specifying the storage location of conference materials related to the conference in which the user participated at that date by simply specifying the date and time. A teleconference system that can be used is conventionally known (see, for example, Patent Document 1).

  In a conventional electronic conference system, materials used for a conference may be stored, for example, in a local storage of a participant's client terminal or a document management server. Further, in the conventional electronic conference system, the user may want to leave not only the material used for the conference, but also information related to the conference (conference information). However, in the conventional electronic conference system, when the conference information is left, the user needs to input and save the conference information using, for example, a memo function, which is troublesome.

  Embodiments of the present invention have been made in view of the above points, and an object thereof is to provide an information processing apparatus capable of storing materials used in a meeting and information related to the meeting.

  In order to achieve the above object, claim 1 of the present application is an information processing apparatus that manages a meeting held between a plurality of terminal devices, and stores materials used in the meeting and information related to the meeting. Read the storage type information of the selected storage type from the storage type information storage unit that stores the storage type information in which rules for storing under different conditions for each type are set, and the meeting based on the read storage type information Information generating means for generating information related to the information, and storage means for storing the material used in the meeting and the generated information regarding the meeting in the output destination set in the read storage type information. It is characterized by.

  According to the embodiment of the present invention, materials used in a meeting and information related to the meeting can be stored.

It is a lineblock diagram of an example of a conference system concerning this embodiment. It is a hardware block diagram of an example of the computer which concerns on this embodiment. It is a functional block diagram of an example of a conference server apparatus. It is a functional block diagram of an example of a client terminal. It is a functional block diagram of an example of a document management server apparatus. It is a block diagram of an example of meeting information. It is a block diagram of an example of preservation | save type information. It is a block diagram of an example of XML tag information. It is an image figure of an example of a preservation | save type setting screen. It is an image figure of an example of a preservation | save type addition / edit screen. It is an image figure of an example of an output information addition / edit screen. It is a flowchart of an example of the process which preserve | saves the material used for the meeting, and the meeting information based on the preservation | save type selected by the user. It is an image figure of an example of a preservation | save type selection screen. It is a sequence diagram of an example of the process which registers the material used for the meeting, and the produced | generated meeting information in a document management server apparatus. It is a sequence diagram of the other example of the process which registers the material used for the meeting, and the produced | generated meeting information with a document management server apparatus. It is a block diagram of the other example of meeting information.

Next, embodiments of the present invention will be described in detail. In the present embodiment, information (meeting information) related to a meeting using materials will be described as an example of information related to a meeting using materials, but the information is not limited to meeting information. Meetings include lectures, classes and seminars in addition to conferences.
[First Embodiment]
<System configuration>
FIG. 1 is a configuration diagram of an example of a conference system according to the present embodiment. The conference system 1A in FIG. 1A shows an example of a configuration in which a conference server device 10, a plurality of client terminals 12, and a document management server device 14 are connected to a network N1 such as a LAN. The conference system 1B in FIG. 1B has a configuration in which a file server device 16 is connected to the network N1 instead of the document management server device 14 of the conference system 1A in FIG.

  The document management server device 14 and the file server device 16 are examples of devices that store materials used in a conference and conference information. Note that the materials and conference information used in the conference can be stored in the conference server device 10. When the material and conference information used in the conference are stored in the conference server device 10, the document management server device 14 or the file server device 16 may be omitted. Further, the document management server device 14 of the conference system 1 </ b> A or the file server device 16 of the conference system 1 </ b> B may be mounted on the same computer as the conference server device 10 as a function of the conference server device 10. Hereinafter, the conference system 1 will be referred to as any one of the conference system 1A and the conference system 1B.

  The conference server apparatus 10 accepts a conference registration request, a material registration request, and the like, and stores conference information, materials used in the conference, and the like, which will be described later. In addition, the conference server device 10 performs conference holding and participation control. The conference server apparatus 10 can be realized by software and services that operate on one or more computers. In addition, the conference server apparatus 10 can take the form of a so-called cloud service. The conference server device 10 is realized by a computer such as a device dedicated to the conference system 1 or a general workstation or PC, for example.

  The client terminal 12 has a function of registering conferences and materials in the conference server device 10 and a function of displaying a conference list and materials. The client terminal 12 may be a device dedicated to the conference system 1 in addition to a terminal device such as a PC, a tablet terminal, a smartphone, a mobile phone, and a PDA, a virtual machine, a projector, and an electronic blackboard.

  The software that operates on the client terminal 12 may be a native application that operates alone, a Web browser, and a Web application that operates on the Web browser. Further, the client terminal 12 has a function of acquiring conference information from the conference server device 10, downloading material data, displaying the material, and participating in the conference. In the conference system 1, any user who participates in the conference may be a presenter.

  While the client terminal 12 participates in the conference, the same material as the other client terminals 12 is displayed. The client terminal 12 receives an input operation (page turning or the like) from another client terminal 12 such as a presenter from the conference server device 10 in real time, and may share (synchronize) a display screen with the other client terminal 12. it can.

  For example, when the document page is turned on the client terminal 12 of the presenter, the page of the document is turned on the client terminal 12 other than the presenter, and the same screen is shared. Further, when a handwritten memo is drawn on the presenter's client terminal 12 to draw a mark or line or add a character by operating a touch pen or a mouse, it is also reflected on the screen of the participant's client terminal 12.

  In the conference system 1A, the conference server device 10, the client terminal 12, and the document management server device 14 are capable of data communication via the network N1. In the conference system 1B, the conference server device 10, the client terminal 12, and the file server device 16 can also perform data communication via the network N1. The network N1 may be the Internet, a dedicated line, a wired line, or a wireless line in addition to the LAN.

<Hardware configuration>
The conference server device 10, the client terminal 12, the document management server device 14, and the file server device 16 are realized by a computer 500 having a hardware configuration as shown in FIG. FIG. 2 is a hardware configuration diagram of an example of a computer according to the present embodiment.

  A computer 500 illustrated in FIG. 2 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like. . Note that the input device 501 and the display device 502 may be connected and used when necessary.

  The input device 501 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 502 includes a display and the like, and displays a processing result by the computer 500.

  A communication I / F 507 is an interface for connecting the computer 500 to various networks. Thereby, the computer 500 can perform data communication via the communication I / F 507.

  The HDD 508 is an example of a nonvolatile storage device that stores programs and data. The stored programs and data include an OS, which is basic software for controlling the entire computer 500, and application software (hereinafter simply referred to as an application) that provides various functions on the OS. The computer 500 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 508.

  The external I / F 503 is an interface with an external device. The external device includes a recording medium 503a. Accordingly, the computer 500 can read and / or write the recording medium 503a via the external I / F 503. Examples of the recording medium 503a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The ROM 505 is an example of a nonvolatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. The ROM 505 stores programs and data such as BIOS, OS settings, and network settings that are executed when the computer 500 is started up. The RAM 504 is an example of a volatile semiconductor memory (storage device) that temporarily stores programs and data.

  The CPU 506 is an arithmetic device that realizes control and functions of the entire computer 500 by reading a program and data from a storage device such as the ROM 505 and the HDD 508 onto the RAM 504 and executing processing.

  The conference server device 10, client terminal 12, document management server device 14, and file server device 16 can implement various processes as will be described later, for example, by executing a program on the computer 500 having the hardware configuration described above. .

<Software configuration>
Here, a conference system 1A that is an example of the conference system 1 according to the present embodiment will be described. The conference server device 10, the client terminal 12, and the document management server device 14 of the conference system 1A according to the present embodiment are realized by the following functional blocks.

<Conference server device>
The conference server device 10 is realized by functional blocks as shown in FIG. 3, for example. FIG. 3 is a functional block diagram of an example of the conference server apparatus. In addition, the functional block of FIG. 3 has shown about the function required for description of this embodiment among the functions which the conference server apparatus 10 provides, and another function may exist.

  The conference server device 10 implements the communication unit 20, the information processing unit 30, and the information management unit 40 by executing the program. In addition, the information processing unit 30 includes a storage type setting unit 31, a conference registration unit 32, a material registration unit 33, a conference control unit 34, a storage type selection reception unit 35, a storage type-specific conference information generation unit 36, and a storage unit 37. The information management unit 40 includes a conference information storage unit 41, a storage type information storage unit 42, and an XML tag information storage unit 43.

  The communication unit 20 communicates with the client terminal 12 and the document management server device 14. The information processing unit 30 includes information processing such as a storage type setting unit 31, a conference registration unit 32, a material registration unit 33, a conference control unit 34, a storage type selection reception unit 35, a storage information classified by storage type 36, and a storage unit 37. I do. The information management unit 40 stores conference information, storage type information, XML tag information, and the like.

  The storage type setting unit 31 accepts in advance the setting of a storage type (storage rule) described later from an administrator or the like, and sets the storage type in the storage type information storage unit 42. The conference registration unit 32 receives a conference registration request from the client terminal 12, sets conference information in the conference information storage unit 41, and registers the conference. The material registration unit 33 receives a material registration request from the client terminal 12 and registers material data. Note that the storage location of the material data may be the information management unit 40 of the conference server device 10 or may be other than the conference server device 10.

  The conference control unit 34 uses the conference information, storage type information, XML tag information, and the like stored in the information management unit 40 to provide conference information, provide materials, hold and end the conference, and participate in the conference Control of the display screen sharing in the client terminal 12 is performed.

  The storage type selection receiving unit 35 displays a storage type selection screen described later on the client terminal 12 and receives a storage type selection from a user such as a presenter or an office. The storage information classified by storage type 36 reads out the storage type information of the storage type selected by the user from the storage type information storage unit 42 and generates meeting information based on the storage type selected by the user. The storage unit 37 outputs the material used for the conference and the conference information based on the storage type selected by the user to the output destination set in the storage type information for storage.

  The meeting information storage unit 41 stores meeting information. The meeting information stored in the meeting information storage unit 41 may be deleted according to a predetermined rule such as an elapsed time after the meeting ends or an old order. Further, the user who can select the storage type may be a user who has input secret information (holding key) for holding a conference, for example.

  The storage type information storage unit 42 stores storage type information. The XML tag information storage unit 43 stores XML tag information. Details of the conference information, the storage type information, and the XML tag information will be described later. The functional blocks shown in FIG. 3 are an example. For example, some of the functional blocks included in the conference server device 10 may operate on another computer. In that case, the functional blocks communicate with each other as necessary to exchange information.

<Client terminal>
The client terminal 12 is realized by, for example, functional blocks as shown in FIG. FIG. 4 is a functional block diagram of an example of a client terminal. Note that the functional blocks in FIG. 4 show the functions necessary for the description of the present embodiment among the functions provided by the client terminal 12, and other functions may exist.

  The client terminal 12 implements the UI display unit 50, the information processing unit 60, the authentication unit 70, the communication unit 80, the information management unit 90, and the search unit 100 by executing the program. The UI display unit 50 includes a display control unit 51 and an input operation control unit 52. The information processing unit 60 includes a stroke processing unit 61, an information synchronization processing unit 62, a material acquisition unit 63, a conference information acquisition unit 64, and the like. The communication unit 80 includes a transmission / reception control unit 81.

  The UI display unit 50 performs control related to UI display such as the display control unit 51 and the input operation control unit 52. The transmission / reception control unit 81 of the communication unit 80 controls communication with the conference server device 10 and the document management server device 14. The information processing unit 60 performs information processing such as a stroke processing unit 61, an information synchronization processing unit 62, a material acquisition unit 63, and a conference information acquisition unit 64. The authentication unit 70 performs processing related to user authentication. The information management unit 90 manages information. The search unit 100 performs processing related to search.

  The display control unit 51 performs UI display control. The input operation control unit 52 receives an input operation from the user and performs control based on the input operation. The information processing unit 60 is connected to the conference server device 10, displays a conference list registered in the conference server device 10, and allows the user to select a conference to be held or participated. The information processing unit 60 acquires meeting information and material data of the conference selected by the user, and causes the UI display unit 50 to display the material.

  After holding or participating in the conference, the information processing unit 60 communicates with the conference server device 10 using the communication unit 80 and shares the display screen of the material with the other client terminals 12. For example, the client terminal 12 of the presenter transmits input operation information such as page turning and memo writing to the conference server device 10. The information processing unit 30 of the conference server apparatus 10 transmits the input operation information received from the client terminal 12 of the presenter to all the client terminals 12 participating in the conference.

  The client terminal 12 that has received the input operation information from the conference server apparatus 10 can share the display screen with the client terminal 12 of the presenter by updating the display screen of the document based on the received input operation information. . The functional blocks in FIG. 4 are an example.

<Document Management Server Device>
The document management server device 14 is realized by functional blocks as shown in FIG. FIG. 5 is a functional block diagram of an example of the document management server apparatus. Note that the functional blocks in FIG. 5 show the functions necessary for the description of the present embodiment among the functions provided by the document management server device 14, and other functions may exist.

  The document management server apparatus 14 implements the document registration tool unit 110 and the document management server unit 120 by executing a program. The document registration tool unit 110 includes a monitoring unit 111, a communication unit 112, and a registration unit 113. The document management server unit 120 includes an information processing unit 121, a communication unit 122, and a display control unit 123.

  The storage 130 is an example of an output destination that stores the material used for the conference from the conference server device 10 and the conference information based on the storage type selected by the user. The monitoring unit 111 of the document registration tool unit 110 monitors a storage location (for example, a folder or a directory) of the storage 130 set as an output destination of the material and the conference information, and detects the storage of the material and the conference information. When the monitoring unit 111 detects the storage of the material and the conference information, the registration unit 113 registers the material and the conference information detected to be stored in the document management server unit 120.

  In the case of the conference system 1B, the file server device 16 has a storage 130. The conference server device 10 stores the material used for the conference and the conference information based on the storage type selected by the user in the storage 130 of the file server device 16 set as an output destination of the material and conference information.

  The functional blocks shown in FIG. 5 are an example. For example, the configuration in which the document registration tool unit 110 and the document management server unit 120 of the document management server device 14 in FIG. 5 are separate is an example. The document management server device 14 may not have the document registration tool unit 110 and the document management server unit 120 may have the function of the document registration tool unit 110. Further, the document management server device 14 may be configured to be notified from the conference server device 10 of the storage of materials and conference information in the storage 130.

  Furthermore, some of the functional blocks included in the document management server apparatus 14 in FIG. 5 may operate on another computer. In that case, the functional blocks communicate with each other to exchange information.

《Meeting information》
For example, conference information shown in FIG. 6 is stored in the conference information storage unit 41 of the conference server device 10. FIG. 6 is a configuration diagram of an example of conference information. The conference information in FIG. 6 includes items such as a conference ID, a conference name, a date and time, an end date and time, a place, a memo, and the number of participants. The conference ID is an example of identification information for uniquely identifying a conference. The meeting name is the name of the meeting. The date and time is the date and time when the meeting is held. The end date and time is the date and time when the conference ends. The place is the meeting place. The memo is a memo input by the user. The number of participants is the number of participants who participated in the conference.

  The conference information includes information manually input by the user at the time of conference registration, such as the conference name, scheduled date / time, and scheduled end date / time, and the number of participants and participating user IDs automatically input by the conference server device 10 after the conference is held. Such information is included.

<Storage type information>
For example, the storage type information shown in FIG. 7 is stored in the storage type information storage unit 42 of the conference server apparatus 10. FIG. 7 is a configuration diagram of an example of storage type information. The storage type information in FIG. 7 includes items such as type ID, type name, output destination, folder, format, and prop1 to n.

  The type ID is an example of identification information for uniquely identifying the storage type. The type name is the name of the storage type. The output destination is a path of a storage location on the storage 130 that stores the material and conference information. The folder is information for designating a folder name when a new folder is created each time a document or meeting information is saved. The format represents an output format of conference information such as XML or text. prop1 to n represent one or more output items of conference information.

  The storage type information is set in advance by an administrator or the like. As shown in FIG. 7, a plurality of storage types can be set in the storage type information. For example, in the storage type of the type name “executive meeting” in FIG.

  In addition, since the type name “Executive Meeting” in FIG. 7 is designated as {DateTime} in the folder, a folder with the current date and time as the folder name is created, and the document and meeting information are saved in the folder. . If the folder is blank, the folder and the conference information are stored in the storage location indicated by the output destination path without creating the folder.

  For example, since the storage type of the type name “executive meeting” in FIG. 7 has the format “XML”, the meeting information in the XML format including the holding date / time, the end date / time, and the memo as output items is stored in the created folder. Thus, in the conference server apparatus 10 according to the present embodiment, one or more output items of conference information can be arbitrarily set according to the use of each storage type. It should be noted that the range of output items that can be set can be changed according to, for example, a charge, contract content, and the like.

《XML tag information》
For example, XML tag information shown in FIG. 8 is stored in the XML tag information storage unit 43 of the conference server apparatus 10. FIG. 8 is a configuration diagram of an example of XML tag information. The XML tag information in FIG. 8 has KEY (key) and Value (value) as items. The XML tag information of FIG. 8 shows the XML tag information of the type name “Executive Meeting” of FIG. 7 as an example. Prop1 to n in FIG. 7 are set in KEY. Also, a tag name in XML format is set for Value. The XML tag information shown in FIG. 8 associates the storage type information prop1 to n with the tag information in the XML format.

  The XML tag information holds tag names of prop1 to n, which are variable values, when storing conference information in XML format. For example, when saving the meeting information shown in FIG. 6 and selecting the save type of the type name “Executive Meeting” shown in FIG. 7, the meeting information in the XML format is output with the tag name set in the XML tag information of FIG. Is done.

  As described above, the conference server apparatus 10 according to the present embodiment can set the tag name in the XML format, so that, for example, the meeting information in the XML format corresponding to the document registration tool unit 110 of the document management server apparatus 14 is output. it can.

  For example, in the example of FIGS. 6 to 8, the prop1 “held date” is expressed as <Date_Property_1> 2015/11/20 13:00 </ Date_Property_1> in the conference information to be output.

<Details of processing>
Below, the detail of the process of the conference system 1 which concerns on this embodiment is demonstrated.

《Save type setting process》
In the conference system 1 according to the present embodiment, storage type information and XML tag information are set in the conference server device 10 before a conference is held. For example, a user such as an administrator performs addition, change, and deletion of a storage type on the storage type setting screen 1000 shown in FIG. FIG. 9 is an image diagram of an example of a storage type setting screen. A user such as an administrator can display a storage type addition / editing screen 1100 as shown in FIG. 10, for example, by pressing an addition button 1001 on the storage type setting screen 1000 in FIG.

  FIG. 10 is an image diagram of an example of a storage type addition / edit screen. A user such as an administrator can add / edit a storage type from the storage type addition / edit screen 1100 of FIG. The save type addition / edit screen 1100 of FIG. 10 can set a save type name, a save destination, a folder creation rule at the time of saving, and a format.

  Further, a user such as an administrator can display an output information addition / editing screen 1200 shown in FIG. 11, for example, by pressing an output information addition / editing button 1101 on the storage type addition / editing screen 1100 in FIG.

  FIG. 11 is an image diagram of an example of an output information addition / editing screen. A user such as an administrator adds / edits one or more output items of conference information as output information from the output information addition / edit screen 1200 of FIG. A user such as an administrator sets an item name, an item ID, an output item, and an initial value in the setting field 1202 of the output information addition / editing screen 1200 and presses a setting update button 1203 to include it in the setting item list 1201. Output information can be updated.

  In addition, a user such as an administrator sets an item name, an item ID, an output item, and an initial value in the setting field 1202 of the output information addition / editing screen 1200, and outputs to the setting item list 1201 by pressing an add button 1204. You can add information. The item ID in the setting column 1202 is a tag name in the meeting information in the XML format. The output item is an item name in the meeting information in the text format.

《Saving materials and meeting information》
The conference server device 10 stores the material used for the conference and conference information based on the storage type selected by the user, for example, according to the procedure shown in FIG. FIG. 12 is a flowchart of an example of processing for storing the material used for the conference and the conference information based on the storage type selected by the user.

  In step S11, the client terminal 12 is connected to the conference server device 10 and displays a registered conference list. The user can select a conference to be held or participated from the displayed conference list. The display control unit 51 of the client terminal 12 displays the materials of the conference that has been held or participated.

  During the holding of the conference, the client terminal 12 that became the presenter transmits a page turning operation and a memo writing operation by the presenter to the conference server device 10. The conference server device 10 transmits the received page turning operation and memo writing operation by the presenter to the client terminals 12 participating in the conference. Therefore, each client terminal 12 can share the display screen with the client terminal 12 of the presenter.

  When the conference server device 10 accepts an operation to end the conference by the presenter, the conference server device 10 proceeds to step S13, and transmits the conference end operation by the presenter to the client terminals 12 participating in the conference. Accordingly, the client terminal 12 participating in the conference can display that the conference has been terminated by the presenter.

  Further, the storage type selection accepting unit 35 of the conference server apparatus 10 displays a storage type selection screen 1300 as shown in FIG. 13 on the client terminal 12 of the presenter to allow the presenter to select a storage type. FIG. 13 is an image diagram of an example of a storage type selection screen. A storage type selection screen 1300 in FIG. 13 shows an example in which a storage type is selected using a radio button. Note that the storage type set in the storage type information of the storage type information storage unit 42 is displayed on the storage type selection screen 1300 of FIG.

  The storage types displayed on the storage type selection screen 1300 may be all the storage types set in the storage type information of the storage type information storage unit 42, or may be storage types associated with the presenter. There may be.

  The presenter performs an operation of selecting a storage type from the storage type selection screen 1300. The storage type selected by the presenter is notified to the conference server device 10 from the client terminal 12 of the presenter.

  In step S <b> 14, the storage information classified by storage type 36 of the conference server apparatus 10 reads storage type information of the storage type selected by the presenter from the storage type information storage unit 42. If the format of the read storage type information of the conference server apparatus 10 is the XML format, the XML tag information of the storage type selected by the presenter is stored in the XML tag information storage unit 43. read out. Further, the save type conference information generation unit 36 reads the conference information of the conference for which the end operation has been performed from the conference information storage unit 41.

  Then, based on the read storage type information and the XML tag information, the storage type classified conference information generation unit 36 generates the storage type conference information selected by the presenter. In step S15, the storage unit 37 stores the material used for the conference and the conference information generated in step S14 in the output destination set in the read storage type information.

  For example, in the conference system 1A according to the present embodiment, the material used for the conference and the conference information generated in step S14 are stored in the storage 130 of the document management server device 14. In the flowchart of FIG. 12, an example is given in which the presenter instructs the storage of the material used for the conference and the conference information generated in step S14 by selecting the storage type from the storage type selection screen 1300, but the present invention is not limited thereto. . For example, by selecting a save type from a screen during a meeting, an instruction to save the material used for the meeting and the meeting information generated in step S14 may be issued.

  When the storage 130 of the document management server device 14 is selected as the output destination, the conference server device 10 can store the material used for the conference and the conference information generated in step S14 in cooperation with the document management server device 14. FIG. 14 is a sequence diagram illustrating an example of processing for registering the material used for the conference and the generated conference information in the document management server device.

  As shown in step S21, the document registration tool unit 110 of the document management server device 14 monitors a storage location such as a directory of the storage 130 set as an output destination of the storage type information. In step S22, the storage unit 37 of the conference server apparatus 10 manages the document data of the materials used for the conference and the conference information based on the storage type selected by the user, as the output destination document management set in the storage type information. The data is stored in the storage 130 of the server device 14.

  In step S23, the document registration tool unit 110 detects that the material data of the material used for the conference and the conference information based on the storage type selected by the user are stored in the storage 130. In step S24, the document registration tool unit 110 reads the material data of the material used for the conference from the storage 130 and the conference information based on the storage type selected by the user. In step S 25, the document registration tool unit 110 registers the material data of the material used for the conference read from the storage 130 and the conference information based on the storage type selected by the user in the document management server unit 120.

  As described above, in the conference system 1A according to the present embodiment, the storage location of the storage 130 monitored by the document registration tool unit 110 is set as the output destination set in the storage type information. As a result, the conference system 1A can automatically register the material used for the conference and the conference information based on the storage type in the document management server device 14 by storing in the output destination set in the storage type information.

  Note that in the conference system 1B according to the present embodiment, the storage location such as the storage directory of the output destination file server device 16 set in the storage type information is based on the material data of the material used for the conference and the storage type. Meeting information is saved.

  As described above, the conference system 1 according to the present embodiment sets the storage type information in advance, and after the conference ends, allows the user such as the presenter to select the storage type, so that the conference is stored together with the materials depending on the type of the conference. Information output items and output formats can be changed. For example, at the end of the audit meeting, by selecting a storage type that includes an output item necessary for the audit, the conference system 1 according to the present embodiment displays the materials used for the audit meeting and the output items necessary for the audit. It is possible to reduce the trouble of storing the conference information including it in the output destination.

  In addition, at the end of a meeting such as a regular meeting, by selecting a storage type that includes a simple output item, materials used for the meeting such as a regular meeting and meeting information including a simple output item are displayed. , You can save the trouble of saving to the output destination.

  For example, when registering together the material data of the material used for the meeting and the meeting information based on the storage type in the document management server device 14, the material is registered as one document and stored as the property of the document It is also possible to register conference information based on type.

In this case, the conference information is stored in the storage 130 that is the monitoring destination of the document registration tool unit 110 together with the material data in a format that can be analyzed by the document registration tool unit 110 (for example, XML format). The document registration tool unit 110 analyzes the conference information and registers the conference information as a document property. As described above, according to the conference system 1A according to the present embodiment, by registering the conference information as the property of the document, the document can be searched by the property item, and the convenience when referring to it later can be improved.
[Other Embodiments]
In the present embodiment, the storage unit 37 of the conference server apparatus 10 uses the document management server apparatus 14 in which the material used for the meeting and the conference information based on the storage type selected by the user are set as the output destination of the storage type information. Stored in the storage 130.

  However, if the output destination of the material used for the conference and the conference information based on the storage type selected by the user is the monitoring destination of the document registration tool unit 110, for example, as shown in the sequence diagram of FIG. Ten storages 130 may be used.

  FIG. 15 is a sequence diagram of another example of processing for registering the material used for the conference and the generated conference information in the document management server apparatus. As shown in step S31, the document registration tool unit 110 of the document management server apparatus 14 monitors a storage location such as a directory in the storage 130 of the conference server apparatus 10 set as an output destination of the storage type information. In step S32, the storage unit 37 of the conference server apparatus 10 outputs the material data of the material used for the conference and the conference information based on the storage type selected by the user as the output destination conference server set in the storage type information. Save in the storage 130 of the device 10.

  In step S <b> 33, the document registration tool unit 110 detects that the material data of the material used for the conference and the conference information based on the storage type selected by the user are stored in the storage 130 of the conference server device 10.

  In step S34, the document registration tool unit 110 reads the material data of the material used for the conference from the storage 130 of the conference server device 10 and the conference information based on the storage type selected by the user.

  In step S35, the document registration tool unit 110 sends the material data of the material used for the conference read from the storage 130 of the conference server device and the conference information based on the storage type selected by the user to the document management server unit 120. sign up. As described above, in the conference system 1A according to the present embodiment, the document registration tool unit 110 monitors the storage 130 of the conference server device 10 so that the material and the conference information stored in the storage 130 of the conference server device 10 are automatically obtained. May be registered in the document management server device 14.

  Note that the conference system 1A according to the present embodiment has the same effect even if the storage system 130 is monitored by the document registration tool unit 110 and the storage system 130 is in a device other than the conference server device 10 or the document management server device 14. Have

  In this embodiment, the storage type selection screen 1300 shown in FIG. 13 is displayed at the end of the conference, and a user such as a presenter selects the storage type. However, as shown in the meeting information of FIG. 16, by adding information that can select a storage type such as a type ID as an item of the meeting information, the storage type can be automatically selected.

  FIG. 16 is a configuration diagram of another example of conference information. The meeting information in FIG. 16 is obtained by adding a type ID as an item to the meeting information item in FIG. The conference information generating unit 36 by storage type of the conference server device 10 can read storage type information of the storage type set in the conference information from the storage type information storage unit 42 and generate conference information based on the storage type.

(Summary)
In the conference system 1 of the present embodiment, by setting the conference information storage type in advance according to the conference characteristics, it is possible to reduce the trouble of storing the conference information based on the storage type. For example, when the conference information stored in the conference information storage unit 41 of the conference server device 10 is erased according to a predetermined rule such as elapsed time or oldest order, the conference system 1 of the present embodiment uses an important conference such as an audit. It is possible to prevent a situation in which the conference information is deleted unintentionally.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims. In the present embodiment, the conference system 1 is shown as an example, but application to other systems such as a seminar system and an education system is also possible.

  For example, the client terminal 12 is an example of a terminal device described in the claims. The conference server device 10 is an example of an information processing device. A meeting is an example of a meeting. The save type classified conference information generation unit 36 is an example of an information generation unit. The storage unit 37 is an example of a storage unit. The meeting information is an example of information related to the meeting.

  The storage type setting unit 31 is an example of a storage type setting unit. The storage type selection receiving unit 35 is an example of a storage type selection receiving unit. The document management server device 14 and the file server device 16 are examples of information storage devices. The storage 130 is an example of a storage unit.

  Note that the conference system 1 having the conference server device 10, one or more client terminals 12, and the document management server device 14 or the file server device 16 is an example, and various system configuration examples may be used depending on applications and purposes. It goes without saying that there is.

1, 1A, 1B Conference system 10 Conference server device 12 Client terminal 14 Document management server device 16 File server device 20 Communication unit 30 Information processing unit 31 Storage type setting unit 32 Conference registration unit 33 Document registration unit 34 Conference control unit 35 Storage type Selection reception unit 36 Conference type generation unit by storage type 37 Storage unit 40 Information management unit 41 Conference information storage unit 42 Storage type information storage unit 43 XML tag information storage unit 50 UI display unit 51 Display control unit 52 Input operation control unit 60 Information Processing unit 61 Stroke processing unit 62 Information synchronization processing unit 63 Data acquisition unit 64 Conference information acquisition unit 70 Authentication unit 80 Communication unit 81 Transmission / reception control unit 90 Information management unit 100 Search unit 110 Document registration tool unit 111 Monitoring unit 112 Communication unit 113 Registration Part 120 Document management server part 121 Information Information processing unit 122 Communication unit 123 Display control unit 130 Storage 500 Computer 501 Input device 502 Display device 503 External I / F
503a Recording medium 504 RAM (Random Access Memory)
505 ROM (Read Only Memory)
506 CPU (Central Processing Unit)
507 Communication I / F
508 HDD (Hard Disk Drive)
1000 Save Type Setting Screen 1100 Save Type Add / Edit Screen 1200 Output Information Add / Edit Screen 1300 Save Type Selection Screen B Bus N1 Network

JP 2008-90383 A

Claims (10)

An information processing apparatus for managing a meeting held between a plurality of terminal devices,
From the storage type information storage unit that stores the storage type information in which rules for storing the materials used in the meeting and the information related to the meeting under different conditions for each storage type are set, the selected storage type is selected. Information generation means for reading storage type information and generating information on the meeting based on the read storage type information;
Storage means for storing the material used in the meeting and the information about the generated meeting in the output destination set in the read storage type information;
An information processing apparatus. The storage type information includes at least one of output items to be included in the information on the meeting to be stored in the output destination, and an output format of information on the meeting to be stored in the output destination, among all items of the information on the meeting One of the settings is received from the user, and further has a storage type setting means for storing in the storage type information storage unit,
The information processing apparatus according to claim 1. Displaying a storage type selection screen for allowing the user to select the storage type in which the storage type information is stored in the storage type information storage unit, and receiving a selection of the storage type from the user Further having means,
The information processing apparatus according to claim 1 or 2. The information generation means reads storage type information of the storage type set in the information about the meeting, and generates information about the meeting based on the read storage type information;
The information processing apparatus according to claim 1 or 2. The storage means stores the material used in the meeting and the information related to the generated meeting in a storage location monitored by the document management apparatus, and generates the material used in the meeting in the document management apparatus. Registering information about the meeting,
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. The storage type setting means further accepts the setting of the folder creation rule when the material used in the meeting and the generated information on the meeting are stored in the folder and stored in the output destination;
The information processing apparatus according to claim 2. An information storage method in an information processing apparatus for managing a meeting held between a plurality of terminal devices,
From the storage type information storage unit that stores the storage type information in which rules for storing the materials used in the meeting and the information related to the meeting under different conditions for each storage type are set, the selected storage type is selected. An information generation step of reading storage type information and generating information on the meeting based on the read storage type information;
A storage step of storing the material used in the meeting and the generated information on the meeting in the output destination set in the read storage type information,
An information storage method. An information processing device that manages a meeting held between a plurality of terminal devices,
From the storage type information storage unit that stores the storage type information in which rules for storing the materials used in the meeting and the information related to the meeting under different conditions for each storage type are set, the selected storage type is selected. Information generation means for reading storage type information and generating information on the meeting based on the read storage type information;
Storage means for storing the material used in the meeting and the generated information on the meeting in the output destination set in the read storage type information,
Program to function as. An information processing system in which an information processing device that manages a meeting performed between a plurality of terminal devices and an information storage device that stores information from the information processing device communicate via a network,
From the storage type information storage unit that stores the storage type information in which rules for storing the materials used in the meeting and the information related to the meeting under different conditions for each storage type are set, the selected storage type is selected. Information generation means for reading storage type information and generating information on the meeting based on the read storage type information;
Storage means for storing the material used in the meeting and the information about the generated meeting in the output destination set in the read storage type information;
Storage means for storing materials used in the meeting stored from the storage means and information about the generated meeting;
An information processing system having Monitoring means for monitoring the storage means;
Registration means for registering the material used in the meeting and the generated information regarding the meeting in the document management unit upon detecting the storage of the material used in the meeting and the information related to the generated meeting in the storage means; Further comprising
The information processing system according to claim 9.

Images