JP2008134707A - Community generation support method and device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To support the selection of the members of a community, the preparation of the community, and the preparation and deletion of a work place (virtual working space) without bothering a user and a manager. <P>SOLUTION: This community generation support method is provided with a community generation and deletion system comprising a presence acquisition part 111 for acquiring the presence information of members at the point of time from a presence DB123 in which the presence information of members is stored; a member decision part 112 for excluding specific members by grouping the members by using location places as keys; a member data generation part 113 for preparing data for community generation; a member data transmission part 114 for transmitting the data to the groupware; and a community decision part 115 for deciding an unnecessary community. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a community generation support method and apparatus, and in particular, a community in groupware composed of a plurality of functional components such as mail, schedule, file sharing, electronic conference room, electronic bulletin board, and telephone book using a Web system. The present invention relates to a community generation support method and apparatus for supporting automatic selection and holding / dissolution of personnel constituting a (virtual team) and a workplace (virtual work space) and creation / deletion of a work space.

  In recent years, in companies, etc., people from different departments are gathered to create a community as a virtual group, and a virtual work space is prepared so that only people who make up the community can create a virtual work space. There is a demand to make it possible to use it. The creation of such a virtual community is generally performed by a user who wants to create a community selecting and collecting each individual person, which requires a lot of work. It was.

