JP2020135023A - Display terminal, sharing system, display control method, and program - Google Patents

Abstract

To provide a display terminal capable of easily finding an action item that a user wants to confirm.SOLUTION: In a sharing system, a transmission/reception section 51 of PC5 receives action item data including a plurality of items of data concerning correspondence to an action item from a schedule management server 8. A display control section 54 displays an action item screen including a list of the plurality of received action item data on a display. A reception section 52 receives a selection of a first selection image (for example, a person-in-charge selection button, a limit date selection button, and a correspondence state selection button) in a specific item among the plurality of items on the action item screen. A display control section 54 rearranges and displays the plurality of action item data included in the action item screen according to contents of the data of the specific item when the selection for the first selection image is received.SELECTED DRAWING: Figure 8

Description

The present disclosure relates to display terminals, shared systems, display control methods and programs.

In recent years, at meetings at companies, educational institutions, government agencies, etc., electronic blackboards have been used in which a background image is displayed on a display and a user can draw stroke images such as characters, numbers, and figures on the background image. (For example, Patent Document 1).

In addition, action items occur at events such as meetings. Then, in order to prevent the execution omission of the action item that occurs in the event, the user uses a PC or the like to access the server or the like that manages the schedule (schedule, schedule, etc.) and registers the action item. For example, Patent Document 2 discloses a content for displaying action item information generated in a past meeting on a terminal device.

However, in the conventional method, the action items registered in the scheduler server or the like are displayed on the terminal device or the like in the recording order, so that it takes time and effort for the user to find the desired action item to be confirmed. There was a challenge.

In order to solve the above-mentioned problems, the invention according to claim 1 is a display terminal capable of communicating with a management system that manages an action item generated in an executed event, and has a plurality of items related to correspondence to the action item. The receiving means for receiving the action item data including the data of the above from the management system, the display control means for displaying the display screen including the list of the received plurality of received action item data on the display unit, and the display screen. When a reception means for receiving selection of a first selected image in a specific item among the plurality of items is provided and selection for the first selected image is received, the display control means is displayed on the display screen. The plurality of included action item data are rearranged and displayed according to the content of the data of the specific item.

According to the present invention, there is an effect that the action item that the user wants to confirm can be easily found.

It is the schematic of the shared system which concerns on this embodiment. It is a hardware block diagram of an electronic blackboard. It is a hardware configuration diagram of a video conferencing terminal. It is a hardware block diagram of a car navigation device. It is a hardware configuration diagram of a PC and a server. It is a software block diagram of an electronic blackboard. It is a software block diagram of a PC. It is a functional block diagram of a shared system. (A) is a conceptual diagram of the user authentication management table, (B) is a conceptual diagram of the access control table, and (C) is a conceptual diagram of the schedule management table. (A) is a conceptual diagram of the execution event management table, and (B) is a conceptual diagram of the content management table. (A) is a conceptual diagram of the user authentication management table, (B) is a conceptual diagram of the user management table, and (C) is a conceptual diagram of the union management table. (A) is a conceptual diagram of the union reservation management table, and (B) is a conceptual diagram of the event management table. (A) is a conceptual diagram of the server authentication management table, and (B) is a conceptual diagram of the project member management table. (A) is a conceptual diagram of an execution event history management table, and (B) is a conceptual diagram of an execution event management table. (A) is a conceptual diagram of a related information management table, and (B) is a conceptual diagram of an action item management table. It is a sequence diagram which showed the registration process of a schedule. It is the figure which showed the sign-in screen. This is an example of the initial screen of a PC. It is a figure which showed the schedule input screen. It is a sequence diagram which showed the event start processing. It is a figure which showed the sign-in screen displayed on the electronic blackboard. It is a figure which showed the reservation list screen of a union. It is a sequence diagram which showed the event start processing. It is the figure which showed the project list screen. It is a figure which showed the detailed information screen of an event. It is an image diagram which showed the state which a user uses an electronic blackboard. It is a sequence diagram which showed the registration process of the execution event history. It is a flowchart which showed the voice-text conversion process. It is a sequence diagram which showed the registration process of the execution event history. It is a flowchart which showed the registration process of an action item. This is an example of a screen that recognizes an action item. This is a screen example showing a list of candidates for executing action items. This is a screen example showing a calendar for selecting the expiration date of an action item. It is a sequence diagram which showed the end processing of an event. It is a sequence diagram which showed the end processing of an event. It is the figure which showed the event end screen on the electronic blackboard. It is a figure which showed the file data upload screen on an electronic blackboard. It is a figure which showed the upload completion screen of a file data on an electronic blackboard. It is a sequence diagram which showed the browsing process of the execution event history. It is a sequence diagram which showed the browsing process of the execution event history. It is a figure which showed the project list screen on the PC. It is a figure which showed the execution event list screen on the PC. It is a figure which showed the execution event history screen on the PC. It is a figure which showed the execution event history screen on the PC. It is a sequence diagram which showed the display process of an action item screen. It is a figure which showed the action item screen on the PC. It is a flowchart which showed the process of sorting action item data according to the deadline date. It is a figure which showed the action item screen which the action item data was sorted in order of the due date. It is a flowchart which showed the process of sorting action item data according to the correspondence state. It is the figure which showed the action item screen which the action item data was sorted according to the correspondence state. It is a sequence diagram which showed the change process of the correspondence state. This is a screen example when the support status change button is selected. This is a screen example showing a status candidate list. It is the figure which showed the action item screen which the correspondence state was changed. This is an example of a screen when the link button is selected. This is a screen example showing a screen for registering created data. It is a flowchart which showed the process of sorting action item data according to the person in charge. It is the figure which showed the action item screen which the action item data was sorted by the person in charge.

The shared system 1 according to the present embodiment will be described in detail below with reference to the drawings. In this embodiment, the "file" indicates an "electronic file".

<< Outline of system configuration >>
First, the outline of the configuration of the shared system 1 will be described. FIG. 1 is a schematic view of a shared system according to the present embodiment.

As shown in FIG. 1, the shared system 1 of the present embodiment includes an electronic whiteboard 2, a video conferencing terminal 3, a car navigation device 4, a PC (Personal Computer) 5, a shared support server 6, and schedule management. It is constructed by a server 8 and a voice-text conversion server 9.

Further, the electronic blackboard 2, the video conferencing terminal 3, the car navigation device 4, the PC 5, the sharing support server 6, the schedule management server 8, and the voice text conversion server 9 can communicate with each other via the communication network 10. The communication network 10 is constructed by the Internet, a mobile communication network, a LAN (Local Area Network), or the like. The communication network 10 may include not only wired communication but also a network by wireless communication such as 3G (3rd Generation), WiMAX (Worldwide Interoperability for Microwave Access) or LTE (Long Term Evolution).

Further, the electronic blackboard 2 is used in the conference room X. The video conferencing terminal 3 is used in the conference room Y. In addition, the union is subject to reservation by each user. The car navigation device 4 is used in the vehicle α. The vehicle α in this case is a vehicle that is subject to car sharing. Vehicles include cars, motorcycles, bicycles, wheelchairs and the like.

A "union" refers to an object, service, space (room), location, or information shared by multiple people or groups. The conference room X, the conference room Y, and the vehicle α are examples of a union shared by a plurality of users. An example of information given to a union is an account. For example, in a specific service provided on the Web, the account used is limited to one.

The electronic blackboard 2, the video conferencing terminal 3, and the car navigation device 4 are examples of communication terminals. The communication terminal used in the vehicle α includes not only the car navigation device 4 but also a smartphone or a smart watch in which a car navigation application is installed.

The PC 5 is an example of a display terminal, and is an example of a registration device for registering a reservation for use of each union and registering an event scheduled to be executed by each user to the schedule management server 8. Events include, for example, meetings, meetings, gatherings, gatherings, consultations, meetings, driving, boarding or traveling.

The sharing support server 6 is a computer and provides support when a union is remotely shared with each communication terminal.

The schedule management server 8 is a computer and manages reservations for each union and schedules for each user.

The voice-to-text conversion server 9 is a computer, and converts sound (voice) data received from an external computer (for example, a shared support server 6) into text data.

Here, the shared support server 6, the schedule management server 8, and the voice-to-speech conversion server 9 are referred to as a management system. The management system may be, for example, a server that bears all or part of each function of the shared support server 6, the schedule management server 8, and the voice-to-speech conversion server 9.

<< Hardware configuration >>
Subsequently, the hardware configuration of the device or terminal for constructing the shared system 1 will be described with reference to FIGS. 2 to 5.

<Hardware configuration of electronic blackboard>
FIG. 2 is a hardware configuration diagram of the electronic blackboard. As shown in FIG. 2, the electronic blackboard 2 includes a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, an SSD (Solid State Drive) 204, and a network I / It includes an F205 and an external device connection I / F (Interface) 206.

Of these, the CPU 201 controls the operation of the entire electronic blackboard 2. The ROM 202 stores a program used to drive the CPU 201 such as the CPU 201 and the IPL (Initial Program Loader). The RAM 203 is used as a work area of the CPU 201. The SSD 204 stores various data such as a program for an electronic blackboard. The network I / F 205 controls communication with the communication network 10. The external device connection I / F 206 controls communication with a USB (Universal Serial Bus) memory 2600, a PC 2700, and an external device (microphone 2200, speaker 2300, camera 2400).

Further, the electronic blackboard 2 includes a capture device 211, a GPU 212, a display controller 213, a contact sensor 214, a sensor controller 215, an electronic pen controller 216, a short-range communication circuit 219, an antenna 219a of the short-range communication circuit 219, and a power switch 222. I have.

Of these, the capture device 211 acquires the image data displayed on the display 220 via the display controller 213 and stores it in the RAM 203 or the like. The GPU (Graphics Processing Unit) 212 is a semiconductor chip that specializes in graphics. The display controller 213 controls and manages the screen display in order to output the output image from the capture device 211 or the GPU 212 to the display 220 or the like. The contact sensor 214 detects that the electronic pen 2500, the user's hand H, or the like has come into contact with the display 220. The sensor controller 215 controls the processing of the contact sensor 214. The contact sensor 214 inputs and detects the coordinates by the infrared blocking method. In this method of inputting coordinates and detecting coordinates, two light receiving and emitting devices installed at both upper ends of the display 220 emit a plurality of infrared rays in parallel with the display 220 and are provided around the display 220. This is a method of receiving light that is reflected by a reflecting member and returns on the same optical path as the light path emitted by the light receiving element. The contact sensor 214 outputs an infrared ID emitted by two light emitting / receiving devices blocked by the object to the sensor controller 215, and the sensor controller 215 specifies a coordinate position which is a contact position of the object. The electronic pen controller 216 determines whether or not there is a touch of the pen tip or a touch of the pen tail on the display 220 by communicating with the electronic pen 2500. The short-range communication circuit 219 is a communication circuit such as NFC (Near Field Communication) and Bluetooth (registered trademark). The power switch 222 is a switch for switching the power ON / OFF of the electronic blackboard 2.

Further, the electronic blackboard 2 is provided with a bus line 210. The bus line 210 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 201 shown in FIG.

The contact sensor 214 is not limited to the infrared blocking method, but is a capacitive touch panel that specifies a contact position by detecting a change in capacitance, and a contact position is specified by a voltage change between two opposing resistance films. Various detection means such as a resistance film type touch panel, an electromagnetic induction type touch panel that detects electromagnetic induction generated by contact of a contact object with a display unit, and specifies a contact position may be used. Further, the electronic pen controller 216 may determine whether or not there is a touch not only on the pen tip and pen end of the electronic pen 2500, but also on a portion held by the user of the electronic pen 2500 and other electronic pen portions.

<Hardware configuration of video conferencing terminal>
FIG. 3 is a diagram showing a hardware configuration diagram of a video conferencing terminal. As shown in FIG. 3, the video conferencing terminal 3 includes a CPU 301, a ROM 302, a RAM 303, a flash memory 304, an SSD 305, a media I / F 307, an operation button 308, a power switch 309, a bus line 310, and a network I / F 311. CMOS (Complementary Metal Oxide Semiconductor) sensor 312, image pickup element I / F 313, microphone 314, speaker 315, sound input / output I / F 316, display I / F 317, external device connection I / F 318, short-range communication circuit 319 and short-range communication The antenna 319a of the circuit 319 is provided. Of these, the CPU 301 controls the operation of the entire video conferencing terminal 3. The ROM 302 stores a program used to drive the CPU 301 such as an IPL. The RAM 303 is used as a work area of the CPU 301. The flash memory 304 stores various data such as a communication program, image data, and sound data. The SSD 305 controls reading or writing of various data to the flash memory 304 according to the control of the CPU 301. An HDD may be used instead of the SSD. The media I / F 307 controls reading or writing (storage) of data to a recording medium 306 such as a flash memory. The operation button 308 is a button that is operated when selecting a destination of the video conferencing terminal 3. The power switch 309 is a switch for switching the power ON / OFF of the video conferencing terminal 3.

Further, the network I / F311 is an interface for data communication using a communication network 10 such as the Internet. The CMOS sensor 312 is a kind of built-in imaging means for capturing an image of a subject and obtaining image data under the control of the CPU 301. The image sensor I / F 313 is a circuit that controls the drive of the CMOS sensor 312. The microphone 314 is a kind of built-in sound collecting means for inputting voice. The sound input / output I / F 316 is a circuit that processes sound signal input / output between the microphone 314 and the speaker 315 under the control of the CPU 301. The display I / F 317 is a circuit that transmits image data to the external display 320 under the control of the CPU 301. The external device connection I / F 318 is an interface for connecting various external devices. The short-range communication circuit 319 is a communication circuit such as NFC or Bluetooth.

Further, the bus line 310 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 301 shown in FIG.

The display 320 is a kind of display means composed of a liquid crystal or an organic EL for displaying an image of a subject, an operation icon, and the like. Further, the display 320 is connected to the display I / F317 by a cable 320c. The cable 320c may be a cable for analog RGB (VGA) signals, a cable for component video, DisplayPort, HDMI® (High-Definition Multimedia Interface) (registered trademark). ) Or a cable for a DVI (Digital Video Interactive) signal.

