JP2015204049A - Conference material retrieval system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a conference material retrieval system capable of improving retrieval accuracy of a conference material desired by a user and reducing time cost of conference material retrieval.SOLUTION: When a material which has been used in the conference is retrieved, using information of the date and place for the conference, and participants as retrieval conditions, retrieval in a conference material management storage which manages the conference materials is performed. With respect to a reference history which is a history of referring to the conference materials, the information of the conference is used as the retrieval condition for performing retrieval. By comparison of the retrieval result to the conference material management storage and the retrieval result to reference history of the conference, the conference material included in both of them, is determined as a final retrieval result.

Description

  The present invention relates to a technique for searching for materials used in a conference after the conference in an office system realized on a cloud system or the like.

  Conventionally, in a meeting held in an office, a meeting with several kinds of meeting materials is often held for discussion. The office environment is becoming computerized and paperless, but many people still use materials output on paper media for various reasons as conference materials. In many cases, the slide material is used by projecting a summary of the contents discussed in the conference.

  However, it is difficult to find the location where the original data is stored from the meeting records such as the minutes when you want to refer to these meeting materials again after the meeting is over. It was costly.

  Patent Document 1 is given as a conventional technique related to material retrieval used in a conference. In Patent Document 1, an identification image for identifying a material is added to a visible image with respect to an output meeting material. The user can retrieve the original data later by reading this identification image with the image identification device and extracting various information in the database corresponding to the conference material.

  However, this technique is based on the premise that the conference material is stored at the user's hand, and if it is not at hand, the identification image cannot be read by the image identification device, and the original data can be searched. Can not.

  Moreover, in patent document 2, the event information which generate | occur | produces in specific space, such as a meeting room, is detected, and the index for a search is provided with respect to a meeting material at the timing. The conference material and the search index are recorded in the conference database. The user can obtain the desired search result by transmitting the event information as search information to the conference database at the time of the search request. When searching for materials used in a specific event during a meeting, this technology can be used to efficiently search for meeting materials.

  However, with this technique, it is necessary to add search index information to the conference material itself when event information is detected in advance for the conference material. In addition, an event information detection device that detects event information that occurs in a specific space such as a conference room is also required, and there is a problem that introduction costs and maintenance costs are required.

  In Patent Document 3, electronic data of materials used in a conference is stored in a specific storage device (such as an HDD device that can be used in common). The conference is managed by a conference schedule management server, and information on the person who enters and leaves the conference room is also managed by the entrance / exit management server. The attendees of the conference are recognized from the conference schedule information and the entrance / exit management information from the conference schedule management server. When it is recognized as a meeting attendee, information on the meeting attendee is recorded in association with the meeting material recorded as electronic data in the storage device as browsing history information. By using this browsing history information, the conference attendee can search the conference material used in the conference even after the conference, and can obtain the electronic data of the desired conference material.

  However, even in this technology, it is premised that an entrance / exit management server that manages whether or not a conference participant has joined the conference is necessary, and information is given in advance as browsing history information to the conference material. There is a need. In addition, in this technique, if it is not registered in the conference schedule management server, it is not registered in the browsing history, so that the conference material used in the conference cannot be searched / referenced later.

JP 2009-268103 A Special table 2007-52566 gazette JP 2008-299626 A

  In Patent Document 1, it is necessary to have original data having an identification image of a conference material. In Patent Document 2, a conference system that detects spatial information (participant and event information) at the time of the conference is necessary, which requires introduction and maintenance costs. In Patent Document 3, there is a problem that a user who has not participated in the conference cannot search and refer to the conference material.

In order to solve the above-described problems, a print data processing apparatus according to the present invention has the following configuration.
A meeting system for managing a meeting held in an office, the meeting schedule managing means for managing a meeting schedule, the meeting material managing means for managing meeting materials used in the meeting, and the meeting materials. Reference means for referencing via the system, reference history recording means for recording a reference history when referred to by the reference means, and search for setting a search condition for searching for desired conference material. Search condition set by the search condition setting unit and information on the conference schedule managed by the conference schedule management unit for the conference material managed by the conference material management unit First meeting means for retrieving desired meeting material, and meeting material managed by the meeting material managing means On the other hand, it comprises second search means for searching for a desired meeting material from the search conditions set by the search condition setting means using the information of the reference history managed by the reference history management means, The search result of the first search means and the search result of the second search means are compared to narrow down the conference material included in both.

  According to the present invention, it is easy to search for conference materials used in a conference even after the conference, even if the original data is not held and the conference is not attended. Further, the present invention does not require a special conference system that detects spatial information during a conference.

