JP2006107282A - Community management system, community server, community management method and community management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily create a community and accurately manage its members. <P>SOLUTION: In a community management system comprising a user terminal for a user to use a community through a communication network and a community server for creating and managing a community according to a request from the user terminal, the community server has an authentication means for authenticating a user using the user terminal, a community management means for generating a screen for creating or managing a community by the authority of user information acquired by the authentication means to display the screen on the user terminal, a member management means for managing a member belonging to the community created by the community management means, and an accumulation means for accumulating various information acquired by the community management means and the member management means, thus solving the problem. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a community management system, a community server, a community management method, and a community management program, and in particular, community management that can easily generate a community and can perform member management with high accuracy. The present invention relates to a system, a community server, a community management method, and a community management program.

  Conventionally, users having the same taste on the Internet form a community and exchange information within the community. In such a community, resources (resource information) are shared among members by a bulletin board or a broadcast mail function.

  On the other hand, in a company, a similar service is provided to a community by the name of groupware.

  As such a community generation method, there is an electronic community management method that can reduce the time required for generating a homepage and a mailing list for generating a community for exchanging information via e-mail via the Internet (for example, , See Patent Document 1).

In Patent Document 1, when mailing list generation information including a mail address is input from a user terminal via a WWW (World Wide Web) browser, the server generates a mailing list based on the mailing list information and notifies the user terminal. . Similarly, when homepage generation information is input from the user terminal, a homepage is generated based on the homepage generation information.
Japanese Patent Laid-Open No. 11-112552

  However, in the conventional method described above, in order to generate a community, it is necessary to ask a system administrator each time, and costs and time are required. Also, the administrator's work requires specialized knowledge, authority to operate the system, etc., and the user who wants to create a community cannot create the community, and the operation is concentrated on a specific worker.

  In addition, management of members is important for a community administrator, and for example, an update operation for removing a person from a community member or adding a new member due to personnel changes or the like is required. In this case, since a person who manages a community of a company with frequent personnel changes needs to be updated frequently, problems such as forgetting to update or mistaken contents of update occur.

  The present invention has been made in view of the above problems, and can easily generate a community by a simple operation, and can perform member management such as member registration and change with high accuracy. A community management system, a community server, a community management method, and a community management program are provided.

  In order to solve the above problems, the present invention employs means for solving the problems having the following characteristics.

  The invention described in claim 1 is a community comprising a user terminal for a user to use a community via a communication network, and a community server that generates and manages a community according to a request from the user terminal. In the management system, the community server generates an authentication unit for authenticating a user who uses the user terminal and a screen for generating or managing a community according to the authority of user information obtained by the authentication unit. And storing community management means to be displayed on the user terminal, member management means for managing members belonging to the community generated by the community management means, and various information obtained by the community management means and the member management means. Storage means for performing

  According to the first aspect of the present invention, it is possible to easily generate a community and to manage members with high accuracy.

  In the invention described in claim 2, the member management means collates employee information obtained by referring to an employee master connected to the communication network and member information stored in the storage means. When different information is present, the target member information is displayed as an alert on the user terminal based on the authority of the user information.

  According to the second aspect of the present invention, when there is a personnel change or the like in a community member, it is possible to easily grasp the process of change, etc., so that the management of the member can be realized quickly and with high accuracy. it can.

  According to a third aspect of the present invention, when the community management unit sets members in the community, the community management unit performs grouping for each category, and sets whether or not to send an e-mail for each grouped member. It is characterized by that.

  According to invention of Claim 3, the community suitable for every member can be provided. In addition, members can be managed with high accuracy.