Instead of the CMOS sensor 312, it may be an image sensor such as a CCD (Charge Coupled Device) sensor. External devices such as an external camera, an external microphone, and an external speaker can be connected to the external device connection I / F318 by a USB cable or the like. When an external camera is connected, the external camera is driven in preference to the built-in CMOS sensor 312 according to the control of the CPU 301. Similarly, when an external microphone is connected or an external speaker is connected, the external microphone and the external speaker are given priority over the built-in microphone 314 and the built-in speaker 315 according to the control of the CPU 301. The external speaker is driven.

Further, the recording medium 306 has a structure that is detachable from the video conferencing terminal 3. Further, as long as it is a non-volatile memory that reads or writes data under the control of the CPU 301, not only the flash memory 304 but also an EEPROM or the like may be used.

<Hardware configuration of car navigation device>
FIG. 4 is a hardware configuration diagram of the car navigation device. As shown in FIG. 4, the car navigation device 4 includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a power switch 405, an acceleration / azimuth sensor 406, a media I / F 408, and a GPS receiver 409.

Of these, the CPU 401 controls the operation of the entire car navigation device 4. The ROM 402 stores a program used to drive the CPU 401 such as an IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data such as a program for the car navigation device 4 under the control of the CPU 401. The power switch 405 is a switch for switching the power ON / OFF of the car navigation device 4. The acceleration / azimuth sensor 406 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect the geomagnetism. The media I / F 408 controls reading or writing (storage) of data to a recording medium 407 such as a flash memory. The GPS receiving unit 409 receives GPS signals from GPS satellites.

Further, the car navigation device 4 includes a long-distance communication circuit 411, an antenna 411a of the long-distance communication circuit 411, a CMOS sensor 412, an image pickup element I / F 413, a microphone 414, a speaker 415, a sound input / output I / F 416, a display 417, and a display. It includes an I / F418, an external device connection I / F419, a short-range communication circuit 420, and an antenna 420a of the short-range communication circuit 420.

Of these, the long-distance communication circuit 411 receives traffic congestion information, road construction information, traffic accident information, etc. provided from the infrastructure outside the vehicle, and conversely transmits the vehicle position, emergency lifesaving signal, etc. to the outside. It is a circuit to do. The external infrastructure is, for example, a road information guidance system such as a VICS® (Vehicle Information and Communication System) system. The CMOS sensor 412 is a kind of built-in imaging means that images a subject and obtains image data under the control of the CPU 401. The image sensor I / F 413 is a circuit that controls the drive of the CMOS sensor 412. The microphone 414 is a kind of built-in sound collecting means for inputting voice. The sound input / output I / F 416 is a circuit that processes sound signal input / output between the microphone 414 and the speaker 415 under the control of the CPU 401. The display 417 is a kind of display means such as a liquid crystal or an organic EL for displaying an image of a subject, various icons, and the like, and has a touch panel function. The touch panel is a kind of input means for the user to operate the car navigation device 4. The display I / F 418 is a circuit for displaying an image on the display 417. The external device connection I / F419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit such as NFC or Bluetooth. Further, the car navigation device 4 includes a bus line 410. The bus line 410 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 401 shown in FIG.

<Hardware configuration of PC and server>
FIG. 5 is a hardware configuration diagram of a PC and a server. The PC 5 is constructed by a computer, and as shown in FIG. 5, the CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, media I / F 507, display 508, network I / F 509, It includes a keyboard 511, a mouse 512, a CD-RW drive 514, a speaker 515 and a bus line 510.

Of these, the CPU 501 controls the operation of the entire PC 5. The ROM 502 stores a program used to drive the CPU 501 such as an IPL. The RAM 503 is used as a work area of the CPU 501. The HD504 stores various data such as programs. The HDD (Hard Disk Drive) controller 505 controls reading or writing of various data to the HD 504 according to the control of the CPU 501. The media I / F 507 controls reading or writing (storage) of data to a recording medium 506 such as a flash memory. The display 508 displays various information such as cursors, menus, windows, characters or images. The display 508 is an example of a display unit. The network I / F 509 is an interface for performing data communication using the communication network 10. The keyboard 511 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions, and the like. The mouse 512 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The CD-RW drive 514 controls reading or writing of various data to a CD-RW (Compact Disc-ReWritable) 513 as an example of a removable recording medium. The speaker 515 outputs a sound signal according to the control of the CPU 501.

The PC 5 also includes a bus line 510. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

Further, the shared support server 6 is constructed by a computer, and as shown in FIG. 5, the CPU 601 and ROM 602, RAM 603, HD 604, HDD controller 605, recording media 606, media I / F 607, display 608, and network. It includes an I / F 609, a keyboard 611, a mouse 612, a CD-RW drive 614 and a bus line 610. These are CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording media 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514 and bus line, respectively, in PC5. Since the configuration is the same as that of 510, the description thereof will be omitted.

Further, the schedule management server 8 is constructed by a computer, and as shown in FIG. 5, the CPU 801 and ROM 802, RAM 803, HD 804, HDD controller 805, recording media 806, media I / F 807, display 808, and network. It includes an I / F 809, a keyboard 811 and a mouse 812, a CD-RW drive 814 and a bus line 810. These are CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording media 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514 and bus line, respectively, in PC5. Since the configuration is the same as that of 510, the description thereof will be omitted.

Further, the voice-to-text conversion server 9 is constructed by a computer, and as shown in FIG. 5, the CPU 901, ROM 902, RAM 903, HD 904, HDD controller 905, recording media 906, media I / F 907, display 908, and the like. It includes a network I / F 909, a keyboard 911, a mouse 912, a CD-RW drive 914 and a bus line 910. These are CPU 501, ROM 502, RAM 503, HD 504, HDD controller 505, recording media 506, media I / F 507, display 508, network I / F 509, keyboard 511, mouse 512, CD-RW drive 514 and bus line, respectively, in PC5. Since the configuration is the same as that of 510, the description thereof will be omitted.

Each of the above programs may be a file in an installable format or an executable format, and may be recorded and distributed on a computer-readable recording medium. Examples of recording media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray Disc, SD card and the like. In addition, the recording medium can be provided domestically or internationally as a program product. For example, a communication terminal such as an electronic blackboard 2 realizes a display control method according to the present invention by executing a program according to the present invention.

Further, the shared support server 6 may be constructed by a single computer, or may be constructed by a plurality of computers arbitrarily assigned by dividing each unit (function, means or storage unit). The same applies to the schedule management server 8 and the voice-to-speech conversion server 9.

<< Software configuration of electronic blackboard >>
Subsequently, the computer software installed on the electronic blackboard 2 will be described with reference to FIG. Here, the computer software (hereinafter referred to as software) is a program related to the operation of the computer and other information used for processing by the computer, and is similar to the program. A program is a command to a computer that is combined so that one result can be obtained. In addition, a program-like thing cannot be called a program because it is not a direct command to the computer, but it has properties similar to a program in that it regulates the processing of the computer. For example, the data structure (the logical structure of data represented by the interrelationship between data elements) corresponds to a program.

In addition, application is a general term for software used to perform a specific process in the classification of software. On the other hand, an operating system (hereinafter referred to as an OS) is software for controlling a computer and making computer resources available to applications and the like. The OS performs basic computer management and control such as input / output control, hardware management such as memory and hard disk, and process management. The application operates by using the function provided by the OS.

FIG. 6 is a diagram showing a software configuration of the electronic blackboard 2. As shown in FIG. 6, the OS 101, the Launcher 102, the schedule viewer 103a, the file viewer 103b, and the browser application 103c operate on the work area 15 of the RAM 203. OS101 is basic software that provides the basic functions of the electronic blackboard 2 and manages the entire electronic blackboard 2.

Launcher 102 is a launcher application that runs on OS 101. The Launcher 102 manages, for example, the start and end of an event such as a conference executed on the electronic blackboard 2, or the management of external applications such as the schedule viewer 103a, the file viewer 103b, and the browser application 103c used during the execution of the event.

The schedule viewer 103a, the file viewer 103b, and the browser application 103c are external applications (hereinafter, referred to as an external application 103 when it is not necessary to distinguish them) that operate on the Launcher 102. The external application 103 executes the process independently of the Launcher 102, and executes the service or function provided on the OS 101. Note that FIG. 6 shows an example in which three external applications, a schedule viewer 103a, a file viewer 103b, and a browser application 103c, are installed on the electronic blackboard 2, but the number of external applications is not limited to this.

<< PC software configuration >>
Subsequently, the computer software installed on the PC 5 will be described with reference to FIG. 7. FIG. 7 is a diagram showing a software configuration of a PC. As shown in FIG. 7, the OS5501, the minutes application 5502a and the browser 5502b operate on the work area 5500 of the RAM 503. OS5501 is basic software that provides the basic functions of the PC5 and manages the entire PC5.

The minutes application 5502a and the browser 5502b are applications for generating and displaying an execution event history screen which is a minutes of an event executed by the electronic blackboard 2 by using various data transmitted from the schedule management server 8. is there. Note that FIG. 7 shows an example in which two external applications, the minutes application 5502a and the browser 5502b, are installed on the PC 5, but the number of external applications is not limited to this.

<< Functional configuration of shared system >>
Subsequently, the functional configuration of the present embodiment will be described with reference to FIGS. 8 to 15. FIG. 8 is a functional block diagram of the shared system. Note that, in FIG. 8, among the terminals, devices, and servers shown in FIG. 1, those related to the processing or operation described later are shown.

<Functional configuration of electronic blackboard>
As shown in FIG. 8, the electronic blackboard 2 includes a transmission / reception unit 21, a reception unit 22, an image / sound processing unit 23, a display control unit 24, a judgment unit 25, a recognition unit 26, an acquisition / provision unit 28, and a storage unit. -Has a read processing unit 29. Each of these parts is a function or means of functioning that any of the components shown in FIG. 8 is operated by an instruction from the CPU 201 according to a program developed on the RAM 203 from the SSD 204. is there. Further, the electronic blackboard 2 has a storage unit 2000 constructed by the RAM 203, SSD 204 or USB memory 2600 shown in FIG.

(Each functional configuration of the electronic blackboard)
Next, each component of the electronic blackboard 2 will be described. The transmission / reception unit 21 is realized by the command from the CPU 201 shown in FIG. 2 and the network I / F205 and the external device connection I / F206, and various data (various data) with other terminals, devices or systems via the communication network 10. Or information) is sent and received.

The reception unit 22 is mainly realized by the command from the CPU 201 shown in FIG. 2, the contact sensor 214, and the electronic pen controller 216, and receives various inputs by the user.

The image / sound processing unit 23 is realized by the command from the CPU 201 shown in FIG. 2 and the capture device 211, and stores the image data displayed on the display 220. Further, the image / sound processing unit 23 is realized by the command from the CPU 201 shown in FIG. 2 and the GPU 212, and performs image processing for displaying the image on the display 220. Further, the image / sound processing unit 23 performs image processing on the image data obtained by the camera 2400 taking an image of the subject. Further, the image / sound processing unit 23 performs voice processing on the sound data related to the voice signal after the user's voice is converted into a voice signal by the microphone 2200. Further, the image / sound processing unit 23 outputs a voice signal related to the sound data to the speaker 2300, and outputs the voice from the speaker 2300. Further, the image / sound processing unit 23 performs a process of converting the drawn image data obtained by drawing on the display 220 with the electronic pen 2500 or the hand H by the user into coordinate data. For example, when the electronic blackboard (2a) of an arbitrary base transmits coordinate data to the electronic blackboard (2b) of another base, the electronic blackboard (2b) is on the side of the other electronic blackboard (2b) based on the coordinate data. The same drawing is displayed on the display 220.

The display control unit 24 is realized by a command from the CPU 201 shown in FIG. 2 and a display controller 213 shown in FIG. 2, and displays a drawn image on the display 220 or supports sharing using a Web browser. It accesses the server 6 and displays various screen data. Specifically, the display control unit 24 starts and executes the Launcher 102 running on the OS 101 shown in FIG. 6 and the external application 103, and various types of drawings are drawn by the API (Application Programming Interface) provided by the OS 101. The screen is displayed on the display 220.

The determination unit 25 is realized by a command from the CPU 201 shown in FIG. 2 and makes various determinations.

The recognition unit 26 is realized by a command from the CPU 201 shown in FIG. 2, and recognizes a designated area 262 surrounded on the display 220 as shown in FIG. 31 described later.

The acquisition / provision unit 28 is executed by the command from the CPU 201 shown in FIG. 2 and the short-range communication circuit 219 and the antenna 219a, and is executed by the short-range communication with a dedicated terminal such as an IC card or a smartphone. Acquires and provides data.

The storage / reading processing unit 29 is executed by the instruction from the CPU 201 and SSD204 shown in FIG. 2, and is a process of storing various data in the storage unit 2000 and reading various data stored in the storage unit 2000. I do. Further, the storage unit 2000 overwrites and stores the image data and sound data received when communicating with another electronic blackboard or video conferencing terminal each time it is received. Of these, the image is displayed on the display 220 by the image data before being overwritten, and the sound is output from the speaker 2300 by the sound data before being overwritten.

Since the video conferencing terminal 3 and the car navigation device 4 have the same functions as the electronic blackboard 2, description thereof will be omitted here.

<Functional configuration of PC>
The PC 5 has a transmission / reception unit 51, a reception unit 52, a display control unit 54, a generation unit 56, a sound control unit 58, and a storage / reading processing unit 59. Each of these parts is a function or a functioning means realized by operating any of the components shown in FIG. 8 by an instruction from the CPU 501 according to a program developed on the RAM 503 from the HD 504. .. In addition, the PC 5 has a storage unit 5000 constructed by the HD 504 shown in FIG.

(Each function configuration of PC)
Next, each component of the PC 5 will be described. The transmission / reception unit 51 is realized by the command from the CPU 501 and the network I / F 509 shown in FIG. 5, and transmits / receives various data (or information) to / from another terminal, device, or system via the communication network 10. The transmission / reception unit 51 is an example of a reception means.