Configuration diagram of the conference system Initial screen of the conference system Conference system menu screen Meeting schedule input screen of the conference system Meeting schedule list screen of the conference system Meeting system management file list screen (file list) Meeting system management file list screen (directory list) Conference system history list screen (printer screen) Conference system history list screen (projector screen) File search screen of conference system Search result screen of the conference system Conference system search results screen (refine search) Conference system authentication screen Device management table User information management table Meeting schedule management table Job history management table Search condition list Search result list for meeting schedule management table Search result list (date) for job history management table Search result list for the job history management table (participants) Search result list for job history management table (participant and date) Flow chart of reference / print processing Flow chart of printing process Flow chart of search processing for conference schedule management table Flow chart of search processing for job history management table Narrowing process flowchart File search screen of conference system (conference image designation) Meeting system file search screen (conference image information) Flow chart of file search process when meeting image is transmitted

  The best mode for carrying out the present invention will be described below with reference to the drawings. First, an example of the configuration of the conference system in the present invention will be described with reference to FIG.

  The conference system according to this embodiment includes a client PC 101, an image forming apparatus 102, an image display apparatus 103, an image projection apparatus 104, a cloud system 105, and a storage 106. The client PC 101, the image forming apparatus 102, the image display apparatus 103, and the image projection apparatus 104 are connected via a cloud system 105 so that they can communicate with each other.

  The client PC 101 can access the cloud system 105 and use the conference system. The client PC 101 can issue a print instruction to the image forming apparatus 102 and a display instruction to the image display apparatus 103 and the image projection apparatus 104 using the conference system.

  The image forming apparatus 102 has various functions such as scanning, printing, and copying. The image display device 103 includes a touch sensor display that can detect contact with the user's display, and can refer to and edit electronic data created in the application file by a user's touch (touch) operation on the display. The conference material managed by the conference system can be received from the client PC 101, and the image display device can go to the conference system as a client.

  The image projection device 104 can project the conference material managed by the conference system onto the projection screen. The conference material can be received from the client PC 101 or can be referred to the conference system as a client.

  The client PC 101, the image forming apparatus 102, the image display apparatus 103, and the image projection apparatus 104 are connected to a plurality of cloud systems 105, and can individually access the conference system and receive operation instructions.

  The cloud system 105 is a computing system realized on a network. In the embodiment of the present invention, the conference system is assumed to be executed on the cloud system 105, but is not particularly limited to a configuration form realized on the cloud system.

  The storage 106 is a storage area for storing data of the conference system realized on the cloud system. In this embodiment, the storage 106 stores only data used in the conference system, is protected by encryption security, and cannot be referenced from other than the conference system on the cloud system. In addition to centrally managing electronic data of conference materials used in the conference system, the storage 106 holds an office map, job history, user information, device information, conference schedule information, etc. used in implementing the present invention. .

  FIG. 2 is a main screen of the conference system displayed on the screen of the client PC 101 of FIG. In this embodiment, the screen displayed on the client PC 103 is described. However, the screen having the same function includes a UI panel of the image forming apparatus 102, a screen of the image display apparatus 103, and a UI of the image projection apparatus 104. It can also be accessed and operated from the panel. The conference system described in this embodiment takes a form of requesting user ID and password input on the initial screen and performing user authentication. The screen in FIG. 1 is a screen for performing this user authentication.

  The input form 201 is an input form for inputting a user ID. The user inputs his / her user ID registered in the conference system in this form. In this embodiment, the content entered on the input form 201 is the user ID, but it may be the user's name or employee ID.

  The input form 202 is an input form for inputting a password. The user inputs a password corresponding to his / her user ID registered in the conference system in this form.

  A button 203 is a button used when making a user authentication inquiry to the cloud system 105 after the user inputs a user ID and password in the input forms 201 and 202. When the user completes input to the input forms 201 and 202 and selects the button 203, the cloud system 105 determines whether the received user ID and password match the combination of the user ID and password registered in the conference system. . If they match, the process proceeds to the menu screen shown in FIG. 3. If they do not match, the user is notified that the user ID or password is incorrect, and the process returns to the initial screen.

  The buttons 204, 205, and 206 are included in all the screens shown in FIGS. 2 to 13, but the operation is the same when selected by the user. The button 204 temporarily hides the currently displayed screen when selected by the user. When the user selects the button 205, the screen size can be changed. When the user selects the button 206, the currently displayed screen can be closed. When the button 206 is selected, even if the user authentication is completed, the conference system can be forcibly terminated and the screen can be closed. When the conference system is used again, it is necessary to enter a user ID and password and perform user authentication.

  FIG. 3 is a menu screen that moves after user authentication from the initial screen of the conference system of FIG. On the menu screen, functions of three items, which can be used in the conference system, are conference schedule management, conference material reference / printing, and conference material search.

  A button 207 is a button for moving to the conference schedule management screen shown in FIGS. On the conference schedule screen, the conference schedule information managed by the conference system can be registered and confirmed.

  A button 208 is a button for moving to the management file list screen shown in FIGS. On the management file list screen, electronic data managed by the conference system can be referenced and printed.

  A button 209 is a button for moving to the history list screen. On the history list screen, the user can check the reference / print history when the management file is referred to and printed by the image forming apparatus 102, the image display apparatus 103, and the image projection apparatus 104 via the conference system.

  A button 210 is a button for moving to a file search screen. On the file search screen, it is possible to search for conference materials stored in the storage 106 and managed by the conference system.

  If the button 211 is selected, the user can exit the conference system and return to the main screen shown in FIG. When the button 211 is selected, the user authentication is canceled. Therefore, when the conference system is used again, it is necessary to input the user ID and password again on the main screen of FIG. This button 211 is also included in the screens shown in FIGS. 4 to 12 described in the following section, and the operation when selected by the user is the same.

  4 and 5 are diagrams showing a conference schedule screen that can be moved from the button 207 of FIG. On the conference schedule screen, two screens, a conference schedule input screen and a conference schedule list screen, can be moved. The screen can be moved by a button 301 shown in FIG. The button 301 is a button for switching between the conference schedule input screen shown in FIG. 4 and the conference schedule list screen shown in FIG. When the button 301 is selected, a conference schedule input item and a conference schedule list item are displayed in a pull-down format. The user can select a desired screen item and move the screen.

  In the conference schedule input screen shown in FIG. 4, a new conference schedule can be registered in the conference schedule managed by the conference system.

  The meeting schedule input drawing has four input items of input forms 302, 303, 304, and 305. The input form 302 is an input form for inputting a meeting date and time. An input form 303 is an input form for inputting a meeting name. The input form 304 is an input form for inputting a meeting place. The input form 305 is an input form for inputting information on participants who participate in the conference. The participant information here may be the name of the participant, an employee ID, or a user ID. The same applies to user information in the following sections. It is also possible to register a plurality of participants. It is not always necessary to input conference information in each input form, and only items that can be input need be input.

  A button 306 is a button for registering conference materials used in the conference. When the button 306 is selected, the reference source of the electronic data of the conference material can be designated. As the electronic data of the conference material, the electronic data stored in the client PC 101 used by the user may be specified, or the electronic data stored in the storage 106 managed by the conference system may be specified. Also good. A plurality of conference materials that can be specified may be specified. The conference material specified here is registered in the conference system when the button 307 is selected. At that time, the file number for identifying the conference material on the conference system is automatically set for the conference material. Is granted. Also, the user information that was created / edited last in the client PC 101 or storage 106 is also given as file information.

  When the button 307 is selected, information on various conferences input to the input forms 302, 303, 304, and 305 and information on conference materials registered by selecting the button 306 are registered in the conference system. Information on the conference schedule registered here can be confirmed in the conference schedule list shown in FIG.

  FIG. 5 shows a conference schedule list screen on which a list of conference schedules managed by the conference system can be confirmed. The conference information included in the conference schedule list is registered on the conference schedule input screen of FIG. 4 described above. The conference schedule list screen displays conference information as a list 308 in a list format.

  The list 308 has information on meeting date and time, meeting place, meeting name, meeting participants, and meeting materials. When the conference information displayed in the list 308 does not fit on the screen, by sliding the slide bar 309, it is possible to confirm all the conference information by sliding the screen.

  The button 310 is included in FIGS. 5 to 12, but the operation when the button 310 is selected by the user is the same. When selected by the user, the screen returns to the menu screen shown in FIG. When the user wants to return to the menu screen from the currently displayed screen, the user can return to the menu screen by selecting this button.

  Next, the management file list screen will be described with reference to FIGS. The management file list screen can be moved by selecting a button 208 in FIG. In the management file list, a desired meeting material is selected from the meeting materials shown in the list format, the selected meeting material is instructed to be printed on the image forming apparatus 102, and the display instruction on the client PC 101 or the image display apparatus 103 is displayed. A projection instruction to the image projector 104 can be performed.

  In addition, the management file list screen displays the conference materials managed by the conference system separately for each of the folders shown in FIG. 7 and the screen in which the file list shown in FIG. 6 is displayed in a list format. There are screens to be displayed. The screen can be moved by a button 405 shown in FIG.

  The list 401 has file information such as a file number, a file name, and user information. This file information is automatically acquired and set by the conference system when the above-described button 306 in FIG. 4 is selected.

  A check box 402 is a check box for selecting conference materials included in the list 401. The conference material selected in the check box 402 is selected by a button 403 or 404 described later, and a print instruction to the image forming apparatus 102, a display instruction to the client PC 101 or the image display apparatus 103, and a projection to the image projection apparatus 104. I can give instructions.

  A button 403 is a button for instructing display of the conference material selected by the check box 402 to the client PC 101 or the image display apparatus 103 and projection to the image projection apparatus 104. When the button 403 is selected, the conference material selected by the check box 402 can be referred to and displayed on the screen of an arbitrary device.

  A button 404 is a button for instructing the image forming apparatus 102 to print the meeting material selected by the check box 402. When the button 404 is selected, the conference material selected by the check box 402 can be referred to and printed on the image forming apparatus 102 installed near the user's seat. The image forming apparatus 102 serving as the output destination is automatically selected by the conference system. This process will be described later with reference to FIG.

  If the user information of the conference material selected by the check box 402 does not match the user information input by the input form 201 in FIG. 2 when the buttons 403 and 404 are selected, display / projection / printing is performed. Authentication processing is required to do this. This authentication process will be described later with reference to FIG.

  When the buttons 403 and 404 are selected and the conference material is referred to / printed, the date / time, file name, output device, and user information at the time of referencing / printing are automatically acquired and stored in the storage 106 as a history. The

  A button 405 is a button for switching between the list-format management file list screen shown in FIG. 6 and the folder-format management file list screen shown in FIG. When the button 405 is selected, file list items and file directory items are displayed in a pull-down format. The user can select a desired screen item and move the screen.

  The directory 406 displays conference materials managed by the conference system by directory. The directory 406 is created for each conference registered in the conference schedule, and holds conference materials used in the conference. The user can confirm the conference material used in the conference by selecting a desired conference directory.

  Next, the history list screen will be described with reference to FIGS. On the history list screen, it is possible to confirm the reference / print history to the conference material managed by the conference system. The client PC 101, the image forming apparatus 102, the image display apparatus 103, and the image projection apparatus 104 can individually access the conference system, and can instruct and refer to the conference material from the management file list screen shown in FIG. Can do. The history screen list is divided for each device that has been referenced and printed, and can be confirmed. FIG. 8 shows a history list printed by the image forming apparatus 102. FIG. 9 shows a history list referring to conference materials using the image projection device 104. Although not shown, the reference history of the client PC 101 and the image display device 103 can be confirmed with a similar screen configuration.

  A list 501 is a list of histories when conference materials are referred to and printed using the conference system. The list 501 has the date and time when it is referred to and printed, the file name, the output device name, and user information. This information is automatically acquired by the conference system when the user references / prints the conference material using the conference system, and is stored in the storage 106.

  A button 502 is a history list screen of the image forming apparatus 102 shown in FIG. 8, a history list screen of the image projection apparatus 104 shown in FIG. 9, and a history list screen of the client PC 101 and the image display apparatus 103 (not shown). It is a button for switching. When the button 502 is selected, printer items and projector, display, and PC items are displayed in a pull-down format. The user can select a desired history list screen item and move the screen.

  Next, the file search screen will be described with reference to FIG. It is possible to move to the file search screen by selecting the button 210 in FIG. On the file search screen, it is possible to search for conference materials stored in the storage 106 and managed by the conference system. On the file search screen, the user inputs search information and performs a search, but if the input search information is small, a large number of meeting materials stored in the storage 106 may correspond. In this case, in the present invention, the reference / print history information described with reference to FIGS. 8 and 10 is used, and the search results are further narrowed down to improve the search accuracy.

  In this embodiment, the file search is performed using the conference information as search information. The file search screen has three input items of input forms 601, 602, and 603. The input form 601 is an input form for inputting a meeting date. The input form 602 is an input form for inputting user information that has participated in the conference. In the input form 602, user information of a plurality of participants may be input. An input form 603 is an input form for a meeting place. It is not always necessary to input conference information in each input form, and only items that can be input need be input.

  When the button 604 is selected, the conference material is searched using the conference information input in the input forms 601, 602, and 603 as a search condition. Specific search processing will be described later with reference to the flowchart of FIG.

  11 and 12 show search result screens. The search result screen displays the result of the search processing performed when the button 604 in FIG. 10 is selected in a list format such as a list 701.

  The list 701 has file number, user information, and file name information. This user information refers to the user information acquired when the button 306 is selected on the conference schedule input screen shown in FIG. 4 and the conference material is registered.

  A check box 402 is a check box for selecting conference materials included in the list 701. The meeting material selected in the check box 702 is projected onto the image forming apparatus 102, displayed on the client PC 101 or the image display apparatus 103, and projected onto the image projection apparatus 104 by selecting buttons 703 and 704 described later. I can give instructions.

  A button 703 is a button for instructing display of the conference material selected by the check box 702 to the client PC 101 or the image display apparatus 103 and projection to the image projection apparatus 104. When the button 703 is selected, the conference material selected by the check box 702 can be referred to and displayed on the screen of an arbitrary device.

  A button 704 is a button for instructing the image forming apparatus 102 to print the meeting material selected by the check box 702. When the button 704 is selected, the conference material selected by the check box 702 can be referred to and printed on the image forming apparatus 102 installed near the user's seat. The image forming apparatus 102 serving as the output destination is automatically selected by the conference system. This process will be described later with reference to FIG.

  When the buttons 703 and 704 are selected, if the user information of the conference material selected in the check box 702 does not match the user information input in the input form of FIG. 2, display / projection / printing is performed. Authentication processing is required. This authentication process will be described later with reference to FIG.

  When the buttons 703 and 704 are selected and the conference material is referred / printed, the date / time, the file name, the output device, and the user information when the conference material is automatically referred / printed are acquired and stored in the storage 106 as a history. The

  Buttons 705, 706, and 707 are buttons for setting conditions for narrowing search. A button 705 sets the date information input in the input form 601 in FIG. 10 as a search condition for narrowing down. A button 706 sets the user information of the participant input in the input form 602 of FIG. 10 as a narrowing search condition. A button 707 sets location information input in the input form 603 of FIG. 10 as a search condition for narrowing down. Buttons 705, 706, and 707 can be selected at locations where conference information is input in the input forms 601, 602, and 603 in FIG. If the conference date information is input in the input form 601, the button 705 can be selected. If the user information of the participant is input in the input form 602, the button 706 can be selected. If location information is input to the input form 603, the button 707 can be selected. Conversely, when conference information is not input to the input forms 601, 602, and 603, the buttons 705, 706, and 707 corresponding to the forms cannot be selected.

  The buttons 705, 706, and 707 can be selected simultaneously, and a plurality of search conditions for narrowing down can be set. For example, in FIG. 12, a button 705 and a button 706 are set as narrowing search conditions. As a result, the search results displayed in the list 701 are narrowed down.

  FIG. 13 shows an authentication screen notified to the client PC 101 of the user registered in the user information of the conference material. When the reference / print instruction is selected from FIGS. 6, 11, and 12, the user information of the conference material selected as the reference / print target does not match the user information input in the input form 201 of FIG. 2. In this case, authentication processing for reference / printing is required. In FIG. 13, it is necessary to obtain authentication as to whether the user registered in the user information of the conference material can be referred to and printed.

  The authentication screen shown in FIG. 13 shows the authentication screen when a print instruction is issued. On the authentication screen, a text notifying that there is a print request, user information of the print request source, and a file name to be printed are notified. When the button 801 is selected, the print requesting user can print the file to be printed. When the button 802 is selected, the user cannot print the file to be printed.

  By performing authentication processing for reference / printing on this authentication screen, a user who does not know the conference material can refer to it without permission and information can be prevented from leaking.

  FIG. 14 is a diagram showing an example of a device management table stored in the storage 106 and managed by the conference system. The management targets of the device management table are the client PC 101, the image forming apparatus 102, the image display apparatus 103, and the image projection apparatus 104 that are connected to the conference system.

  The device management table has items of device ID, device name, and installation location. The device ID is identification information of the device that is uniquely determined by the conference system. The device name is the name of the device. The installation location is information on a location where the device is installed.

  In this embodiment, the device management table is used when the user refers to / prints the conference material from the conference system.

  FIG. 15 shows an example of a user information management table stored in the storage 106 and managed by the conference system. The user information management table manages user information registered in the conference system.

  The user information management table has items of user ID, user name, and seat location. The user ID is identification information of the user that is uniquely determined by the conference system. The user name is the name of the user. The seat location is information on the seat location in the user's office.

  In the present embodiment, the conference information is referred to and printed from the conference system using the user information management table and the device management table described with reference to FIG. The search / print processing using these two management tables will be described later with reference to FIGS.

  FIG. 16 shows an example of a conference schedule management table stored in the storage 106 and managed by the conference system. The conference schedule management table has conference schedule information that is input on the conference schedule input screen described in FIG. 4 and registered in the conference system.

  The conference schedule management table has items of conference ID, conference name, conference location, date and time, participants, and conference materials. The conference ID is identification information of the conference that is uniquely determined by the conference system. The meeting name is the name of the meeting. The meeting place is information on a meeting room where the meeting is held. The date / time is information on the date / time of the conference. Participant is information of the participant who participates in the conference. The conference material is information on the material used in the conference.

  In this embodiment, the conference system manages the conference schedule using this conference schedule management table.

  FIG. 17 is a job history management table managed by the conference system and stored in the storage 106. The job history management table has information of conference material reference / print processing performed through the conference system as a history.

  The job history management table has items of job ID, date / time, data name, output device, user name, and output location. The job ID is identification information of the job that is uniquely determined by the conference system. The date and time is information on the date and time when the job was executed. The data name is the electronic data name of the conference material that has been referenced and printed. The output device is information on a device on which the job is executed. The user name is user information that executed the job. The output location is information on the location where the job is output.

  In the present embodiment, a narrowing search is performed using this job history management table. Details of the narrowing search process will be described later in detail with reference to the flowcharts of FIGS.

  FIG. 18 is an example of a search condition list created when search information is input on the file search screen of FIG. The search condition list is used as a search condition when searching for the conference material desired by the user from the conference material managed by the conference system.

  The search condition list has items of date, place, and participant. The date of the event is information on the date and time input in the input form 601 in FIG. The holding place is information on the place entered in the input form 603 of FIG. Participants are user information entered in the input form 602 of FIG. The item of participant may hold a plurality of user information.

  In this embodiment, in FIG. 10, input to each item of the input forms 601, 602, and 603 is not indispensable, and thus there may be no information in the items in the search condition list. FIG. 18 shows an example in which the information on the venue is not input.

  FIG. 19 shows a search result list showing search results when the button 604 on the file search screen of FIG. 10 is selected and the conference system is searched for by the conference system. In this embodiment, the search process searches the conference schedule management table shown in FIG. 16 for conference materials corresponding to the items in the search condition list shown in FIG. Specific search processing will be described in detail later using the flowchart of FIG.

  The search result list has items of data ID, data name, date, place, participant, and conference name. The data ID is identification information of the data that is uniquely determined by the conference system. The data name is the name of the data. The date is date information of the conference in which the data is used. The place is information on a place where the data is used. The participant is information of the participant who participated in the conference using the data. The conference name is the name of the conference using the data.

  In order to search for the conference material corresponding to the search condition from the conference schedule management table, the search result includes information on the conference in which the conference material was used.

  In the present invention, in order to obtain a more accurate search result for the search result list shown in FIG. 19, a narrow search using a job history management table is performed. The narrowing search is executed when the buttons 705, 706, and 707 in FIG. 11 are selected.

  In the refinement search, first, the search process is performed using the information in the job history management table separately from the search result created by the search process using the information in the conference schedule management table described in FIG. . Then, the search result obtained from the job history management table is compared with the search result obtained from the conference schedule management table, and narrowing down is performed by selecting materials included in both search results.

  When performing a narrow search, first, a search process is performed on the job history management table shown in FIG. 17 using the search conditions in the search condition list in FIG. At that time, the number of items used as a search condition from the search condition list varies depending on whether or not the buttons 705, 706, and 707 in FIG. 11 are selected. When the button 705 is selected, the date of the date in the search condition list is used as the search condition. When the button 706 is selected, the item of the participant in the search condition list is used as the search condition. When the button 707 is selected, the item of the location in the search condition list is used as the search condition. Since the buttons 705, 706, and 707 can be selected at the same time, each item in the search condition list may be used as a plurality of search conditions.

  For example, FIG. 20 shows a search result for the job history management table when the button 705 in FIG. 11 is selected and the date of the date in the search condition list is used as the search condition. When the date of the date in the search condition list is used as a search condition, a job executed before the date of the date is selected from the job history management table. This is because conference materials are often created, referenced, and printed before the date of the conference. Since meeting materials are rarely referred to and printed after the date of the event, if the date of the event is selected as a search condition, it is deleted from the search result.

  FIG. 21 shows a search result for the job history management table when the button 706 of FIG. 11 is selected and the item of the participant in the search condition list is used as the search condition. When the item of the participant in the search condition list is used as the search condition, a job having the same user information as the participant who executed the job is selected from the job history management table. This is because users who refer to and print conference materials are often conference participants. Since users who have not participated in the conference rarely refer to, edit, or print the conference material, if the participant is selected as a search condition, it is deleted from the search result.

  Although not shown, when the button 707 in FIG. 11 is selected and the location item in the search condition list is used as a search condition, a job whose output location is close to the event location is determined from the job history management table. Is selected. This is because the conference material is often referred to and printed by a device near the conference room where the conference is held. From the viewpoint of information leakage, it is rarely referred to or printed in a place far from the conference room, so if the event location item is used as a search condition, it is deleted from the search result.

  As described above, the search processing for the job history management table can set a plurality of search conditions. For example, FIG. 22 shows a search result for the job history management table when the buttons 705 and 706 of FIG. 11 are simultaneously selected and the date of the search condition list and the item of the participant are used as the search conditions. In this case, a job that is executed before the date of the event and whose executed user information is the same as that of the participant is selected from the job history management table. Since a plurality of search conditions are set, the search results can be further narrowed down.

  When the search processing for the job history management table is completed, the search result is narrowed down from the conference schedule management table of FIG. Specifically, the conference material included in the search result from the job history management table described with reference to FIGS. 20, 21, and 22 is selected for the conference material included in the conference schedule search result.

  As described above, in the present invention, the narrowing search is performed using the search result from the conference schedule information and the search result from the job history information. By this processing, when a large number of conference materials correspond to the search result from the conference schedule information, the job history information is used to improve the search accuracy of the conference materials used in the conference desired by the user.

  Next, reference / printing processing to be performed when any one of the buttons 403 and 404 in FIG. 6 and the buttons 703 and 704 in FIG. 11 in the present embodiment is selected will be described with reference to the flowchart in FIG.

  First, when the user selects any one of the buttons 403 and 404 in FIG. 6 and the buttons 703 and 704 in FIG. 11 and the reference / print processing is started, in S1001, the cloud system 105 receives the reference / print from the user. Receive print instructions.

  In step S <b> 1002, the cloud system 105 receives user information for transmitting a reference / print instruction.

  Next, in S1003, the cloud system 105 refers to the user information management table shown in FIG. Here, the cloud system 105 identifies the seat location of the user from the user information acquired in S1002.

  In step S1004, the cloud system 105 refers to the management file list as displayed on the management file list screen of FIG. Here, the cloud system 105 identifies the conference material requested by the user. In addition, information on the user who registered the conference material by selecting the button 306 on the conference schedule input screen of FIG. 4 is also acquired.