For example, a technique described in Patent Document 1 is known as a conventional technique that can generate a community with less effort as described above. This prior art relates to a method for automatically creating a community, which is a group of people having the same purpose and hobbies. An attribute is assigned in advance to members who participate in the mailing list, and the user himself / herself is based on the attribute. Creating a community.
JP 2002-269003 A

  Although the above-mentioned conventional method can easily create a community, it requires the effort of assigning attributes to members who participate in the mailing list, so registration by the user himself is necessary. In addition, since it is necessary for the administrator to collect similar attributes, there is a problem that an efficient community cannot be created. In addition, this conventional technique has a problem that the number of communities becomes enormous because the community is being created and does not have a mechanism for deleting the community.

  The object of the present invention is to solve the above-mentioned problems of the prior art, and in the groupware composed of mail, schedule, file sharing, electronic conference room, electronic bulletin board, telephone book, etc. using a Web system, the user himself Alternatively, a community generation support method and apparatus are provided that facilitate the operation of an administrator and can support selection of community members, creation of a community, creation of a workplace (virtual work space), and deletion. There is to do.

  According to the present invention, the object is a community generation support method in a community generation support device that performs support for selecting a member constituting a community and generating a community, wherein the community generation support device acquires information about a user. A database in which information about the user is stored, and a member determination unit that groups users satisfying a predetermined condition as members, and a member data generation unit that generates community generation data The information on the user is acquired from the information, and the member determination unit groups users satisfying a predetermined condition from the acquired information on the user as members, excludes a specific member from the grouped members, and the member data generation unit , It is achieved by creating a community of serial grouped members.

  According to the present invention, it is possible to save time and effort for selecting a member when creating a community, and it is possible to control the lifetime of the generated community, so that security can be considered. An effect can be obtained.

  Embodiments of a community generation support method and system according to the present invention will be described below in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a community generation support system according to an embodiment of the present invention. In FIG. 1, 101 and 122 are servers, 102 is a bus, 103 is a CPU, 104 is a display, 105 is a keyboard, 106 is a secondary storage device, 107 is a network interface, 108 is a main storage device, 109 is an operating system, 110 Is a community generation / deletion system, 111 is a presence information acquisition unit, 112 is a member determination unit, 113 is a member data generation unit, 114 is a member data transmission unit, 115 is a community determination unit, 116 is a community management unit, and 117 is an electronic conference Room function 118 is a file sharing function, 119 is groupware, 120 is a client terminal, 121 is a network, 123 is a presence database, and 124 is an entrance / exit management system.

  A community generation support system according to an embodiment includes a server 101, an entrance / exit management system 124 for using information of the system in the embodiment, and a presence database that stores information about users from the entrance / exit management system 124. A server 122 that manages the network 123 and a client terminal 120 are connected to a network 121 such as a corporate LAN. Then, main functions constituting the system according to the present invention are built in the server 101.

  In the above description, the entrance / exit management system 124 collects and manages information of people entering and exiting a predetermined place and the like, and the embodiment of the present invention is for people entering / exiting from such an entrance / exit management system 124. This information is acquired as information about the user, and a community is generated by selecting a user who satisfies a predetermined condition as a member constituting the community. Accordingly, the entrance / exit management system 124 is not limited to this, and any system that can acquire people's information as information about the user may be used.

  The server 101 is an information processing apparatus configured by connecting a CPU 103, a display 104, a keyboard 105, a secondary storage device 106 such as a hard disk, a network interface 107, and a main storage device 108 to the bus 102. In the main memory 108, a community generation / deletion system 110, a groupware 119, and an operating system 109 are stored.

  The community generation / deletion system 110 includes a presence information acquisition unit 111 that acquires each person's presence information from the presence database 123, and a member list that selects, as members from the presence database 123, information about users that satisfy a predetermined condition including the location. Member determination unit 112 that determines the creation and non-target users, member data generation unit 113 that generates member data to be sent to the community management unit 116 of the groupware 119 for community creation, and member data for community creation as groupware 119, a member data transmission unit 114 to be sent to the community management unit 116, a community determination unit 115 for checking the access status to the community and generating or deleting the community, grouping Over data 701 is configured to include a community generation data 801. The groupware 119 includes a community management unit 116, an electronic conference room function 117, and a file sharing function 118.

  The electronic meeting room function 117 and the file sharing function 118 included in the groupware 119 have a function as a workplace (virtual work space) used by people constituting the community created in the embodiment of the present invention. It is.

  The function units 111 to 115 constituting the community generation / deletion system 110 stored in the main storage device 108, the function units 116 to 118 constituting the groupware 119, and the operating system 109 are configured by programs. Each function is constructed by being executed by the operating system 109 after being stored in the next storage device 106 and loaded into the main storage device 108.

  In the above-described embodiment, each functional element constituting the present embodiment is allocated in the server 101 which is a single computer. However, in the present embodiment, a plurality of computers in which each functional element is connected via a network. It may be configured to be assigned to.

  Further, the client terminal 120 connected via the network 121 deletes unnecessary communities from the temporary community list created by the embodiment of the present invention and accesses temporary community information. It is used for determining the community, creating a community desired by the user, and the like. Although only one client terminal 120 is shown in FIG. 1, a plurality of client terminals 120 may be provided.

  FIG. 2 is a diagram showing a data structure of one record 201 of an entry record recorded by the entry / exit management system 124 and transmitted to the server 122, and FIG. 3 is a diagram showing a data structure of an entry record 301 that details the entry record. It is.

  One record 201 of the entry record is recorded by the entry / exit management system 124 that manages the entry / exit of people entering / exiting a specific place, room, etc., and is the entry information transmitted from the entry / exit management system 124 to the server 122. Yes, one record is created for each user who enters the room. As shown in FIG. 2, the record 201 includes a unique user ID in a system for identifying a user, a unique location ID indicating where the user is, a room entry date and time, and the like. The detailed room entry record 301 is made up of a plurality of records, specifically specifying the above-mentioned items of user ID, location ID, and room entry date / time.

  The entry record 301 includes the items as shown in FIG. 3 at a minimum, but if there are alternative items, it is not necessary to specify a system for generating the record, and the entry / exit management system 124 may be, for example, an entrance management system using RFID, a biometric authentication system such as a fingerprint or an iris, or the like.

  FIG. 4 is a diagram showing a data structure of one record 401 stored in the presence database 123, and FIG. 5 is a diagram showing a detailed data structure of the presence record 501 stored in the presence database 123.

  The entry record 301 transmitted from the entry / exit management system 124 described with reference to FIGS. 2 and 3 is received by the server 122 and stored as a presence record 501 in the presence database 123. As shown in FIG. 4, one record 401 of the presence record 501 is a unique user ID and a unique user ID in the system for identifying the user, as in the case of the one record 201 of the room entry record. It is configured to include location ID, date of entry, etc. The presence record 501 is made up of a plurality of records, specifically specifying each of the above-mentioned user ID, location ID, and room entry date / time.

  The presence record 501 includes the items as shown in FIG. 5 at a minimum, but if there is an alternative item, it is not necessary to specify the system that generates the record.

  FIG. 6 is a diagram showing an example of a record of user IDs to be excluded from community members registered in the presence database 123 in advance. The user who has the ID excluded from the community members is, for example, a person outside the company or a person in charge who temporarily enters the conference room, and is registered as a person who excludes these persons in advance. The ID registered in this table is deleted from grouping data 701, which will be described later, and community generation data 801 is created.

  FIG. 7 is a diagram showing a data structure of grouping data 701 generated from presence records. This grouping data 701 is generated by the member data generation unit 113 and is temporarily stored, and is composed of a temporary community ID and a user ID.

  The temporary community ID is created using the location ID and the time of community generation timing described later. In addition, the user IDs of members belonging to the community are registered in pairs with the temporary community ID. The provision method of provisional community ID is not limited to the above-described method and may be imparted in any way as long as it can be uniquely assigned so as not to overlap with other IDs. In FIG. 7, a plurality of member user IDs are shown separated by “,” (comma), but the separation method and characters are not specified.

  FIG. 8 is a diagram illustrating a data configuration of community generation data generated as a result of excluding a specific ID from grouping data. This community generation data is temporarily stored by the member data generation unit 113 generated by deleting the exclusion ID described with reference to FIG. 6 from the grouping data 701 described above from the user ID.

  FIG. 9 is a flowchart for explaining the entire process of generating a temporary community in the embodiment of the present invention. Next, this will be described.