The reception unit 52 is mainly realized by the command from the CPU 501 shown in FIG. 5 and the keyboard 511 and the mouse 512, and receives various inputs by the user. The reception unit 52 is an example of reception means.

The display control unit 54 is realized by a command from the CPU 501 shown in FIG. 5, and displays an image on the display 508 or accesses the shared support server 6 using a Web browser to display various screen data. To do. Specifically, the display control unit 54 accesses the shared support server 6 or the schedule management server 8 by, for example, starting and executing the minutes application 5502a or the browser 5502b running on the OS 5501 shown in FIG. .. Then, the display control unit 54 downloads, for example, a Web APP (Web Application) including HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JAVA SCRIPT, and the like, and various image data generated by the Web APP are downloaded. , Displayed on the display 508. The display control unit 54 causes the display 508 to display image data generated by HTML5 including data in, for example, XML (Extensible Markup Language), JSON (JavaScript Object Notation), or SOAP (Simple Object Access Protocol) format. The display control unit 54 is an example of the display control means.

The generation unit 56 is a function realized by a command from the CPU 501 shown in FIG. 5 and generates various image data to be displayed on the display 508. The generation unit 56 generates various image data using the content data received by the transmission / reception unit 51. For example, the generation unit 56 generates image data related to the text data which is the content image data in order to render the text data which is the content data and display the rendered data. Rendering is a process of interpreting data described in a language for describing a Web page (HTML, CSS, XML, etc.) and calculating the arrangement of characters, image data, and the like actually displayed on the screen.

The sound control unit 58 is a function realized by a command from the CPU 501 shown in FIG. 5 and outputs a sound signal from the speaker 515. The sound control unit 58 sets the sound data to be output from the speaker 515, and outputs the sound signal related to the set sound data from the speaker 515 to reproduce the sound data.

The storage / reading processing unit 59 is executed by a command from the CPU 501 shown in FIG. 5 and an HDD controller 505 or the like to store various data in the storage unit 5000 or read various data from the storage unit 5000. Perform processing.

<Functional configuration of shared support server>
The shared support server 6 has a transmission / reception unit 61, an authentication unit 62, a creation unit 63, a generation unit 64, a determination unit 65, and a storage / reading processing unit 69. Each of these parts functions or functions as any of the components shown in FIG. 8 operates by an instruction from the CPU 601 according to the sharing support program developed on the RAM 603 from the HD 604. It is a means. Further, the shared support server 6 has a storage unit 6000 constructed by the HD 604 or the like shown in FIG.

(User authentication management table)
FIG. 9A is a conceptual diagram showing a user authentication management table. In the storage unit 6000, a user authentication management DB 6001 configured by a user authentication management table as shown in FIG. 9A is constructed. In this user authentication management table, a user ID for identifying a user, a user name, an organization ID for identifying an organization to which the user belongs, and a password are associated and managed. The organization ID also includes a domain name representing a group or organization for managing a plurality of computers on a communication network.

(Access control table)
FIG. 9B is a conceptual diagram showing an access management table. In the storage unit 6000, an access management DB 6002 configured by an access management table as shown in FIG. 9B is constructed. In this access management table, the organization ID, the access ID required for authentication when accessing the schedule management server 8, and the access password are associated and managed. The access ID and access password are obtained by the shared support server 6 by the schedule management server 8 via a Web API (Application Programming Interface) or the like using an HTTP (Hypertext Transfer Protocol) or HTTPS (Hypertext Transfer Protocol Secure) protocol. It is necessary to use the provided service (function). The schedule management server 8 manages a plurality of schedulers, and the schedulers used may differ depending on the organization. Therefore, it is necessary to manage them in the access management table.

(Schedule management table)
FIG. 9C is a conceptual diagram showing a schedule management table. A schedule management DB 6003 composed of a schedule management table as shown in FIG. 9C is constructed in the storage unit 6000. In this schedule management table, for each scheduled event ID and execution event ID, the organization ID, the user ID of the reservation person, the presence / absence of participation of this reservation person, the reservation person name, the scheduled start time, the scheduled end time, the event name, etc. The user ID of the participant, the presence / absence of participation of other participants, the names of other participants, and the file data are associated and managed.

Of these, the scheduled event ID is identification information for identifying a reserved event. The scheduled event ID is an example of scheduled event identification information for identifying an event scheduled to be executed. The execution event ID is identification information for identifying an event that was actually executed among the reserved events. The execution event ID is an example of execution event identification information for identifying the event being executed. The name of the person making the reservation is the name of the person who reserved the union, for example, the name of the organizer when the union is a conference room, and the name of the driver when the union is a vehicle. The scheduled start time indicates the scheduled start time of the union. The scheduled end time indicates the scheduled end time of use of the union. The event name indicates the name of the event scheduled to be executed by the reservation person. The user IDs of other participants are identification information for identifying participants other than the reservation person. Other participant names are the names of participants other than the reservation person, and include unions. That is, the users in this case include unions as well as reservations and other participants. The file data is the file data of the material file used in the event corresponding to the scheduled event ID registered by the user A using the schedule input screen 550 (see FIG. 19) described later. The file data is data in a predetermined file format created by using various applications. The file format of the file data is, for example, a PowerPoint file, an Excel file, or the like.

(Execution event management table)
FIG. 10A is a conceptual diagram showing an execution event management table. In the storage unit 6000, an execution event management DB 6004 configured by an execution event management table as shown in FIG. 10A is constructed. In this execution event management table, the execution event ID is associated and managed for each project ID. The project ID is identification information for identifying the project (an example of the project identification information). A project represents a group, team, or group of members to achieve a particular goal, plan, or project. Members belonging to the same project can share the execution event history such as the minutes of the event associated with the project ID. As shown in FIG. 24 described later, the project ID is assigned to each project such as next year's policy and customer development. The project ID may be referred to as a group ID or a team ID.

(Content management table)
FIG. 10B is a conceptual diagram showing a content management table. In the storage unit 6000, a content management DB 6005 composed of a content management table as shown in FIG. 10B is constructed. In this content management table, the content processing ID, the type of content processing, the content of the content, and the start date and time and the end date and time of the content processing are managed in association with each execution event ID. Here, the content is the content of an execution event that occurred in an event such as a meeting in a certain project, or the material used in the event. Types of content processing include recording, snapshots, receiving audio text, generating action items, sending materials, and so on. Further, the content processing ID is identification information for identifying the processing of the content generated in each event.

Here, the content includes historical information indicating the execution content of the event and action items generated by the executed event. The history information is data such as recorded data, snapshots, voice texts or materials. A snapshot is a process of acquiring a display screen as image data at a certain point in time of an event being executed. Note that snapshots are also referred to as, for example, capture or image recognition.

When the type of content processing is "recording", the content of the content includes a URL indicating a storage destination of the recorded sound data. When the type of content processing is "snapshot", the content of the content includes a URL indicating a save destination of the image data of the screen acquired by the snapshot (capture). The capture is to save the image (still image, moving image) displayed on the display 220 as image data. Further, when the type of content processing is "voice text reception", the content of the content includes a URL indicating a storage destination of the text data of the received voice text.

Here, the action item indicates the content of an action that occurs at an event such as a meeting in a certain project and should be handled by a person related to the event. When the type of content processing is "action item occurrence", the content content is the user ID of the performer of the action item, the deadline date for completing the action item, and the URL indicating the storage destination of the image data indicating the action item. including.

(Each function configuration of the shared support server)
Next, each functional configuration of the shared support server 6 will be described in detail. In the following description, in explaining each functional configuration of the shared support server 6, among the constituent elements shown in FIG. 5, the main constituent elements for realizing each functional configuration of the shared support server 6 are used. The relationship is also explained.

The transmission / reception unit 61 of the shared support server 6 shown in FIG. 8 is realized by the instruction from the CPU 601 shown in FIG. 5 and the network I / F 609 shown in FIG. 5, and is realized via the communication network 10. Sends and receives various data (or information) to and from other terminals, devices, or systems.

The authentication unit 62 is realized by the command from the CPU 601 shown in FIG. 5, and the information (user ID, organization ID and password) sent from the communication terminal is registered in the user authentication management DB 6001 in advance. Authentication is performed by determining whether the information is present.

The creation unit 63 is realized by the instruction from the CPU 601 shown in FIG. 5, and is as shown in FIG. 22 described later based on the reservation information and the schedule information sent from the schedule management server 8. Create a reservation list screen 230.

The generation unit 64 is realized by the instruction from the CPU 601 shown in FIG. 5, and generates the execution event ID, the content processing ID, and the URL of the storage destination.

The determination unit 65 is realized by the command from the CPU 601 shown in FIG. 5 and makes various determinations. This determination will be described later.

The storage / reading processing unit 69 is realized by the command from the CPU 601 shown in FIG. 5 and the HDD controller 605 shown in FIG. 5, and various data can be stored in the storage unit 6000 or stored in the storage unit 6000. Performs processing such as reading out various stored data.

<Functional configuration of schedule management server>
The schedule management server 8 has a transmission / reception unit 81, an authentication unit 82, a generation unit 83, and a storage / reading processing unit 89. Each of these parts functions or functions as any of the components shown in FIG. 8 operates by an instruction from the CPU 801 according to a schedule management program developed from the HD 804 on the RAM 803. It is a means. Further, the schedule management server 8 has a storage unit 8000 constructed by the HD 804 shown in FIG.

(User authentication management table)
FIG. 11A is a conceptual diagram showing a user authentication management table. In the storage unit 8000, a user authentication management DB 8001 composed of a user authentication management table as shown in FIG. 11A is constructed. In this user authentication management table, an organization ID and a password for identifying an organization to which a user belongs are associated with a user ID for identifying a user and managed.

(User management table)
FIG. 11B is a conceptual diagram showing a user management table. In the storage unit 8000, a user management DB 8002 composed of a user management table as shown in FIG. 11B is constructed. In this user management table, the user ID and the user name (user name) indicated by the user ID are associated and managed for each organization ID.

(Union management table)
FIG. 11C is a conceptual diagram showing a union management table. In the storage unit 8000, a union management DB 8003 composed of a union management table as shown in FIG. 11C is constructed. In this union management table, the union ID for identifying the union and the name of the union (union name) are associated and managed for each organization ID.

(Union reservation management table)
FIG. 12A is a conceptual diagram showing a union reservation management table. The union reservation management DB 8004 configured by the union reservation management table as shown in FIG. 12A is constructed in the storage unit 8000. In this union reservation management table, reservation information in a state in which each information is associated is managed. The reservation information includes a union ID, a union name, a user ID of the reservation person, a scheduled start date and time of use, a scheduled date and time of end of use, and an event name for each organization ID. Of these, the scheduled start date and time of use indicates the scheduled start date and time of use of the union. The scheduled end date and time of use indicates the scheduled end date and time of use of the union. Each date and time shows the year, month, day, hour, minute, second, and time zone, but in FIG. 12A, due to space limitations, the year, month, day, hour, and minute are also shown.

(Event management table)
FIG. 12B is a conceptual diagram showing an event management table. In the storage unit 8000, an event management DB 8005 composed of an event management table as shown in FIG. 12B is constructed. In this event management table, schedule information in a state in which each information is associated is managed. In the schedule information, a user ID, a user name, an event start scheduled date and time, an event end scheduled date and time, and an event name are associated and managed for each organization ID. Of these, the scheduled start date and time of the event indicates the scheduled start date and time when the event is executed. The scheduled end date and time of the event indicates the scheduled end date and time when the event is executed. Each date and time shows the year, month, day, hour, minute, second, and time zone, but in FIG. 12B, due to space limitations, the year, month, day, hour, and minute are also shown. Further, in the event management table, the file data of the material file used in the event shown in the schedule information is managed in association with the schedule event ID.

(Server authentication management table)
FIG. 13A is a conceptual diagram showing a server authentication management table. In the storage unit 8000, a server authentication management DB 8006 configured by a server authentication management table as shown in FIG. 13A is constructed. In this server authentication management table, the access ID and the access password are managed in association with each other. The access ID and access password have the same concept as the access ID and access password managed by the access management DB 6002 of the shared support server 6.

(Project member management table)
FIG. 13B is a conceptual diagram showing a project member management table. The storage unit 8000 is constructed with a project member management DB 8007 composed of a project member management table as shown in FIG. 13 (B). In this project member management table, the project ID, the project name, and the user ID of each project member are managed in association with each organization ID.