In step S <b> 1005, the cloud system 105 determines whether the information on the user who registered the conference material requested to be referenced / printed matches the user information acquired in step S <b> 1002. If they match, the process proceeds to S1008. If not, the process proceeds to S1006.
In step S1006, the cloud system 105 notifies the user who has registered the conference material that is the target of the reference / print request that there is a reference / print request from another user. The print request screen shown in FIG. 13 is a notification screen in the case of a print request in this step.

  In step S <b> 1007, the cloud system 105 determines whether reference / printing has been approved by the user who registered the conference material that is the target of the reference / printing request. If the reference / print request is approved, the process advances to step S1008. If the reference / print request is not approved, the reference / print process is terminated.

  In step S1008, the cloud system 105 determines whether the received reference / print request is a print request. If it is a print request, the process proceeds to S1009. If it is not a print request, the process proceeds to S1010.

  In step S1009, the cloud system 105 performs print processing. The printing process will be described later with reference to FIG.

  In S1010, since the request received from the user is a reference request, the cloud system 105 transmits the electronic data of the conference material specified in S1004 to the user.

  In S1011, the cloud system 105 updates the job management table shown in FIG.

  With the above processing, the reference / print processing through the conference system on the cloud system 105 is performed.

  Next, print processing via the conference system corresponding to S1009 in FIG. 23 will be described with reference to the flowchart in FIG. In the printing process via the conference system in this embodiment, the seat location of the user is specified by referring to the information in the user information management table held on the storage 106 by the conference system. Then, the image forming apparatus 102 installed at the position closest to the user is automatically searched from the anus at the installation location of the device information management table, and the conference material is transmitted to the image forming apparatus 102.

  When the printing process is started, in S2001, the cloud system 105 refers to the device management table shown in FIG. Here, the cloud system 105 acquires information on the installation location of each device included in the device management table.