The invention described in claim 4 is a community server that acquires a request from a user terminal via a communication network and generates and manages a community from the acquired request content.
An authentication unit for authenticating a user who uses the user terminal and a screen for generating or managing a community according to the authority of user information obtained by the authentication unit are generated and displayed on the user terminal. It has community management means, member management means for managing members belonging to the community generated by the community management means, and storage means for storing various information obtained by the community management means and the member management means. And

  According to the fourth aspect of the present invention, it is possible to easily generate a community and to manage members with high accuracy.

  According to a fifth aspect of the present invention, the member management means collates employee information obtained by referring to an employee master connected to the communication network and member information stored in the storage means. When different information is present, the target member information is displayed as an alert on the user terminal based on the authority of the user information.

  According to the fifth aspect of the present invention, when there is a personnel change or the like in a community member, it is possible to easily grasp the process of change, etc., so that the management of the member can be realized quickly and with high accuracy. it can.

  The invention described in claim 6 is a community management method for acquiring a request from a user terminal via a communication network and generating and managing a community from the acquired request content. An authentication stage for authenticating a user, a community management stage for generating or displaying a screen for generating or managing a community according to the authority of user information obtained by the authentication stage, and displaying the screen on the user terminal; and the community management A member management stage for managing members belonging to the community generated by the stage, and an accumulation stage for accumulating various information obtained by the community management stage and the member management stage.

  According to the sixth aspect of the present invention, the community can be easily generated, and the members can be managed with high accuracy.

  In the invention described in claim 7, in the member management stage, employee information obtained by referring to an employee master connected to the communication network is compared with member information accumulated in the accumulation stage. When different information is present, the target member information is displayed as an alert on the user terminal based on the authority of the user information.

  According to the seventh aspect of the present invention, when there is a personnel change or the like in a community member, it is possible to easily grasp the process of change, etc., so that the management of the member can be realized quickly and with high accuracy. it can.

  The invention described in claim 8 is a community management program for acquiring a request from a user terminal via a communication network, and causing a computer to execute processing for generating and managing a community from the acquired request content. A screen for generating or managing a community is generated according to the authentication process for authenticating the user who uses the user terminal and the authority of the user information obtained by the authentication stage, and is displayed on the user terminal. Employee information obtained by referring to a community management process, an employee master connected to the communication network, and the member information stored in advance, and the user information when different information exists And a member management process for displaying the target member information on the user terminal as an alert based on the authority of the user. To be executed by the data.

  According to the eighth aspect of the present invention, it is possible to easily generate a community and to manage members with high accuracy. In addition, if there is a personnel change in a member of the community by the member management process, the administrator can easily grasp the process of the change, etc., so that the management of the member can be realized quickly and with high accuracy. it can. Furthermore, by installing the program, the generation and management of the community in the present invention can be easily realized by a general-purpose personal computer or the like.

  According to the present invention, it is possible to easily generate a community. In addition, members can be managed with high accuracy.

<Outline of the present invention>
The present invention provides a place for sharing information in a department homepage and in-house project activities by a simple registration operation. Specifically, in response to a community request from a user, a system administrator creates a community, and after various settings are completed, operation registration of members to be used is transferred to the community administrator.

  In addition, community members can be managed in conjunction with the employee master, displaying alerts, etc. when personnel changes, allowing community managers to add, delete, and change members accurately and quickly. . Moreover, each operation in a community administrator can be performed easily.

  The community generated in the present invention includes functions such as a member management function, a broadcast mail function, a bulletin board function, an event schedule display function, a library function, an electronic conference room function, and a related link display function.

  Hereinafter, embodiments in which a community management system, a community server, a community management method, and a community management program according to the present invention are suitably implemented will be described with reference to the drawings.

<System configuration>
FIG. 1 is a schematic configuration example of a community management system according to the present invention. A community management system 10 shown in FIG. 1 is configured to include a community server 11, at least one or more user terminals 12-1 to 12-n, and an employee master 13, and is represented by the Internet, a local network, or the like. Connected by a communication network 14.

  The community server 11 performs user authentication in response to a connection request from the user terminal 12, and performs community generation, reference, member management, and the like based on authority corresponding to preset user information. The authority is roughly divided into a system administrator who creates a community, a community manager who manages the created community, and a general user who uses the community.

  Moreover, the community server 11 accumulate | stores the various information of the produced | generated community, and discloses (provides) a community to a user as a web server. Furthermore, the community server 11 also stores information on community members. When there is a personnel change or the like with respect to the community members in comparison with the employee master 13, the system administrator and the community are based on this information. Notify the administrator of the information.

  The user terminal 12 accesses the community server 11 via the communication network 14 and manages community generation and reference according to the user's authority.

  Here, when the authority of the user is for the system administrator, the community is generated based on a request from the client who requests generation of the community. Specifically, the setting is performed on the interface screen of the community published on the Web. It should be noted that the generation of the community is easy and inexpensive by displaying a screen form (template) preset by the community server 11 on the screen of the user terminal 12 and selectively setting the basic functions of the community. A community can be generated quickly and quickly. Details of the screen interface displayed by the community server 11 for the system administrator will be described later.

  If the user authority is for a community manager, the community created by the system manager is managed. That is, community setting information stored in the community server 11 is referred to via the communication network 14, and member management such as member registration, change, and deletion, and bulletin board management are performed. Details of the screen interface displayed by the community server 11 for the community manager will be described later.

  In addition, when the user authority is a general user, it is possible to confirm a meeting, check a schedule, use a bulletin board or the like for a community that is a member. The details of the screen interface displayed by the community server 11 for general users will be described later.

  The employee master 13 is set with the employee's name, affiliation, address, e-mail address, and the like. This information is managed by the personnel department or general affairs department in the company, and the latest employee information can be obtained. The community server 11 can easily realize member management in the community by using employee information obtained by the employee master 13 and a database in the community server 11. As a result, the community can be generated quickly and inexpensively.

  Here, the community server 11 described above can be controlled by a dedicated device configuration, but generates an execution program capable of causing a computer to execute each function. For example, a general-purpose personal computer, workstation, etc. By installing the program, community generation and management in the present invention can be realized. Also, a general-purpose personal computer or the like can be used in the user terminal 11 that uses the community.