(Execution event history management table)
FIG. 14A is a conceptual diagram showing an execution event history management table. In the storage unit 8000, an execution event history management DB 8008 configured by an execution event history management table as shown in FIG. 14A is constructed. In this execution event history management table, the content processing ID, the type of content processing, the content of the content, and the start date and time and the end date and time of the content processing are managed in association with each project ID and the execution event ID. The execution event history management DB 8008 manages a part of the same data as the content management DB 6005. The same data is the execution event ID, the content processing ID, the type of content processing, the start date and time and the end date and time of the content processing. The contents of the content are the same, except that the notation method (http: // or c: //) of the save destination of the content data is different.

(Execution event management table)
FIG. 14B is a conceptual diagram showing an execution event management table. In the storage unit 8000, an execution event management DB 8009 composed of an execution event management table as shown in FIG. 14B is constructed. In this execution event management table, an event name, an event start date and time, and an event end date and time are associated and managed for each execution event ID. The execution event management DB 8009 manages information related to an actually executed event among the schedule information managed in the event management DB 8005.

(Related information management table)
FIG. 15A is a conceptual diagram showing a related information management table. In the storage unit 8000, a related information management DB 8010 configured by a related information management table as shown in FIG. 15A is constructed. In this related information management table, related information in a state in which each information (data) is associated is managed for each project ID and execution event ID. The related information is managed in association with the time zone in which the content is generated, the sound data, the voice text data, and the screen data. The content occurrence time zone indicates the elapsed time from the start date and time of the event at the time when the content is generated in the executed event. The time zone in which the content is generated is an example of time information. Further, the sound data includes a content processing ID and a content type. The voice text data and the screen data include a content processing ID, a content type, and a sequence number. The sequence No. indicates the order of occurrence time when the content processing occurs in each of the voice text data and the screen data.

(Action item management table)
FIG. 15B is a conceptual diagram showing an action item management table. In the storage unit 8000, an action item management DB 8011 configured by an action item management table as shown in FIG. 15B is constructed. In this action item management table, action item data in a state in which information (data) of a plurality of items related to correspondence to action items is associated with each project ID and execution event ID is managed. The action item data is associated with the content of the action item, the user ID of the performer of the action item, the deadline for completing the action item, the status of the response to the action item, and the output generated by the response to the action item. Is managed. The content of the action item includes a URL indicating a storage destination of image data indicating the received action item. Further, the state of correspondence to the action item is represented by "ToDo" or "Doing" for the action item requiring the correspondence, and is represented by "Doing" for the corresponding action item. The state of the action item is changed by the corresponding state change button 716 such as the action item screen 710 described later. Further, the output includes a URL indicating a storage destination of the created data created by corresponding to the action item.

(Each function configuration of schedule management server)
Next, each functional configuration of the schedule management server 8 will be described in detail. In the following description, in explaining each functional configuration of the schedule management server 8, among the constituent elements shown in FIG. 5, the main constituent elements for realizing each functional configuration of the schedule management server 8 are used. The relationship is also explained.

The transmission / reception unit 81 of the schedule management server 8 shown in FIG. 8 is realized by the instruction from the CPU 801 shown in FIG. 5 and the network I / F809 shown in FIG. 5, and is realized via the communication network 10. Sends and receives various data (or information) to and from other terminals, devices, or systems. The transmission / reception unit 81 is an example of transmission means.

The authentication unit 82 is realized by the command from the CPU 801 shown in FIG. 5, and the information (user ID, organization ID and password) sent from the union is registered in the user authentication management DB 8001 in advance. Authentication is performed by determining whether the information is present. In addition, the authentication unit 82 authenticates by determining whether the information (access ID and access password) sent from the shared support server 6 is the information registered in advance in the server authentication management DB 8006.

The generation unit 83 is a function that is realized by the instruction from the CPU 801 shown in FIG. 5 and generates the related information registered in the related information management DB 8010.

The storage / reading processing unit 89 is realized by the command from the CPU 801 shown in FIG. 5 and the HDD controller 805 shown in FIG. 5, and various data can be stored in the storage unit 8000 or stored in the storage unit 8000. Performs processing such as reading out various stored data.

<Functional configuration of voice-to-text conversion server>
The voice-text conversion server 9 includes a transmission / reception unit 91, a conversion unit 93, and a storage / reading processing unit 99. Each of these parts is a function or a functioning means realized by operating any of the components shown in FIG. 5 by an instruction from the CPU 901 according to a program developed on the RAM 903 from the HD 904. .. Further, the voice-to-text conversion server 9 has a storage unit 9000 constructed by the HD904 shown in FIG.

(Voice-text conversion server function configuration)
Next, each functional configuration of the voice-to-text conversion server 9 will be described in detail. In the following, in explaining each functional configuration of the voice-text conversion server 9, among the constituent elements shown in FIG. 5, the main constituent elements for realizing each functional configuration of the voice-text conversion server 9. The relationship with is also explained.

The transmission / reception unit 91 of the voice-to-text conversion server 9 shown in FIG. 8 is realized by the command from the CPU 901 shown in FIG. 5 and the network I / F 909 shown in FIG. 5, and provides the communication network 10. Sends and receives various data (or information) to and from other terminals, devices, or systems via.

The conversion unit 93 is realized by the command from the CPU 901 shown in FIG. 5, and converts the sound data received by the transmission / reception unit 91 via the communication network 10 into text data.

The storage / reading processing unit 99 is realized by the command from the CPU 901 shown in FIG. 5 and the HDD controller 905 shown in FIG. 5, and various data can be stored in the storage unit 9000 or stored in the storage unit 9000. Performs processing such as reading out various stored data.

Each of the above IDs is an example of identification information. In addition, the organization ID includes a company name, a business establishment name, a department name, an area name, and the like. The user ID includes an employee number, a driver's license number, my number in Japan's social security / tax number system, and the like.

<< Processing or operation of the embodiment >>
Hereinafter, the processing or operation of each embodiment will be described.

<Schedule registration process>
Here, a process in which the reservation person A (Rikotaro) registers his / her own schedule from the PC 5 to the schedule management server 8 will be described with reference to FIGS. 16 to 19. FIG. 16 is a sequence diagram showing a schedule registration process. FIG. 17 is a diagram showing a sign-in screen. FIG. 18 is an example of an initial screen of a PC. FIG. 19 is a diagram showing a schedule input screen.

First, when the user A operates the keyboard 511 or the like of the PC 5, the display control unit 54 of the PC 5 displays the sign-in screen 530 for signing in on the display 508 as shown in FIG. Display (step S11). On the sign-in screen 530, an input field 531 for entering the user ID and organization ID of the user, an input field 532 for entering the password, a sign-in button 538 pressed when signing in, and sign-in are displayed. It includes a cancel button 539 that is pressed when canceling. Here, the user ID and the organization ID are the e-mail addresses of the user A. The user name part of the e-mail address is the user ID, and the domain name part is the organization ID. The input field 531 may be an input field for separately inputting the user ID and the organization ID instead of the e-mail address.

Next, when the user A inputs his / her user ID and organization ID in the input field 531, enters his / her password in the input field 532, and presses the sign-in button 538, the reception unit 52 signs in. (Step S12). Then, the transmission / reception unit 51 of the PC 5 transmits the sign-in request information indicating the sign-in request to the schedule management server 8 (step S13). The sign-in request information includes the information (user ID, organization ID, and password) received in step S12. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the sign-in request information.

Next, the authentication unit 82 of the schedule management server 8 authenticates the user A by using the user ID, the organization ID, and the password (step S14). Specifically, the storage / reading processing unit 89 is a user corresponding to the set of the user ID, the organization ID, and the password received in step S13 in the user authentication management DB 8001 (see FIG. 11A). Search for ID, organization ID and password pairs. If there is a corresponding pair, the authentication unit 82 determines that the requesting user A is a legitimate user. If there is no corresponding pair, the authentication unit 82 determines that the user A is an unjust (illegal) user. If it is not valid, the transmission / reception unit 81 notifies the PC5 that it is not valid, but here, the case where it is valid will be continued.

Next, the transmission / reception unit 81 transmits the authentication result to the PC 5 (step S15). As a result, the transmission / reception unit 51 of the PC 5 receives the authentication result.

Next, when the authentication result is received in step 15, the generation unit 56 of the PC 5 generates an initial screen 540 as shown in FIG. 18 (step S16). Then, the display control unit 54 of the PC 5 displays the initial screen 540 as shown in FIG. 18 on the display 508 (step S17). The initial screen 540 includes a "schedule registration" button 541 for registering a schedule and a "execution event history browsing" button 543 for browsing action items. Here, when the user presses the "schedule registration" button 541, the reception unit 52 accepts the schedule registration (step S18). Then, the transmission / reception unit 51 transmits a schedule registration request to the schedule management server 8 (step S19). As a result, the transmission / reception unit 81 of the schedule management server 8 receives the schedule registration request.

Next, the storage / reading processing unit 89 of the schedule management server 8 searches the user management DB 8002 (see FIG. 11B) using the organization ID received in step S13 as a search key, and all the corresponding items. Read the user ID and all user names (step S20). Then, the transmission / reception unit 81 transmits the schedule input screen information to the PC 5 (step S21). The schedule input screen information includes all user IDs and all user names read in step S20. All the user names also include the name (name) of the reservation person who is the user A who input for sign-in in step S12. As a result, the transmission / reception unit 51 of the PC 5 receives the schedule input screen information.

Next, in the PC 5, the generation unit 56 generates the schedule input screen 550 by using the schedule input screen information received in step S21. (Step S22). Then, the display control unit 24 of the PC 5 displays the schedule input screen 550 as shown in FIG. 19 on the display 508 (step S23).

In this schedule input screen 550, input the input field 551 for inputting the event name, the input field 552 for inputting the union ID or the union name, and the scheduled start date and time of event execution (use of the union). Input field 553 for, event execution (use of union) input field 554 for inputting the scheduled end date and time, input field 555 for inputting memos such as agenda, display area for displaying the name of the person making the reservation 556, selection menu 557 for selecting the participant name of a participant other than the reservation person, "OK" button 558 for being pressed when registering a reservation, canceling the entered or entered contents Includes a "CANCEL" button 559 for. The reservation person name is the name of the user who entered the PC5 for sign-in in step S12. The mouse pointer p1 is also displayed.

An e-mail address may be entered in the input field 552. Also, when a union name is selected in the selection menu 557, the union is also added as another participant.

Next, the user A inputs a predetermined item in the input fields 551 to 555, selects the name (user name) of the user who wants to participate in the event from the selection menu 557 using the mouse pointer p1. When the "OK" button 558 is pressed, the reception unit 52 accepts the input of the schedule information (step S24). Then, the transmission / reception unit 51 transmits the schedule information to the schedule management server 8 (step S25). This schedule information includes an event name, a union ID (or union name), a scheduled start date and time, a scheduled end date and time, a user ID of each participant, and a memo. When the union ID is entered in the input field 552 on the schedule input screen 550, the union ID is transmitted, and when the union name is entered in the input field 552, the union name is entered. Is sent. Further, on the schedule input screen 550, the user name is selected in the selection menu 557, but since the user ID is also received in step S21, the user ID corresponding to the user name is transmitted. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the schedule information.

Next, the schedule management server 8 searches the union management DB 8003 (see FIG. 11 (C)) using the union ID (or union name) received in step S25 as a search key to search for the corresponding union. Read the name (or union ID) (step S26).

Next, the storage / reading processing unit 89 stores the reservation information in the union reservation management DB 8004 (see FIG. 12A) (step S27). In this case, the storage / reading processing unit 89 adds the reservation information for one record to the union reservation management table of the union reservation management DB 8004 managed by the scheduler registered in advance. The reservation information is configured based on the schedule information received in step S25 and the union name (or union ID) read in step S26. The scheduled start date and time in the union reservation management DB 8004 corresponds to the scheduled start date and time in the schedule information. Further, the scheduled end date and time of use in the union reservation management DB 8004 corresponds to the scheduled end date and time in the schedule information.

Further, the storage / reading processing unit 89 stores the schedule information in the event management DB 8005 (see FIG. 12B) (step S28). In this case, the storage / reading processing unit 89 adds the schedule information for one record to the event management table of the event management DB 8005 managed by the scheduler registered in advance. The schedule information is configured based on the schedule information received in step S25. The scheduled event start date and time in the event management DB 8005 corresponds to the scheduled start date and time in the schedule information. The scheduled event end date and time in the event management DB 8005 corresponds to the scheduled end date and time in the schedule information.

As described above, the user A can register his / her own schedule in the schedule management server 8.

<Event start processing>
Here, using FIGS. 20 to 26, a process of having a meeting with other participants using the electronic blackboard 2 in the meeting room X reserved by the reservation person A (Rikotaro) will be described. 20 and 23 are sequence diagrams showing the start processing of the event. FIG. 21 is a diagram showing a sign-in screen displayed on the electronic blackboard. FIG. 22 is a diagram showing a reservation list screen of the union. FIG. 24 is a diagram showing a project list screen. FIG. 25 is a diagram showing a detailed information screen of the event. FIG. 26 is an image diagram showing a state in which the user uses the electronic blackboard.

First, when the user A presses the power switch 222 of the electronic blackboard 2, the reception unit 22 of the electronic blackboard 2 receives the power ON from the user (step S31). When the power ON is received by the reception unit 22, the Launcher 102 shown in FIG. 6 is activated. Then, as shown in FIG. 21, the display control unit 24 of the electronic blackboard 2 displays a sign-in screen 110 for signing in on the display 220 (step S32). On the sign-in screen 110, the selection icon 111 that is pressed when the user A signs in using his / her IC card, and the user A signs in by entering his / her e-mail address and password. Includes a selection icon 113 that is pressed when the power is turned off, and a power icon 115 that is pressed when the power is turned off without signing in.

Next, when the user A presses the selection icon 111 or the selection icon 113 and communicates with the short-distance communication circuit 219 such as an IC card reader or the user A inputs his / her own e-mail address and password. The reception unit 22 receives the sign-in request (step S33). Then, the transmission / reception unit 21 transmits the sign-in request information indicating the sign-in request to the sharing support server 6 (step S34). The sign-in request information includes time zone information of the country or region where the electronic blackboard 2 is installed, a user ID and organization ID of the communication terminal (here, the electronic blackboard 2), and a password. As a result, the transmission / reception unit 61 of the sharing support server 6 receives the sign-in request information.

Next, the authentication unit 62 of the shared support server 6 authenticates the user A by using the user ID, the organization ID, and the password (step S35). Specifically, the storage / reading processing unit 69 receives the above in the user authentication management DB 6001 (see FIG. 9A) using the user ID, organization ID, and password received in step S35 as search keys. Search for the set of user ID, organization ID and password corresponding to the set of user ID, organization ID and password. If there is a corresponding pair, the authentication unit 62 determines that the requesting user A is a legitimate user. If there is no corresponding pair, the authentication unit 62 determines that the requesting user A is an unjust (illegal) user. If it is not valid, the transmission / reception unit 61 notifies the electronic blackboard 2 that it is not valid, but here, the case where it is valid will be continued.

Next, the storage / reading processing unit 69 of the shared support server 6 searches the access management DB 6002 (see FIG. 9B) using the organization ID received in step S34 as a search key to obtain the corresponding access ID and Read the access password (step S36).

Next, the transmission / reception unit 61 transmits the reservation request information indicating the request for the reservation information of the union and the schedule request information indicating the request for the user's schedule information to the schedule management server 8 (step S37). The reservation request information and the schedule request information include the time zone information received in step S34, the user ID and organization ID of the communication terminal, and the access ID and password read in step S36. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the reservation request information and the schedule request information.

Next, the authentication unit 82 of the schedule management server 8 authenticates the shared support server 6 by using the access ID and the access password (step S38). Specifically, the storage / reading processing unit 89 sets the access ID and access password corresponding to the set of access ID and access password received in step S37 in the server authentication management DB 8006 (see FIG. 13A). To search for. If there is a corresponding pair, the authentication unit 82 determines that the requesting shared support server 6 is a legitimate accessor. If there is no corresponding pair, the authentication unit 82 determines that the requesting shared support server 6 is an unjustified (illegal) accessor. If it is not valid, the transmission / reception unit 81 notifies the shared support server 6 that it is not valid, but here, the case where it is valid will be continued.

The storage / reading processing unit 89 of the schedule management server 8 uses the user ID of the communication terminal received in step S37 as a search key, and manages the union reservation management DB 8004 by the scheduler specified above (FIG. 12 (FIG. 12). By searching (see A)), the corresponding reservation information is read out (step S39). In this case, the storage / reading processing unit 89 reads out the reservation information whose scheduled start date and time is today.

Further, the storage / reading processing unit 89 responds by searching the event management DB 8005 (see FIG. 12B) specified above using the user ID of the communication terminal received in step S37 as a search key. Read the schedule information to be performed (step S40). In this case, the storage / reading processing unit 89 reads out the schedule information whose scheduled event start date and time is today. If the schedule management server 8 is located in a country or region different from the communication terminal such as the electronic blackboard 2, the time zone is set according to the country or region where the communication terminal is installed based on the time zone information. I'm adjusting.

Next, the storage / reading processing unit 89 uses the communication terminal user ID received in step S37 as a search key to search the project member management DB 8007 (see FIG. 13B) to use the communication terminal. Read out the project IDs and project names of all the projects including the person ID (step S41).

Next, the transmission / reception unit 81 tells the shared support server 6 the reservation information read in step S39, the schedule information read in step S40, and all the project IDs and all projects read in step S41. The name is transmitted (step S42). As a result, the transmission / reception unit 61 of the shared support server 6 receives the reservation information, the schedule information, all the project IDs, and all the project names.

Next, the creation unit 63 of the sharing support server 6 creates a reservation list based on the reservation information and the schedule information received in step S42 (step S43). Then, the transmission / reception unit 61 transmits the reservation list information indicating the contents of the reservation list, all project IDs, and all project names to the electronic blackboard 2 (step S44). As a result, the transmission / reception unit 21 of the electronic blackboard 2 receives the reservation list information, all project IDs, and all project names.

Next, on the electronic blackboard 2, the display control unit 24 displays the reservation list screen 230 as shown in FIG. 22 on the display 220 (step S45). The reservation list screen 230 includes a display area 231 for displaying a union name (here, a place name) and a display area 232 for displaying today's date and time. Further, on the reservation list screen 230, event information 235, 236, 237 and the like indicating an event using today's union (here, conference room X) are displayed. Each event information includes the scheduled start time and end time of use of the union, the event name, and the name of the person who reserved the union (reserver name) for each event. The event information includes start buttons 235s, 236s, 237s and the like that are pressed when the user identifies an event to be started.

Next, in FIG. 23, when the user A presses the start button 235s with, for example, the electronic pen 2500, the reception unit 22 accepts the selection of the event indicated by the event information 235 (step S51). Then, the display control unit 24 displays the project list screen 240 as shown in FIG. 24 on the display 220 based on the project ID and the project name received in step S42 (step S52). The project list screen 240 includes project icons 241 to 246 indicating each project. Further, the project list screen 240 includes an "OK" button 248 to be pressed when confirming the selected project icon, and a "CANCEL" button 249 to cancel the selection of the project icon.

Next, in FIG. 24, when the user A presses the project icon 241 with, for example, the electronic pen 2500, the reception unit 22 accepts the selection of the project indicated by the project icon 241 (step S53).

Next, the transmission / reception unit 21 of the electronic blackboard 2 transmits the scheduled event ID indicating the scheduled event selected in step S51 and the project ID indicating the project selected in step S53 to the shared support server 6. (Step S54). The process of step S54 is a process of requesting transmission of execution event identification information. As a result, the transmission / reception unit 61 of the shared support server 6 receives the selected scheduled event ID and the selected project ID.

Next, in the shared support server 6, the generation unit 64 generates a unique execution event ID (step S55). Then, the storage / reading processing unit 69 manages the execution event ID generated in step S55, the reservation event ID received in step S54, the user ID and organization ID of the reservation person, and the event information in association with each other (step). S56). The user ID and organization ID of the reservation person, and the event information are IDs and information based on the reservation information and the schedule information received in step S42. At this point, there is no entry in the participation presence / absence column in the reservation management table (see FIG. 9C).