(1) The presence information acquisition unit 111 first checks the community generation timing, and acquires the presence record 501 from the presence database 123 when the community generation timing is reached. This presence record 501 is generated by the server 122 as described above. The presence database 123 is generated when the server 122 receives the entry record 301 generated by the entry / exit management system 121 (steps 1001 and 1002).

(2) Next, the member determination unit 112 performs grouping of user IDs using the location ID in the presence record 501 as a key, the member data generation unit 113 generates a grouping record 701, and the exclusion ID 601 is used as the grouping record 701. The community generation data 801 is created by deleting from the list (steps 1003 and 1004).

(3) Next, the member data transmission unit 114 transmits the created community generation data 801 to the community management unit 116 of the groupware 118, and a temporary community and a workplace are generated (steps 1005 and 1006). .

  FIG. 10 is a flowchart for explaining the process of checking the community generation timing in step 1001 of the flow shown in FIG. 9, which will be described next.

(1) When this process is started, first, the current time is acquired, and the time when the community was generated last time is acquired (steps 1101 and 1102).

(2) Calculate the difference between the acquired current time and the time when the community was generated last time, check whether the time has passed a predetermined time interval, and if not, the specified time Until step elapses, the processing from step 1101 is repeated (step 1103).

(3) If the specified time has passed in the check in step 1003, the processing here is terminated, and the processing shifts to the presence record acquisition processing in step 1002 of the flow shown in FIG.

  The community generation timing check described above was a check to determine whether the elapsed time from the previous community generation time has reached a predetermined time, but the timing for generating the community includes scheduled conference information. It may be determined in such a way that the start time, the conference end time, or a few minutes after the conference start time.

  FIG. 11 is a flowchart for explaining the exclusion ID check process in step 1004 of the flow shown in FIG. 9, which will be described next. This process is a process for removing the specific ID described in FIG. 6 from the grouping data 701 shown in FIG.