<Hardware configuration>
Here, an example of a hardware configuration of a computer capable of generating / managing and using a community according to the present invention will be described with reference to the drawings. FIG. 2 is a diagram illustrating an example of a hardware configuration capable of realizing generation / management and use of a community according to the present invention.

  2 includes an input device 21, an output device 22, a drive device 23, an auxiliary storage device 24, a memory device 25, a CPU (Central Processing Unit) 26 for performing various controls, and a network connection device. 27, and these are connected to each other by a system bus B.

  The input device 21 has a pointing device such as a keyboard and a mouse operated by a user, and inputs various operation signals such as execution of a program from the user. The output device 22 has a display for displaying various windows and data necessary for operating the computer main body for performing the processing according to the present invention, and displays the program execution progress, results, and the like by the control program of the CPU 26. can do.

  Here, in the present invention, the execution program installed in the computer main body is provided by, for example, the recording medium 28 such as a CD-ROM. The recording medium 28 on which the program is recorded can be set in the drive device 23, and the execution program included in the recording medium 28 is installed in the auxiliary storage device 24 from the recording medium 28 via the drive device 23.

  The auxiliary storage device 24 is a storage means such as a hard disk, and can store an execution program according to the present invention, a control program provided in a computer, etc., and perform input / output as necessary.

  Based on a control program such as an OS (Operating System) and an execution program read out and stored by the memory device 25, the CPU 26 performs various operations and data input / output with each hardware component, etc. Each process in community generation, management, etc. can be realized by controlling the process. Various information necessary during the execution of the program can be acquired from the auxiliary storage device 24 and can also be stored.

  The network connection device 27 acquires an execution program from another terminal connected to the communication network 14 by connecting to a communication network or the like, or an execution result obtained by executing the program or the present invention. The execution program itself can be provided to other terminals.

  With the above-described hardware configuration, community generation / management and use in the present invention can be executed. Next, the functional configuration of the community server 11 will be described with reference to the drawings.

  FIG. 3 is a diagram illustrating an example of a functional configuration of the community server 11 in the present embodiment. The community server 11 shown in FIG. 3 includes an authentication unit 31, a community management unit 32, a member management unit 33, a mail generation unit 34, a bulletin board management unit 35, a schedule management unit 36, a library management unit 37, Related link management means 38, conference room management means 39, and database (hereinafter referred to as DB) 40 are configured.

  In response to the connection request from the user terminal 12, the authentication unit 31 inputs user information and performs collation with user information registered in the DB 40 in advance. The web screen related to the community is displayed on the user terminal 12.

  Moreover, the community management means 32 manages the production | generation of a community, when the user authority based on the user information input from the user terminal 12 is a system administrator. That is, the community management unit 32 causes the connected user terminal 12 to display a setting registration form (template) for easily generating a community on the screen of the user terminal 12. The system administrator performs various community settings according to the setting registration form based on the community generation request requested by the requesting department or the like.

  The member management means 33 performs setting of members registered in the community. That is, a community manager or the like can arbitrarily designate a member. Moreover, when a member changes personnel, the contents can be quickly grasped based on the DB 40 and the employee master 13, and processing such as member deletion, addition, and change is performed based on the contents.

  The mail generation unit 34 generates a mail for notifying the target member of various information registered in the community. Specifically, a dedicated form is displayed on the user terminal screen, such as a broadcast mail, and a mail is generated by setting a member to be sent to the mail address of the member registered in advance in the DB 40. Can send emails to. The bulletin board management means 35 provides a bulletin board dedicated to community members, generates a screen for writing or browsing from the members, and provides it to the user terminal 12.

  The schedule management means 36 registers and manages events (schedules) and the like of members participating in the community. In addition, the schedule management unit 36 displays schedule contents corresponding to a schedule browsing request from the user terminal 12 on the screen of the user terminal 12.

  The library management unit 37 registers, stores, and manages information (document files, image files, etc.) shared among members, and provides corresponding information in response to a request from the user terminal 12. The related link management unit 38 sets, displays, etc., a collection of links to highly relevant web pages for members. The conference room management means 39 provides members with a place of an electronic conference room, and provides a bulletin board function that allows discussion revisions to be shared among members. Further, the DB 40 stores various information in community generation and management, member information, and the like.