Next, the storage / reading processing unit 69 manages the project ID received in step S54 in association with the execution event ID generated in step S55 (step S57).

Next, in the sharing support server 6, the transmission / reception unit 61 transmits the file data transmission request information indicating the transmission request of the file data registered in the schedule management server 8 to the schedule management server 8 (step S58). The file data transmission request information includes the event ID received in step S54, the user ID and organization ID of the communication terminal received in step S34, and the access ID and access password read in step S36. There is. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the file data transmission request information.

Next, the storage / reading processing unit 89 of the schedule management server 8 is associated with the event ID by searching the event management DB 8005 (see FIG. 12B) using the event ID received in step S58 as a search key. Read the file data (step S59). Then, the transmission / reception unit 81 transmits the file data read in step S59 to the sharing support server 6 (step S60). As a result, the transmission / reception unit 61 of the sharing support server 6 receives the file data.

Next, the storage / reading processing unit 69 of the shared support server 6 associates the scheduled event ID received in step S54 and the execution event ID generated in step S55 with the file data received in step S60. It is stored and managed in the schedule management DB 6003 (step S61).

Then, the transmission / reception unit 61 transmits the execution event ID generated in step S55 and the file data received in step S60 to the electronic blackboard 2 (step S62). As a result, the transmission / reception unit 21 of the electronic blackboard 2 receives the execution event ID and the file data.

Next, in the electronic blackboard 2, the storage / reading processing unit 29 stores the execution event ID and the file data in the storage unit 2000 (step S63). Here, the file data transmitted from the shared support server 6 is stored in a specific storage area of the storage unit 2000. Therefore, the electronic blackboard 2 causes the display control unit 24 to display the file data stored in the specific storage area on the display 220 by accessing the specific storage area during the execution of the event.

Next, the display control unit 24 displays the detailed information screen 250 of the selected event on the display 220 as shown in FIG. 25 (step S64). The detailed information screen 250 of this event includes a display area 251 for the event name, a display area 252 for the scheduled event implementation time (scheduled start time and scheduled end time), and a display area 253 for the reserved person name. Further, on the event detailed information screen 250, a display area 256 for displaying the contents of the memo, a display area 257 for displaying the names of prospective participants, and a file stored in a specific storage area of the storage unit 2000 are displayed. A display area 258 for displaying identification information (for example, a file name) for identifying data is displayed. In the display area 257, the name of the reserved person and the names of other selected participants shown in FIG. 19 are displayed, and each prospective participant name is used to check who is actually attending the meeting. Check box is displayed. Further, in the display area 258, the file data stored in the specific storage area of the storage unit 2000, that is, the file name of the file data downloaded from the sharing support server 6 is displayed, and the file data is downloaded from the sharing support server 6. The file name of the file data inside is also displayed. Further, on the lower right side of the event detailed information screen 250, a "close" button 259 for closing the detailed information screen 250 is included.

Next, when the user checks the check box of the user who is actually participating among the names of the prospective participants and presses the "close" button 259, the reception unit 22 accepts the selection of the participant. (Step S65). Then, the transmission / reception unit 21 transmits the user ID of each prospective participant and information indicating the presence / absence of participation to the shared support server 6 (step S66). As a result, the transmission / reception unit 61 of the shared support server 6 receives the user ID of each prospective participant and information indicating the presence / absence of participation.

Next, the shared support server 6 stores and manages the presence / absence of participation in the participation presence / absence column that has not been entered in the schedule management DB 6003 (step S67).

As described above, the user A starts the event (here, the policy decision meeting) by using the union (here, the conference room X) and the communication terminal (here, the electronic blackboard 2). Then, as shown in FIG. 26, the user A can hold a conference in the conference room X by using the electronic blackboard 2. The display control unit 24 displays the remaining time during which the union can be used in the upper right area of the display 220. In this case, the display control unit 24 displays the time (remaining time) between the current time and the scheduled end time indicated by the event information selected in step S51.

Further, the display control unit 24 stores the icon r1 pressed when registering the action item, the icon r2 pressed when viewing the execution event history, and the material file stored in the specific storage area of the storage unit 2000. The icon r3 pressed when browsing and the file data r4 of the material file are displayed. The icon r3 is an example of a selection image that accepts a selection for displaying the file data stored in a specific storage area. For example, when the user of the electronic blackboard 2 presses the icon r3, the reception unit 22 accepts the selection of the icon r3, and the display control unit 24 is a file of the material file stored in the specific storage area of the storage unit 2000. Display the data r4.

<Registration process of execution event history>
Subsequently, the registration process of the execution event history will be described with reference to FIGS. 27 to 33. 27 and 29 are sequence diagrams showing the registration process of the execution event history. FIG. 28 is a flowchart showing the voice-to-text conversion process.

First, the determination unit 25 of the electronic blackboard 2 determines the type of content processing in the started event (step S71). Specifically, when the content is sound data generated by recording by the image / sound processing unit 23, the determination unit 25 determines that the type of content processing is “recording”. When the content is image data acquired by a snapshot (capture) by the image / sound processing unit 23, the determination unit 25 determines that the processing type of the content is “snapshot”. When the content is the material file data transmitted by the transmission / reception unit 21, the determination unit 25 determines that the processing type of the content is "material transmission".

Next, the transmission / reception unit 21 transmits the registration request information indicating the registration request of the generated content to the sharing support server 6 (step S72). In this case, the transmission / reception unit 21 automatically transmits the registration request information each time the content is generated. This registration request information includes the execution event ID, the user ID of the content sender, the content data, the content processing type information, and the start date and time and end date and time of the content processing (recording, snapshot, transmission). There is. As a result, the transmission / reception unit 61 of the sharing support server 6 receives the registration request information.

Next, the determination unit 65 of the sharing support server 6 determines the type of content processing received based on the type information included in the registration request information received by the transmission / reception unit 61 (step S73). Then, when the transmission / reception unit 61 of the sharing support server 6 determines that the content processing type is "recording" by the determination unit 65, the transmission / reception unit 61 transmits the sound data which is the content data to the voice text conversion server 9 (step). S74). As a result, the transmission / reception unit 91 of the voice-text conversion server 9 receives the sound data. When the type of content processing is other than "recording", the shared support server 6 shifts to the processing of step S77 without performing the processing of steps S74 to S76.

Next, the conversion unit 93 of the voice-text conversion server 9 converts the sound data received by the transmission / reception unit 91 into text data (step S75). Here, the voice-text conversion process in the voice-text conversion server 9 will be described with reference to FIG. 28. First, the conversion unit 93 acquires information indicating the date and time when the sound data was received by the transmission / reception unit 91 (step S75-1). The information acquired in step S75-1 may be information indicating the date and time when the shared support server 6 received the sound data or the date and time when the shared support server 6 transmitted the sound data. In this case, the transmission / reception unit 91 of the voice-text conversion server 9 receives the sound data transmitted from the sharing support server 6 and the information indicating the date and time in step S74.

Next, the conversion unit 93 executes a text conversion process of the sound data received by the transmission / reception unit 91 (step S75-2). Then, when the text conversion process of the sound data is completed (YES in step S75-3), the conversion unit 93 shifts the process to step S75-4. On the other hand, the conversion unit 93 repeats the process of step S75-2 until the text conversion process of the sound data is completed. Then, the conversion unit 93 generates the text data converted from the sound data (step S75-4). As a result, the voice-text conversion server 9 converts the sound data transmitted from the sharing support server 6 into text data. The voice-to-speech conversion server 9 repeatedly executes the process shown in FIG. 28 each time it receives the sound data transmitted from the sharing support server 6.

Returning to FIG. 27, the description of the execution event history registration process will be continued. The transmission / reception unit 91 transmits the text data converted by the conversion unit 93 to the sharing support server 6 (step S76). Here, the transmission / reception unit 91 transmits the text data and the information indicating the date and time acquired in step S75-1 to the sharing support server 6. The transmission / reception unit 91 may transmit the text data and information indicating the date and time when the text data was generated by the conversion unit 93 to the sharing support server 6. As a result, the transmission / reception unit 61 of the sharing support server 6 receives the text data.

Next, the generation unit 64 generates a unique content processing ID for identifying the content processing generated by the event (step S77). In addition, the generation unit 64 generates a URL of content data indicating the content of the content (step S78). Then, the storage / reading processing unit 69 refers to the content management DB 6005 (see FIG. 10B) for each execution event ID received in step S72, such as the type of content processing, the start date / time and end date / time of the content processing. , The content processing ID generated in step S77, and the URL indicating the storage destination of the content generated in step S78 are associated and managed (step S79). Here, when the type of content processing is "voice text reception", the start date and time and end date and time of the content processing are information indicating the date and time received in step S76. When the type of content processing is "voice text reception", the start date and time and end date and time of the content processing may be information indicating the date and time when the sharing support server 6 received the text data in step S76.

Next, in FIG. 29, the storage / reading processing unit 69 of the sharing support server 6 searches the execution event management DB 6004 (see FIG. 10A) using the execution event ID received in step S72 as a search key. , Read the corresponding project ID (step S91). Next, the storage / reading processing unit 69 reads out the corresponding organization ID by searching the user authentication management DB 6001 (see FIG. 9A) using the user ID of the content transmission source as a search key (step). S92).

Next, the storage / reading processing unit 69 reads the corresponding access ID and access password by searching the access management DB 6002 (see FIG. 9B) using the organization ID read in step S92 as a search key (step). S93).

Next, the transmission / reception unit 61 transmits the content registration request information indicating the content data registration request to the schedule management server 8 (step S94). The content registration request information includes the project ID read in step S91, the execution event ID received in step S72, the sender user ID, the content data, the start date and time and end date and time of the content processing, and step S77. The content processing ID generated in step S78, the URL of the content data generated in step S78, the access ID read in step S93, and the access password are included. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the content registration request information.