(1) First, it is checked whether or not there is a record to be read that has not yet been processed in the grouping data 701 shown in FIG. 7, and if there is an unprocessed record, that one record is read (steps 1201 and 1202). .

(2) It is determined whether or not the exclusion ID registered in the server 122 is included in advance in the user ID of the read record. If the exclusion ID is not included, the process returns to step 1201 to Processing for the record is continued (step 1203).

(3) If it is determined in step 1203 that the user ID of the read record includes an exclusion ID registered in the server 122 in advance, the exclusion ID is deleted from the table, and the processing from step 1201 is performed. Returning, the process for the next record is continued, and the process is repeated until there are no more records to be read from the grouping data, and the process is terminated (step 1204).

  FIG. 12 is a diagram showing a configuration example of a temporary community list (before check) managed by the community management unit 116 of the groupware 119. The temporary community list 1301 is created by the member determination unit 112 through the above-described processing. The temporary community ID that allows the community to be uniquely identified, the creation date and time indicating the date and time when the community was generated, and the access to the community. An access flag indicating this, a user ID as community member information, and the like.

  FIG. 13 is a diagram showing a configuration example of a temporary community list (after checking) when an unnecessary community is deleted by a community deletion process described later. The temporary community list shown in FIG. 13 is a temporary community list shown in FIG. 12 that is a community that has not been accessed for a certain period of time since it was created by the process described later with reference to FIG. Created by deleting from.

  FIG. 14 is a flowchart for explaining the entire process of deleting the temporary community generated in the embodiment of the present invention. Next, this will be explained.

(1) First, the community determination unit 115 acquires the temporarily created community list 1301 shown in FIG. 12, and determines whether or not the check for all the communities to be checked has been completed (step 1501). 1502).

(2) If all the communities have not been checked in the check in step 1502, one record is read from the community list 1301, and it is determined whether or not access to the community of the record has not been performed for a certain time or more. Determination is made (steps 1503 and 1504).

(3) If there is an access from a community member for a predetermined time in the determination in step 1504, it is determined whether or not there is a deletion request from the user for the community (step 1505).

(4) If there is no access from a community member for a predetermined time in the determination in step 1504, or if there is a deletion request from the user in the determination in step 1505, the temporary community is deleted, Returning to the process from step 1502, the process for the next record is continued. At this time, the creation and deletion history may be left in the log or the like (step 1507).

(5) If there is no deletion request from the user in the determination in step 1505, it is determined whether or not there is a community generation request from the user. If there is a community generation request, the request from the user is followed. If there is no community generation request after generating the community, the process returns to step 1502 without doing anything, and the process for the next record is continued, and the temporarily created community list 1301 is not yet stored. If there are no more check records, the processing here is terminated (step 1506).

  Each process in the above-described embodiment of the present invention is configured by a program and can be executed by a CPU included in the present invention. These programs are stored in a recording medium such as an FD, CDROM, or DVD. It can be provided and can be provided by digital information via a network.

  FIG. 15 is a diagram illustrating a screen display example displayed on the client terminal 120 in response to a request from the user as a result of performing provisional community generation and deletion.

  A display screen 1601 shown in FIG. 15 displays a temporary community list and details of the community when one community is selected from the temporary community list. In this display screen, if the user selects one community from the temporary community list and presses the delete button, the community is deleted without waiting for a certain period of time, and the user presses the create button. Thus, a new community can be created by inputting member information. In addition, this screen allows the user to use the temporary community generated by the system as an official community, and to use a newly created community as the official community. Can be able to.

  In the above-described embodiment of the present invention, the members who participate in the conference are selected from the user ID, location ID, and presence time presence data managed by the entrance / exit management system 124 to select members constituting the community. Although the present invention has been described as being performed, the present invention can be selected from participants in a physical TV conference system, a TV conference system using a personal computer, etc. You can also choose from among them.