<Database configuration>
Here, examples of the database (DB 40) and the employee master 13 described above will be described with reference to the drawings.

  FIG. 4 is a diagram for explaining data examples of the database and the employee master in the present invention. 4A shows the DB 40 that the community server 11 has, and FIG. 4B shows the employee master 13.

  As an example, the DB 40 shown in FIG. 4A is arranged for each community generated in the procedure described later, and includes “community name”, “category”, “employee number”, “affiliation”, It consists of items such as “name” and “role”.

  Here, the category is identification information for further grouping within the community, and a plurality of groups can be set for one community. One category can be grouped into a plurality of categories such as category 1, category 2, category 3,... The employee number is identification information for identifying a member and exists in the employee master. The member information is collated based on the employee number. The role indicates a role in the community. Based on this “role” information, the community server 11 provides a screen corresponding to the system administrator and the community administrator to the user terminal 12.

  In addition to the above, information stored in the DB 40 includes authentication information such as a user ID and a password in an authentication process performed when an employee accesses the community server 11 from the user terminal 12.

  On the other hand, the employee master shown in FIG. 4B includes items such as “employee number”, “affiliation”, “name”, “mail address”, “address”, and “phone number”. This employee master is a database that is managed by, for example, a personnel department in a company, and is a database that is quickly changed when a personnel change or the like is changed. Community creation, management, and the like in the present invention can be realized using the above-described data and the like.

<Screen interface>
Next, an example of a screen interface in the present invention provided by the community server 11 to the user terminal 12 will be described with reference to the drawings.

  First, when the user terminal 12 requests access to the community server 11, authentication processing is performed by the authentication unit 31. The screen at this time is a screen for inputting a user ID and password such as an employee number that are generally used. A user who is authenticated based on this screen can access the community server 11. In addition, the screens for the system administrator, community administrator, and general user are displayed based on the authority for the user set in advance.