Next, in the schedule management server 8, the authentication unit 82 authenticates the shared support server 6 by using the access ID and the access password (step S95). Since this authentication is the same process as in step S36, the description thereof will be omitted. Here, the case where it is valid will be continued.

Next, the storage / reading processing unit 89 stores and manages various data (information) received in step S94 in the execution event history management DB 8008 (see FIG. 14A) (step S96). The storage / reading processing unit 89 stores various data (information) in the execution event history management DB 8008 in association with the project ID and the execution event ID received in step S94. As a result, the schedule management server 8 manages data having the same contents as the shared support server 6 side.

In addition, the generation unit 83 of the schedule management server 8 generates related information in which the content data received in step S94 is associated with each content generation time zone (step S97). Then, the storage / reading processing unit 89 of the schedule management server 8 stores and manages the related information generated by the generation unit 83 in the related information management DB 8010 (step S98). As a result, the schedule management server 8 manages the content data having different types of content processing in association with each content generation time.

Further, the storage / reading processing unit 89 of the schedule management server 8 stores and manages the action items included in the content data received in step S94 in the action item management DB 8011 (step S99). As a result, the schedule management server 8 manages the action item data including the data of a plurality of items related to the correspondence to the action item for each action item.

As described above, the electronic blackboard 2 can transmit the event ID of the event in the predetermined project and the content generated by the execution of the corresponding event to the schedule management server 8. Further, the schedule management server 8 can store the received contents in the execution event history management DB 8008 for each event ID associated with the project ID. As a result, the shared system 1 allows the user to select which project the event belongs to at the start of the event, so that the content generated by the event can be stored for each project.

(Action item registration process)
Here, the processing when the generated content is an action item will be described with reference to FIGS. 30 to 33. FIG. 30 is a flowchart showing the registration process of the action item. FIG. 31 is an example of a screen for recognizing an action item. FIG. 32 is a screen example showing a list of candidates for executing an action item. FIG. 33 is a screen example showing a calendar for selecting an expiration date of an action item.

First, in FIG. 30, when the user presses the icon r1, the reception unit 22 accepts the action item registration request (step S71-1). Next, as shown in FIG. 31, after the user draws an action item (here, “submit minutes”) on the drawing screen 260a of the electronic blackboard 2 using the electronic pen 2500, the action is taken. When the image (drawing image) 261 showing the contents of the item is surrounded by a line (designated area) 262, the reception unit 22 accepts the designation of the predetermined area including the image 261 and the recognition unit 26 is included in the predetermined area. Recognize the image 261 (step S71-2). Although FIG. 31 has described an example in which the image (drawing image) 261 is surrounded by a line (designated area) 262, the recognition unit 26 recognizes a region distant from the designated area 262 as an image 261. It may be a configuration. The designation of the predetermined area is performed by drawing a predetermined predetermined shape such as a circle or a polygon with the electronic pen 2500.

Next, as shown in FIG. 32, the display control unit 24 displays the candidate list 265 of the performer of the action item on the drawing screen 260b (step S71-3). Then, when the user selects a specific executor to execute the action item using the electronic pen 2500, the reception unit 22 accepts the selection of the specific executor (step S71-4).

Next, as shown in FIG. 33, the display control unit 24 displays a calendar 267 for accepting the designation of the execution deadline date of the action item on the drawing screen 260c (step S71-4). Then, when the user selects a specific deadline date using the electronic pen 2500, the reception unit 22 accepts the selection of the specific deadline date (step S71-5). The calendar 267 is an example of a deadline designation screen. The deadline designation screen may be a date list or the like on which the day of the week or the like is not described.

By such a process, the electronic blackboard 2 transmits the content registration request information indicating the action item registration request to the sharing support server 6 as the content registration request. The registration request information of this content includes an execution event ID indicating an event in which an action item has occurred, a user ID of the performer of the action item selected in step S71-4, and an action item recognized in step S71-2. The image data (here, the image data of "submit minutes") and the deadline date for execution of the action item accepted in step 71-5 are included. That is, the transmission / reception unit 21 transmits the image data in the predetermined area as image data indicating the contents of the action item generated in the event being executed. As a result, the transmission / reception unit 61 of the sharing support server 6 receives the content registration request information. Since the processing after the sharing support server 6 receives the content registration request information is the same as the processing shown in FIGS. 27 and 29, the description thereof will be omitted.

<Event end processing>
Subsequently, the process of ending the event being executed will be described with reference to FIGS. 34 to 38. 34 and 35 are sequence diagrams showing the end processing of the event. FIG. 36 is a diagram showing an event end screen on an electronic blackboard. FIG. 37 is a diagram showing a file data upload screen on the electronic blackboard. FIG. 38 is a diagram showing a file data upload completion screen on the electronic blackboard.

In FIG. 26, when the user A closes the screen displayed on the display 220, the reception unit 22 receives the end of the event being executed (step S301).

Then, the transmission / reception unit 21 transmits the execution event start / end information indicating the start date / time and the end date / time of the execution event, and the file data registration request information indicating the file data registration request to the shared support server 6 (step). S302). The execution event start / end information includes the execution event ID, the event name, the start date / time of the event, and the end date / time. Further, the registration request information of the file data includes the execution event ID, the user ID of the transmission source, the file data, and the start date and time and end date and time of the content processing. As a result, the transmission / reception unit 61 of the sharing support server 6 receives the execution event start / end information and the file data registration request information.

Next, the generation unit 64 of the sharing support server 6 generates a unique content processing ID for identifying the content processing generated by the event (step S303). In addition, the generation unit 64 generates a URL of content data indicating the content of the content (step S304). Then, the storage / reading processing unit 69 refers to the content management DB 6005 (see FIG. 10B) for each execution event ID received in step S302, such as the type of content processing, the start date / time and end date / time of the content processing. , The content processing ID generated in step S303, and the URL indicating the storage destination of the content generated in step S304 are associated and managed (step 305).

Next, the storage / reading processing unit 69 of the shared support server 6 searches the execution event management DB 6004 (see FIG. 10A) using the execution event ID received in step S72 as a search key, and thereby corresponds to the corresponding project. Read the ID (step S306). Next, the storage / reading processing unit 69 reads out the corresponding organization ID by searching the user authentication management DB 6001 (see FIG. 9A) using the user ID of the content transmission source as a search key (step). S307).

Next, the storage / reading processing unit 69 reads the corresponding access ID and access password by searching the access management DB 6002 (see FIG. 9B) using the organization ID read in step S92 as a search key (step). S308).

Next, in FIG. 35, the transmission / reception unit 61 transmits the execution event start / end information received in step S302 and the file data registration request information indicating the file data registration request to the schedule management server 8 ( Step S309). The registration request information of the file data includes the project ID read in step S306, the execution event ID received in step S302, the user ID of the sender, the file data, and the start date and time and end date and time of the content processing. The content processing ID generated in step S303, the URL of the file data generated in step S304, the access ID read in step S308, and the access password are included. As a result, the transmission / reception unit 81 of the schedule management server 8 receives the execution event start / end information and the file data registration request information.

Next, in the schedule management server 8, the authentication unit 82 authenticates the shared support server 6 by using the access ID and the access password (step S310). Since this authentication is the same process as in step S36, the description thereof will be omitted. Here, the case where it is valid will be continued.

Next, the storage / reading processing unit 89 of the schedule management server 8 stores the execution event start / end information received in step 309 in the execution event management DB 8009 (see FIG. 14B) (step S311). .. In this case, the storage / reading processing unit 89 adds execution event start / end information for one record to the execution event management table of the execution event management DB 8009.

Next, the storage / reading processing unit 89 stores and manages various data (information) received in step S309 in the execution event history management DB 8008 (see FIG. 14A) (step S312). The storage / reading processing unit 89 stores various data (information) including file data in the execution event history management DB 8008 in association with the project ID and the execution event ID received in step S309. As a result, the schedule management server 8 manages the same file data as the shared support server 6 side.

Next, the transmission / reception unit 81 transmits the file data registration information indicating that the file data has been registered to the sharing support server 6 (step S313). As a result, the transmission / reception unit 61 of the sharing support server 6 receives the file data registration information.

Then, the transmission / reception unit 61 of the sharing support server 6 transmits the file data registration information transmitted from the schedule management server 8 to the electronic blackboard 2 (step S315). As a result, the transmission / reception unit 21 of the electronic blackboard 2 receives the file data registration information.

Next, when the file data registration information is received by the transmission / reception unit 21, the storage / reading processing unit 29 of the electronic blackboard 2 deletes the file data stored in the specific storage area of the storage unit 2000 (step S316). .. As a result, the electronic blackboard 2 can reduce the risk of leakage of conference information and the like by deleting the file data transmitted to the sharing support server 6.

Here, the screen transition of the screen displayed on the electronic blackboard 2 at the end of the event being executed will be described. First, in step S301, when the end of the event being executed by the reception unit 22 is received, the display control unit 24 displays the event end screen 270 as shown in FIG. 36 on the display 220. .. On the event end screen 270, a toolbar area 271, a file display area 272, a file upload selection area 273, a "Close" button 278 for advancing the end processing of the running event, and canceling the end processing of the running event. Includes "CANCEL" button 279 for. In the toolbar area 271, an image showing the icons r1, r2, r3 as shown in FIG. 26 is displayed. In the file display area 272, file data images 272a, 272b, 272c for identifying the file data of the material file stored in the specific storage area of the storage unit 2000 are displayed. The file upload selection area 273 includes a check box for accepting selection of whether or not to upload the file data corresponding to the file data image displayed in the file display area 272 to the sharing support server 6.

When the reception unit 22 accepts the selection of the "Close" button 278 while the file upload selection area 273 is selected, the display control unit 24 displays the file upload screen 280a as shown in FIG. 37 on the display 220. Is displayed. The file upload screen 280a is displayed on the display 220 when the file data stored in the specific storage area of the storage unit 2000 is uploaded to the sharing support server 6. The file upload screen 280a includes an event name 281 of the event to end, an event end date and time 282, a file data upload progress display area 283, and a "CANCEL" button 288 for interrupting (stopping) file data upload. There is. In the upload progress display area 283, the number of file data to be uploaded (for example, "3" shown in FIG. 37) and the number of file data for which upload has been completed (for example, "0" shown in FIG. 37). ) Is displayed.

Then, when the upload of the file data is completed, the display control unit 24 displays the upload completion screen 280b as shown in FIG. 38. The upload completion screen 280b includes a "Close" button 288 for pressing when the event is terminated. When the upload completion screen 280b is displayed on the display 220, as shown in step S315, the storage / reading processing unit 29 of the electronic blackboard 2 stores the uploaded file data in a specific storage area of the storage unit 2000. Remove from.

On the other hand, when the file upload screen 280a is displayed on the display 220 and the file data upload fails, the display control unit 24 receives information (for example, a file) for identifying the file data for which the upload failed. First name) is displayed. As a result, for example, when a failure of the communication network 10 occurs, the event participants can print the file data created or edited at the event, or store the file data in the USB memory 2600 connected to the electronic blackboard 2. By doing so, you can bring back the file data that failed to be uploaded.

Further, when the file data remains in the specific storage area of the storage unit 2000 even after the event ends, the storage / reading processing unit 29 of the electronic whiteboard 2 starts, for example, the next event using the electronic whiteboard 2. Occasionally deletes file data stored in a particular storage area. As a result, the electronic blackboard 2 can reduce the risk of leakage of conference information and the like.

<Browsing process of execution event history>
Subsequently, the browsing process of the execution event history will be described with reference to FIGS. 39 to 45. 39 and 40 are sequence diagrams showing browsing processing of the execution event history. FIG. 41 is a diagram showing a project list screen on a PC. FIG. 42 is a diagram showing an execution event list screen on the PC. 43 and 44 are views showing an execution event history screen. FIG. 45 is a diagram showing an action item screen on a PC. Since the processing of steps S111 to S117 of FIG. 39 is the same as the processing of steps S11 to S17 of FIG. 16, the description thereof will be omitted.

When the user presses the "execution event history browsing" button 543 on the initial screen 540 shown in FIG. 18, the reception unit 52 accepts the browsing of the execution event history (step S118).

Then, the transmission / reception unit 51 transmits the execution event history browsing request information indicating the execution event history browsing request to the schedule management server 8 (step S119). As a result, the transmission / reception unit 81 of the schedule management server 8 receives the execution event history viewing request information.

Next, the storage / reading processing unit 89 of the schedule management server 8 searches the project member management DB 8007 using the user ID and organization ID received in step S113 as search keys to obtain the corresponding project ID and project name. Read (step S120). Then, the transmission / reception unit 81 transmits the project ID and the project name to the PC 5 (step S121).

Next, the generation unit 56 of the PC 5 uses the project ID and the project name received in step S121 to generate the project list screen 560 as shown in FIG. 41 (step S122). Then, in the PC 5, the display control unit 54 displays the project list screen 560 generated by the generation unit 56 on the display 508 (step S123). As shown in FIG. 24, the project list screen 560 shows the same contents as the project list screen 240 displayed on the electronic blackboard 2. That is, the project icons 561-566 and buttons 568 and 569 in FIG. 41 correspond to the project icons 241-246 and buttons 248 and 249 in FIG. 24, respectively.

Next, in FIG. 40, when the user A presses the project icon 561 with, for example, the mouse 512, the reception unit 52 accepts the selection of the project indicated by the project icon 561 (step S124).

Next, the transmission / reception unit 51 of the PC 5 transmits the project ID of the project selected in step S124 to the schedule management server 8 (step S125). As a result, the schedule management server 8 receives the project ID.

Next, in the schedule management server 8, the storage / reading processing unit 89 reads out the corresponding execution event ID by searching the execution event history management DB 8008 using the project ID received in step S125 as a search key (step S126). ). In this case, the storage / reading processing unit 89 reads out all the execution event IDs associated with the project ID received in step S125. Then, the storage / reading processing unit 89 reads out the corresponding execution event start / end information by searching the execution event management DB 8009 using the execution event ID read in step S126 as a search key (step S127). The execution event start / end information includes an execution event ID, an event name, a start date / time, and an end date / time.