It is a block diagram which shows the structure of the community production | generation assistance system by one Embodiment of this invention. It is a figure which shows the data structure of one record of the room entry record recorded with the entrance / exit management system and transmitted to a server. It is a figure which shows the data structure of the entrance record which refined the figure room record. It is a figure which shows the data structure of one record of the presence record stored in a presence database. It is a figure which shows the detailed data structure of the presence record stored in a presence database. It is a figure which shows an example of the record of a user's ID excluded from the community member previously registered into the presence database. It is a figure which shows the data structure of the grouping data produced | generated from a presence record. It is a figure which shows the data structure of the data for community production | generation produced | generated as a result of excluding specific ID from grouping data. It is a flowchart explaining the whole process which produces | generates a temporary community in embodiment of this invention. It is a flowchart explaining the process of a community production | generation timing check in step 1001 of the flow shown in FIG. 10 is a flowchart for explaining exclusion ID check processing in step 1004 of the flow shown in FIG. 9. It is a figure which shows the structural example of the temporary community list (before check) managed by the community management part of groupware. It is a figure which shows the structural example of a temporary community list (after a check) when an unnecessary community is deleted by the deletion process of a community. It is a flowchart explaining the whole process which deletes the temporary community produced | generated in this embodiment. It is a figure which shows the example of a screen display displayed on the client terminal 120 by the request | requirement from a user as a result of implementing temporary community production | generation and deletion.

Explanation of symbols

101, 122 Server 102 Bus 103 CPU
104 Display 105 Keyboard 106 Secondary storage device 107 Network interface 108 Main storage device 109 Operating system 110 Community generation / deletion system 111 Presence information acquisition unit 112 Member determination unit 113 Member data generation unit 114 Member data transmission unit 115 Community determination unit 116 Community Management unit 117 Electronic meeting room function 118 File sharing function 119 Groupware 120 Client terminal 121 Network 122 Server 123 Presence database 124 Entrance / exit management system

Claims (5)

In the community generation support method in the community generation support device that supports the generation of the community by selecting members constituting the community,
The community generation support device includes an acquisition unit that acquires information about a user, a member determination unit that groups users satisfying a predetermined condition as members, and a member data generation unit that generates data for community generation,
The acquisition means acquires information about the user from a database storing information about the user,
The member determination means groups users satisfying a predetermined condition from information about acquired users as members, excludes specific members from the grouped members,
The member data generation means generates a community of the grouped members.   2. The community generation support method according to claim 1, wherein the information on the user stored in the database is presence information acquired from an entry / exit management system, and the predetermined condition is a predetermined location. In the community generation support method for generating a community by selecting members constituting the community and supporting the deletion of the generated community,
In the information processing apparatus, an acquisition unit that acquires information about the user, a member determination unit that groups users who satisfy a predetermined condition as members, a member data generation unit that generates data for generating a community, and a community determination unit Configure
The acquisition means acquires information about the user from a database storing information about the user,
The member determination means groups users satisfying a predetermined condition from information about acquired users as members, excludes specific members from the grouped members,
The member data generation means generates a community by the grouped members,
The community determination support method, wherein the community determination unit deletes the generated community according to a predetermined condition.   4. The deletion of the community is performed when there is no access to the generated community from a community member for a predetermined period of time or when there is a deletion request from a user. Community generation support method. In the community generation support device that supports the generation of the community by selecting members constituting the community,
The community generation support device includes an acquisition unit that acquires information about a user, a member determination unit that groups users satisfying a predetermined condition as members, and a member data generation unit that generates data for community generation,
The acquisition means acquires information about the user from a database storing information about the user,
The member determination means groups users satisfying a predetermined condition from information about acquired users as members, excludes specific members from the grouped members,
The member data generation unit generates a community of the grouped members.

Images