<Community settings>
FIG. 5 is a diagram illustrating an example of a community setting registration screen. Note that the screen shown in FIG. 5 is a screen displayed when the user information authenticated by the user authentication is a system administrator.

  Here, when the user information authenticated by the authentication unit 31 has the authority of the system administrator, for example, “community management”, “member management”, “bulletin board management”, “schedule” displayed on the top page screen, for example. A corresponding screen form is displayed by selecting a management content to be set from a menu such as “management”, “library management”, “conference room theme management”. The system administrator sets the community based on the displayed form.

  In the community management screen 50 shown in FIG. 5, the system administrator makes settings in the community basic information setting area 51 based on the request content (request) from the request department or the like. Specifically, it sets about a community name, a community manager name (or identification information, such as user ID for identifying a user), and the activity content (summary) of a community.

  Next, in the member management area 52, whether or not the community can be used only by members is set by a check box. In addition, a radio button is used to set whether all members can use the mail transmission function setting area 53 or only an administrator (system administrator and / or community administrator) can use.

  Next, regarding the bulletin board setting area 54, whether to use, update, etc., notify the member by e-mail, allow only the administrator to post, or display by member category is set. . Here, the member category represents a type for each member, and a general user can display corresponding to each member by displaying each category in the community.

  The event schedule setting area 55 is used to set whether to use the event schedule function or to notify the change, update, etc. by e-mail. The library setting area 56 is used to set whether to use the library function or to notify members of changes, updates, etc. by e-mail.

  Also, the related link setting area 57 sets whether to use a related link or notify a member of changes, updates, etc. by e-mail. The electronic conference room setting area 58 sets whether to use an electronic conference room or to accept anonymous input when used.

  Also, whether to display the URL in the mail transmitted to the member is set by the URL display setting area 59 in the mail. In addition, whether to display the broadcast address in the mail is set by the broadcast address display setting area 60 in the mail. In addition, a mail attachment file setting area 61 is used to set whether to allow attachment of a file to a mail transmitted to a member. Further, after the setting for the above is completed, by selecting the registration button 62, a community is generated based on the conditions set above.

  The generated community is displayed in the community display area 63 as a community list. Here, the manager name, usage status (number of accesses), member management, e-mail transmission, bulletin board, event, library, related link, presence / absence of functions based on the above setting conditions, etc. (in FIG. “Yes” is displayed. In addition, when the content of the generated community is corrected or the community is deleted, the processing button 64 such as a “correct” button or a “delete” button is used for correction and deletion. Information registered, updated, etc. by the above-described processing is stored in the DB 40.

<Member registration>
Next, an example of a member registration screen when the system administrator authority is used will be described. FIG. 6 is a diagram illustrating an example of a member registration screen when the system administrator authority is used. As shown in FIG. 6, when performing member registration at the time of system administrator authority, member registration and setting change are performed based on the member registration screen 70.

  First, all the existing communities are displayed in the community selection area 71 of the member registration form 70. The system administrator selects a community for registering or changing members from the community selection area 71. Next, after selecting the community, the employee number (identification information) of the member to be registered is set in the user information setting area 72, and the member category set in the category setting area 73 is set. Here, the president, head office management department, manufacturing department, project members, etc. are classified. Next, when the member to be registered is a community administrator, the setting category in the administrator category setting area 74 is checked.

  Then, by selecting the registration button 75, the community member list display 76 displays the member as a member.

  In addition, as members of the member list displayed in the community member list display 76, the “employee number” of the member for each category of the community, “role” for displaying the role such as who is the administrator, “ “Affiliation”, “Name”, “Process”, etc.

  Here, when there is a change in the member affiliation due to personnel changes or the like, personnel change information is displayed, an alert or the like is displayed to the administrator, and an easy-to-manage screen is provided to the system administrator.

  Here, for example, when the affiliation is changed due to a change, the affiliation after the change is displayed in red, flashing, highlighting, etc. Is highlighted.

  Specifically, in FIG. 6, it is assumed that the employee number AA001 has been transferred from “3 head office sales department” to “head office sales promotion department”. In this case, “→ Head Office Sales Promotion Department” is held in red. In this case, the system administrator changes the setting of the target member by selecting a “modify” button or a “delete” button provided in “processing”. For example, even if the affiliation is changed, the work before the change may be continued. In this case, the system administrator changes the affiliation by selecting the “Modify” button on the user terminal 12. It will be included in community members. The affiliation before the change is member information stored in the DB 40, and the new affiliation after the change is employee information of the employee master 13. Since the information in the employee master 13 is generally changed quickly, the system administrator can also quickly manage members corresponding to the change based on this information. The alert display is not limited to affiliation. For example, when the surname is changed, the display portion of the name is displayed as an alert.

  Thus, the member registration form 70 allows the system administrator to easily register or change members.

<Bulletin board registration>
Next, an example of a bulletin board registration screen for the system administrator will be described with reference to the drawings. FIG. 7 is a diagram illustrating an example of a bulletin board registration screen. As shown in FIG. 7, when registering a bulletin board with the authority of the system administrator, the bulletin board is registered based on the bulletin board registration screen 80.

  First, all the communities existing at the present time are displayed in the community selection area 81 of the bulletin board registration 80. The system administrator selects a community for registering the bulletin board from the community selection area 81. Next, after selecting a community, the period is set in the posting period setting area 82 of the bulletin board. In addition, the title of the bulletin board is set in the title setting area 83. The content setting area 84 describes the purpose and contents of the bulletin board. In addition, a file to be attached to the bulletin board is set in the attached file setting area 85.

  After completing the setting described above, the registration button 86 is selected to complete the setting of the bulletin board, and the contents are stored in the DB 40.

<Schedule registration>
Next, a schedule registration screen for the system administrator will be described with reference to the drawings. FIG. 8 is a diagram illustrating an example of a schedule registration screen. As shown in FIG. 8, when registering a schedule (schedule) with the system administrator authority, the schedule is registered based on the schedule registration screen 90.

  First, all the communities existing at the present time are displayed in the community selection area 91 of the schedule registration screen 90. The system administrator selects a community for registering a reservation from the community selection area 91. Next, after selecting a community, presence / absence of display is set for each category of the community in the category selection area 92.

  Furthermore, the reservation setting area 93 sets the reservation date and time (date, time), title, location, content, target person, and the like. When performing reservation registration, a registrant is automatically set based on user information obtained at the time of authentication by the authenticating means 31. Further, whether to notify the reservation information by e-mail is set by the e-mail information setting area 94. Specifically, the presence / absence of mail transmission, the mail text, the transmission target person, etc. are set.

  After the above setting is completed, the reservation information is registered in the community server 11 by selecting the registration button 95, and at the same time, reservation information (theme name, date, etc.) for each community is displayed in the reservation information list display 96. Here, when the reservation information already registered is corrected and deleted, the setting is performed by selecting the processing button 97 including “correction” or “deletion”. Here, the set contents are accumulated in the DB 40.

<Conference room theme management>
Next, a conference room theme management registration screen for managing conference room themes by the system administrator will be described with reference to the drawings. FIG. 9 is a diagram illustrating an example of a conference room theme management screen. As shown in FIG. 9, when performing conference room theme management registration at the time of system administrator authority, schedule registration is performed based on the conference room theme management screen 100.

  First, all the communities existing at the present time are displayed in the community selection area 101 of the conference room theme management form 100. The system administrator selects a community for registering a reservation from the community selection area 101. Next, after selecting a community, the theme setting area 102 sets the theme of the conference room related to the selected community. Specifically, the theme name and the display order (priority) of the conference room theme are set.

  Next, after the above setting is completed, by selecting the registration button 103, a conference room theme is set, and the theme is displayed in the conference room theme list display area 104.

  In the conference room theme list display area 104, each theme for each conference room for each community is displayed. Specifically, “display order”, “theme name”, “internal code”, and “processing” for each community are displayed. Here, “internal CODE” is a number assigned when the registration button 103 is selected.

  If the theme of the conference room is to be corrected or deleted, it can be easily set by selecting a processing button 105 such as a “correct” button or a “delete” button. Here, the set contents are accumulated in the DB 40.

  By using the registration / management screen for the system administrator as described above, it is possible to easily generate a community with system management authority. Furthermore, when a member changes personnel or retires, the manager or the like can be urged to change by displaying an alert on the person to be transferred.

<Community management>
Next, an example of a screen for a user having the authority of a community manager and a general user will be described with reference to the drawings.

  FIG. 10 is a diagram illustrating an example of the top page screen of the community manager. The top page screen 110 shown in FIG. 10 has a menu display area 111, a community information display area 112, and a related information display area 113. Various items are displayed in the display area 111 based on community conditions corresponding to the user's authority. By selecting an item for which the top page is displayed on the surface 110 for each community user or general user, it is possible to transition to a corresponding screen.

  Further, the community information display area 112 displays the community name, administrator, community activity content, etc. set in FIG. Further, the related information display area 113 displays the latest information on the bulletin board, the schedule list, and the like for the community. For example, in FIG. 10, a schedule for the next five days that is already scheduled is displayed. By displaying the related information display area 113 on the top page screen 110 in this way, the user can quickly grasp the changed information.

<Member List & Email Settings>
Next, an example of a member list and a mail setting screen for users having the authority of community managers and general users will be described with reference to the drawings. FIG. 11 is a diagram illustrating an example of a member list and an email setting screen. The member list and mail setting screen 120 shown in FIG. 11 is roughly divided into a mail setting area 121 and a member list display area 122.

  The mail setting area 121 selects a destination from the members displayed in the member list display area 122. The mail setting area 121 sets a sender (mail address) based on the user information input at the time of authentication by the authentication means 31. Specifically, the mail title and message are input.

  The member list display screen 122 can display members corresponding to the community for each category such as “secretariat” and “responsible person”. At this time, since a check box 123 is provided for each member in order to set the sender of the mail, by checking the box, the mail address is received from the DB 40, set as the destination, and output. Note that all members may be checked in advance, and the destination may be set by removing the check from there. Further, by selecting the send button 124, the mail is transmitted to the checked target member.

<Member registration>
Next, a member registration screen example for a user having the authority of a community manager will be described with reference to the drawings. FIG. 12 is a diagram illustrating an example of a member registration screen in the community administrator. A member registration screen 130 shown in FIG. 12 is used to register, modify, and delete a new member for the community. Specifically, it can be roughly divided into a member registration area 131 and a community member list display area 132.

  The member registration area 131 includes an employee number that is a type for identifying a member, a member category (classification), and an administrator classification for setting whether the member is an administrator. After the setting is completed, the set content is displayed in the community member list display area 132 by selecting the registration button 133.

  In addition, as shown in FIG. 6 described above, the community member list display area 132 includes items “employee number”, “role”, “affiliation”, “name”, “name” for each category of the community. Processing ".

  Here, when there is a change in the member affiliation due to personnel changes or the like, personnel change information is displayed, an alert or the like is displayed to the administrator, and an easy-to-manage screen is provided to the community administrator. In other words, as shown in FIG. 6, when there is a change in affiliation, the alert is changed. Specifically, the community administrator can set the “Modify” button, “Delete” provided in “Process”. By selecting the processing button 134 consisting of the “” button, the setting of the target member is changed. For example, even if the affiliation is changed, there is a case where the business before moving is continued. In this case, the community administrator selects the “Modify” button on the user terminal 12 to change the affiliation. It will be included in community members.

<Category management>
Next, the category management screen will be described with reference to the drawings. FIG. 13 is a diagram illustrating an example of a category management screen. The category management setting screen 140 shown in FIG. 13 is roughly divided into a category setting area 141 and a category display area 142. The category setting area 141 sets a category name and display order (priority). After setting, the category is displayed in the category display area 142 by selecting the registration button 143. When the set category is changed, it is changed or deleted by a processing button 144 such as a “modify” button or a “delete” button.

<Bulletin board registration>
Next, an example of a bulletin board registration screen for users having the authority of community managers and general users will be described with reference to the drawings.

  FIG. 14 is a diagram illustrating an example of a bulletin board registration screen. The bulletin board registration screen 150 shown in FIG. 14 sets the posting period, title, contents, and attached file in the bulletin board registration setting area 151. Further, the publisher can be acquired by the user information by the authentication means 31.

  Further, after the setting is completed, the setting is registered in the DB 40 by selecting the registration button 152. Further, by displaying the list of bulletin boards on the top page shown in FIG. 10 described above, the user can quickly grasp the information on the bulletin board.

<Register library>
Next, an example of a library registration screen for users having the authority of community managers and general users will be described with reference to the drawings.

  FIG. 15 is a diagram illustrating an example of a library registration screen. The library registration screen 160 shown in FIG. 15 sets category 1, category 3, title, content, and attached file in the library registration setting area 161. Further, the publisher can be acquired by the user information by the authentication means 31. After the setting is completed, the setting is registered in the DB 40 by selecting the posting button 162. The list of library registrations is displayed as shown in FIG. FIG. 16 is a diagram illustrating an example of a library list screen.

  As shown in FIG. 16, the library list screen 170 displays the information registered in the library for each library in the latest order. Thereby, the community manager and the general user can easily acquire desired library information.

  By providing the screen as described above to the user terminal, it is possible to provide the user with a community place that is easy to use with high accuracy. In particular, in member management, the latest employee information can be acquired by referring to the employee master 13, and system management is performed by displaying an alert when there is no personnel change in the acquired employee information. And a community manager can be provided with high-precision and rapid processing.

  In the present invention, the screen provided from the community server 11 to the user terminal 12 includes related link display and the like in addition to the above.

  As described above, the community server 11 can be controlled by a dedicated device configuration, but generates an execution program that can cause a computer to execute each function as described above, for example, a general-purpose personal computer. By installing a program on a workstation or the like, community generation and management in the present invention can be realized.

  Next, a processing procedure in the execution program will be described using a flowchart. The following processing procedure will be described in particular with respect to the community member display in the community server 11 of the present invention.

<Member display processing procedure>
FIG. 17 is a flowchart illustrating an example of the member display processing procedure. First, when there is an access request from the user terminal 12 to the community server 11, an authentication process is performed (S01). As for the authentication process of S01, the input user ID (employee number) and password are compared with the user information (member information) stored in the DB 40 in the community server and match. Will output that information. In S01, if authentication is not possible, after allowing the re-input for a preset number of times, if the input content does not match the user information, processing such as rejection of use is performed.

  If the authentication is successful in S01, the above-described various screens corresponding to the authority are displayed on the user terminal 12 (S02). In addition, when participating in a plurality of communities, a community selection screen can be displayed first, and the community selected by the user can be displayed. It is also possible to display a plurality of communities simultaneously in different frames on a web browser, different screens, or the like.

  Next, in community generation, management, and use, when a screen that requires member display such as member list display is specified (S03), the accessing user has system authority or community administrator authority. It is judged whether it is a thing (S04).

  Here, when the authority is not the system administrator authority or the community administrator authority (NO in S04), only the members are displayed because they are general users (S05).

  If the system administrator authority or community administrator authority is determined in S04 (YES in S04), the employee master 13 connected via the communication network 14 is referred to (S05). The displayed member is collated (S06). In step S06, collation is performed based on the user identification information (employee number), and it is determined whether there is a change in affiliation or name (S07). If there is no change (NO in S07), the corresponding member information is output (S08). If the affiliation or the like is changed (YES in S07), the alert display as described above is performed on the corresponding member and displayed on the screen (S09).

  As a result, the system administrator or community administrator can manage members easily, quickly, and with high accuracy. In addition, member management can be realized at low cost without requiring a special device configuration. Moreover, community generation and management can be easily realized by installing the program.

  As described above, according to the present invention, it is possible to easily generate a community and to manage members with high accuracy. In this way, by introducing this system, for example, every time a request such as “I want to open a department homepage” or “I want to share information among project members” occurs, a series of steps from preparation to development and start of use Work can be done quickly.

  For end users who want to share information via the Web, etc., but cannot develop into a concrete image, open up a community in the form of “trial” and provide an essentially necessary system at no cost. be able to.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications, within the scope of the gist of the present invention described in the claims, It can be changed.

It is a schematic structural example of the community management system in this invention. It is a figure which shows an example of the hardware constitutions which can implement | achieve the production | generation / management of community, and utilization in this invention. It is a figure which shows an example of a function structure of the community server 11 in this embodiment. It is a figure for demonstrating the data example of the database and employee master in this invention. It is a figure which shows an example of the setting registration screen of a community. It is a figure of an example which shows the example of a member registration screen at the time of system administrator authority. It is a figure which shows an example of a bulletin board registration screen. It is a figure which shows an example of a schedule registration screen. It is a figure which shows an example of a meeting room theme management screen. It is a figure which shows an example of the top page screen of a community administrator. It is a figure which shows an example of a member list and an email setting screen. It is a figure which shows an example of the member registration screen in a community administrator. It is a figure which shows an example of a category management screen. It is a figure which shows an example of a bulletin board registration screen. It is a figure which shows an example of a library registration screen. It is a figure which shows an example of a library list screen. It is a flowchart of an example which shows a member display processing procedure.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Community management system 11 Community server 12 User terminal 13 Employee master 14 Communication network 21 Input device 22 Output device 23 Drive device 24 Auxiliary storage device 25 Memory device 26 CPU
27 Network Connection Device 28 Recording Medium 31 Authentication Unit 32 Community Management Unit 33 Member Management Unit 34 Mail Generation Unit 35 Bulletin Board Management Unit 36 Schedule Management Unit 37 Library Management Unit 38 Related Link Management Unit 39 Conference Room Management Unit 40 Database (DB)
50 Community Management Screen 70 Member Registration Screen 80,150 Bulletin Board Registration Screen 90 Schedule Registration Screen 100 Meeting Room Theme Management Screen 110 Top Page Screen 120 Member List and Email Setting Screen 130 Member Registration Screen 140 Category Management Setting Screen 160 Library Registration Screen 170 Library List screen

Claims (8)

In a community management system comprising a user terminal for a user to use a community via a communication network and a community server that generates and manages a community according to a request from the user terminal,
The community server includes an authentication unit for authenticating a user who uses the user terminal;
A community management means for generating a screen for generating or managing a community according to the authority of user information obtained by the authentication means, and displaying the screen on the user terminal;
Member management means for managing members belonging to the community generated by the community management means;
A community management system comprising storage means for storing various information obtained by the community management means and the member management means. The member management means includes
If there is different information by comparing employee information obtained by referring to an employee master connected to the communication network and member information stored in the storage means, the authority of the user information 2. The community management system according to claim 1, wherein the target member information is displayed as an alert on the user terminal. The community management means includes
3. The community management system according to claim 1, wherein when setting members in the community, grouping is performed for each category, and whether or not an e-mail is transmitted is set for each grouped member. . In a community server that acquires a request from a user terminal via a communication network and generates and manages a community from the acquired request content,
An authentication means for authenticating a user using the user terminal;
A community management means for generating a screen for generating or managing a community according to the authority of user information obtained by the authentication means, and displaying the screen on the user terminal;
Member management means for managing members belonging to the community generated by the community management means;
A community server comprising storage means for storing various information obtained by the community management means and the member management means. The member management means includes
If there is different information by comparing employee information obtained by referring to an employee master connected to the communication network and member information stored in the storage means, the authority of the user information 5. The community server according to claim 4, wherein the target member information is displayed as an alert on the user terminal. In a community management method for acquiring a request from a user terminal via a communication network and generating and managing a community from the acquired request content,
An authentication stage for authenticating a user using the user terminal;
A community management step of generating a screen for generating or managing a community according to the authority of user information obtained by the authentication step, and displaying the screen on the user terminal;
A member management stage for managing members belonging to the community generated by the community management stage;
A community management method comprising: an accumulation stage for accumulating various information obtained by the community management stage and the member management stage. The member management stage includes
When there is different information by comparing employee information obtained by referring to an employee master connected to the communication network and member information accumulated by the accumulation step, the user information is authorized. 7. The community management method according to claim 6, wherein the target member information is displayed as an alert on the user terminal based on the alert. In a community management program for acquiring a request from a user terminal via a communication network and causing a computer to execute processing for generating and managing a community from the acquired request content,
An authentication process for authenticating a user who uses the user terminal;
A community management process for generating a screen for generating or managing a community according to the authority of user information obtained by the authentication step, and displaying the screen on the user terminal;
Employee information obtained by referring to an employee master connected to the communication network is compared with member information stored in advance, and when different information exists, based on the authority of the user information A community management program for causing a computer to execute a member management process for displaying an alert on target member information on the user terminal.

Images