Then, the transmission / reception unit 81 transmits the execution event ID, the event name, the start date / time, and the end date / time read in step S127 to the PC 5 (step S128). As a result, the transmission / reception unit 51 of the PC 5 receives the execution event ID, the event name, the start date / time, and the end date / time.

Next, the generation unit 56 of the PC 5 uses the data (information) received in step S128 to generate the execution event list screen 570 as shown in FIG. 42 (step S129). Then, in the PC 5, the display control unit 54 displays the execution event list screen 570 generated by the generation unit 56 on the display 508 (step S130). As shown in FIG. 42, the execution event list screen 570 includes information 571 to 573 indicating an execution event. For example, the information 571 to 573 indicating the execution event includes the execution event name, the start date and time of the event, and the end date and time. The information 571 to 573 indicating the execution event is an example of the history information selection area that accepts the selection for displaying the history information indicating the execution content of the event. Further, the lower right portion of the execution event list screen 570 includes a "close" button 575 that is pressed when the execution event list screen 570 is closed. Further, the lower left portion of the execution event list screen 570 includes an "action item" button 577 that is pressed when the action item is browsed. The "action item" button 577 is an example of an action item selection area that accepts selections for displaying an action item.

Next, the reception unit 52 of the PC 5 accepts the selection of the execution event included in the execution event list screen 570 (step S131). Specifically, when the user selects the information indicating the execution event included in the execution event list screen 570, the reception unit 52 accepts the selection of the information indicating the execution event. Then, the transmission / reception unit 51 of the PC 5 transmits the execution event ID of the execution event selected by the reception unit 52 to the schedule management server 8 (step S132). As a result, the transmission / reception unit 81 of the schedule management server 8 receives the execution event ID.

Next, the storage / reading processing unit 89 of the schedule management server 8 reads the corresponding execution event history information by searching the execution event history management DB 8008 using the execution event ID received in step S132 as a search key (step). S133). The execution event history information includes a content processing ID, a content processing type, a start date / time and an end date / time of the content processing.

Further, the storage / reading processing unit 89 of the schedule management server 8 reads out the corresponding related information by searching the related information management DB 8010 using the execution event ID received in step S132 as a search key (step S134). This related information includes a content generation time zone, a content processing ID, a content processing type, and a sequence number. The time zone in which the content included in the related information occurs is an example of the time information.

Further, the storage / reading processing unit 89 reads out the content data indicating the content of the execution event history from the storage destination of the content data indicating the content of the execution event history read in step S133 (step S135). Further, the storage / reading processing unit 89 reads out the action item data indicating the data related to the correspondence to the action item from the content data indicating the content of the execution event history read in step S133 (step S136). Then, the transmission / reception unit 81 transmits the read related information, the content data, and the action item data to the PC 5 (step S137). As a result, the transmission / reception unit 51 of the PC 5 receives the related information, the content data, and the action item data.

Next, the sound control unit 58 of the schedule management server 8 sets the reproduction location of the sound data, which is the content data received in step S137 (step S138). In this case, the sound control unit 58 sets the reproduction portion corresponding to the sound data associated with the content generation time zone “0:00:00” among the received related information as the reproduction portion of the sound data.

Next, the generation unit 56 of the PC 5 uses the related information and the content data received in step S137 to generate the execution event history screen 580 as shown in FIG. 43 (step S139). More specifically, the generation unit 56 causes the execution event to display the image related to the text data, which is the received content data, in the text data display area 582 in the order of the sequence numbers included in the received related information. Generate a history screen 580. In addition, the generation unit 56 displays the execution event history screen 580 in the snapshot display area 583 in the order of the sequence numbers included in the received related information so that the image related to the screen data which is the received content data is displayed. Generate. Further, the generation unit 56 executes the execution event history screen 580 so that the reproduction point 581p included in the reproduction location display area 581 is displayed at the position related to the sound data set in step S138 in the total reproduction time of the sound data. To generate.

Then, the display control unit 54 of the PC 5 displays the execution event history screen 580 generated by the generation unit 56 on the display 508 (step S140). Further, the sound control unit 58 of the PC 5 reproduces the sound data of the reproduction portion set in step S138. As shown in FIG. 43, the execution event history screen 580 shows the data of the content generated by the executed event for each type of content processing. On the execution event history screen 580, when viewing a playback location display area 581 for displaying the playback location of recorded data, a text data display area 582 for displaying voice text, a snapshot display area 583 for displaying a snapshot, and an action item. The "action item" button 584 pressed to, the "material file" button 585 pressed when viewing the material used in the event, and the "pagination" button pressed when displaying the pagination display area 589 described later. Button "588 is included.

Here, in the reproduction location display area 581, a reproduction point 581p indicating the reproduction portion in the total reproduction time, a slider 581b indicating the reproduction history (reproduction process) of the recorded data, and a reproduction time display image indicating the reproduction time in the total reproduction time 581t is included. The reproduction point 581p and the slider 581b form a seek bar. The seek bar is an operation area for displaying the reproduction location of the recorded data and for designating the reproduction location of the recorded data. The user can visually grasp which part of the recorded data is being reproduced from the beginning to the end by the positions of the reproduction point 581p and the slider 581b. In addition, the user can move the reproduction point 581p by using an input means such as a mouse 507, whereby the recorded data can be reproduced from an arbitrary reproduction point. The reproduction point 581p is an example of a reproduction location specific image. The seek bar including the reproduction point 581p and the slider 581b is an example of the reproduction history display image.

Further, in the text data display area 582, text data 582a, 582b, 582c, 582d, 582e are displayed in chronological order from top to bottom. Similarly, in the snapshot display area 583, snapshot (capture) images 583a, 583b, 583c are displayed in chronological order from top to bottom. In this way, the text data display area 582 and the snapshot display area 583 are displayed in parallel in chronological order. As a result, for example, if the user browses the image 583b, he / she can easily grasp the time zone in which the pie chart was explained at the conference. Therefore, the image related to the text data displayed in parallel with the image 583b. 582c and 582d can be easily found. In this case, the images 583a and 583b are snapshot images of the entire display 220. Further, the image 583c is an image of the action item image-recognized (snapshot) in step S71-2.

Further, FIG. 44 is an image displayed on the display 508 when the user presses the “pagination” button 588 shown in FIG. 43. Here, "pagination" is a navigation provided to move between pages when the information is expanded / divided into a plurality of pages. For example, in the case of a Web page, "pagination" indicates that a page having a large amount of content is divided into a plurality of pages and links to each page are arranged. By using "pagination", it becomes easier for the user to access and it becomes easier to grasp which page the user is viewing. In addition, "pagination" is also referred to as "pagination", "page turning", "paging", and "pager".

When the user presses the "pagination" button 588, the reception unit 52 accepts the press of the "pagination" button 588. As a result, the display control unit 54 displays the pagination display area 589 at the bottom of the execution event history screen 580, as shown in FIG. 44. In this pagination display area 589, for example, the time zone in which the content is generated in an event such as a conference (here, every 5 minutes) is shown, and the same time zone as the time of the playback location of the playback point 581p is framed. It is surrounded by (elapsed time display area 589j). The reception unit 52 is in a waiting state for pressing the "pagination" button 588 until it is accepted.

As a result, the shared system 1 can easily share the execution event history generated by the events belonging to the same project among the members belonging to the same project. In addition, the shared system 1 allows the user to view the execution event history managed for each project by registering or changing the members belonging to the project using the project registration screen 520 displayed on the PC 5. In addition, processing such as browsing settings for each executed event can be omitted.

<Browsing process of action items>
Subsequently, the browsing process of the action item generated by the executed event will be described with reference to FIGS. 45 to 58. FIG. 45 is a sequence diagram showing the display processing of the action item screen. FIG. 46 is a diagram showing an action item screen on a PC.

When the user presses the "action item" button 584 on the execution event history screen 580 shown in FIG. 43 or FIG. 44, the reception unit 52 of the PC 5 accepts the selection of the "action item" button 584 (step S401). ..

Next, the generation unit 56 of the PC 5 uses the action item data received in step S137 to generate the action item screen 710 as shown in FIG. 46 (step S402). Then, the display control unit 54 of the PC 5 displays the action item screen 710 generated by the generation unit 56 on the display 508 (step S403). As shown in FIG. 46, the action item screen 710 shows action item data including data of a plurality of items related to the correspondence to the action item generated by the executed event for each action item. .. On the action item screen 710, for example, as action item data, information indicating the content of the action item, the person in charge of responding to the action item (executor), the deadline date for completing the action item, and the status of the response to the action item. It is shown. The content of the action item is the image data of the action item image-recognized (snapshot) in step S71-2.

Further, on the action item screen 710, the person in charge selection button 711 pressed when selecting the person in charge, the deadline date selection button 713 pressed when selecting the deadline date, and the state of correspondence to the action item are selected. Correspondence state selection button 715 pressed when doing, correspondence state change button 716a to 716f pressed when changing the correspondence state to each action item (correspondence state change button when it is not necessary to distinguish below 716), the link button 717 pressed when registering the created data (output) created in response to the action item, and the action item data are searched using the keywords entered in the input area 718a. It includes a search button 718 that is pressed when the button is pressed, a "close" button 719 that is pressed when the action item screen 710 is closed, and a mouse pointer 720.

On the action item screen 710 shown in FIG. 46, a list of a plurality of action item data received in step S137 is displayed so as to be viewable. In addition, the person in charge selection button 711, the deadline date selection button 713, and the correspondence status selection button 715 are pressed when the plurality of action item data displayed on the action item screen 710 are sorted according to the contents of each item. Sort button. The person in charge selection button 711, the deadline date selection button 713, and the correspondence state selection button 715 are examples of the first selection image.

(Switching the display of the action item screen)
Here, a process for switching the display of the action item screen 710 displayed on the PC 5 will be described with reference to FIGS. 47 to 58. First, the process of rearranging the action item data displayed on the action item screen 710 according to the deadline date will be described with reference to FIGS. 47 and 48. FIG. 47 is a flowchart showing a process of rearranging the action item data according to the deadline date. FIG. 48 is a diagram showing an action item screen in which the action item data is sorted in order of the expiration date.

First, in FIG. 47, when the user presses the deadline date selection button 713 on the action item screen 710 shown in FIG. 46 using the mouse pointer 720, the reception unit 52 of the PC 5 selects the deadline date selection button 713. Is accepted (step S411).

Next, the generation unit 56 of the PC 5 rearranges the plurality of action item data included in the action item screen 710 in the order of earliest deadline (step S412). Specifically, the generation unit 56 extracts the data of the item of the due date included in the plurality of action item data received in step S137, and sets the action item data as the due date according to the extracted data of the due date. Sort in the order of earliest. Then, the display control unit 54 of the PC 5 displays the action item screen 710a generated by the generation unit 56 on the display 508 (step S413).

FIG. 48 shows the action item screen 710a displayed on the display 508 in step S413. The action item screen 710a shown in FIG. 48 shows a state in which the expiration date selection button 713 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710a are sorted in order of earliest expiration date. In this way, the PC 5 can display the action item data sorted in the order of the earliest deadline date by receiving the selection of the deadline date selection button 713 by the reception unit 52. Therefore, for example, the PC 5 can have the user preferentially confirm the contents of the action item that needs to be dealt with early because the deadline is approaching. The PC 5 may be configured to display the action item data sorted in the order of the latest expiration date by accepting the selection of the expiration date selection button 713 by the reception unit 52.

Next, a process of rearranging the action item data displayed on the action item screen 710 according to the corresponding state of the action item will be described with reference to FIGS. 49 and 50. FIG. 49 is a flowchart showing a process of rearranging the action item data according to the correspondence state. FIG. 50 is a diagram showing an action item screen in which the action item data is sorted according to the corresponding state.

First, in FIG. 49, when the user presses the corresponding state selection button 715 on the action item screen 710 shown in FIG. 46 by using the mouse pointer 720, the reception unit 52 of the PC 5 selects the corresponding state selection button 715. Is accepted (step S421).

Next, the generation unit 56 of the PC 5 sorts the plurality of action item data included in the action item screen 710 according to the corresponding state (step S422). Specifically, the generation unit 56 extracts the data of the corresponding state items included in the plurality of action item data received in step S137, and sets the action item data in the corresponding state according to the extracted data of the corresponding state. Sort to. For example, the generation unit 56 rearranges the action item data so that the data indicating the state in which the correspondence state needs to correspond to the action item such as "ToDo" or "Doing" is displayed at the upper part. On the other hand, the generation unit 56 rearranges the action item data so that the data indicating the state in which the correspondence state does not need to correspond to the action item (supported) such as "Done" is displayed at the lower part. Then, the display control unit 54 of the PC 5 displays the action item screen 710b generated by the generation unit 56 on the display 508 (step S423).

The action item screen 710b displayed on the display 508 in step S423 is shown in FIG. The action item screen 710b shown in FIG. 50 shows a state in which the corresponding state selection button 715 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710b are sorted according to the corresponding state. In this case, on the action item screen 710b, the action item data is rearranged and displayed in the order of "ToDo", "Doing", and "Done" in the corresponding state. In this way, the PC 5 can display the action item data sorted according to the corresponding state by receiving the selection of the corresponding state selection button 715 by the reception unit 52. Therefore, the PC 5 can give priority to the user to confirm the contents of the action item that needs to be dealt with, for example. The display format of the corresponding status such as "ToDo", "Doing", and "Done" is not limited to this. Further, the PC 5 may be configured so that the action item data whose correspondence is completed (corresponding) (for example, the action item data whose correspondence state is "Done" is not displayed on the action item screen 710b.

Next, the process of changing the correspondence state of the action item data displayed on the action item screen 710 will be described with reference to FIGS. 51 and 56. FIG. 51 is a sequence diagram showing a change process of the corresponding state. FIG. 52 is a screen example when the correspondence state change button is selected. FIG. 53 is a screen example showing a state candidate list. FIG. 54 is a diagram showing an action item screen whose correspondence state has been changed. FIG. 55 is an example of a screen when the link button is selected. FIG. 56 is a screen example showing a screen for registering created data.

First, in FIG. 51, when the user presses the correspondence state change button 716 on the action item screen 710c-1 as shown in FIG. 52 by using the mouse pointer 720, the reception unit 52 of the PC 5 presses the correspondence state change button. The selection of 716 is accepted (step S431). The correspondence state change button 716 is an example of the second selection image. The action item screen 710c-1 shown in FIG. 52 shows a state in which the corresponding state change button 716a is selected.

Next, as shown in FIG. 53, the display control unit 54 displays the state candidate list 721 on the action item screen 710c-2 (step S432). In the status candidate list 721, a check box is pressed when selecting the corresponding status after the change, an "OK" button 721a is pressed when changing the corresponding status, and a button is pressed when canceling (ending) the change process. The "CANCEL" button 721b to be performed is included. Then, when the user uses the mouse pointer 720 to select the check box of the changed corresponding state and selects the "OK" button 721a, the reception unit 52 accepts the selection of the changed corresponding state (step S433). ). The action item screen 710c-2 shown in FIG. 53 shows a state in which “Done” is selected as the corresponding state after the change.