In S2002, the cloud system 105 is installed at a location closest to the user from the information on the seating location of the user specified in S1003 in FIG. 22 and the information on the installation location of the device acquired in S2001. The image forming apparatus 102 is specified.
In step S2003, the cloud system 105 transmits a conference material print job to the image forming apparatus 102 closest to the user's seat position specified in step S2002, and the print processing ends.

  With the above processing, the printing processing by the conference system on the cloud system 105 is performed.

  Next, file search processing executed from the file search screen of FIG. 10 in the present embodiment will be described with reference to the flowchart of FIG. In the file search process described here, a meeting that meets the search condition set by the user is searched from the meeting schedule management table, and meeting materials used in the meeting are extracted. In the flowchart of FIG. 25, M is an index to the conference ID.

  When the file search process is started, in S3001, the cloud system 105 creates a search condition list shown in FIG. 18 from the search information input in the input forms 601 602 603 included in the file search screen of FIG.

  In S3002, the cloud system 105 refers to the conference schedule management table shown in FIG.

  Next, in S3003, the cloud system 105 assigns 1 to M, which is an index to the conference ID, and initializes it.

  Next, in S3004, the cloud system 105 determines whether or not the date of the event is set in the search condition list created in S3001. If the event date item is set in the search condition list, the process advances to step S3005. If the date of the event is not set in the search condition list, the process proceeds to S3007.

  In S3005, the cloud system 105 determines whether or not the date of the conference whose conference ID is M in the conference schedule management table is later than the date of the date of the search condition list. If it is a later date, the process proceeds to S3007. If the date of the meeting with the meeting ID M is not later than the date of the date of the search condition list, the process proceeds to S3006.

  In S3006, the cloud system 105 creates a search result list, and adds conference materials used in the conference with the conference ID M to the search result list.

  In S3007, the cloud system 105 determines whether an item of the venue is set in the search condition list. If the event location item is set in the search condition list, the process advances to step S3008. If the event item is not set in the search condition list, the process advances to step S3010.

  Next, in S3008, the cloud system 105 determines whether or not the meeting location of the meeting with the meeting ID M matches the holding place of the search condition list. When the meeting place of the meeting with the meeting ID M matches the holding place of the search condition list, the process proceeds to S3009. If the meeting place of the meeting with the meeting ID M does not match the place of the search condition list, the process proceeds to S3010.

  In step S3009, the cloud system 105 refers to the search result list. If the conference material used in the conference with the conference ID M is not in the search result list, the cloud system 105 adds the conference material to the search result list and updates it. If the conference material has already been added in S3006, it is not added to the search result list.

  In step S3010, the cloud system 105 determines whether the participant item is set in the search condition list. If a participant item is set in the search condition list, the process advances to step S3011. If no participant item is set in the search condition list, the process advances to step S3013.

  In S3011, the cloud system 105 determines whether the participants in the search condition list are included in the conferences whose conference ID is M. If the participant whose conference ID is M includes the participant in the search condition list, the process proceeds to S3012. If the participant whose conference ID is M does not include the participant in the search condition list, the process proceeds to S3013.

  In S3012, the cloud system 105 refers to the search result list. If the conference material used in the conference with the conference ID M is not in the search result list, the cloud system 105 adds or updates the conference material to the search result list. If the conference material has already been added in S3006 and S3009, it is not added to the search result list.

  In S3013, the cloud system 105 adds 1 to M, which is an index to the conference ID, and advances the index.

  In step S <b> 3014, the cloud system 105 determines whether a conference with the conference ID M exists in the conference schedule management table. If a conference with the conference ID M exists in the conference schedule management table, the process returns to S3004 and the process is repeated. If the conference with the conference ID M does not exist in the conference schedule management table, the process proceeds to S3015.

  In S3015, the cloud system 105 displays the search result screen shown in FIG. 11, notifies the user of the search results added and updated in S3006, S3009, and S3012, and ends the process.

  Through the above processing, the conference material search processing for the conference schedule management table is executed.

  Next, the narrowing search process executed when the buttons 705, 706, and 707 in FIG. 11 are selected will be described with reference to the flowcharts in FIGS.

  In the narrowing search processing, first, search processing is performed on the job history management table using information set in the items of the search condition list. Thereafter, the search result obtained from the job history management table is compared with the search result obtained from the conference schedule management table, and a narrowing process for selecting materials included in both search results is performed.

  FIG. 26 shows a flowchart of the search process for the job history management table in the narrowing search process.

  FIG. 27 shows a narrowing-down process in which the search results obtained from the job history management table and the search results obtained from the meeting schedule management table are compared in the narrowing-down search process, and materials included in both search results are selected. The flowchart of is shown.

  In the flowcharts of FIGS. 26 and 27, M is an index to the job ID and data ID, respectively. Each will be explained in detail.

  In FIG. 26, when the narrowing search process is started, in S4001, the cloud system 105 refers to the search condition list created in S3001.

  In step S4002, the cloud system 105 refers to the job history management table illustrated in FIG.

  In step S4003, the cloud system 105 initializes the search result list, and copies all history information included in the job management table referred to in step S4002 to the search result list.

  In step S4004, the cloud system 105 determines whether the button 706 in FIG. 11 has been selected. Since the button 706 in FIG. 11 is a button for using the participant information as the narrowing-down condition, it is determined here whether the participant information is used as the narrowing-down condition. If the button 706 is selected, the process proceeds to S4010. If the button 706 has not been selected, the process proceeds to S4005.

  In step S4005, the cloud system 105 assigns 1 to M, which is an index to the job ID, and initializes it.

  In step S4006, the cloud system 105 refers to the search result list, and determines whether the user information of the job whose job ID is M is included in the user information set in the search condition list. If the user information of the job whose job ID is M is included in the user information set in the search condition list, the process proceeds to S4008. If the user information of the job whose job ID is M is not included in the user information set in the search condition list, the process proceeds to S4007.

  In step S4007, the cloud system 105 search result list is referred to, and the conference material information used in the job with the job ID M is deleted. Here, as a result of determining by adding the participant's condition to the search result list created in S4003, the conference material that is not targeted is deleted from the search result list.

  In S4008, the cloud system 105 adds 1 to M, which is an index to the job ID, and advances the index.

  In step S <b> 4009, the cloud system 105 determines whether a job with job ID M exists in the search result list. If a job with job ID M exists in the search result list, the process returns to S4006 to repeat the process. If no job with job ID M exists in the search result list, the process advances to step S4015.

  In S4010, the cloud system 105 determines whether the button 705 in FIG. 11 has been selected. Since the button 705 in FIG. 11 is a button for using date information as a narrowing-down condition, it is determined here whether date information is used as the narrowing-down condition. If the button 705 is selected, the process proceeds to S4011. If the button 705 has not been selected, the process proceeds to S4016.

  Next, in S4011, the cloud system 105 substitutes 1 for M, which is an index to the job ID, and initializes it.

  In step S4012, the cloud system 105 refers to the search result list, and determines whether the date of the job having the job ID M is earlier than the date set in the search condition list. If the date of the job whose job ID is M in the search result list is a date before the date set in the search condition list, the process advances to step S4014. If the date of the job whose job ID is M in the search result list is not earlier than the date set in the search condition list, the process advances to step S4013.

  In step S <b> 4013, the cloud system 105 refers to the search result list and deletes information on the conference material used in the job with the job ID M. Here, as a result of adding and determining the date condition to the search result list created in S4003, the conference material that has been excluded is deleted from the search result list.

  In S4014, the cloud system 105 adds 1 to M, which is an index to the job ID, and advances the index.

  In step S <b> 4015, the cloud system 105 determines whether a job with job ID M exists in the search result list. If a job with job ID M exists in the search result list, the process returns to S4012 to repeat the process. If no job with job ID M exists in the search result list, the process advances to step S4016.

  In S4016, the cloud system 105 determines whether the button 707 in FIG. 11 has been selected. Since the button 707 in FIG. 11 is a button for using location information as a narrowing condition, it is determined here whether location information is used as the narrowing condition. If the button 707 is selected, the process proceeds to S4017. If the button 705 has not been selected, the process ends.

  Next, in S4017, the cloud system 105 substitutes 1 for M, which is an index to the job ID, and initializes it.

  In step S <b> 4018, the cloud system 105 refers to the search result list, and determines whether the output location of the job whose job ID is M is near the holding location set in the search condition list. If the output location of the job whose job ID is M in the search result list is near the holding location set in the search condition list, the process advances to S4020. If the output location of the job whose job ID is M in the search result list is not near the holding location set in the search condition list, the process advances to S4019.

  In step S4019, the cloud system 105 refers to the search result list and deletes information on the conference material used in the job with the job ID M. Here, as a result of determining by adding the location condition to the search result list created / edited in S4003, the conference material that is not the target is deleted from the search result list.

  In S4020, the cloud system 105 adds 1 to M, which is an index to the job ID, and advances the index.

  In step S <b> 4021, the cloud system 105 determines whether a job with job ID M exists in the search result list. If a job with job ID M exists in the search result list, the process returns to S4018 to repeat the process. If a job with job ID M does not exist in the search result list, the process ends.

  Through the above processing, the search processing using the search condition list can be performed on the job history management table.

  In FIG. 27, when the narrowing process is started, in S5001, the cloud system 105 refers to two search result lists created by the search process for the conference schedule management table and the search process for the job history management table.

  Next, in S5002, the cloud system 105 adds 1 to M, which is an index to the data ID, and advances the index.

  In step S <b> 5003, the cloud system 105 includes the meeting material whose data ID is M included in both the search result list created by the search process for the meeting schedule management table and the search process for the job history management table. to decide. If the conference material with the data ID M is included in both the search processing for the conference schedule management table and the search result list created by the search processing for the job history management table, the process proceeds to S5004. If the conference material whose data ID is M is not included in both the search processing for the conference schedule management table and the search result list created by the search processing for the job history management table, the process advances to step S5005.

  In step S5004, the cloud system 105 creates a narrowing list and adds information on the conference material with the data ID M.

  In step S5005, the cloud system 105 adds 1 to M, which is an index to the data ID, and advances the index.

  In S5006, the cloud system 105 determines whether the conference material with the data ID M exists in both the search result list created by the search processing for the conference schedule management table and the search processing for the job history management table. If the conference material with the data ID M exists in both the search result lists created by the search processing for the conference schedule management table and the search processing for the job history management table, the process returns to S5003 and the processing is repeated. If the conference material whose data ID is M does not exist in both of the search result lists created by the search processing for the conference schedule management table and the search processing for the job history management table, the processing ends.

  With the above processing, narrowing-down processing using the search result list created by the search processing for the conference schedule management table in FIG. 25 and the search result list created by the search processing for the job history management table in FIG. 26 is realized. The

  In this embodiment, the search condition is set by the user as described in the file search screen of FIG. However, as another embodiment, an embodiment in which search conditions are set by transmitting an image taken at the time of a meeting to the cloud system 105 is also conceivable.

  FIG. 28 shows a file search screen when an image taken at the meeting is transmitted to the cloud system 105 to set a search condition. When the button 901 is selected, the user can specify an image taken during the meeting. The image taken at the time of the meeting may be an image taken of the meeting, an image taken of the contents of the meeting such as a whiteboard image, or a group photo of the participants of the meeting. Depending on the device that captures the image, the image may be stored with the location, time, and participant information at the time of capture added, so this additional information can also be included in the image. When the button 902 is selected by the user, the conference image can be transmitted to the cloud system 105.

  FIG. 29 is a conference image information screen displayed when the button 902 is selected. The transmitted conference image is analyzed, and the shooting date, shooting location, and image title are displayed. In addition, when the image is received, the user information that transmitted the image is also acquired. When the button 903 is selected, the shooting date / time is set as the date of the conference, the shooting location is set as the conference location, and the transmitted user information is set as the participant information as search conditions. Processing is performed. When the button 904 is selected, the screen returns to the file search image of FIG.

  FIG. 30 shows a flowchart of the file search process when an image taken at the time of the meeting is designated on the file search screen of FIG. 28 and the meeting image is transmitted by the button 902.

  When the user selects the button 902 on the file search screen in FIG. 28 and a conference image is transmitted, in S6001, the cloud system 105 receives the conference image.

  Next, in S6002, the cloud system 105 analyzes the information added to the conference image. In this embodiment, the shooting date / time, shooting location, and transmitted user information are acquired.

  Next, in S6003, the cloud system 105 displays the additional information of the conference image analyzed in S6002 on the screen as shown in FIG.

  In step S6004, the cloud system 105 determines whether a search instruction has been given by the user selecting the buttons 903 and 904 in FIG. If the button 903 is selected and there is a search instruction, the process advances to step S6005. If the button 904 is selected and there is no search instruction, the process ends.

  In S6005, the cloud system 105 sets the additional information acquired in S6002 as a search condition, and executes the search process for the conference schedule management table described in FIG. Note that the search condition set here can also be used in the narrowing search process described with reference to FIGS.

  With the above processing, the conference material search using the information of the conference image can be performed.