Then, the display control unit 54 displays the action item screen 710c-3 as shown in FIG. 54 on the display 508 (step S424). As shown in FIG. 54, on the action item screen 710c-3, the correspondence state of the action item data corresponding to the correspondence state change button 716a is changed from "ToDo" to "Done". In this way, the PC 5 can change the correspondence state of the specific action item data by receiving the input of the specific correspondence state change button 716 by the reception unit 52.

Next, when the user presses the link button 717 on the action item screen 710c-4 as shown in FIG. 55 using the mouse pointer 720, the reception unit 52 accepts the selection of the link button 717 (step S435). .. The action item screen 710c-4 shown in FIG. 55 shows a state in which the link button 717a corresponding to the action item data whose corresponding state has been changed is selected.

Next, as shown in FIG. 56, the display control unit 54 registers the creation data (output) created in response to the action item on the action item screen 710c-5 on the registration screen 723. Is displayed (step S436). On the registration screen 723, an input area 723a for inputting the URL of the save destination of the created data, an "attach" button 723b pressed when attaching the created data data file, and pressed when registering the created data. Includes a "register" button 723c and a "CANCEL" button 723d that is pressed when canceling (terminating) the registration process. Then, when the user inputs to the input area 723a or registers the data file with the "attach" button 723b using the mouse pointer 720 and selects the "register" button 723c, the reception unit 52 receives the created data. Accept registration (step S437).

Next, the transmission / reception unit 51 of the PC 5 transmits the action item data including the correspondence state changed by the process of step S433 and the created data received by the process of step S437 to the schedule management server 8 (step S438). As a result, the transmission / reception unit 81 of the schedule management server 8 receives the action item data transmitted from the PC 5. Then, the storage / reading processing unit 89 of the schedule management server 8 updates the action item data by storing the action item data received in step S438 in the action item management DB 8011 (step S439). As a result, the schedule management server 8 manages the action item data in which the correspondence to the action item is completed and the created data is registered. In this way, the PC 5 can register the created data created in response to the action item in the schedule management server 8 as an output. Therefore, the PC 5 can prevent the result (output) for the action item from being unknown even though the correspondence to the action item is completed (the correspondence state is "Done"). If it is not necessary to register the output to the action item, the process of steps S435 to S437 is omitted.

Next, a process of rearranging the action item data displayed on the action item screen 710 according to the person in charge of responding to the action item will be described with reference to FIGS. 57 and 58. FIG. 57 is a flowchart showing a process of rearranging the action item data according to the person in charge. FIG. 58 is a diagram showing an action item screen in which the action item data is sorted by the person in charge.

First, in FIG. 57, when the user presses the person in charge selection button 711 on the action item screen 710 shown in FIG. 46 using the mouse pointer 720, the reception unit 52 of the PC 5 selects the person in charge selection button 711. Is accepted (step S441).

Next, the generation unit 56 of the PC 5 sorts the plurality of action item data included in the action item screen 710 by the person in charge (step S442). Specifically, the generation unit 56 extracts the data of the item of the person in charge (executor of the action item) included in the plurality of action item data received in step S137, and according to the extracted data of the correspondence state. , Sort action item data by person in charge. For example, the generation unit 56 sorts the action item data in the order of the person in charge with the most associated action items. Then, the display control unit 54 of the PC 5 displays the action item screen 710d generated by the generation unit 56 on the display 508 (step S443).

FIG. 58 shows an action item screen 710d displayed on the display 508 in step S443. The action item screen 710d shown in FIG. 58 shows a state in which the person in charge selection button 711 is pressed by the mouse pointer 720. The plurality of action item data shown on the action item screen 710d are sorted by the person in charge. In this case, the action item data is rearranged and displayed on the action item screen 710d in the order of "Goro Kondo", "Jim Berger", and "Yoshio Yamashita". In this way, the PC 5 can display the action item data sorted by the person in charge by accepting the selection of the person in charge selection button 711 by the reception unit 52. Therefore, the PC 5 can, for example, make the user collectively confirm the contents of the action items that the user himself / herself needs to deal with. The PC 5 may be configured to receive the selection of the person in charge selection button 711 by the reception unit 52 so that the action item data is sorted and displayed in the order of the person in charge with the fewest associated action items. Further, the reception unit 52 accepts the input of the person in charge name for the input area 718a included in the action item screen 710 and the selection of the search button 718, so that the person in charge input in the input area 718a is displayed at the upper part of the PC5. The action item data may be rearranged and displayed so as to be displayed.

As described above, the PC 5 can display the action item data sorted according to the items related to the correspondence to the action item. Therefore, the user of PC5 can easily find the action item to be confirmed.

In the above description, an example in which the action item data is rearranged and displayed according to the content of each item has been described, but in the PC5, each selection button (person in charge selection button 711, deadline selection) is selected by the reception unit 52. The action item data may be filtered by accepting the selection of the button 713 or the corresponding state selection button 715). In this case, the person in charge selection button 711, the deadline date selection button 713, and the correspondence status selection button 715 are filter buttons for switching a plurality of action item data displayed on the action item screen 710 according to the content of each item. ..

Further, in the above description, an example in which the action item associated with the specific project ID and the execution event ID is displayed has been described, but the PC 5 is another project ID or the execution event ID registered in the schedule management server 8. The action item associated with may be displayed on the action item screen 710. For example, in the execution event list screen 570 shown in FIG. 42, when the reception unit 52 accepts the selection of the "action item" button 577, the display control unit 54 receives the action item associated with each execution event ID. Each of the above is displayed in a list on the action item screen 710.

<< Main effects of the embodiment >>
According to the present embodiment, as shown in FIGS. 45 to 58, the PC 5 (an example of a display terminal) is a schedule management server 8 (an example of a management system) that manages action items that occur in an executed event. ) Is a display terminal that can communicate with. Further, the transmission / reception unit 51 (an example of the reception means) of the PC 5 receives the action item data including the data of a plurality of items related to the correspondence to the action item from the schedule management server 8, and the display control unit 54 (display control means). (One example) displays an action item screen 710 (an example of a display screen) including a list of a plurality of received action item data on a display 508 (an example of a display unit), and a reception unit 52 (an example of a reception unit) displays the reception unit 52 (an example of a reception means). The action item screen 710 accepts the selection of the first selection image (for example, the person in charge selection button 711, the deadline date selection button 713, or the correspondence state selection button 715) in a specific item among the plurality of items. Then, when the selection for the first selected image is accepted, the display control unit 54 rearranges and displays a plurality of action item data included in the action item screen 710 according to the data content of the specific item. .. As a result, the user of the PC 5 can easily find the action item to be confirmed.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the action item data included in the action item screen 710 (an example of the display screen) is an action item generated in the event being executed. Includes image data generated by the event indicating the content of. As a result, the user of the PC 5 can easily grasp the contents of the action item by checking the action item screen 710.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the action item screen 710 (an example of the display screen) is a schedule management server for creating data created in response to the action item. Includes a link button 717 (an example of a registered image) for registering to 8 (an example of a management system). As a result, it is possible to prevent the PC5 from being in a state where the result (output) for the action item is not known even though the correspondence to the action item is completed (the correspondence state is "Done"). ..

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of the display control means) of the PC 5 (an example of the display terminal) has the corresponding state selection button 715 (an example of the display control means). When the selection for (an example of the selected image of 1) is accepted, a plurality of action item data included in the action item screen 710 (an example of the display screen) are sorted and displayed according to the corresponding state. As a result, the PC 5 can preferentially confirm the contents of the action item that needs to be dealt with by the user.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the reception unit 52 (an example of the reception means) of the PC 5 (an example of the display terminal) has the action item screen 710 (an example of the display screen). ), The display control unit 54 (an example of the display control means) accepts the selection for the correspondence state change button 716 (an example of the second selection image) for changing the correspondence state to a specific action item. When the selection for the correspondence state change button 716 is accepted, the action item screen 710c-3 (an example of the display screen) in which the correspondence state of the specific action item is changed is displayed. As a result, the user of the PC 5 can change, for example, the display of the correspondence status of the action item for which the correspondence has been completed.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of the display control means) of the PC 5 (an example of the display terminal) has the deadline date selection button 713 (an example of the display control means). When the selection for (an example of the selected image of 1) is accepted, the plurality of action item data included in the action item screen 710 (an example of the display screen) are sorted and displayed in the order of earliest deadline. As a result, the PC 5 can preferentially confirm the contents of the action item that the deadline is approaching and needs to be dealt with at an early stage.

Further, according to the present embodiment, as shown in FIGS. 45 to 58, the display control unit 54 (an example of the display control means) of the PC 5 (an example of the display terminal) has the person in charge selection button 711 (an example of the display control means). When the selection for (an example of the selected image of 1) is accepted, a plurality of action item data included in the action item screen 710 (an example of the display screen) are sorted and displayed according to the person in charge. Thereby, for example, the PC 5 can make the user collectively confirm the contents of the action items that the user himself / herself needs to deal with.

<< Supplement >>
Each function of the embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" in the present specification is a processor programmed to execute each function by software such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array), SOC (System on a chip), GPU (Graphics Processing Unit) and conventional circuit modules. ..

1 Shared system 2 Electronic blackboard (an example of communication terminal)
3 Video conferencing terminal (example of communication terminal)
4 Car navigation device (example of communication terminal)
5 PC (an example of display terminal)
6 Shared support server 8 Schedule management server (an example of management system)
9 Voice-to-text conversion server 10 Communication network 21 Transmission / reception unit 22 Reception unit 24 Display control unit 29 Storage / reading processing unit 51 Transmission / reception unit (example of receiving means)
52 Reception Department (Example of reception means)
53 Display control unit (an example of display control means)
508 display (an example of display)
710, 710a, 710b, 710c, 710d Action item screen (example of display screen)
711 Person in charge selection button (an example of the first selection image)
713 Deadline date selection button (an example of the first selection image)
715 Correspondence status selection button (an example of the first selection image)
716 Correspondence status change button (an example of the second selection image)
81 Transmitter / receiver (example of transmission means)

JP-A-2016-105241 JP-A-2018-32097

Claims (13)

A display terminal that can communicate with the management system that manages the action items that occur in the executed event.
A receiving means for receiving action item data including data of a plurality of items related to correspondence to the action item from the management system, and
A display control means for displaying a display screen including a list of a plurality of received action item data on the display unit, and
The display screen includes a reception means for accepting selection of a first selected image in a specific item among the plurality of items.
When the selection for the first selected image is accepted, the display control means rearranges and displays the plurality of the action item data included in the display screen according to the content of the data of the specific item. Display terminal. The display terminal according to claim 1, wherein the action item data includes image data generated by the event indicating the content of the action item generated in the event being executed. The display terminal according to claim 1 or 2, wherein the display screen includes a registration image for registering created data created in response to the action item in the management system. The data of the specific item indicates the state of correspondence to the action item.
When the selection for the first selected image is accepted, the display control means displays the action item data requiring the correspondence among the plurality of the action item data included in the display screen at the upper part. The display terminal according to any one of claims 1 to 3. When the selection for the first selected image is accepted, the display control means requests to display the action item data for which the correspondence has been completed among the plurality of action item data included in the display screen at the lower part. Item 4. The display terminal according to item 4. The reception means receives a selection for a second selection image for changing the correspondence state of a specific action item included in the display screen.
The display terminal according to claim 4 or 5, wherein when the selection for the second selected image is accepted, the display control means displays the display screen in which the corresponding state of the specific action item is changed. The data of the specific item indicates the deadline date for the response to the action item.
When the selection for the first selected image is accepted, the display control means displays the plurality of action item data included in the display screen in order of earliest deadline date, claims 1 to 6. The display terminal described in any one of the above. The data of the specific item indicates the person in charge of responding to the action item.
When the selection for the first selected image is accepted, the display control means is any one of claims 1 to 7, which causes the display control means to sort and display the plurality of the action item data included in the display screen according to the person in charge. The display terminal described in item 1. The first selected image is the sort button according to any one of claims 1 to 8, which is a sort button that sorts a plurality of the action item data included in the display screen according to the content of the specific item. Display terminal. The display according to any one of claims 1 to 9, wherein the first selected image is a filter button for switching a plurality of the action item data to be displayed on the display screen according to the content of the specific item. Terminal. A shared system including the display terminal according to any one of claims 1 to 10 and the management system.
The management system
A shared system including a transmission means for transmitting the action item data to the display terminal. A display control method executed by a display terminal that can communicate with a management system that manages action items that occur in an executed event.
A reception step for receiving action item data including data of a plurality of items related to correspondence to the action item from the management system, and
A first display control step for displaying a display screen including a list of a plurality of received action item data on the display unit, and
On the display screen, a reception step that accepts the selection of the first selected image in a specific item among the plurality of items, and
When the selection for the first selected image is accepted, the second display control step of rearranging and displaying the plurality of the action item data included in the display screen according to the data content of the specific item. When,
Display control method to execute. A program that causes a computer to perform the method according to claim 12.