101 client PC, 102 image forming apparatus, 103 image display apparatus,
104 image projector, 105 cloud system, 106 storage

Claims (10)

A conference system for managing conferences held in an office,
A meeting schedule management means (308) for managing a meeting schedule;
Meeting material management means (401) for managing meeting materials used in the meeting;
Reference means (403, 404) for referencing the conference material via the conference system;
Reference history recording means (501) for recording a reference history when referred to by the reference means;
The conference system has search condition setting means (FIGS. 10 and 28) for setting a search condition for searching for conference materials,
For the conference material managed by the conference material management unit, the conference material is searched from the conference schedule information managed by the conference schedule management unit and the search condition set by the search condition setting unit. A first search means (604, 903);
With respect to the conference material managed by the conference material management unit, the conference material is obtained from the search condition set by the search condition setting unit using the reference history information managed by the reference history management unit. A second search means (FIG. 26) for searching;
A meeting system characterized in that the search result of the first search means and the search result of the second search means are compared to narrow down the meeting material included in both. In the conference schedule management means (308), the information to be managed is the date and time of the conference, the location of the conference, the name of the conference, the information of the conference system user participating in the conference, and the information of the conference material. The conference system according to claim 1. In the conference schedule management unit (308) and the conference material management unit (401), the conference material information to be managed includes the conference material ID, the name of the conference material, and the conference system user who registered the conference material in the conference system. The conference system according to claim 1, wherein the conference system is information. In the reference means (403, 404), the conference material is referred to the client PC (101), the image forming apparatus (102), the image display apparatus (103), and the image projection apparatus (104) of the conference system user. The conference system according to any one of claims 1 to 3, wherein the conference system is possible. The reference history recording means (501) includes the date and time when the conference material was referenced using the conference system, the name of the conference material that referred to the conference material, the name of the device that referred to the conference material, and the device that referred to the conference material. The conference system according to any one of claims 1 to 4, wherein information of a conference system user who refers to the installation location and the conference material is recorded. The search condition setting means includes search condition setting means (601, 602, 603) by which a conference system user can set a search condition for conference materials, and the search condition setting means uses a conference material. 6. The date of the conference, the location of the conference in which the conference material is used, and the information of the conference system user who participates in the conference in which the conference material is used are set as search conditions. The conference system according to any one of the above. The search condition setting means designates a conference image designation means (902) that allows the conference system user to designate an image taken at the time of the conference, and designates the conference image shooting date, the conference image shooting location, and the conference image from the conference image. A conference image information acquisition unit (S6002) for acquiring the user information, and the shooting date and time of the conference image acquired by the conference image information acquisition unit is set to the date of the conference in which the conference material is used. To the location of the conference where the conference material was used, and the information of the conference system user who specified the conference image to the information of the conference system user who joined the conference where the conference material was used. The conference system according to any one of claims 1 to 6, wherein the conference system is characterized. The first search means (604, 903) selects a meeting date that is earlier than the date of the search condition set by the search condition setting means from the meetings managed by the meeting schedule management means. A search means (S3005) and a meeting place search means (S3008) for selecting a meeting to be held at the place of the search condition set by the search condition setting means from the meetings managed by the meeting schedule management means. And a meeting participant search means for selecting a meeting including information on a conference system user who has participated in a meeting with the search condition set by the search condition setting means from the meetings managed by the meeting schedule management means ( The conference date search means, the conference location search means, and the conference participants Conference system according to any one of claims 1 to 7, characterized in that to set the conference material used in the conference selected by the search means as a search result. The second search means (FIG. 26) selects the reference history information that is earlier than the date of the search condition set by the search condition setting means from the reference history managed by the reference history recording means. Reference date search means (S4012) and a reference place for selecting the reference history information referred to in the vicinity of the holding place of the search condition set by the search condition setting means from the reference history managed by the reference history recording means From the reference history managed by the reference history recording means, search means (S4018) and reference history information including information on the conference system user who participated in the meeting of the search conditions set by the search condition setting means are obtained. A reference user search means (S4006) to select, the reference date search means, the reference location search means, and the reference user search means Conference system according to any one of claims 1 to 8, characterized in that setting the referenced conference material included in the reference history selected as the search result by. The conference system user information managed in the conference schedule management means (308) and the conference material management means (401) is the name of the conference system user and the ID of the conference system user. The conference system according to any one of claims 1 to 9.