JP2002203039A - Server for recruitment management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform recruitment management in a unified and efficient manner on the premise of previous registration of personal information on a job seeker, particular a student with a job seeker master. SOLUTION: A hosting site is provided with a Web server 1 for enterprise, a Web server 2 for student, a mail server 3 and a database server 4. A person in charge of an enterprise or a business agent can gets access, from clients 5, 6 through the Internet, to the Web server 1 for enterprise to perform viewing the list of the number of the registration, application status and explanatory meeting/interview status, narrowed-down retrieval, the setting of explanatory meeting/interview, the setting of acceptance condition thereof, e-mail management or the like. A student can get access, from a student client 7, to the Web server 2 for student to apply for the explanatory meeting/interview.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a server in an employment management system and an employment management method using the server.

[0002]

[Background Art] For job seekers, especially students who are expected to graduate, job seekers (companies or individuals engaged in recruitment activities) hold company briefings and discuss the company's business contents, occupations, working conditions, welfare facilities, etc. Explain sufficiently. Subsequently, an interview is conducted. Interviews often consist of multiple stages, such as primary interviews, secondary interviews, and executive interviews. The recruiter evaluates the recruiter in a series of these processes (selection process), and finally determines a successful candidate.

[0003] In a series of processes from such a company guide to final recruitment, a recruiter handles an enormous amount of data. For example, company briefing sessions will be held in large numbers at different times and locations, and many large companies have many applicants for briefing sessions. First, we need to know how many applicants there are. Personal information about each applicant (job seeker) must also be managed.
It is also necessary to keep track of the progress of each candidate in the selection process. Otherwise, it will not be possible to schedule interviews or provide guidance for interviews. E-mail inquiries may also be received from job seekers.

In the past, these recruitment management-related business processes were, of course, performed using a computer, but were individual and inadequate. For example, notices about company briefings (schedules, venues, reception conditions, etc.) are posted on the company information website, and applications to the website can be made. Since anyone can apply, the recruiter must determine whether or not the applicant is in the range that the company wants (eg, college graduation, science, etc.). There may be letters, postcards and telephone applications. The recruiter creates a list of applicants for the company briefing session on the computer. At the next stage of the interview, a list of applicants for the interview will be created separately from the list of applicants for the company briefing. Such a condition is inefficient.

[0005]

DISCLOSURE OF THE INVENTION An object of the present invention is to enable uniform and efficient recruitment management on the premise that personal information of a job applicant is registered in a job applicant information master in advance.

An object of the present invention is to make it possible to immediately grasp the status of registered job seekers (a quick reference table of the number of cases such as registration status and selection process status).

Another object of the present invention is to make it possible to immediately grasp the status of application for a briefing session or interview (status table).

It is another object of the present invention to provide a search condition from the viewpoint of job seeker information and to narrow down (search) to form a group of job seekers.

SUMMARY OF THE INVENTION It is an object of the present invention to form a group based not only on narrowing down, but also on the basis of the number-of-cases table and situation table described above.

A further object of the present invention is to enable management based on groups formed.

As group management, it is possible to store a group, display a list of applicable persons, narrow down processing, send an e-mail, and combine groups.

Still another object of the present invention is to make it possible to easily create a new group from two or more groups.

Another object of the present invention is to enable effective management of electronic mail addressed to a job seeker and electronic mail from a job seeker.

According to the present invention, the status of a large number of sent and received mails can be understood at a glance.

A further object of the present invention is to enable a job seeker to make an application for a briefing session or an interview using a network, and to check whether the application satisfies the acceptance conditions. That is, only job seekers who meet the reception conditions can apply.

According to the present invention, the above-mentioned reception conditions can be set and saved.

According to the present invention, it is possible to set a venue for a briefing or an interview, and a date and time. This is necessary for the situation table, application, etc. described above.

The server according to the invention is, in the most preferred embodiment, a web server (server means server computer). Through the Internet, not only job seekers such as students, but also recruiters in the company can access the server from their own clients (meaning client computers).

The server is provided with a job seeker information master as the most basic information. This job seeker information master stores at least registration information including the identification code, name, address, and educational background of the job seeker, and selection information including the selection process.

In a preferred embodiment, the job seeker information master further includes, as registration information, the job seeker's desired information regarding the occupation or work location.

Further, a mail address is stored in the job seeker information master to cope with the electronic mail. The password used by the registered job seeker to access the server is also registered in the job seeker information master.

The above-mentioned educational background includes a school name, a department, a department, and the like. Further, for convenience of processing, a school division, a science division, and the like are also stored. The selection information includes evaluation data in addition to the selection process. In addition, an identification code indicating a briefing session / interview where the selection was performed is also stored as necessary. Briefing / interview is the meaning of briefing and / or interview, and should be understood as a concept that includes only briefings, interviews only, both explanations and interviews, and also includes examinations (such as written examinations). The job applicant information master can also store data on qualifications, abilities, and the like.

A server according to the present invention, which performs a quick look-up process, comprises a job applicant information master storing at least registration information including an identification code, a name, an address and an educational background of the job applicant, and selection information including a selection process. For each combination of the condition that determines the range for at least one item of the registration information in the master and the type of the number table, the number of applicable persons stored in the job applicant information master is searched in advance. A quick-reference table data table that stores the results as numerical values in the cells of the number-of-counts quick-reference table for each combination of the above-mentioned conditions and types. Means for transmitting data for displaying the number-of-counts table reference condition selection screen on the client, and the number-of-counts table reference condition selection screen And means for transmitting data for displaying the number-of-accounts quick-view screen to the client based on the data of the corresponding quick-reference table data table in response to the specification of the condition and the type input in the above. is there.

The above conditions include, for example, a section related to the address in the registration information and a section related to the educational background. The east-west section and the cultural section in the embodiment correspond to each other.

The type of the above-mentioned number reference table is, for example, as follows.
Includes educational background classification, address classification and selection process classification.
The table of the number of cases by student, the table of the number of cases by prefecture, and the table of the number of cases by the selection process in the embodiment correspond to these.

As described above, when the job seeker information master further includes the job seeker's desired information regarding the occupation or work location as the registration information, the type of the number reference table includes the desired category. It is a table of the number of cases according to a questionnaire result in an example.

According to this invention, the combination of the condition and the type is searched in advance (for example, every night) and the result is recorded in the quick-reference table data table. If a condition and a type are designated in the client, a desired number table can be obtained immediately. The person in charge can grasp the registration status and the selection status of job seekers by using the number reference table.

Since the status of registration in the job applicant information master changes every moment, in response to an update request from a client,
It is preferable that the server further includes means for updating the quick look-up table data table based on the information of the latest job seeker information master.

Individual information can also be obtained from the number table.

For example, the server further searches for a job applicant corresponding to the specified cell in the job applicant information master in response to designation of any cell of the count reference table displayed on the client. Forming a group of applicable persons and creating a list of job applicants belonging to the group, and means for transmitting data for displaying the applicable person list screen including the created list to the client ing. It is possible to know a group of job seekers who satisfy a predetermined condition in the number-of-cases table of a specific type.

The present invention further provides a server capable of outputting a status table showing the status of the applicant for the briefing session / interview (with or without the function of outputting the above-mentioned number reference table). Is provided.

This server provides a briefing session / interview table in which data relating to briefing sessions / interviews for job seekers is set, and corresponds to the identification code of the briefing sessions / interviews. According to the selection of the briefing session / interview range at the client, a means for transmitting data for displaying the screen for selecting the range of the briefing session / interview to the client, and the client to select the range of the briefing session / interview Make a list of the briefings / interviews that belong to that range,
There is provided a means for transmitting data for causing the client to display an explanatory meeting / interview management screen including this list. The scope of the briefing / interview means the range of the venue for the briefing / interview (East Japan, West Japan, etc.), the scope of the audience for the briefing / interview (science, humanities, etc.) Association /
Whether it is an interview.

The recruitment manager of the company can easily know the status of the briefing / interview.

Also in this situation table, it is possible to further draw out the specific contents of the job seeker applying for a specific briefing session / interview. That is, the server responds to the designation of the briefing session / interview in the list displayed on the briefing session / interview management screen and, in response, specifies the job applicant who has applied for the designated briefing session / interview. Means for forming a group of applicants that are read from the applicant table and obtained, and for creating a list of applicants belonging to the group, and data for causing the client to display a corresponding person list screen including the created list Is further provided.

It is also possible to see information on a specific job seeker in the applicable person list obtained from the number table or the situation table. The server further includes means for reading the information of the designated job seeker from the job seeker information master in response to the designation of the job seeker in the list on the applicable person list screen, and transmitting the information in a form that can be displayed on the client. In addition. The client displays the job seeker's profile screen. The agent can also modify the job seeker's information (for example, add a selection rating).

As described above, it is possible to form a group that satisfies a specific condition based on the table of the number of cases or the situation table. The server further includes means for giving a group name to the group formed in this way and creating a group table for storing data on job seekers constituting the group. Here, the group table is a concept including the group management table and the group registered student table in the embodiment, and should be interpreted as corresponding to one or both depending on the content of the processing.

One of the central features of the present invention is that job seekers registered in the job seeker information master can be grouped by giving conditions, and various processes can be executed in groups.

The groups are most typically formed by a refinement process. A server having a narrow-down processing function according to the present invention provides a job applicant information master storing at least registration information including an identification code, a name, an address and an educational background, and selection information including a selection process, and information in a job applicant information master. Means for transmitting data for displaying a narrowing-down screen for prompting selection or designation over a plurality of items to the client; one or more search conditions defined by one or more items selected or designated on the narrowing-down screen In response to the transmission of the narrowing-down condition including the narrowing-down condition, the searching unit searches the job-seeker information master according to the narrowing-down condition, forms a group of job-seekers satisfying the narrowing-down condition, and outputs the result obtained by the search to the client. And means for creating and transmitting a screen to be displayed. The term narrowing condition is used to mean that search conditions are combined.

When the job seeker information master further includes the job seeker's request regarding the occupation or work location as the registration information, the item relating to the job seeker's request can be selected or specified on the narrowing-down screen.

The search results displayed on the client are, in one embodiment, the number of persons or a list of persons.

The server further includes means for giving a group name to the formed group and creating a group table for storing data on job seekers constituting the group. In a preferred embodiment, the group table creating means stores, in the group table, a use category indicating a use assigned to the formed group. By inputting a use, a group suitable for the use can be easily found.

In another preferred embodiment, the means for creating a group table stores data representing a group management type in the group table. In one embodiment, the data representing the group management type includes data representing the variable group. In this case, the job recruiter information master is searched again according to the narrowing condition used to form the group for the group in which the data representing the variable group is stored in the group table, and the group is determined by the job seeker who satisfies the narrowing condition. It is desirable that a group updating means for updating be further provided. The group update processing is executed each time a command to that effect is issued or periodically. Even if the information of the job seeker changes, a group that matches the change and satisfies a specific narrowing condition can be quickly obtained when necessary.

In a further preferred embodiment, one or more job seekers can collectively register specific data in the job seeker information master. The server capable of collective data registration includes a first means for prompting selection of a group to be subjected to collective data registration, a second means for prompting selection of an item for which collective data registration is to be performed, and referring to the group table, A means for creating and displaying a list of job seekers belonging to the selected group, and for all the job seekers selected from the displayed list, the job seeker information master of the job seeker has information on the above-mentioned selected items. A means for registering data is provided. Here, the first means and the second means are preferably realized by means for transmitting a screen for prompting group selection to the client and means for transmitting a screen for prompting selection of an item to the client, respectively. When a list of job seekers belonging to the selected group is displayed on the client, the user selects the job seekers to be registered collectively on the screen, so the selection result is sent to the server and sent to the job seeker information master. Is registered. In this way, the same data can be registered uniformly for a plurality of job seekers.

More preferably, in response to designation of the job seeker in the list of applicable persons, information on the designated job seeker is read from the job seeker information master and can be displayed on the client (profile screen). The server is provided with a means for transmitting the data.

If the group to be narrowed down has already been determined, the search means executes a search within the range of job seekers belonging to the already determined group. This depends on the screen transition at the client.

Preferably, the server further comprises means for creating a narrowing-down condition table for storing the one or more search conditions together with their identification codes. The narrowing conditions are saved.

More preferably, the server further comprises means for transmitting data for displaying a screen for inputting a narrowing condition name to the client. The narrowing condition table creating means stores the narrowing condition name transmitted from the client in the narrowing condition table. In saving the filtering conditions, the person in charge can give an arbitrary name.

In one embodiment, the narrowing-down condition table contains
The identification code of the group formed by the search according to the narrowing condition is stored. The narrowing condition and the group are linked.

In still another embodiment, data on search targets (all registered job seekers, persons belonging to a specific group, etc.) are stored in the narrowing-down condition table.

In a preferred embodiment of the present invention,
A recruiter team table is provided for associating one or more narrowing conditions used to form a group with recruiter teams allowed to access a group satisfying the narrowing condition. The recruiter team is, in one embodiment, identified by a major classification and a minor classification. More preferably, a person in charge table for storing information on persons in charge belonging to the recruiter team is further provided. The recruiter team is, for example, a team of recruiters in one company, and can be accessed by each team (for example, they can browse and modify data). One or more groups of job seekers are defined using the refinement criteria. It is possible to manage job seekers suitable for each recruiter team.

In a further preferred embodiment, in response to a request from a client, a list of narrowing condition names stored in a narrowing condition table is created, and data for displaying the list to the client is transmitted. In response to the selection of one of the narrowing condition names from the narrowing condition name list displayed in, the search condition of the corresponding narrowing condition table is read, and data for displaying the narrowing screen including the search condition to the client. Is provided in the server. The saved search conditions can be called up and used.

It is also possible to see a group list formed using the narrowing conditions. The server further includes means for creating a list of groups stored in the group table in response to a request from the client, and transmitting data for displaying the group list screen in the client.

It is also possible to specify a specific group in this group list and to know the members of that group. Means for, in response to the group being specified on the group list screen, generating a list of job seekers constituting the corresponding group and transmitting screen data for displaying the list to the client; Is further provided.

A new group can be created by performing a logical operation on such two or more groups. This is called group combination processing.

The server having the group combination processing function includes an area for specifying a plurality of groups and an area for specifying the type of logical operation, including displaying a list of group names in which a group table is created. Means for transmitting, to the client, data for displaying a group combination screen having a group combination screen, and in response to the data indicating the plurality of specified groups and the data indicating the type of the logical operation being transmitted from the client, Performs the specified logical operation on job seekers belonging to multiple groups
Means are provided for forming a new group based on the result of the logical operation, giving a group name to the group, and creating a new group table. A group formed by group combination is stored with a group name.

As described above, a group of job seekers can be created from a quick reference table, a situation table, a narrowing process, and a group combination. The group thus formed is used for various purposes.
One of them is the display of a list of job seekers belonging to the group as described above, and from this list, it is possible to see the profile of an individual. Also, the group is used to define the range in which a briefing session / interview can be applied, as described later, and also to define the range to be narrowed down. Send e-mail,
As will be described later, it can be performed in groups.

The server has the following configuration for realizing mail transmission in groups. That is, the mail address of the job seeker is registered in the job seeker information master. The server sends data to the client to display a mail creation screen including a destination area including a list of group names in which the above group table is created, a subject input area, and an email body input area. In response to the transmission of the mail creation screen in which the means and the group name as the transmission destination, the subject and the text of the mail have been input, the job applicant who belongs to the above group is referred by referring to the above group table and job applicant information master Means are provided for creating and transmitting an e-mail including a mail address for each job seeker belonging to the group.

A server having a mail management function according to the present invention stores data relating to e-mail transmitted for each individual subject or for each group including a plurality of subjects. It stores at least one of the identification code of the subject as the transmission destination and the mail address of the transmission destination, a transmission mail table storing the subject, the transmission date and time, and the text, and data relating to the received e-mail. Incoming mail ID, sender's mail address, outgoing mail ID of outgoing mail corresponding to the received mail, unknown classification data indicating whether there is a corresponding outgoing mail, identification code of subject of sender, subject, receiving Received mail table that stores the date and time and text, and the above-mentioned transmission Outgoing mail including the subject of sent mail, sent date and time, data related to the destination, the number of sent mails, and the number of replies indicating the number of received mails corresponding to the sent mail, with reference to the send mail table and the received mail table. There is provided a means for creating a list, and means for transmitting data for displaying the sent mail list on the client. When handling transmission for each group, the transmission mail table may store the number of transmissions in addition to the group ID. It is preferable to provide a group table that stores identification codes indicating the subjects belonging to the group corresponding to the group ID.

From the sent mail list, the status of sent and received mail can be grasped at once. In particular, since data relating to the received mail corresponding to the transmitted mail is also displayed, the relationship between the sent and received mail can be easily understood. If necessary, add the unread number to the list, which indicates the number of received mail that has not been read.

The server associates one or a plurality of received mails sent from the mail server with the received mails and the transmitted mails to create the received mail table, and compares the association result with the transmitted mail ID and the unknown mail. There is provided means for storing data relating to the received mail in the received mail table, expressed as data of the section.

Each outgoing mail,
You can also access the contents of the incoming mail. That is, in response to a request from a client indicating that a specific outgoing mail has been specified in the outgoing mail list, the server can read data of the specified outgoing mail from the outgoing mail table and display the data on the client. Means for transmitting in form. In response to a request from the client indicating that the contents of the received mail corresponding to the specific sent mail should be acquired in the sent mail list, the server reads the data of the received mail from the received mail table and reads the data of the received mail. There is provided a means for transmitting in a form that can be displayed on a computer.

This mail management server also has a group transmission function. In other words, the server displays a subject information master that stores at least the mail address of the subject, a group table for each group that stores the subjects belonging to the group along with the group ID, and a list of group names for which the group table is created. Means for sending data to the client to display a mail creation screen having a destination area including a subject, a subject input area, and an email body input area, and a group name as a destination,
In response to the transmission of the mail creation screen in which the subject and the text of the mail are entered, the e-mail including the e-mail address of the subject belonging to the group belongs to the group by referring to the group table and the subject information master. There is a means for creating and transmitting for each subject.

A mail addressed to an individual can be created and transmitted. The server is a subject information master that stores at least the email address of the subject, an area for inputting the destination,
A means for sending data to the client to display an email composition screen with an area for entering the subject and an area for entering the email text, and responding to the transmission of the email creation screen with the destination, subject, and email text entered Means for creating and transmitting an e-mail including the mail address of the target person by referring to the target person information master.

With the above-described group transmission or individual transmission function, it is possible to call for a job seeker to apply for a briefing session / interview. The server address (U
RL). The job seeker accesses the server using the URL and applies for a briefing / interview.

The job seeker (and the person in charge of the company)
The server that can apply for an interview has the following configuration.

The server is provided with a briefing session / interview table, a briefing session / interview table storing data representing the briefing session / interview identification code, the venue / date and time of the briefing session / interview, the selection process, the capacity and the range of applicants who can apply. A briefing session / interview applicant table that stores the identification code of the job seeker who applied for the briefing session / interview corresponding to the interview identification code, and access to the briefing session / interview application including the identification code of the job seeker from the client In response, referring to the data indicating the range of applicants who can apply in the briefing / interview table, means for creating a list of briefings / interviews that can be applied by the job seeker who accessed the application, the created list Means for transmitting data for displaying a briefing session / interview application screen including
In addition, in response to the client sending a notice indicating that the application was made by specifying the briefing session / interview on the briefing session / interview application screen, the relevant briefing session / interview applicant table is displayed in the corresponding briefing session / interview applicant table. Means for writing an identification code is provided.

When a job seeker has access, only the briefing session / interview that the job seeker can apply for is guided, so that no confusion occurs in both the job seeker and the job seeker. In addition, it is possible to efficiently execute a briefing session / interview application process.

Preferably, upon receiving a notice of the application from the client, it is checked whether or not the application of the applied job seeker is approved, and if so, the identification code of the job seeker is set to the briefing session / interview applicant table. Write to. If not, the client may be notified.

More preferably, the briefing session / interview table also includes data relating to briefing sessions / interviews that do not limit the range of target persons who can apply, and these briefing sessions that limit the range of target persons who can apply. Add the interview / interview to the list above.

The range of applicants who can apply can be defined by the above-mentioned group or by the receiving conditions (similar to the above-described narrowing conditions). Further, the number of persons may be limited for a predetermined item in the reception conditions.

The server having the function of setting and storing the reception conditions transmits data for displaying the reception condition selection screen for prompting the client to select or specify a plurality of items of the information in the job applicant information master to the client. means,
In response to the transmission of the reception condition including one or more conditions specified by one or more items selected or specified on the reception condition selection screen, the reception condition is made to correspond to the reception condition name. A means for creating a reception condition table is provided.

The briefing / interview can be set in the corporate client. For this purpose, the server sends data to the client to display a briefing / interview setting screen for inputting data indicating the name of the briefing / interview, venue, date and time, selection process, capacity, and the range of applicants who can apply. And a means for responding to the reception of the data input on the briefing session / interview setting screen from the client and using the data to create a briefing session / interview table.

The above-mentioned number-of-views table processing, status table processing, narrowing processing, narrowing condition saving processing, group management processing, group joining processing, mail management processing, mail transmission processing, briefing / interview application processing, reception condition table creation processing One server may have functions such as a briefing session / interview setting process, or a server having a function of only individual processes or a combination of several processes may be considered. It is preferable to have a common database.

The present invention also provides a recruitment management method, a group management method, a mail management method, and a medium recording a program for causing the server to execute these methods, which are executed by all the servers described above.

[0075]

DESCRIPTION OF THE PREFERRED EMBODIMENTS (1) Overall Configuration of System FIG. 1 shows the overall configuration of an employment management system.

In this embodiment, a recruiter (a company or an individual engaged in recruitment activities) is simply expressed as a "company," and a job seeker (a person seeking a job or a person who has applied for a job in a company:
Applicant) is represented by "student".

The main part of the recruitment management system is a hosting site, which includes a corporate web server (computer) 1 and a student web server (computer).
2, a mail server (computer) 3 and a plurality of database servers (computers) (referred to as DB servers) 4 are provided. These servers 1, 2, 3, and 4 are interconnected by a LAN or the like. As will be described later, a corporate web server 1 and a student web server 2
Have different functions (work), but the functions of these servers 1 and 2 can also be realized by one server (computer). This one server may have the function of the mail server 3. A plurality of DB servers 4 can also be realized by one server (database server computer). It is also possible to realize the functions of all servers 1, 2, 3, and 4 with one server (computer).

In the recruitment management system, companies using this system are registered in advance as members. These companies are provided with a client (computer) 5. Large companies are generally provided with a server (not shown). In the same company, one or more clients (computers) 5 are connected to a server by a LAN or the like, and a plurality of persons in charge
Can access the hosting site through the server. In a company without a server, the clerk accesses the hosting site from the client 5, usually through the server of the provider. When referring to a plurality of companies (four in FIG. 1), A,
B, C, and D codes are used.

A server (computer) and a client (computer) 6 are also provided at the agency that operates this recruitment management system on behalf of the personnel personnel of one or a plurality of companies.

The student has a client (computer) 7. Students access the hosting site from the client 7, typically through the provider's server. The clients 5, 6, and 7 are generally realized by a personal computer (PC) on which a web browser is installed.

The corporate, agency, and student clients 5, 6, and 7 access the hosting site corporate web server 1 or student web server 2 or mail server 3 through the Internet (or other network). Server can execute desired processing, and the result can be obtained as needed. Communication between these clients and a web server or a mail server is performed using an HTML format file.

Preferably, the corporate web server 1 and the student web server 2 have different URLs (addresses or domain names). However, these web servers may have the same domain name and different sub-domain names.

FIG. 2 shows the database 8 of the DB server 4.
The outline of the contents is shown. Although each of the plurality of DB servers 4 has a database, FIG. 2 shows the contents of these databases collectively, and each DB server 4 assigns a part of the contents of FIG. Please understand that it is held as a database. This database 8 is used for the corporate web server 1 and the student web server 2
Access.

The database 8 is provided with a company information master (file) (or a company information table).
The company information master registers a company as a member who can use the recruitment management system, and holds information on the company. The information held in the company information master includes a company ID, a company name, an address of the company, an e-mail address of the company, a URL of a server of the company, and a person in charge of the company assigned to the company. There is a sign-on user name and a sign-on password used to access the (corporate web server) 1 and other information (for example, a mail update date and time described later).

The database 8 is further provided with a sub database 9 for each member company. The client 5 of each company can access only the sub-database 9 assigned to the company (through the enterprise web server 1), or can only perform processing using the sub-database 9 assigned to the company. 1 cannot be executed, and cannot access the sub-database of another company. Of course, each company can only obtain the processing result using the data of the sub-database 9 assigned to that company, and cannot obtain the processing result based on the data of the sub-database 9 of another company. Such access control and control of the processing of the sub-database 9 are performed by the corporate web server 1 based on the identification of the member company by the sign-on user name and the sign-on password sent from the corporate client. The agency client 6 accesses the hosting site (sub database 9) on behalf of the member company.

As described later, students apply for recruitment of one or more companies through various reception media. Such information about the student is stored only in the sub-database 9 about the company to which the student applied.

The database 8 of the DB server 4 is independent of each other for each member company (it can be said that processing is also independent).
Since the sub-database 9 is provided, for both the member company and the student, it looks as if there is a company-specific hosting site (web server and mail server) and is handled as such.

The student web server 2 has a URL (address) for identifying a member company. For example, a company-specific code for each member company is set as a subdomain name of the student web server 2. Student Client 7
Accesses the student web server 2 using the address including the subdomain name. As a result, the student accesses the student web server 2 with an awareness of accessing the server of the company to which he / she applied. Students and corporations can have a one-to-one correspondence through this recruitment management system.
The student web server 2 also performs processing using only the sub-database 9 on the accessed (specified) company when the student client 7 specifies a company and accesses (with a subdomain name). Will be.

(2) Contents of Database FIGS. 3 to 8 show details of the contents of the sub-database 8 for each company.

The most important information is information on students who applied for the company, which is stored in the student information master shown in FIG. FIG. 3 shows the main student information.

The information stored in the student information master includes information (registration information) written when registering the student information,
The information can be categorized as information (selection information) that is recorded or updated during the selection process for the employment of registered students.

[0092] The registration information includes the following.

Student ID This is the student identification number, and is assigned so that the DB server 4 (or the web server 1 or 2) of the hosting site does not overlap.

Name, etc. This includes the last name, first name, their reading, gender, date of birth, and the like.

Contact information (current address) Information necessary for contacting the current address, e-mail address,
There are a postal code, a prefecture ID (to be described later), a prefecture, an address, a telephone number, and the like.

Contact information (homecoming destination) Information required for contacting the homecoming destination, such as a postal code, a prefecture ID, a prefecture, an address, and a telephone number.

School information Information on the school where the student is enrolled (expected to graduate) or graduated from the school, including school division (described later), school name, undergraduate (or graduate school), department (or major), And the like (to be described later).

Questionnaire Information A member company presents a questionnaire questionnaire to a student and indicates the result of the student's response to the questionnaire. The desired job type (for example, job type for each company such as general affairs, human resources, sales, research, development, etc.) , Desired workplaces (locations of headquarters, branch offices, branches, laboratories, sales offices, factories, etc., etc., depending on the company) and desired courses (general staff, general staff, etc.)

Reception media-related information Student information registered in the student information master is input through various media. The most typical thing is to access the student web server 2 from the student client 7 via the Internet and register (input information) (Internet). In some cases, student information already registered in a database of a system other than the recruitment management system is registered in the student information master of the recruitment management system (for example, from the agency client 6) (another database). Student calls member company, postcard,
When a member company is contacted by replying to direct mail (DM) or the like, the member company records the student information about the student and then registers it in the student information master from the company client 5 (telephone, postcard). , D
M). Such Internet, other databases, telephones, postcards, and DM are called reception media. The reception media-related information includes the type of reception media and the reception date and time. Since information about one student may be input through a plurality of media, the information can be stored for a plurality of reception media.

Qualifications, etc. Students' comments (free comments) (can be freely entered), qualifications, TOEIC score, TOEFL score, etc.

Registration Date Indicates the date when the student information was registered in this student information master.
It is automatically stored by the web server 1 or 2 or the DB server 4.

Password The password is used when a student accesses the web server 2 from the client 7, and is input by the student from the client 7 through the Internet.

The selection information includes the following.

Selection Process Information The purpose of the student to register his / her information (student information) in the student information master of a specific member company of this recruitment management system is as follows.
Ultimately, you have to hire the company. From the perspective of a company, registered students will be selected. The selection process represents the stage of selection for each company, and specifically includes a company briefing session (hereinafter simply referred to as a briefing session), a written test, a primary interview, a secondary interview, and an officer interview. The selection process name is a name given by the member company to identify these selection processes (stages). As mentioned above,
Hold briefings and interviews during the selection process. The same briefing session may be held in a different location (for example, Osaka, Tokyo, etc.) or for a different audience (national science, private science, national and public arts, etc.). The same is true for interviews. The briefing / interview ID distinguishes these briefings and interviews.
It is. The evaluation and evaluation comments were given to the student by the person in charge of the company during each selection process. These selection process names, briefing sessions / interview IDs, evaluations and evaluation comments are accumulated for each selection process.

Rejection Information In the course of the selection process, a student may voluntarily decline. The decline section indicates whether or not the decline has been made. The name of the selection process at the time of withdrawal indicates the selection stage that has progressed by the time of decline. The date of decline (decline date) is also recorded.

The registration of student information via the Internet, which is a typical reception medium, will be described.

The student accesses the student web server 2 of a specific company from his / her client 7. In response, the web server 2 sends data (HTML file) for displaying the registration screen to the student client 7. On the registration screen displayed on the student client 7, the student can enter the contact information (current address) (return home),
Enter school information, questionnaire information, qualifications, etc. in a form that answers the questionnaire. Also, the student enters a password.
These input data are transmitted from the student client 7 to the student web server 2 and registered in the student information master of the sub-database 9 of the corresponding company. The reception media-related information and the registration date are set by the web server 2 or the DB server 4. The student ID is also automatically assigned by the server 2 or 4 and registered in the student information master. The student ID is notified to the student client 7.

The student IDs are numbered so as not to be duplicated.
When a student ID is assigned, a duplicate check is performed, so that the same student is not registered twice in the student information master of one member company.

When the reception medium is other than the Internet, such as a postcard, the last name, first name, current address, telephone number, and school information are described on the postcard as essential information for application. Based on this information, the person in charge of the member company inputs student information from the company client 5. A student information master for the student is created based on the input student information. Student ID is assigned,
The date of registration is also recorded.

After that, the authentication information (including the student ID) is sent to the registered student by mail or e-mail by the person in charge of the hosting site. The student uses the received authentication information to access the student web server 2 from the client 7 via the Internet, inputs information not yet recorded in the student information master (for example, questionnaire information), and inputs a password. be able to. These input information will be additionally recorded in the student information master of the student.

FIGS. 4A to 4G show basic masters (files).

In the prefectural master of FIG. 4A, a prefectural ID, a prefectural name, and an east-west section are stored in association with each other. The east-west division is a code indicating which prefecture belongs to when Japan is divided into eastern and western Japan. The method of dividing into East Japan and West Japan may differ depending on the member company.

The school master in FIG. 4B stores a school ID, a school name, a national and public division, and a school division. The national public division indicates whether it is national, public, or private. The school division indicates a graduate school, a university, a junior college, a technical college, a high school, and other divisions.

The undergraduate master in FIG. 4C stores the undergraduate ID and the undergraduate name.

The desired job type masters shown in FIGS. 4D, 4E, and 4F
The desired work location master and the desired course master store information that is the basis for creating the above-described questionnaire information. A job code and a job name are stored in the desired job master as a pair. The desired work location master stores a work location code and a work location name in association with each other. The desired course master stores a course code and a course name in association with each other.

In the selection process master of FIG. 4G, a selection process code indicating a selection stage of a company and a selection process name are stored in association with each other.

FIGS. 5A and 5B show tables (files) holding data for group management.

In the number-of-items lookup table processing, narrowing-down processing, briefing session / interview status table processing, group combining processing, etc., which will be described later,
A condition or range is specified, and students who meet the condition or range are extracted from registrants (students registered in the student information master) or formed by logical operation between existing groups. Group.

Information on groups is registered in the group management table shown in FIG. That is, in this table, the group ID, the group name, the registration date and time, the number of affiliated students, and the sending ID are recorded. The name assigned to the group (generally assigned by the person in charge of the company) is the group name, and its identification code is the group ID (assigned automatically by the server 1). The date and time when the group was created is the registration date and time, and the number of students belonging to the group is the number of students belonging. The items to be sent are materials such as a company brochure (brochure) and direct mail (DM). The materials sent vary by group. It is the sentence ID that specifies the material to be sent or sent to the group.

The group-registered student table of FIG. 5B records information on the students registered in the group for each group, and corresponds to the ID (affiliation) of the student belonging to the group corresponding to the group ID. Student ID) is stored. In addition, the student's name (first name, last name), school name, and department are stored.

FIGS. 6A, 6B and 6C show tables and masters (files) relating to briefings / interviews.

In FIG. 6A, a briefing session / interview ID, a briefing session / interview name (for students),
Briefing session / interview name (inside the company), display category for students, briefing session / interview text category, selection process name, target group ID (multiple possible), date and time, venue ID, capacity, internet capacity, number of applications, internet application Data such as numbers, open classifications, and restrictions are stored. Restriction ID, reception condition I
There are D, limit value, and number of applications, which will be described later in detail.

One briefing / interview has two names, a student name and a company name. These are the briefings / interview names (for students) and (inside the company). For example, if a student has a briefing / interview with the same name (for example, a company briefing), but the group of students participating in the briefing is different (for example, an undergraduate or graduate student), This is because there are times when we want to call this distinction (for example, a briefing session for undergraduates or a briefing session for graduate students).

The display section for students indicates whether or not it can be displayed on the student client 7 as a briefing session / interview (guidance) application screen. In some cases, for example, it is not necessary to display a secondary interview, an officer interview, or the like, or it is not preferable to display it for students.

The explanation session / interview literature division is a code indicating which of the subjects of the explanation session or the interview is divided into the humanities and the sciences. There is also a category of "others", which is classified when the selection of the humanities or the sciences is not made.

The selection process name indicates at which stage of the selection the briefing or interview is.

As described above, a student group is formed for recruitment management. A target group ID specifies a group to which a student who can call for participation in an explanatory meeting or an interview or who can apply is included, and a plurality of group IDs can be registered here.

The venue ID indicates the venue for the briefing or interview (see FIG. 6 (C) briefing / interview venue master).

There is a capacity for briefings / interviews. Of these capacity, the capacity that can be applied especially through the Internet is called Internet capacity. It is possible to register both the total number of applications and the number of applications through the Internet. The application other than the Internet includes, for example, a telephone application (a telephone to a company or an agency).

The open category indicates whether or not the briefing / interview information is to be disclosed to all the students registered in the student information master (if the information is open to the public, the application for the briefing / interview is permitted).

In the briefing session / interview applicant table of FIG. 6B, the student ID indicating the student who applied, the category of application, and the date and time of application are stored using the briefing session / interview ID as a key. The application category indicates whether the application was made through the Internet or not (application by telephone as described above). In the case of a telephone application, the person in charge of the company or the agency will input the application information from the clients 5 and 6.

[0132] The briefing / interview room master shown in FIG.
Information about the venue where the briefing or interview is held is stored in advance. That is, this information is
D, venue name, venue east-west division, map data file name and description. The venue east-west section indicates whether the briefing / interview venue is in East Japan or West Japan. The map data file name is used when accessing the map data (not shown) of the briefing session / interview venue stored in the database 8. The explanation is an explanation about the explanation session / interview venue.

FIGS. 7A and 7B show tables (files) relating to mail management (management of transmission and reception of electronic mail).

The outgoing mail table shown in FIG. 7A is sent from the company to the student (from the hosting site to the student client 7).
E-mail) (this is called outgoing mail). A group ID for specifying a group of students to whom the outgoing mail is to be sent, using the outgoing mail ID for specifying the outgoing mail as a key. Destination (student's first and last name, etc.), student's e-mail address, student ID, ID of briefing session / interview related to the sent e-mail, number of destinations that sent (or sent) sent e-mail (number of transmissions) (group transmission ), Subject, sent date and time, and text (contents of e-mail) are stored.
The subject is given by the sender of the mail, but when registered in the sent mail table, the sent mail ID is always added to the head of the name given by the mail sender.

There are two types of e-mail to be sent to students from the viewpoint of the person to whom the e-mail is sent. The first is to send to individual students. In this case, there is one destination, one email address, and one student ID.
The number of transmissions is also one. In some cases, the group ID is not recorded. The second is to send a group to multiple students belonging to the group. In this case, the text is the same sentence for a plurality of students belonging to the group. The number of transmissions is equal to the number of students belonging to the group.
Multiple groups I if sending to multiple groups of students
D is stored.

The received mail table shown in FIG. 7B is created every time a company receives an electronic mail (this is called a received mail) from a student. The member company naturally has an e-mail address, and an e-mail addressed to the e-mail address of the member company is sent from the student client 7 to the mail server 3. The received mail table contains the mail address of the student who sent the mail, using the received mail ID as a key,
ID of the outgoing mail corresponding to the received mail, unknown classification indicating the presence or absence of the transmitted mail corresponding to the received mail (whether or not it was identified as corresponding), read classification indicating whether the received mail has already been confirmed, received mail , The subject, the date and time of reception, and the text (contents of the received mail) are stored.

In many cases, a member company sends an e-mail (transmitted mail) to a student (registered student), and in response, the student returns an e-mail (received mail) to the company. If a student who receives an e-mail (outgoing mail) from a company creates an e-mail (incoming mail) using the subject included in the outgoing mail as it is,
The subject of the received mail will be the same as the subject of the sent mail. Since the subject of the outgoing mail includes the outgoing mail ID as described above, the subject can be used to associate the incoming mail with the outgoing mail.

If the student creates an e-mail with a subject different from the subject of the outgoing e-mail (e-mail sent from the company to the student), the subject is used to receive the e-mail (sent from the student to the company). Therefore, the mail received by the company) cannot be associated with the outgoing mail. In this case, the destination e-mail address of the outgoing mail (student's e-mail address: this is the e-mail address registered in the student information master) is compared with the source e-mail address of the received e-mail (the student's e-mail address). I do. If the e-mail addresses match, the received e-mail and the transmitted e-mail are associated. If a student sends an e-mail using a computer other than his client computer, the sender's e-mail address in the received e-mail is registered in the student information master (stored in the e-mail table). May be different from your e-mail address. In this case, the correspondence between the received mail and the transmitted mail cannot be made. Such a correspondence process (association process) of the received mail corresponding to which sent mail is performed by the corporate web server 1, and the result is stored in the received mail table as an unknown category. The unknown category indicates whether there is an outgoing mail corresponding to the received mail.

When the unknown section data indicates that there is no corresponding outgoing mail, the received mail is called an unknown mail. There are two types of unknown mail:
The subject of the received e-mail does not include the outgoing e-mail ID The e-mail source of the received e-mail is not the one registered in the student information master

FIG. 8 shows another table.

The narrowing-down condition table shown in FIG. 8A holds one or a plurality of search conditions (narrowing-down conditions) set in a narrowing-down process described later. In this table, using the narrowing condition ID as a key, the ID of the group formed by the narrowing process, the code indicating the narrowing target group (search target), and one or a plurality of set search conditions (search conditions) 1, 2, 3, etc.), and a narrowing condition creation date are stored. The search target is all students registered in the student information master when the process shifts from the menu screen to the narrowing down process. After the group is formed, if the group is further narrowed down by adding a search condition, the group becomes a search target. Generally, the number of students registered in the student information master increases with time. Therefore, even if the same narrowing conditions are used, if the date and time are different, the groups obtained by the narrowing process are not necessarily the same. As the group ID, the one indicated by the latest group among the groups formed using the narrowing conditions is stored.

The narrowing-down condition table is also used for storing the reception conditions set in the later-described briefing session / interview reception condition setting / storing process and the creation date thereof (details will be described later). When the reception condition is stored, a reception condition flag is set.

FIG. 8B shows a quick-reference table data table. This quick-reference table data table uses a quick-reference table type code (a code for designating the type of the number of quick-reference tables described later; see FIG. 14) as a key. It stores the quick reference table ID to be specified, the east-west section, the cultural section, and the decline section (these sections are conditions specified in the quick table condition selection, see FIG. 14), the update date and time, and data (plural) of the number of students cell. The quick reference table is in a table format, and the numerical value (number of people) of each cell of the table is stored in the student number cell.

The delivery table shown in FIG. 8C is the delivery ID.
Is used as a key to store the name of the sending item, the sending date and time, the ID of the group to which the sending item was sent (sending group ID), the student ID (plural) indicating the student who sent the sending item, and the like.

(3) Overall Processing by Web Server FIG. 9 shows the overall processing of the web servers 1 and 2 of the hosting site. 2 web servers 1 and 2 for convenience
Is also shown in the figure, but as described later,
The sharing is performed according to the functions of the web servers 1 and 2.

When the hosting site is accessed from the client 5 of the company, the client 6 of the agency, or the client 7 of the student (step 11), whether it is from the company (including the agency) or from the student Is determined (step 12). As mentioned above,
The corporate web server 1 and student web server 2 are URLs
Since this is different, this judgment actually means which server has been accessed.

In the case of access to the corporate web server 1, it is determined whether the access includes a logon (login) (start procedure) command (step 13) or a menu selection result (step 13). Step 15). If it is a logon, the process proceeds to an authentication process (step 14), and if it includes a menu selection result, the process proceeds to the selected process (steps 20 to 28).

Similarly, in the case of access to the student web server 2, if the command includes a logon command, the process proceeds to the authentication process (steps 16 and 17). In the case of menu selection, the selected process is performed. (Steps 18 and 30).

The processes related to logon and menu selection are substantially the same for the corporate web server 1 and the student web server 2, and the explanation of this process is summarized in FIG.

In FIG. 10, in response to a logon request access from the client 5 of the company, the client 6 of the agency, or the client 7 of the student (collectively referred to as clients), the corporate web server 1 or the student web server 2 (These are collectively referred to as a server) transmits the HTML file of the logon screen (hereinafter, simply referred to as "transmit screen") (step 31).

In the client, a logon screen is displayed on the display device. The logon screen includes a box for inputting a user name (in the case of a corporate client or a client of an agency) or an ID number (in the case of a student client), a box for inputting a password, and a sign-on button. The user (company representative, agency representative or student) writes the user name or ID number and password in these boxes (step 4).
2) When the sign-on button is pressed (pointing with the cursor and clicking the mouse; hereinafter, simply referred to as "pressing a button" or "clicking"), these input data are sent from the client to the server ( Step 43).

The server uses the sign-on user name and sign-on password of the company information master (FIG. 2) in the database 8 or the student ID and password of the student information file (sub-database 9) (FIG. 3). Check the input data sent from the client. This is ID and password authentication (step 32).

The input data sent from the client corresponds to the corresponding data (user name, ID
(No., password, etc.), the authentication is OK (step 33), and in this case, the server transmits a menu screen to the client (step 34). If the authentication is not successful, error processing, for example, re-authentication is performed (step 35).

Upon receiving the menu screen (file) from the server, the client displays the menu screen on its display device (step 44).

FIG. 11 shows an example of a menu screen displayed on the client 5 of the company or the client 6 of the agency. On this menu screen, the left column shows processing items that can be selected by the user. These are "number table reference table", "refinement", "refinement condition management", "group management", "group combination", "explanatory meeting / interview", and "mail management". "Information session /
Except for "interview", the user can select these items (the cursor is placed on these character portions and the mouse is clicked; hereinafter, simply referred to as "click"). For "Briefing / Interview", subdivided items such as "Status table", "Settings (with no reception conditions specified)", "Settings (with reception conditions specified)", "Reception condition setting / save", etc. Is selected by the user.

The user selects any of these menus (step 45). The client sends this selection result to the server (corporate web server 1) (step 46). The server proceeds to the process selected in the menu (steps 20 to 28 in FIG. 9). Regardless of which item “Setting (with no reception condition specified)” or “Setting (with reception condition specified)” is clicked in the item of the briefing / interview, the process proceeds to the briefing / interview setting process (step 28).

An example of a menu screen displayed on the student client 7 is shown in FIG. Here, only “explanatory meeting / interview application” is shown as a menu, but it goes without saying that other menus can be provided.

When the student selects the menu of “explanatory meeting / interview application” (step 45), the result is sent from the student client 7 to the server (student web server 2), and the server performs processing according to the menu selection. It will proceed (FIG. 9, steps 18, 30).

(4) Quick Reference Table FIG. 13 shows details of the quick reference table processing (step 20 in FIG. 9). The number-of-cases table processing refers to the application status of students to a specific company (registration status) and the status of progress of applicants toward recruitment (progress status) (for example, the number of participants in seminars, the number of participants in interviews) , The number of people who have passed the primary interview, etc.) are promptly grasped by the user (person in charge of the company).

When the user selects the number reference table on the menu screen, the process proceeds to the number reference table processing, and the server (corporate web server 1) transmits the number reference table condition to the client (company client 5 or agency client 6). Send the selection screen (HTML file) (step
51).

On the client, a number-of-items quick-view table condition selection screen as shown in FIG. 14 is displayed (step 61). On this screen, the user selects the "condition" (range) and the "type of quick reference table" for the target person (step 62).

The conditions (target range) include “East West”, “Bunri”, and “Decline”. "East-west" refers to the east-west division of prefectures. The east-west section of each student can be found from the current address prefecture ID of the student information master in FIG. 3 and the east-west section of the prefectural master in FIG. 4 (A). "All" means including both East Japan and West Japan. “Science” indicates whether it is a humanities or a sciences, and can be identified by the humanities division data of the student information master (FIG. 3). "Rejected" means whether or not the applicant has applied but canceled (or rejects recruitment) an intention to do so. The code for the rejection is shown in the reject category of the student information master (Fig. 3). .

The types of the number reference table include "by educational background", "by reception media", "by selection process", "by questionnaire results", and "by prefecture".

The table of the number of cases by educational background is created based on the school classification by linking the school name data in the student information file (FIG. 3) to the school master (FIG. 4B). That is, the quick reference table of the number of cases by educational background shows the number of students who applied for a specific company, classified by educational background.

The number-of-acquisitions-by-reception-medium table is formed by referring to the data (reception media information) on the reception media in the student information master (FIG. 3) and counting the number of each reception media. The quick reference table of the number of applications by reception media shows the number of applicants for a specific company by the type of reception media (Internet, other databases, telephone, postcards, etc.).

The number-of-selections-by-selection process chart is formed by counting the number of students for each selection process name in the student information master (FIG. 3). The quick reference table of the number of applications by selection process shows the progress of the selection of students who applied for a specific company (the number of people in each selection process) by selection process (stage).

[0167] The quick reference table of the number of cases according to the questionnaire results is based on the questionnaire information (desired occupation, desired work location and desired court) in the student information master (FIG. 3), for each desired occupation, for each desired work location, and for each individual. It is created by counting the number of people for each desired course. The questionnaire table by questionnaire results is a table showing the number of questionnaire items answered by students when applying for a specific company.

The prefectural case count chart is created by counting the number of people for each current address prefectural ID in the student information master (FIG. 3). The prefecture count chart is a table that shows the number of students who applied for a specific company by prefecture at the current address.

In any kind of table, the number of persons belonging to each combination is counted for each combination of all divisions within the range specified by the condition (target item).

FIG. 15 shows an example of the table of the number of cases by educational background. This is based on the number of students who applied for a particular company, regardless of the east-west division (East-West: All), regardless of the literature division (Course: All), and with or without withdrawal (Declination: All). It is shown by gender and culture. The term “all in humanities” means that the humanities are divided into humanities and sciences, and the numbers of both are expressed. If (texture) is only humanities, only humanities are displayed. (East and West) All include Japan. (East West) If only East Japan, the number of East Japan students is displayed. (Decline) Students who declined because they are all are counted.

For all combinations of “conditions” (range of target persons) and “type of quick reference table”, (in most (literary) all humanities and sciences are counted separately, so only humanities and sciences only Combinations are not necessary),
The corporate web serve 1 searches the sub-database 9 for each company during midnight and totals the data to create a quick-reference table data table (FIG. 8B).

In the quick-reference table data table, the quick-reference table type code specifies the “type of quick-reference table”.
The east-west section, the literature section, and the decline section indicate "conditions". The update date and time is the latest creation date and time of the quick-reference table data table. As can be seen from FIG. 15, the number-of-items lookup table includes a number of cells arranged vertically and horizontally to represent numerical values (number of people). These cells are numbered in a predetermined order, such as cell 1, cell 2, and cell 3. The numerical value (number of people) represented in each cell is stored in the student number cell 1, student number cell 2, student number cell 3 of the quick look-up table data table.

Returning to FIG. 13, when the user (person in charge of the company) inputs the conditions and type of the number table in the company client 5 on the number table reference condition selection screen (step
62), and the data is sent to the server (step 63).
The server selects one that matches the designated condition and type from the number-of-items quick-reference table (quick-reference table data table) created in advance, and transmits it to the client (step 52). Since the quick reference table data for all combinations is created in advance, the quick reference table is quickly delivered to the client.

The client displays the number reference table transmitted from the server (step 64). For example, the screen of FIG. 15 is displayed.

When the user clicks the "update" button (step 65), the fact is sent from the client to the server (step 66). The server accesses the sub database 9 of the company and creates a new number table (quick table data table) in order to create a number table that matches the "condition" and "type" entered in step 62. Create it (step 53). The number table (reference table data table) of the reference table ID created earlier is updated with this new table (the update date is also entered) (step 5).
4), send the updated number table to the client (step 55). The updated number reference table is displayed on the client (step 67).

On the display screen shown in FIG. 15, when the user designates a cell in which the number of students is displayed with the cursor and clicks the mouse (step 68), a narrowing-down process (to be described later) is performed.
Proceed to 16 steps 83 or 86). As a result, a narrowing-down process is performed, so that a group can be created and stored. In other words, each cell in the count reference table indicates a kind of filtering condition, which is transmitted to the server 1 (FIG. 1).
6, step 83). For example, the cell at the upper left (number of people 1808) in the case count table shown in FIG. 15 indicates a narrowing-down condition of graduate school, humanities, and male (these are connected by AND). Clicking on the cell for the number of students not only in the quick reference table by educational background but also in the quick reference table by selection process will proceed to narrowing down in the same way. You may make it move to a narrowing-down process from a chart of the number of cases of other types.

(5) Narrowing-down processing (narrowing-condition preserving processing, narrowing-condition calling processing), narrowing-condition management processing Narrowing is synonymous with retrieval. One or more search conditions are set for the narrowing down process. The set of one or a plurality of set search conditions is called a narrowing condition. The term “narrowing” is used here to distinguish and express individual search conditions and narrowing conditions as a combination thereof. The substance of the narrowing-down process is to perform a search in accordance with a combination (AND or OR combination) of one or a plurality of search conditions.

The narrowing-down (search) process is basically executed on the student information master (FIG. 3), but other masters or tables related to the search condition are also searched depending on the search condition. When the menu screen (FIG. 11) is switched to the narrowing down process, all the registered students are targeted for the narrowing down process (group). If a group has already been formed, the students belonging to that group are to be narrowed down. In any case, the target of the narrowing down process depends on the screen transition (from which screen the narrowing down process is started).

FIG. 16 shows the procedure of the narrowing down process. In the menu screen, narrow down processing (step 21)
The case where is selected will be described as an example. The company (agent) client 5 (6) notifies the corporate web server 1 that the narrowing-down process is selected on the menu screen. Since the server 1 transmits the narrowing-down screen in response to this (step 71), a narrowing-down screen as shown in FIG. 20 is displayed on the client (step 81).

In FIG. 20, when the “recall condition” button or the “save current condition” button displayed at the top is pressed, the narrowing condition recall process (step 85, FIG.
18) or the refinement condition saving process (step 86, FIG. 17)
Reference) (after the narrowing condition saving process or the input of the narrowing condition). The “condition call” button is also used for calling “acceptance conditions” described later.

On the narrowing-down screen shown in FIG. 20, the user (person in charge of the company) can input narrowing-down conditions (individual search conditions).

The narrowing-down conditions can be roughly classified into company information / selection information, school information, questionnaire information, qualification information, personal information, current address, homecoming destination, and the like. Search conditions in these categories are all AND
Are combined. If you do not want to use the search condition, you do not need to enter data (there is no search condition if there is no data input).

In the item of the selection process of the company information / selection information, one of the selection processes is selected from a list that appears by pull-down. This means searching for students who have progressed to the selected selection process.

As will be described later, registered students apply for company briefings and interviews. Data on the application is described in the briefing session / interview table and the briefing session / interview applicant table (Fig. 6 (A),
(B)). After the briefing / interview is completed, the evaluation is registered in the student information master (FIG. 3).

In the item of the briefing session / interview application, the search condition is that the applicant has already applied for such a briefing session / interview, or the search condition is that the briefing / interview has been completed and the evaluation has already been determined. Is entered (selection of reserved (evaluated), reserved (evaluated), or no).

The term of the textual division is either the text or the science already described, and can be selected without specification.

The date and time of the briefing / interview may already be determined. If it is necessary to select students who have applied for a briefing / interview held during a specific period or have already participated in a briefing / interview, enter the above specific period in the selection date section. The venue ID is entered in the selection place. The east-west section is the east-west section of the venue.

If the evaluation has already been determined, the rank of the selection evaluation (S, A, B, C, D, Z, etc.) can be input as a search result.

In the classification of the company information / selection information, the input data of each of the above-mentioned items is used as a search condition.
D.

Next, the school information will be described. In a school division, when two or more are checked, those search conditions are combined by OR. The same applies to national and private items, and to items in the cultural division.

In the school name item, the school name is entered as a search condition. Search conditions of a plurality of school names are combined by OR. The same applies to undergraduate / graduate school items and department / major items.

The search conditions for these school divisions, public and private, school names, cultural divisions, and faculties / graduate schools and departments / departments are A
Connected by ND.

As described above, the questionnaire information includes the desired job type, the desired work location, and the desired course, and these are also selected from the pull-down list.

The qualification information is selected as needed from the list displayed by pull-down. TOEIC, TO
For EFL, a range of points is input.

Personal information is gender and age (range of date of birth)
Is the search condition.

The current address and homecoming destination can also be input as search conditions.

When the user inputs a desired narrowing condition (search condition) on the narrowing screen (step 82) and presses a search button, the input narrowing condition is displayed on the client 5.
It is transmitted from (6) to the corporate web server 1 (step 83). The condition defining each cell of the above-mentioned count reference table is also transmitted to the server in this step 83 as a search condition. When multiple cells are specified, they
Linked by R.

The corporate web server 1 searches the sub-database 9 according to the received narrowing-down condition, and extracts students matching the narrowing-down condition (step 72). With the extracted students as one group, a group ID is assigned to the group (step 73). The server 1 retrieves the search results (extracted number of people, extracted first and last name of student, student ID,
A list of school names, departments, etc.) is transmitted to the client 5 (6) together with the display screen (step 74).

Then, in the client 5 (6),
A search result screen as shown in FIG. 21 is displayed (step 84). On this screen, only the number of applicable persons (the number of extracted students) is displayed.

When the user clicks on a character in the hit list, specific information of the extracted student (the above-mentioned student's first and last name, student ID, school name, department, etc.) is displayed (hit list processing described later). Step 88, FIG. 27, FIG. 32).

In the screen shown in FIG. 21, a desired group name is entered in the box of the group storage item, and when the “save” button is pressed, the input group name is transmitted to the server 1. In the server 1, a group management table and a group registration student table (FIGS. 5A and 5B) are created using the data on the students extracted by the narrowing down process, the group ID, and the input group name. Then, the group formed by the narrowing down process is stored (step 87) (see the group storing process in FIG. 26 described later).

From the screen shown in FIG. 21, narrowing down processing (step 2
1), it is also possible to proceed to the mail transmission processing (step 89) and the group combination processing (step 24) (click on the corresponding character). For example, looking at the search results, if the number of relevant students is too large, and if it is desired to further increase the search conditions and narrow down the search again, the narrowing down process may be performed again. Of course, after saving the group, the narrowing down process can be performed again on the saved group. The mail transmission process and the group combining process will be described later.

In the screen of FIG. 20, after the user inputs the narrowing conditions (step 82), if the user wants to save the input narrowing conditions, the narrowing condition saving process (step 82) is performed.
Go to 86). The conditions that define each cell specified in the above-mentioned number reference table can also be registered as the narrowing conditions in the narrowing condition storage processing.

In the narrowing-down condition storing process, referring to FIG. 17, in the narrowing-down screen of FIG. 20, the name of the narrowing-down condition is input in the box on the upper left of the button “Save current condition”, and “ Press the "Save current condition" button (step 101). Then, the input narrowing conditions and narrowing condition names are transmitted from the client 5 (6) to the server 1 (step 102).

The server 1 creates a narrow-down condition table (FIG. 8A) using the received narrow-down conditions and narrow-down condition names and stores it in the sub database 9 (step 91).
In this narrowing-down condition table, one or a plurality of search conditions, which are elements of the narrowing-down condition, include a narrowing-down condition ID and a group I.
D (if any), search target (all students or group I
D), and the registration date and time. If the group has not been formed yet (search on the server (step 72) has not yet been performed)
Does not record the group ID. After performing the search in the server, the process proceeds to the narrowing down process again. When the narrowing down conditions are stored (the skipping condition input in step 82 is skipped), there is a group created using the narrowing down conditions. The group ID is stored in the condition table.

Thereafter, the server 1 transmits a narrow-down screen including data such as narrow-down conditions and narrow-down condition names to the client 5 (6) for confirmation (step 92).

In the client 5 (6), a narrowing-down screen in which the narrowing-down condition names are described and the previously input narrowing-down conditions are displayed as shown in FIG. 22 is displayed (step 103). Since most of FIG. 22 is the same as FIG. 20, illustration of the lower half is omitted.

Thereafter, if necessary, the user can further add a search condition to perform a narrowing-down process (step 21), or press a “call condition” button to proceed to a narrowing-down condition calling process. (Step 85).

FIG. 18 shows a narrowing-down condition calling process (step 8).
5), and the process transits from the narrowing-down screen in FIG. 20 (see step 81 in FIG. 16) or the narrowing-down screen in FIG. 22 (see step 103 in FIG. 22). Calling of a reception condition, which will be described later, is performed in exactly the same way in this narrowing-down condition calling process.

On these narrowing-down screens, pulling down the box on the left side of the “condition call” button displays all narrowing-down condition names (including reception condition names) that have already been set (set in the narrowing-down condition table). The list appears as shown in FIG. 23 (when the corporate web server 1 sends the narrowing-down screen to the client, it also sends a list of narrowing-down condition names that have already been set).
The user selects a desired narrowing condition name from this list (step 121). The selected narrowing condition name is transmitted to the corporate web server 1 (step 122).

The server 1 searches the narrowing-down condition table for a table having the selected narrowing-down condition name, reads out the search conditions described in the table (step 111), edits the search condition in the narrowing-down screen, and edits the client screen. 5 (6) (step 112).

As a result, for example, a narrowing-down screen as shown in FIG. 22 (or a briefing session / interview reception condition setting / storing screen as shown in FIG. 45) is displayed on the display device of the client 5 (6). (Step 123). Thereafter, the user can proceed to the narrowing-down process (step 21) or the narrowing-down condition storing process (step 86).

FIG. 19 shows the processing executed when the narrowing-down condition management processing (FIG. 9, step 22) is selected on the menu screen. The narrowing condition management processing includes displaying a list of narrowing condition names, selecting narrowing condition names, displaying the selected narrowing conditions, deleting narrowing conditions (names), and the like.

When data indicating that the narrowing condition management is selected is transmitted from the client 5 (6), the corporate web server 1 checks the narrowing condition names and the registration dates and times of all the narrowing condition tables (including the receiving conditions). Is read out to create a list (step 131), and a refinement condition management screen including this list is transmitted to the client 5 (6) (step 13).
2).

As a result, the client 5 (6) has
Is displayed (step 141). On this screen, a list of condition names of narrowing conditions that have already been created and their registration (creation) dates and times is displayed. The user can call up the narrowed-down screen of the clicked condition name by clicking the narrowed-down condition name in this list. Further, the user can delete the selected narrowing condition by checking a box corresponding to the narrowing condition name and pressing a “delete” button. When the client sends the name of the narrowing-down condition and a message to the server 1 to the server 1, the server 1 deletes the corresponding narrowing-down condition table. Equivalent treatment).

When the user clicks a narrowing condition name in the narrowing condition list, the client 5
When the narrowing condition name is transmitted from (6), the corporate web server 1 reads the narrowing condition table having the corresponding narrowing condition name (step 133), and creates a narrowing screen using the search condition data of this table. And sends it to the client 5 (6) (step 134).

For example, the client 5 (6)
A narrowing-down screen as shown in FIG. 2 is displayed (step 14
Four ). The user can proceed to the narrowing down process (step 21) or the narrowing down condition storing process (step 86).

(6) Group management processing (group storage processing, applicable person list processing), group joining processing A group of students extracted by the above-described narrowing down processing (search processing) is a group, and these groups are group management tables. It is managed using the group registration student table (FIGS. 5A and 5B). The group also
It is also formed by a group combining process described later.

FIG. 25 shows the flow of the group management process. The group management processing includes displaying a group list, selecting a group, displaying the number of members constituting the selected group, displaying specific student information, deleting a group, and the like.

When the user selects group management on the menu screen (FIG. 11) (step 23 in FIG. 9), the fact is transmitted from the client 5 (6) to the corporate web server 1. In response, the server 1 searches the group management table (FIG. 5 (A)) and finds out the group names and registration dates and times (creation date: year, month, day, hour, A list of minutes (minutes, seconds) and the number of students belonging (number of applicable persons) is created (step 151), and the group management screen including this list is edited and the client 5
It is transmitted to (6) (step 152).

In the client 5 (6), a group management screen as shown in FIG. 29 is displayed on the display device. This screen displays the above list.

On this group management screen, the user can select a desired group by clicking the group name (step 162). The selected group name is transmitted to server 1 (step 163).

When the user checks the box to the left of the group name on the group management screen and presses the “Delete” button, the fact is transmitted to the server 1. The server deletes the data related to the relevant group from the sub-database. (Actually, a code indicating that the data has been deleted is entered in the relevant group management table and the group registration student table, and the data is treated as deleted in the subsequent processing. Be able to do that).

Upon receiving the group name selected in step 162, the corporate web server 1 reads the group management table having the selected group name and the group registered student table of the students belonging to the group (step 153), The group information is transmitted to the client 5 (6) together with the group operation screen (step
154).

The display device of the client 5 (6)
A group operation screen as shown in FIG. 30 is displayed (step 164). This screen is displayed when the group A is selected, and the number of applicable persons is shown as 23. Fig. 30
The screen shown in Fig. 21 is the same as in Fig. 21 except that the group name is displayed.
It is the same as the screen shown in FIG. On this screen, the user can proceed to the selected processing by clicking and selecting the characters of applicable person list, narrowing down, mail transmission or group combination (steps 166, 21, 89, 2).
Four). The user can also enter the group name in the box on the right side of the character of the group storage to move to the group storage processing (step 87).

FIG. 26 shows the group storing process. There are two types of group storage processing. One of them is the group formed by the refinement process (as shown in Figure 21).
This is a process of assigning a group name and storing the group information in the sub database 9 (new storage). the other one is,
This is a process of storing a group that has already been assigned a group name and stored in the sub database 9 with another group name (as shown in FIG. 30) (save as another name).

In any case, the user is required to enter the information shown in FIG.
A desired group name is entered in the box on the right side of the character of the group storage on the screen shown in FIG. The input group name is transmitted to server 1 (step 182).

The corporate web server 1 stores the group temporarily formed by the narrowing-down process (FIG. 16, steps 72 and 73) or the selected group (FIG. 25, steps 163, 153,
154), the group name input in step 181 is assigned, a new group ID is issued, and data relating to those groups is newly created in the sub-database 9 by creating a group management table and a group registration student table. It is stored (step 171). In the case of saving under a different name, data relating to the group selected earlier (in step 163 in FIG. 25) is left as it is. Of course, the content of the previous group is the same as that of the group to which the alias is added, but the group name, the group ID, and the registration date and time are different.

Thereafter, the server 1 creates a group operation screen including the data relating to the group registered in step 171 and transmits it to the client 5 (6) (step 172).
). In the client 5 (6), a group operation screen as shown in FIG. 31 is displayed. As is clear from comparison between FIG. 30 and FIG. 31, only the group name is different. From this screen, the user can proceed to narrow-down processing, mail transmission processing, applicable person list processing, group combination processing, and the like (steps 21, 89, 166, 24). Of course, the process can also proceed to a group storage process (not shown).

When the user clicks a character in the corresponding person list on the group operation screen, the processing of the corresponding person list shown in FIG. 27 is performed. Data indicating that the user has selected the applicable person list is sent from the client 5 (6) to the server 1. The corporate web server 1 stores the information of the students belonging to the group of the group name selected at that time (displayed in FIG. 31) in the group registration student table (FIG. 5B).
) And the student information master (FIG. 3) to create an applicable person list (step 191) and transmit it to the client 5 (6) together with the applicable person list screen (step 192).
).

On the display screen of the client 5 (6),
The hit list screen as shown in Fig. 32 is displayed (step
201). On this screen, the names (first and last names), school names, department names, departments, and telephone numbers of the students belonging to a specific group (group C in the transition from FIG. 31) are displayed in the form of a list.

From this screen, the user can selectively proceed to some processing. One is to get detailed information on a particular student in the list. In this case, click the name in the list (step 202
).

Second, in the list, click "apply" in the last cell of each student's column (row). In this case, the briefing / interview application process (step 205
). The details will be described later.

The third is to click the “set group name” button at the top left of the screen. In this case, the screen transits to the screen shown in FIG. 21 or FIG. 31, and the group is saved (set the group name).

The fourth is to check the box on the left side of the list and press the "Delete from list" button. In this case, the checked student is removed from the group (the corresponding group registered student table is deleted).

The third and fourth steps are not shown in FIG. 27 as other processing.

When the user selects the above one process and designates one student (step 202), the name of the designated student is transmitted from the client 5 (6) to the server 1 (step 203).

The corporate web server 1 reads the designated student data from the student information master (step 193), edits the profile screen using the read student information, and sends it to the client 5 (6) (step 193). 194
).

As shown in FIG. 33, almost all information (reception media, selection process, decline information, personal information, school information, questionnaire information, qualifications, etc.) about the target student is displayed on the client 5 (6). Is done. The person in charge of the company can also click the “correct” button to correct the predetermined information.

By clicking on the characters of received mail list, transmitted mail confirmation, mail transmission, briefing session / interview setting or briefing session / interview application at the top of the screen, the process proceeds to the corresponding process (step 206). , 207,
89, 208, 209).

FIG. 28 shows the group combining process.
Menu screen (Fig. 11) or group operation screen (Fig. 21,
In FIGS. 30 and 31), when the user selects the group combination (FIGS. 9, 16, 25, 26, step 24), the fact is transmitted from the client 5 (6) to the server 1. The corporate web server 1 retrieves all groups created so far from the group management table to create a list of group names (step 211), edits the group combination screen including this list, and edits the client 5 It is transmitted to (6) (step 212).

In the client 5 (6), a group combination screen is displayed (step 221). FIG. 34 shows an example of the group combination screen.

The term "group combination" refers to performing a logical operation (logical operation on the students constituting the group) between two or three or more existing groups to form a new group.

In the group combining process of this embodiment, a logical operation is performed between two groups for simplicity. When performing a logical operation on three or more groups, the group combining process is repeated a plurality of times, such as performing a logical operation on two groups and performing a logical operation on the result and another group.

It is necessary to specify two groups for group combination. These two groups are clearly shown as a target group 1 and a target group 2 on the screen of FIG.

The target group 1 is, in principle, a group formed or selected immediately before the transition to the group combination screen. For example, when the screen transits from the screen in FIG. 21, it is a group formed by the narrowing down process. In this case, since this group has not been given a group name yet, "NO-NAME" is displayed as the target group 1 on the screen of FIG. When the screen changes from FIG. 30 or FIG. 31 to the screen of FIG.
Or group C.

When the box of the target group 1 is pulled down on the screen of FIG. 34, the group name list transmitted from the server 1 is displayed. In any case, the desired group name is selected from the pull-down list. Can be selected. Figure from the menu screen in Fig. 11
When the screen transitions to screen 34, this pull-down list will be used exclusively.

The target group 2 is selected from a group name list displayed by pull-down in a box on the right side.

In this embodiment, the types of logical operations in group combination are OR (logical sum), AND (logical product), NO
T (No), from which the user selects. OR means that a set of students belonging to at least one of the target group 1 and the target group 2 is set as a new group. AND is to form a new group by a set of students belonging to the target group 1 and also to the target group 2. NO
T is to set a set of students belonging to the target group 1 but not to the target group 2 as a new group.

On the group combination screen shown in FIG. 34, the user selects the target group 1, the target group 2, and the combination method (the type of logical operation), and presses the "execute" button (step 222). Then, the group name to be combined and the combining method are transmitted to the server 1 (step 223).

The corporate web server 1 reads the group management table having the group name selected by the client and the group registration student table associated therewith, and for the students belonging to the two target groups, according to the selected joining method. The calculation is performed, the students belonging to the new group are specified, and a new group is created (step 213). The new group is assigned a group ID (step 214). Of course, the assigned group ID is different from the already used group ID.

The group operation screen including the number of students belonging to the newly formed group (the number of students) and the group ID is sent from the server 1 to the client 5 (6) (step 215).

On the display screen of the client 5 (6), for example, a group operation screen as shown in FIG. 21 is displayed (step 224). On this screen, the user can proceed to a group saving process in which a new group is given a group name and saved (step 87). Step 214
The temporary group formed by the above becomes a formal group by the group storage processing. After the group storing process, the group combining process can be performed again. After the group saving process or without performing the group saving process, a narrowing-down process can be performed by inputting a narrowing-down condition for a newly formed group (step 21). It is also possible to proceed to the applicable person list processing for the new group (step 166), and to the mail transmission processing described later (step 89).

(7) Briefing session / interview status table process, briefing session / interview reception condition setting / storing process, briefing session / interview setting process, briefing session / interview application process FIG. 35 shows the briefing session / interview status table process. Things. In this process, the user selects the briefing / interview status table on the menu screen (FIG. 11), and the client 5
The process is started in response to transmission from (6) to the corporate web server 1.

First, the server 1 transmits a status table condition selection screen to the client 5 (6) (step 231). In response, a status table condition selection screen as shown in FIG. 42 is displayed on the display device of client 5 (6) (step 241).
).

The explanation session / interview status table process is a process of displaying the number of applicants for various company explanation sessions and interviews set by the user (company) in a table.

This condition selection screen is for setting the range (condition) of the briefing session / interview where the situation table is to be displayed. The selection process is for inputting which stage of the briefing / interview you want to know, and can be selected from a pull-down list. The selection process varies from company to company, but is generally represented by words such as briefings, primary interviews, and secondary interviews (described in the briefing / interview table), as described above. (East and West) restricts the venue for the briefing / interview where the situation table should be displayed to either East or West Japan, and there is an option to be all regardless of East or West (see the briefing / figure in Figure 6 (C)). See Interview Venue Master). (Course) is equivalent to the briefing / interview literature section described in the briefing / interview table in FIG. 6 (A), and is a briefing / interview for humanities students or a briefing / interview for science students. , To choose not to stick to them.
(End) is used to select whether the briefing session / interview has already ended, the briefing session / interview that has not ended, or all. Since the date and time of the briefing / interview are described in the briefing / interview table (FIG. 6 (A)), selection can be made by comparing the date and time at which the meeting was held with the date and time at that time.

When the user inputs the range or restriction (these are referred to as conditions) as described above (step 242) and presses the "display" button (step 243), the selected conditions are transmitted from the client 5 (6) to the server. 1 (step 243).

The enterprise web server 1 having received the status table condition searches the briefing session / interview table (FIG. 6A) for a briefing session / interview meeting the conditions (step 232), and obtains the information. A list (situation table) is created based on the data regarding the briefing session / interview, and a state table screen including the state table is transmitted to the client 5 (6) (step 233).
In the client 5 (6), a status table screen as shown in FIG. 43 is displayed.

[0260] In the situation table, the briefing session / interview name (inside the company)
Corresponding to the date, time (holding date and time), location (venue),
The Internet capacity, the number of applicants via the Internet, the total capacity, and the total number of applicants are displayed.

In the briefing / interview situation table, the user can proceed to two main processes. One of them is to change the name of a specific briefing session / interview, the date and time of the meeting, the venue, etc., or to set a new briefing session / interview. In this case, the user clicks the desired briefing / interview name (including creating new briefing / interview data based on the briefing / interview data) in the status table (step 24).
Five ). The other is to display a list of students who have applied for the briefing / interview. In this case, the user clicks a cell (either Internet application or entire application) in which the number of applicants in the row of the desired briefing / interview name is displayed (step 251).

When the name of the briefing / interview is clicked (step 245), the name of the briefing / interview is displayed on the client 5.
It is transmitted to the server 1 from (6). The server 1 reads out necessary data from the briefing session / interview table having the transmitted briefing session / interview name (step 234), creates a briefing session / interview detail screen so that a list can be displayed, and creates a client 5
It is transmitted to (6) (step 235). As a result, a detailed explanation / interview screen as shown in FIG. 44 is displayed on the display device of the client 5 (6) (step 247).

[0263] On the briefing session / interview detail screen, data that has been set for the briefing session / interview specified by the user is displayed in the form of a table. These data include briefings / interview names (inside the company) and briefings / interview names (for students)
(For students), display for students (display classification for students), target group (target group ID), interviewer (not shown in FIG. 6 (A)), date and time (holding date and time), location ( Venue ID), overall capacity (capacity), net capacity (Internet capacity), and the like. At the bottom of the screen, a "Modify" button and a "Copy" button are displayed. When correcting the displayed briefing / interview data, the user needs to “correct”
When the user creates a new briefing session / interview data based on the displayed briefing session / interview data (setting of briefing session / interview), the user presses a “copy” button. The button press information is transmitted to the server 1 and the briefing session /
The process proceeds to an interview setting process (step 28).

When the user clicks the cell of the number of applicants in the briefing session / interview status table (step 251), the corresponding briefing session / interview name is transmitted to server 1 (step 25).
2).

The server 1 receives a briefing session / interview table (FIG. 6 (A)) having the briefing session / interview name, and a briefing session / interview applicant table linked by the briefing session / interview ID (FIG. 6 (A)). B)) and the student information of the student information master (FIG. 3) obtained using the applicant student ID described in the applicant table as a key, is read from the sub database, and a list of applicant students is created (step 236). Then, a corresponding person list screen including this list is created and transmitted to the client 5 (6) (step 237).

The client 5 (6) displays the corresponding person list screen transmitted from the server 1 (this includes a student list similar to that shown in FIG. 32) (step 253).
). As shown in the description of FIG. 32, there is also a “group name setting” button on the hit list screen displayed in step 253, and when this button is pressed, the “group name setting” button is pressed.
Is transmitted from the server 1 and displayed on the client 5 (6). When a group name is input on the group operation screen, the server 1 forms a group by a set of students listed in the above list, and the group management table and the group registration student table (FIGS. 5A and 5B) are displayed. It is created and stored in the sub-database 9. That is, based on the situation table,
A group of applicants for the selected briefing / interview will be created.

In the hit list screen displayed in step 253, in the hit list (see the list in FIG. 32), there is an evaluation input cell next to the telephone number cell.
In this cell, an evaluation list can be displayed by pull-down. Users can enter ratings for individual students. The evaluation data of the student is sent to the server 1 and recorded in the student information master (FIG. 3) of the student.

FIG. 36 shows a briefing session / interview acceptance condition setting / storing process. This process also transits from the menu screen (FIG. 9, step 27).

The briefing session / interview acceptance condition setting / storing process is to create data indicating the range (conditions) of students who can apply for the briefing session / interview in advance and save it in the sub database 9. . Only students who meet the set conditions will be able to view information on briefings / interviews via the Internet. Also, only students who meet the set conditions can apply for a briefing / interview.

Since the corporate web server 1 transmits the briefing / interview acceptance condition setting / save screen to the client 5 (6) (step 261), a screen as shown in FIG. 45 is displayed on the client (step 271). ). This screen contains almost the same contents as the previously described narrowing down screen (FIG. 20). The user inputs desired conditions on this screen (step 272), and inputs a reception condition name in the box on the left side of the "save current conditions" button in the upper row (step 273). When the “save current condition” button is pressed, the input reception conditions and the reception subject are transmitted to the server 1.

The server 1 creates a reception condition table having the same format as the narrowing condition table (FIG. 8) and stores it in the sub database 9 (step 262).
). The contents of the reception condition table and the narrowing-down condition table are basically the same (the reception condition table does not form a group, so that the reception condition table contains the group I
D is different.) The reception condition table and the narrowing-down condition table are recognized by the servers 1 and 2 as being separate by the reception condition flag.

Thereafter, the corporate web server 1 includes the reception condition names and the registration date and time for all the reception condition tables created so far (existing in the sub-database 9) including the one registered this time. A list is created, and a briefing session / interview acceptance condition saving screen including this list is transmitted to the client 5 (6).

In the client 5 (6), as shown in FIG. 46, a briefing session / interview reception condition management screen including the above list is displayed (step 275). In this list,
If there is the reception condition name input in step 273, the user can confirm that the previously stored reception condition has been registered. The user can also specify (check the box) a specific reception condition name and delete it. The filtering condition name is not included in the reception condition name list.

The flow of the briefing / interview setting process is shown in FIG. The briefing session / interview setting is basically to create the briefing session / interview table shown in FIG. 6 (A), and includes modifying it. A new briefing session / interview table can also be created using a briefing session / interview table that has already been created.

The client 5 (6) notifies the server 1 that the setting (no reception condition specification) or the setting (reception condition specification) character in the briefing / interview has been clicked on the menu screen (FIG. 11). Or when
Client 5 indicates that the "Modify" button or the "Copy" button was pressed on the 44 briefing / interview detail display screen.
The briefing / interview setting process starts when the server 1 is notified from (6) (FIG. 9, step 28, or FIG. 35, step 28).

The corporate web server 1 is a client 5
The client 5 based on the information transmitted from (6)
Select the briefing / interview setting screen to be sent to (6) and fill in the blanks in the table on the screen as necessary (step
281).

When the server 1 receives a notification that the setting (no reception condition designation) has been clicked on the menu screen, the server 1 selects the briefing / interview setting screen as shown in FIG. 47 and sends it to the client 5 (6). Send (Step 282
).

The explanatory meeting / interview setting screen shown in FIG. 47 allows the user to specify a target group that can receive (can accept) the explanatory meeting / interview. This screen is
Briefing session / interview name (for company) (inside company), briefing session / interview name (for student) (for students), literary division (explanatory meeting / interview literary division), selection (selection process name), target group (target) Group ID), date and time (holding date and time), location (venue ID),
The interviewer (not shown in Fig. 6 (A)), the total capacity (capacity) and the net capacity (internet capacity) are provided. (Since the briefing / interview is newly set, These fields are blank). The name of the group (group name) (see the group management table in FIG. 5A) that has already been set by the pull-down method appears in the column of the target group, so that the user can select a group from this. . An open briefing session is a briefing session where students outside the target group can participate even if the target group is designated. If this open briefing session box is checked, the briefing / interview to be set is positioned as an open briefing (open classification). In step 282, the server 1 transmits an explanatory meeting / interview setting screen (FIG. 47) including a pull-down list of group names to the client 5 (6).

When it is notified that the setting (with reception condition designation) is clicked on the menu screen, the server 1 selects the briefing / interview setting screen as shown in FIG. 48 and sends it to the client 5 (6). (Step 282).

When the screen of FIG. 48 is compared with the screen of FIG. 47, there is no column of the target group, and there is a column of restriction instead. This restriction column also defines the range of students who can participate in the briefing / interview. However, as shown in the screen in FIG.
It is determined using the interview acceptance conditions.

There is a cell in the restriction column where a plurality of restrictions can be entered. A list of the explanation session / interview acceptance conditions that have already been set in each cell by the pull-down method is displayed. The user selects a desired reception condition from this list. As can be seen from FIG. 45, the acceptance conditions are set from the viewpoints of school division, national and private, school name, cultural division, undergraduate / graduate school, department / major, desired occupation, desired work location, desired course, etc. Things. A numerical limit is imposed on any of these set conditions. For example, the acceptance condition that any of public, private, or science and technology can be used in the science and technology divisions (both national and public and private and science and technology categories are all) If the condition of only universities is included, it can be said that the conditions are defined as the whole acceptance conditions), and in that case, the limit of national university science and science is limited to 60%, This is the "limit". The same applies to 30% of private university sciences. 60% of national university sciences and 30% of private university sciences have the same acceptance conditions, and 10% of student sciences have other acceptance conditions. These plural reception conditions are connected by OR. That is, when a plurality of acceptance conditions for students who can apply for one briefing session / interview are determined, students who satisfy any of the acceptance conditions can apply for the briefing session / interview. In any case, a briefing /
When transiting to the interview setting screen (FIG. 48), each field of this setting screen is blank, and the server 1 attaches the pull-down list of the reception condition name to the client 5 (6) in step 282 with the pull-down list of the reception condition name. Will be sent.

When the “correct” or “copy” button on the detailed explanation / interview screen in FIG. 44 is pressed, the explanatory meeting / interview has already been specified. The server 1 accesses the briefing session / interview table having the briefing session / interview name displayed on the briefing session / interview detail screen (FIG. 44) and checks whether the table has data indicating the restriction ID. If there is no data of the restriction ID, the server 1
If there is data indicating the restriction ID on the interview setting screen, the user selects the briefing / interview setting screen shown in FIG. Then, put the data of the briefing / interview shown in the screen of FIG. 44 in each column of the selected screen, attach the parentheses group name list or the reception condition name list, and set the briefing / interview setting screen to the client. 5 (6) (step 282).

The user inputs desired data on the briefing / interview setting screen displayed on the client 5 (6),
Or make corrections, and finally press the “Set” button (step
292). These data are transmitted to the server 1 (step 293).

The corporate server 1 that has received the information (data) on the briefing / interview setting screen determines whether it is a new registration (step 283). The registration is new when entering the briefing / interview setting process from the menu screen and when entering the briefing / interview setting process by pressing the “copy” button on the detailed explanation / interview screen of FIG. In the case of new registration, the server 1 compares the contents of the already-prepared briefing session / interview table in the sub-database 9 with the newly registered briefing session / interview information to determine whether there is the same one. (Steps 284, 285). If they are the same, it is an error, and error processing is performed (step 28).
8). For example, the client is notified that the same briefing session / interview has already been set, and the client is canceled or restarted.

In the case of correction, or when it is determined that there is no same briefing / interview in the new registration, the server 1 transmits a confirmation screen to the client 5 (6) (step 286).
). The confirmation screen is similar to the screen shown in FIG. 44, 47 or 48, and has a "Complete" button, a "Send Mail" button (or text), and a "Status Table" button. When the user sees the confirmation screen displayed on the client (step 294) and presses the "complete" button (step 295), the fact is transmitted to the server 1 (step 296).

The server 1 creates a new briefing session / interview table based on the briefing session / interview information created by the client 5 (6) and registers it in the sub-database 9 (or deletes the existing briefing session / interview table). Correct) (step 287). In the client 5 (6), the user performs the mail transmission processing (step 89) or the status table processing (step 89).
You can proceed to 26). This registration process (step 287
), The target group is the corresponding target group I
Replaced by D. Also, the contents of the restriction (such as the science of a national university) are replaced with the restriction ID indicating the restriction (a correspondence table between the restriction contents and the restriction ID is created). Numerical values such as 60% and 30% are limit values. In the briefing / interview table of FIG. 6A, it can be understood that the limit ID, the reception condition ID, the limit value, and the number of applications (the number of application students satisfying the “limit”) are set as a set.

[0287] The description proceeds to the explanation of the process of the briefing session / interview application. There are two types of this processing. The first is done by a company or agency representative. For example, upon receiving a call from a student indicating that he / she wants to apply for a briefing session / interview, the person in charge processes the application from the client 5 (6) on behalf of the student.
This is shown in FIGS. 38 and 39. The other is for the student to access the student web server 2 from his client 7 and apply for a briefing / interview.
This is shown in FIG.

In FIG. 38, the person in charge of the company or agency (user) clicks the “application” cell in the corresponding student column on the applicable person list screen shown in FIG.
Transition to interview application processing (from step 201 in FIG. 27)
205) or click the text of the briefing / interview application on the profile screen in FIG. 33 to move to the briefing / interview application process (from step 204 to 205 in FIG. 27).

In any case, data on the relevant student from the client 5 (6) (student ID, name, etc.)
Is transmitted to the server 1, the server 1 reads out the student information master (FIG. 3) and the group registration student table (FIG. 5 (B)) of the student, and also provides a briefing session / interview table and a briefing session / interview applicant. The tables (FIGS. 6A and 6B) are read. With reference to these masters and tables, the server 1 extracts briefing sessions / interviews that the student can apply for and has already applied for, and creates a list of briefing sessions / interviews that can be applied. This list will include the following and / or satisfying briefings / interviews.

The date and time of the event described in the briefing / interview table is after the current date and time The target group ID described in the briefing / interview table
The student belongs to the group specified in 1. The student information of the student matches the contents of the restriction ID (contents of the restriction) described in the briefing / interview table

When the open section of the briefing session / interview table is set to allow all students to be accepted (open briefing session / interview), only the above-mentioned date and time check is performed, and the date and time not yet held Will be added to the open briefing / interview list. It is also determined based on the briefing session / interview applicant table whether the student has already applied.

[0292] In this manner, when a list of available briefing sessions / interviews and a list of open briefing sessions / interviews are created (step 301), the corporate web server 1 displays a briefing session / interview application screen including these lists. Is created and transmitted to the client 5 (6) (step 302).

In the client 5 (6), a briefing session / interview list screen as shown in FIG.
321). In this screen, the upper list is a list of available briefing sessions / interviews, and the lower list is a list of open briefing sessions / interviews. In each case, the name of the briefing / interview (inside the company), the date and time (date and time of the meeting), the location (venue) and the status are displayed. In the situation, "Applicable" indicates that application is possible, and "Applied" indicates that the student has already applied for the briefing / interview. Even if the student information matches the content of the restriction ID, if the number of applications has already reached the limit, application is basically not possible, but it is up to the person in charge of the company to approve the application. Since it is up to you, even if the above is the case, it will be displayed that application is possible.

In the screen shown in FIG. 49, when the user clicks the character string “Display all briefings / interviews”, the fact is sent to server 1. Server 1 responds by
A list of all the briefing sessions / interviews for which the briefing session / interview table has been created is created and transmitted to the client 5 (6).

A list of all the briefings / interviews is displayed on the client 5 (6) as shown in FIG. In this display, all of the status columns indicate that application is possible or has already been applied. Compared to the list of available briefings / interviews in FIG. 49, there should be some unavailable briefings / interviews.
List of all briefings / interviews is Corporate Client 5
Since it is displayed only in (6), it is possible to apply for all briefings / interviews from the viewpoint of leaving the decision on whether to accept the application to the person in charge of the company.

[0296] In the list of the screen shown in either Fig. 49 or Fig. 50, if you click on a cell for which application is possible, you have applied for participation in the briefing / interview corresponding to that cell.
Clicking on the cell of "applied" cancels (cancels) the application for the briefing / interview corresponding to that cell (step 322). Data representing the name of the briefing / interview for which the user has applied or canceled is sent to the server 1 (step 323).

FIG. 39 (Steps for the briefing / interview application in FIG. 38)
303 (shown in detail), in the case of application (step 304), the student has already applied for another briefing session / interview with the same selection process name as the briefing session / interview that was applied. It is checked whether it is (step 305).
As mentioned above, there are often multiple briefings / interviews with the same selection process name. A student should not be allowed to apply for multiple briefings / interviews with the same selection process name.

If it is not an application for a plurality of briefings / interviews with the same selection process name, the server 1 transmits an application confirmation screen to the client 5 (6) (step 306) and displays it on the client 5 (6). (Step 325).

This application confirmation screen includes the contents of the briefing session / interview applied in step 322, a sentence confirming that the application for this briefing session / interview is acceptable, and a “confirm” button. When the user presses the "Confirm" button (step 32
6), and the fact is transmitted to the server 1 (step 327).
).

The server 1 performs an application process in response to this (step 311). In the application process, a briefing session / interview applicant table indicating that the student has applied for the briefing session / interview is created and stored in the sub-database 9, and the briefing session / interview briefing session / interview table for the applied student is provided. Is incremented. Thereafter, a profile screen is created based on the student information of the student and transmitted to the client 5 (6) (step 312). Since a profile screen as shown in FIG. 33 is displayed on the client (step 328), the user can confirm that the application for the briefing session / interview has been made by viewing the selection process information on this profile screen.

In the case of applying for a plurality of briefings / interviews with the same selection process name, whether or not the screening evaluation / interview already applied (for the selection process) has been evaluated by the student information A judgment is made from the information on the master selection process (step 307). If the selection evaluation has already been made, a screen is created to indicate that fact and that the evaluation has already been completed and that an application for a briefing session / interview cannot be made, and sent to the client 5 (6) (step 30).
8). This screen is displayed on the client (step 324).

If the selection evaluation has not been completed, the will of this application will be respected, and the already applied briefing session / interview will be canceled and the newly applied briefing session / interview will be newly registered (this Change confirmation screen) to the server 1
Is created and transmitted to the client 5 (6) (step
309).

This change confirmation screen is displayed on the client 5 (6) (step 325). If the user inputs a confirmation of application (change) (step 326), the fact is sent to the server 1 (step 326). 327).

At the server 1, the briefing session already applied /
The application data for the interview is deleted (deletion of the applicable briefing session / interview applicant table and the number of applicants in the briefing session / interview table is decremented) (step 310). Application processing is performed (step 311). A profile screen for the student is transmitted to the client 5 (6) (step 31).
2). A profile screen is displayed on the client 5 (6) (step 328).

In the case of cancellation (step 304),
A cancellation confirmation screen is displayed from the server to the client 5 (6), indicating that the contents of the briefing session / interview designated to be canceled and the cancellation should be confirmed (step 313).

A cancellation confirmation screen is displayed on the client 5 (6) (step 325). When the user inputs a confirmation of cancellation (step 326), the fact is sent to the server 1 (step 327).

The server 1 checks whether a screening evaluation has already been given for the briefing session / interview for which cancellation is desired, based on the student information master of the student (step 314).

If the selection evaluation has not been performed yet, the application for the corresponding briefing session / interview of the student is canceled (step 316), and the profile screen of the student is transmitted (step 312). If the selection evaluation has already been performed, an evaluation confirmation screen is sent to the effect that the evaluation has been completed and it is no longer possible to cancel (including that the application cannot be applied, of course) (step
315). This screen is displayed on the client 5 (6) (step 324).

With reference to FIGS. 40 and 41, a process in which a student accesses the student web server 2 from his / her client 7 and applies for a briefing session / interview will be described.

[0310] In the menu screen (Fig. 12) appearing on the student client 7, the student clicks the text of the briefing / interview application. This is transmitted from the student client 7 to the student web server 2, and the briefing / interview application process (FIG. 9, step 30) is started.

When the student client 7 accesses the student web server 2, the student client 7 sends the student ID and password, so that the student web server 2 can identify the accessing student.

[0312] The student web server 2 prepares a briefing session / interview application screen to be transmitted to the student client 7 by accessing the student information master (Fig. 3) and the group registration student table (Fig. 5 (B)). ), The briefing session / interview table and the briefing session / interview applicant table (FIGS. 6A and 6B).

[0313] In the briefing session / interview table, those for which the display category for students indicates that they can be displayed for students are subject to the briefing session / interview list. No interview table is extracted.

[0314] Briefing session / Briefing session to be displayed on the interview application screen
The subject (explanatory meeting / interview) to be included in the interview list satisfies the above conditions and meets the following conditions and / or above.

The date and time of the event described in the briefing / interview table is after the current date and time The target group ID described in the briefing / interview table
The student belongs to the group specified in 1. The student information of the student matches the contents of the restriction ID (contents of the restriction) described in the briefing / interview table

[0316] Among the items listed in the briefing session / interview list, the briefing session /
The interview will be completed. If the number of applications has reached the limit value, applications cannot be made. Other than these can be applied.

If the open section of the briefing / interview table allows all students to be accepted (open briefing / interview), only the above date and time check is performed. Added to the open briefing / interview list.

In this way, when a list of briefing sessions / interviews and a list of open briefing sessions / interviews that can be applied (partly including the above-mentioned applied and non-applicable) are created (step 331), the student web The server 2 creates a briefing session / interview application screen including these lists and
(Step 332).

The student client 7 displays a briefing / interview list screen as shown in FIG. 51 (step 35).
1). This screen is almost the same as that shown in FIG.
However, the word “Show all briefings / interviews” does not appear.

In the list on the screen of FIG. 51, clicking on a cell for which application is possible means that an application for participation in the briefing / interview corresponding to that cell has been made, and clicking on the cell of "Applied" corresponds to that cell. The application for the briefing / interview to be performed is canceled (canceled) (step 352). Data representing the name of the briefing / interview for which the student has applied or canceled is sent to the student web server 2 (step 353).

FIG. 41 (details of step 333 in FIG. 40 are shown)
, In the case of application (step 334), it is checked whether the student has already applied for another explanation session / interview with the same selection process name as the applied explanation session / interview (step 334). 335). A student is not allowed to apply for multiple presentations / interviews with the same selection process name.

If it is not an application for a plurality of briefings / interviews with the same selection process name, the student web server 2 transmits an application confirmation screen to the student client 7 (step 336), and is displayed on the client 7. (Step 355).

This application confirmation screen includes the contents of the briefing session / interview applied in step 352, a sentence confirming that the application for the briefing session / interview is acceptable, and a “confirm” button. When the student presses the "confirm" button (step 356)
), And the fact is transmitted to the student web server 2 (step 357).

In response to this, the server 2 performs an application process (step 342). In the application process, a briefing session / interview applicant table indicating that the student has applied for the briefing session / interview is created and stored in the sub-database 9, and the briefing session / interview briefing session / interview table for the applied student is provided. The number of applications (including the number of Internet applications) is incremented. After that, the contents of the briefing session / interview that the student applied for (name of the briefing session / interview, selection process name, date and time of the meeting, venue, etc.) and a completion notification screen containing a message indicating that the application was completed are sent from the server 2. Sent to student client 7 (step 343). Since the completion notification screen is displayed on the student client 7 (step 358), the student can confirm that the application for the briefing session / interview has been completed.

In the case of applying for a plurality of briefings / interviews with the same selection process name, the student information indicates whether or not the screening evaluation / interview already applied (for the selection process) has been completed. It is determined from the information on the master selection process (step 337). If the screening process has already been performed, an evaluation-confirmed confirmation screen is created to indicate that fact and that the evaluation has been completed and that the application for a briefing session / interview cannot be made, and sent to the student client 7 (step 338). . This screen is displayed on the client (step 354).

In the case where the selection evaluation has not been completed, the intention of this application will be respected, the explanation session / interview already applied will be canceled, and the explanation session / interview applied this time will be newly registered. Processing proceeds.

If the date and time of the briefing / interview that has already been applied is before (and has passed) the date and time at that time, the briefing / interview has already been conducted. However, the student who did not participate has no information, so the student can no longer apply for a briefing / interview of the same selection process. An application refusal confirmation screen expressing such a situation is created in the server 2 and transmitted to the student client 7 (step 344), and the screen is displayed on the client 7 (step 344).

If the briefing session / interview previously applied for has not been held yet, the change confirmation screen indicating that the already applied briefing session / interview will be canceled and the currently applied briefing session / interview will be registered. Is created by the student web server 2 and transmitted to the student client 7 (step 340).

The change confirmation screen is displayed on the student client 7 (step 355). If the student inputs a confirmation of application (change) (step 356), the fact is sent to the student server 2 (step 357). ).

The student server 2 cancels the application data for the briefing session / interview that has already been applied (step 341), and performs the student's application processing for the briefing session / interview that was applied this time (step 342). A screen indicating completion is transmitted to the student client 7 (step 343). A completion notification screen is displayed on the student client 7 (step
358).

In the case of cancellation (step 334),
A cancellation confirmation screen is displayed from the server 2 to the student client 7 indicating that the contents of the briefing session / interview designated to be canceled and the cancellation should be confirmed (step 345).

A cancellation confirmation screen is displayed on the student client 7 (step 355). When the student inputs confirmation of cancellation (step 356), the fact is sent to the server 2 (step 357).

The student web server 2 cancels the student's application for the briefing / interview (step 34).
6), send a cancellation completion notification screen (step 34)
3). This screen is displayed on the student client 7 (step 358).

(8) Mail management processing, mail transmission processing, received mail list processing, transmitted mail confirmation processing (transmission contents confirmation processing, unknown mail confirmation processing, unknown mail association processing,
Email update processing)

FIG. 52 shows the mail management process.
Basically, the mail management process is started by clicking the mail management character on the menu screen (FIG. 11) (FIG. 9, step 25). Unknown mail confirmation processing described later (Fig. 5
The process also transitions to the mail management process from the unknown mail list screen (7) of (7). Email management processing is corporate client 5
(Or the agency client 6) and the enterprise web server 1 (and the mail server 3). Email means electronic mail (e-mail).

When the corporate client 5 (6) transmits to the corporate web server 1 a message indicating that a character or button for mail management is clicked, the server 1 accesses the transmitted mail table (FIG. 7A). A list of all stored outgoing mails is created (step 361).
The server 1 transmits the mail management screen including the transmission mail list to the client 5 (6) (step 362).
), A mail management screen as shown in FIG. 61 is displayed on the client 6 (5) (step 371).

This mail management screen includes the outgoing mail list created in the server 1. The transmission mail list includes the subject, date and time (transmission date and time), transmission destination (group name or student name), transmission number (for the above, refer to the transmission mail table), reply number and unread number. The number of replies is counted with reference to the received mail table (FIG. 7B). That is, the number of received mails associated with the transmitted mail is the number of replies. The unread number is counted by referring to the read section. A transmission mail ID is attached to the head of the subject. For example, the eight-digit number “04131318 Thank you for your application” on the first line is the transmitted mail ID (assigned by the server 1 when transmitting the transmitted mail).

[0338] When a cell in which the number of replies or the number of unread messages is displayed in the desired subject column of the transmitted mail list is clicked, the reception of the mail (received mail) returned to the transmitted mail of the subject is performed. Proceed to mail confirmation processing (step 372). When the cell of the subject is clicked, the process proceeds to the transmission content confirmation processing for the transmitted mail (step 373). Click the “Unknown mail” button at the top of the screen to check the unknown mail (step
374). When the button of "update to the latest information" is clicked, the process moves to the mail update process (step 375). FIG.
As described in the company information master, the member company has an e-mail address. Incoming mail is stored in the mailbox of each company in the mail server 3, and the process of taking the received mail into the database 8 of the corporate server 1 is a mail updating process. The mail update process is executed when is pressed. The date and time of the last update (including hours, minutes, and seconds) is also displayed on the mail management screen. Checking the box to the left of the subject and pressing the "Delete" button sets a deletion flag in the corresponding outgoing mail table.

FIG. 53 shows the transmission content confirmation processing. The client 5 (6) sends a notification of the transmission content confirmation specifying the subject, and upon receiving the notification, the server 1
Reads out the transmission contents (text) from the transmission mail table of the corresponding subject (step 381). The read text is transmitted from the server 1 to the client 5 (6) together with the transmission content screen (step 382).

FIG. 62 shows an example of the transmission content confirmation screen displayed on the display device of client 5 (6). On this screen, the destination, the subject, and the text of the mail (text) are displayed, and a “Resend” button appears. The user (person in charge of the company) checks the text of the e-mail and can finish the processing here (close the file).

After confirming the text of the mail, the user can correct the text of the mail, change the transmission destination, etc., and proceed to the transmission of the mail. For example, if you send an email to a specific group of students, but the number of replies is very small, send the same email body (or add a reminder text) to the same group of students, Transmission, etc. can be performed. In addition, a new mail body can be created (or corrected) using the mail body sent in the past, and sent to students in other groups.

In such a case, the user clicks the “Retransmit” button on the transmission content confirmation screen shown in FIG. 62 (step 392). Then, the mail information including the message that the resend button was clicked and the mail text is displayed on the server 1.
(Step 393).

The server 1 edits the mail creation screen using the received mail information and transmits it to the client 5 (6).
The mail creation screen as shown in 63 is displayed (Step
394).

The mail creation screen shown in FIG. 63 differs from the transmission content screen shown in FIG. 62 in that one or a plurality of destinations can be input. When you pull down the box for the destination, a list of group names that have already been set appears. In this list, one or more groups to which the mail should be sent can be specified. Of course, it is also possible to enter the student's personal name as the destination.
In addition, the body of the mail can be modified or changed. These are performed in the mail transmission process (step 89). The mail transmission processing will be described later.

The characteristic of the example of the mail text in FIG. 62 or 63 is that the URL (address) of the corporate server is entered in the mail text. This e-mail text is a guide for the briefing. A student who has received such a briefing session guide by e-mail can access the corporate server 1 using the URL of the corporate server, and can immediately proceed to the briefing session / interview application described above.

FIG. 54 shows the received mail confirmation processing.
The received mail confirmation process is started by clicking on the number of replies or unread cells on the mail management screen (FIG. 61) and notifying the user and the subject of the transmitted mail from the client 5 (6) to the server 1.

The enterprise server 1 searches the received mail table (FIG. 7B) based on the subject of the transmitted mail notified from the client 5 (6), and retrieves the received mail corresponding to the transmitted mail of the subject. , The list is created (step 401). The server 1 creates a received mail confirmation screen including the received mail list and sends it to the client 5 (6).

At the client 5 (6), a received mail confirmation screen as shown in FIG. 64 is displayed (step
411). This screen contains the subject of the outgoing mail “041311318 Thank you for your application” and the received mail list. The received mail list includes the sender (the student's name is known from the student ID), the university name of the university to which the student belongs, and the date and time of reception.

When the subject of the outgoing mail is clicked, the flow proceeds to the outgoing mail transmission contents confirmation processing (step 372).
The received mail can be deleted by using the “Delete” button. Click on the sender's cell to get more information about the student. When you click the cell of the reception date and time,
The received mail corresponding to the received date and time is selected (step 412), and data indicating the selected received mail is transmitted from the client 5 (6) to the server 1 (step 413).

The server 1 reads the received mail table of the selected received mail (step 403) and transmits the contents to the client 5 (6) as a received content screen (step 404). A reception content screen as shown in FIG. 65 is displayed (step 414)
).

[0351] The sender (student's name,
(Student ID and sender email address), subject, date and time of reception, and text of received mail are displayed. Also, a "Reply" button and an "Email link" button appear.
When the “mail association” button is pressed, the process proceeds to the unknown email association process (step 419), but the example in FIG. 65 is not directly related because it is not an unknown email. The unknown mail association process will be described later.

The "reply button" is pressed when creating a reply mail to the received mail or when creating other mails. When the "Reply" button is pressed (step 41
5), that fact and the received mail information
It is transmitted from (6) to the server 1 (step 416). The server 1 creates a mail creation screen based on the received information and sends it to the client 5 (6) (step 405).

The client 5 (6) displays a mail creation screen as shown in FIG. 66 (step 417). This e-mail creation screen differs from the e-mail creation screen shown in FIG. 63 in that the e-mail address of the sender (student) of the received e-mail is entered as the transmission destination. The transmission destination depends on what process (or screen) has changed to the mail creation screen. Of course, it is also possible to correct the transmission destination. Using this mail creation screen, the user can perform mail transmission processing (step 89).

FIG. 55 shows the transmission mail confirmation processing.
This sent mail confirmation processing is started by clicking the sent mail confirmation character on the profile screen of FIG. 33 and notifying the server 1 of the click (step 207 in FIG. 27).

[0355] The profile screen is a display screen of information about a specific student. Since the student ID of the student is sent from the client 5 (6) to the server 1, the corporate server 1 sends the mail using the student ID as a key. The table is searched and a list of all outgoing e-mails for the student is created (step 421). The outgoing mail confirmation screen including this outgoing mail list is displayed from server 1 to client 5 (6).
(Step 422), a screen as shown in FIG. 67 is displayed (step 431). The outgoing mail list displayed on this screen includes the subject and the date and time. Clicking on the subject cell will select the subject email. A specific mail can be deleted by a “delete” button.

When the transmission mail is selected by clicking the subject (step 432), the subject and the student ID are transmitted to the server 1, and the process proceeds to the transmission content confirmation processing described above (step 372) (see FIG. 53). .

The received mail list processing shown in FIG. 56 is also started by clicking a character in the received mail list on the profile screen. The server 1 receiving the click of the received mail list and the student ID searches the received mail table using the student ID as a key and creates a list of received mails including the corresponding student ID (step 44).
1). Since the received mail list screen including the created received mail list is transmitted from the server 1 to the client 5 (6) (step 442), the client 5 (6) receives the message shown in FIG.
The received mail list screen including the received mail list as shown in (1) is displayed (step 451).

The subsequent processing is the same as the received mail confirmation processing shown in FIG. 54 (steps 443 to 445 in FIG. 56 and steps 403 to 405 in FIG. 54, steps 452 to 457 and 89 in FIG. 56 and FIG. 54).
Compare steps 412 to 417, 89, respectively.)

FIG. 57 shows the unknown mail confirmation processing.
The unknown mail confirmation process is performed on the mail management screen in Fig. 61.
It starts when the "Unknown mail" button is pressed.

When the client 5 (6) notifies the server 1 that the "unknown mail" button has been pressed, the server 1 searches the received mail table for an unknown section and determines that the received mail table is classified as unknown (transmission Then, a list (unknown mail list) is created (step 461). The server 1 displays the unknown mail screen including the unknown mail list on the client 5
It is transmitted to (6) (step 462).

At the client 5 (6), an unknown mail confirmation screen as shown in FIG. 69 is displayed. Unknown mail is managed for each date and time of reception. The unknown mail list displayed on the screen in FIG. 69 shows the number of received mails and the number of unread mails corresponding to the reception date (reception date and time). This screen also has a “mail management” button, so that the user can proceed to the mail management processing.

When the user wants to know the details of the unknown mail, the user clicks a desired reception date in the unknown mail list (step 472). Since the clicked reception date is sent to the server 1 (step 473), the server 1 reads out the information except the text of the corresponding received mail from the received mail table, and creates a list thereof (step 46).
3). Since an unknown mail list screen including a list of unknown mail information is sent from server 1 to client 5 (6) (step 464), the screen shown in FIG. 70 is displayed (step 474).

On the unknown mail list screen of FIG. 70, a list including the reception date, the sender, the school name, the reception date and time, and the subject of the unknown mail is displayed. In addition, a “mail management” button and a “delete” button are displayed on the screen of FIG.

As described above, the unknown mail does not include the transmission mail ID in the subject, and the transmission destination address indicating the sender does not match the mail address of the student information master (as a result, the student ID is unknown). Many).

When the user wants to know the contents of a specific received mail in the unknown mail list, he clicks on the subject cell (step 475). The clicked subject is sent from client 5 (6) to server 1 (step
476). The server 1 specifies the received mail using the subject and the received date, extracts data including the text of the received mail from the received mail table, and sends it to the client 5 (6) as a received content confirmation screen (step 465).

[0366] The client 5 (6)
Display a received content confirmation screen like 65 (Step 477
). The user can send e-mail from this screen (step 8
9) Or the unknown mail association process (step 419) can be performed.

FIG. 58 shows an unknown mail association process (step
419). A reception content confirmation screen as shown in FIG. 65 is displayed on the display device of the client 5 (6). In the case of an unknown mail, the transmission mail ID is not described in the subject column. Also in the sender column, there is a case where a message whose source mail address does not match the mail address of the student information master is displayed, or a student ID is not displayed.

[0368] The unknown mail association is that the user writes the outgoing mail ID in the subject column and the student ID in the sender column, and finally associates (associates) with the outgoing mail. is there.

After reading the contents of the received mail, the user, for example, sees a mail management screen (list of transmitted mails) as shown in FIG. 61 and is convinced or corresponds to the received mail which is an unknown mail. Look for outgoing mail that is likely to be. Then, the outgoing mail ID of the found outgoing mail is entered in the subject field of the received content confirmation screen. Also, the student's name (in the body of the received email)
The student information master is searched using the as a key, the student ID is obtained, and the student ID is entered in the sender field (step 491).
). Thereafter, the "mail association" button is clicked (step 492).

The subject (including the outgoing mail ID) and the student ID entered together with the information on the received mail are sent from the client 5 (6) to the server 1 (step 493).
). When receiving this information, the server 1 writes the outgoing mail ID and the student ID in the corresponding received mail table which has been positioned as an unknown mail, and determines that the data of the unknown category is not an unknown mail (step
481).

Thereafter, the server 1 edits the information of the corresponding received mail table into a received content confirmation screen and sends it to the client 5 (6) (step 482), and the client 5 (6) displays the screen shown in FIG. Is displayed (Step 49
Four ). The user can confirm that the fields such as the sender and the subject are correctly described.

FIG. 59 shows the mail update process. The mail update processing is mainly performed in the enterprise server 1 in response to the pressing of the “update to latest information” button on the mail management screen of FIG.

The corporate mail server 1 issues a request to the mail server 3 to have the received mail stored in the mailbox of the mail address of the company be transmitted. When the received mail transmitted by the mail server 3 is received (step 501), it is checked whether each received mail can be taken into the sub database 9 (step 502). For example, it is determined that the mail body having a predetermined number of words or more, a file having an attached file, and the like cannot be stored in the sub-database 9.

With respect to the received mail that can be taken into the sub-database 9, it is determined whether the source address of the received mail matches the mail address registered in any of the student information masters (step 503).
If the e-mail address matches, then it is checked whether the data included in the subject in the received e-mail matches the outgoing e-mail ID in one of the outgoing e-mail tables (step 504). A received mail having a subject including data matching any of the transmitted mail IDs can be associated with the transmitted mail, and a received mail table is created for the received mail (step 50).
Five ). Outgoing mail IDs and student IDs are written in the received mail table, and it is described that an unknown category can be associated.

Incoming mail having a sender address that does not match any of the registered student's mail addresses and receiving mails whose entire or part of the subject does not match any of the sending mail IDs in the sending mail table are classified as unknown. A received mail table is created describing an unknown mail (steps 507 and 506). The sent mail ID is not described in this received mail table. The date and time at that time is set as a mail update date and time (corporate information master) (step 508), and a list excluding unknown mails among the received mails fetched from the mail server 3 is created and incorporated into the mail management screen and the client 5 (6)
Send to The client 5 (6) displays a screen as shown in FIG. 61 (step 521).

The mail update process performed in the early morning is the same as in FIG. 59, but the transmission of the mail management screen (step 509)
Is not performed.

The received mail determined not to be taken into sub database 9 is forwarded to the person in charge of the company or error processing is performed (step 510).

[0378] Finally, the mail transmission processing will be described.
Search result display screen (group operation screen) (Fig. 21), group operation screen (Fig. 30, Fig. 31), profile screen (Fig. 3
3) and briefing / interview confirmation display screen (Figure 37, Step 2)
In step 94), in response to the mail transmission being clicked, the flow transits to the mail transmission process. In this case, FIG.
1 is sent from the server 1 to the client 5 (6) and displayed on the client 5 (6) (step 540). In addition, the mail transmission process consists of a mail creation screen (Figs. 63 and 66) and a reception confirmation screen (Fig. 6
Started in 5).

On the mail creation screen, a mail body is created or corrected, and a destination is set, changed or added (step 541). "Verification"
When the button (FIGS. 63 and 66) or the "reply" button (FIG. 65) is clicked (step 542), information such as the created mail text and the destination is transmitted from the client 5 (6) to the server 1. (Step 543).

The server 1 checks whether the number of words in the received mail text is within a predetermined number (step 531).
), If within a predetermined number (YES in step 532),
The transmitted mail information including the received mail text is transmitted to the client 5 (6) as a mail confirmation screen as it is (step 533). If the number of words exceeds the predetermined number, the client is notified of the fact and the mail text is recreated (step 539).

[0381] A mail confirmation screen is displayed on the client 5 (6). Since this screen is provided with a "Send" button, when the user clicks the "Send" button (step 545), the contents of the mail confirmation screen are sent to the server 1 (step 546).

The server 1 issues a transmission mail ID (step 534), creates a transmission mail table using the created transmission mail information, and stores it in the sub database 9 (step 535). Further, the server 1 edits the outgoing mail information into a mail format (step 536), and the mail server 3
(Step 537). If the destination input on the mail transmission screen is a group name, the server 1 specifies the student belonging to the group by referring to the group registered student table, and further refers to the student information master to specify all the students belonging to the group. Get email addresses about students and subscribe to each outgoing email. Similarly, when the transmission destination is only the name, the server 1 obtains the mail address from the student information master and uses the mail address for editing the mail. Mail server 3
Sends outgoing mail to the destination address. The server 1 creates a transmission completion screen, sends it to the client 5 (6) (step 538), and displays it on the client 5 (6) (step 547), so that the user can confirm that the mail has been transmitted.

The server executes the above-described processing according to programs such as an employment management program, a server OS, and a server web browser installed on the server. The function of creating and transmitting data (file) for displaying an image to a client is mainly executed by a web browser. The process of storing the received data in a database or the like is executed by the OS. Therefore, in a strict sense, the recruitment management program executes processing excluding the parts executed by the web browser and the OS in the processing represented by the illustrated flowchart. Since it is the recruitment management program that puts the data in a transmittable state or instructs data storage, it can be understood that the processing represented by the illustrated flowchart is executed substantially according to the recruitment management program. In this sense, the means and methods described in the claims are also realized by the recruitment management program. This specification also discloses a re-expression of each means and method described in the claims as the contents of an employment management program and a medium on which the program is recorded.

(9) Another Embodiment Another embodiment will be described.

Contents of Database FIGS. 72 to 77 show details of the contents of the sub-database 9 for each company which are different from those in the above embodiment and which are added.

The student information master shown in FIG. 72 includes, in addition to the information described in the student information master shown in FIG. 3, a selection process display flag, an interviewer comment, a job offer notification date, a recruiter team ID, a recruiter team name, and a flag. , Submission documents, entry sheet evaluations, company free comments and contact status are recorded.

Selection process display flag This flag is used to set whether or not future selection information is to be displayed.

Interviewer Comment This is given to the student by the interviewer at the interview in each selection process.

Notification Date of Job Offer The company records the notification date of job offer to the student.

Recruiter Team ID, Recruiter Team Name There may be a case where a single company has a plurality of human resources teams. For example, a team in charge of ○ △ university, a team in charge of XX district, etc. The group of students that can be operated by one recruiter team is defined according to the team. The contents that the recruiter team can process (for example, browsing only) are also determined according to the team. The team name and the team ID are used to distinguish the personnel team.

Flag In each selection process, a person in charge of the company performs color coding according to information on the selection of students. For example, a student's (internal) impression or the like can be color-coded in a briefing session, an interview, or the like.

Documents to be Submitted Documents such as resumes, transcripts, and graduation prospect certificates that are submitted by students are recorded.

Entry sheet evaluation This is given to the student by the person in charge of the company. For evaluation, S, A, B, C, D, Z, PA, PB,
There is PD. This evaluation is recorded in the evaluation table shown in FIG.

[0394] Free comment for companies [0390] A person in charge of a company can freely enter a comment for a student.

[0395] Contact Situation This shows the state of contact between the student and the company during each selection process (specifically, the person in charge of the company, specifically, a member of the recruiter team talks with the student). Contact status names include job offer, contact, absence, decline, reject, and no contact. This contact status is recorded in the contact status table shown in FIG.

In the contact situation table shown in FIG. 73, information on the contact situation is registered. That is, the contact status ID and the contact status name are stored in this table.

FIGS. 74 (A) and (B) show FIGS. 5 (A) and 5 (B).
It corresponds to.

In the group management table shown in FIG. 73A, information of a group management type name and a use distinguishing name is recorded in addition to the information of the group management table shown in FIG. 5A. The group management type name indicates whether the group is a fixed group or a variable group.

As described above, a group designates a condition or range, and a student meeting the condition or range is extracted from students recorded in the student information master, or a logical operation between groups is performed. Formed by (number table processing, screening processing, briefing / interview situation processing,
Group join processing). Even if the conditions or range for forming a group are the same, if the student information recorded in the student information master changes, the student whose information has changed may belong to or be excluded from the group. For example, if the student's information changes due to the result of a briefing / interview, etc., if the student registers the student information, obtains a qualification and updates the student information accordingly, TOEIC, T
This is the case, for example, when a student with a higher score in the OFFL changes the registered information. Such a process of re-creating a group according to the change of the student information of the student information master is called a group update process (variable group update process). The group to be subjected to this group update processing is a variable group.
Fixed groups are not subject to group update processing. In other words, the group update process is performed only for a group whose group management type name is a variable group.

[0400] The use distinguishing name indicates the use of the group for the user (person in charge of the company) to manage the group, and the classification includes no classification, selection process, and mail. If the group is segmented in the selection process, this group is used to indicate that there is a deliverable in the next selection stage, etc. It is used to indicate a notice or notice at the next selection stage. If there is no particular need to identify the application, there is no classification.

The group registered student table shown in FIG. 74 (B) is the same as the group registered student table shown in FIG. 5 (B).

The recruiter team table shown in FIG. 75A is provided for each recruiter team, and registers information about the recruiter team. That is, in this table, the recruiter team major classification name, the recruiter team major classification ID, the recruiter team minor classification name, the recruiter team minor classification ID, the narrowing-down condition ID, the number of affiliation students, the affiliation student ID, and the student's reading (surname, Name), school name, department, selection process name, briefing session / interview ID, evaluation and evaluation comment are stored. Examples of the recruiter team's large classification include universities and business establishments, and examples of the recruiter team's small classification include ○ if the major classification is by university.
× University, XX University, etc. The student group that can be operated (accessed) by the recruiter team is determined by the narrowing condition ID.

A recruiter user account table shown in FIG. 75 (B) is provided for each person in charge of the recruiter team (user), and information on the user is registered. This table stores a user ID, a user name, a user password, a user authority level, a large classification ID of a recruiter team in charge to which the user belongs, and a small classification ID of a recruiter team in charge. The user ID, user name, and user password are used at the time of logon (login) when accessing the corporate web server 1. The user authority level is a numerical value indicating the position of the user and has 1 to 7 levels. The range of recruiter teams to which the user authority has is determined by numerical values. For example, a user of numerical value 1 is only one recruiter team of a small classification, and a numerical value of 7
Users range up to three recruiter teams.

[0404] The user setting table shown in FIG. 75 (C) is provided for each user, and information on user settings is registered. That is, this table stores a user ID, a user name, a department, a user authority level, a user password, and a memo. The department to which the user belongs is the department to which the user belongs in the company.

The narrowing-down condition table shown in FIG.
The quick-reference table data table shown in (B) and the delivery table shown in (C) are the narrowing-down condition table shown in FIG.
It is basically the same as the quick look-up table table shown in (B) and the delivery table shown in (C), except that the recruiter team minor classification ID is added in the narrowing-down condition table of FIG. 75 (A). . The narrowing conditions (that is, groups formed by the conditions) and the recruiter teams are linked by the recruiter team minor classification ID.

FIGS. 77A and 77B show a newly added table.

The evaluation table of FIG. 77 (A) stores data related to evaluation in the student information master (FIG. 72), and describes an evaluation ID and an evaluation name. The evaluation includes S, A, B,. Where P
A of A, PC and PD indicates that the evaluation is suspended.

The flag table in FIG. 77 (B) shows the contents of the flags in the student information master (FIG. 72). The flag is for displaying the student ID in different colors, and the flag table includes a flag ID and a flag name. The flag name represents a color, for example, standard (black), red, blue,.

[409] The prefecture master, school master,
Undergraduate master, desired job master, desired work location master, desired course master, selection process master, briefing session / interview table shown in FIG. 6, briefing session / interview applicant table, briefing session / interview venue master, and transmission shown in FIG. The mail table and the received mail table are used as they are in other embodiments.

FIG. 78 shows the entire processing of the hosting web servers 1 and 2 according to another embodiment.

[0411] The processing of the web servers 1 and 2 is basically the same as the processing of the web servers 1 and 2 of the hosting site in FIG. 9 described above, but will be described later by making a selection according to the guidance on the menu selection screen. The difference is that the process can proceed to the recruiter team registration process (step 165) and the recruiter team setting process (step 750).

In all the flowcharts described below including FIG. 78, the same processes as those already described (or can be evaluated as the same) are denoted by the same reference numerals, and redundant description will be avoided.

FIG. 79 shows the procedure of a narrowing-down process in another embodiment. The narrowing-down process shown in FIG. 79 is basically the same as the narrowing-down process shown in FIG. 16 described above. However, after the search result display (step 84A), the process can also proceed to the recruiter team registration process (step 165). Are different. As other processes, the process can proceed to a download process and a batch data registration process described later.

In the narrowing-down screen shown in FIG. 86 displayed on the display device of the client 5 (6) (step 81A),
If the “call” button of the condition call item displayed at the top is pressed when the narrowing conditions are already saved, the narrowing condition is called (step 85A, see FIG. 82).
Proceed to. Also, on the refinement screen (Fig. 86),
81A), enter the refinement conditions (step 82), and press the “Save New” button in the condition save section, or add the refinement conditions (step 82) and press the “Save” button to refine. The process proceeds to the condition storing process (step 86A, see FIG. 80).

Also, the narrowing-down screen (FIG. 86) (step 81)
When the "New" button of the variable group item is pressed in A), the process proceeds to a new variable group creation process (see FIG. 81). If the “update” button is pressed, the process proceeds to the variable group update process (see FIG. 83).

Note that the input field of the narrowing condition displayed on the narrowing screen shown in FIG. 86 is the same as the input field of the narrowing condition shown in FIG. 20 described above.

[0417] The user (person in charge of the company) selects the narrowing-down screen (Fig.
At 86), the narrowing-down condition is input (step 82), and the "search" button is pressed to perform the narrowing down process (step 8)
3, 72, 73, 74).

As a result, the client 5 (6)
Is displayed (step 84A).

FIG. 80 shows the narrowing-down condition storing process (step 86).
This shows the procedure of A). The difference from the narrowing condition storage processing shown in FIG. 17 is that the narrowing screen is displayed (step 103).
A, a screen similar to that in FIG. 88) and the narrowing-down screen allow the process to proceed to the new variable group creation process (step 104) (FIG. 81).

FIG. 81 shows the new variable group creation process (step 104).

On the narrowing-down screen of FIG. 88, after the user inputs the narrowing-down conditions (step 82), the name of the variable group is input in the box of the condition storage item at the top, and the “new creation” of the variable group item is entered. Press the button (step 551)
). Then, the input variable group name is transmitted from the client 5 (6) to the server 1 (step 552).
(The narrowing-down conditions have already been transmitted in step 102 in FIG. 80).

The corporate web server 1 searches the sub-database 9 in accordance with the received narrowing-down condition, and extracts students matching the narrowing-down condition (step 561). The server 1 transmits the search result (the list of the extracted number of people, the extracted first and last names of the students, the student ID, the school name, the department, etc.) to the client 5 (6) together with the display screen (step 562).

Then, in the client 5 (6),
A search result screen is displayed (step 553). On this screen, only the number of applicable persons (the number of extracted students) is displayed.

The search result screen is almost the same as the screen shown in FIG. 87, and “* NO-NAM
E "is displayed. For a variable group, “*” is displayed before the variable group name. In the box of the storage section, the name of the previously entered variable group is entered. In addition, the user can check one or both boxes of the selection process or the mail of the classification item, and classify the variable group. If no division is made, the box without division is checked (the box without division is checked from the beginning). Press the "Save New" button in the Save section (step
554), and the displayed variable group name and category (usage category) are transmitted to the server 1 (step 555).

In the server 1, a group management table and a group registration student table (FIGS. 74 (A) and (B)) are created using the extracted student data, the group ID thereof, and the input variable group name. Step 56
3), the group formed by the narrowing down process is stored as a variable group (step 564). In the group management table, data “variable group” is stored as the group management type name.

[0426] A variable group name different from the variable group name input in step 551 may be entered in the box of the storage section of the search result screen displayed in step 553. In this case, the variable group is saved with the variable group name input on the search result screen.

The server 1 sends the change group management screen to the client 5 (6) (step 565). The change group management screen shown in FIG. 89 is displayed on the display device of the client 5 (6) (step 556).

FIG. 82 shows a narrowing-down condition calling process (FIG. 79, FIG. 80, step 85A) in another embodiment.
This processing is shown in FIG. 79, the narrowing screen of step 81A (FIG. 86)
Alternatively, the process transits from the narrowing-down screen of step 103A in FIG.

The narrowing-down condition calling process shown in FIG.
18 is different from the narrowing condition calling process shown in FIG. 18 in that the process can proceed to the new changing group creation process (step 104) and the changing group update process (step 124) in the narrowing screen display (step 123A) shown in FIG.

FIG. 79, step 81A or FIG. 80, step
When pulling down the box on the left side of the "call" button of 103A, a list of all narrowing condition names (including reception condition names) that have already been set (set in the narrowing condition table) is displayed as shown in FIG. 90. (When the corporate web server 1 transmits the narrowing-down screen to the client, it also sends a list of narrowing-down condition names that have already been set). When the user selects a desired narrowing condition name from this list (step 121A), a narrowing condition calling process is executed (steps 122, 111, 112).

As a result, a narrowing-down screen as shown in FIG. 88 is displayed on the display device of the client 5 (6). From this refinement screen (Fig. 88), the refinement process (step 2
It is possible to proceed to 1), the narrowing-down condition storing process (step 86A), the new variable group creating process (step 104), and the variable group updating process (step 124).

FIG. 83 shows the variable group update processing. This processing is performed by selecting the narrowing screen shown in FIG. 88 (see step 123A in FIG. 82, and FIG. 85 and step 144A described later).
See)).

On the narrowing-down screen (FIG. 88), the “update” button of the item of the variable group is pressed (step 571). Then, the narrowing conditions and narrowing condition names displayed on the narrowing screen are transmitted from the client 5 (6) to the server 1 (step 572).

In the server 1, the sub-database 9 searches the received narrowing condition table having the narrowing condition and the narrowing condition name, reads the corresponding group ID (step 581), and reads the group management table having the read group ID. It is determined whether or not it is a variable group from the data of the group management type name stored in (step 582).

If it is not stored as a variable group (NO in step 582), an error message is transmitted to client 5 (6) (step 583), and a message to that effect is displayed on client 5 (6) (step 574).
).

If it is stored as a variable group (YES in step 582), a narrowing search of the student information master is performed based on the narrowing conditions (step 584).

The student information in the group registered student table having the above group ID is rewritten based on the result of the narrowed search (step 585). Further, the number of students belonging to the group management table having the group ID is rewritten (step 586). Data for displaying the fluctuating group update screen is transmitted to the client 5 (6) (step 58).
7).

The client 5 (6) displays a variable group update screen as shown in FIG. 91 (step 575).
). This screen displays the group name and the number of people who belong to the groups before and after the variable group update process.

When the character string "to group management" is clicked on the variable group update screen, the selection of group management is transmitted from client 5 (6) to server 1 (step 576).

Upon receiving the group management selection, the server 1 transmits a group operation screen to the client 5 (6) (step 588). Client 5 accordingly
A group operation screen is displayed on the display device (6) (step 577).

The group operation screen is the same as the screen shown in FIG. 89, and the user can narrow down the processing (step 21), send mail (step 89), combine the group (step 24), and perform the corresponding person list processing (step 24). 166) and recruiter team registration processing (step 165).

If the above-described variable group update processing is automatically performed (batch processing), the briefing / interview setting processing (step 28) or the mail transmission processing (step 89)
(For example, see FIG. 78), there is no need to search for a new student, and these processes can be executed quickly.

FIG. 84 shows a batch process for updating a variable group. This batch process is executed periodically (for example, every day at midnight).

This batch processing is performed by the DB server 4 (of course, it may be performed by another server 1, 2, or 3). The DB server 4 searches for a group management table indicating that the group management type name is a variable group, and reads a group ID from the group management table (step 591). Group I read
The narrowing-down condition is read from the narrowing-down condition table based on D (step 592), and a narrowing-down search is performed on the student information master according to the read-out narrowing-down condition (step 584). Based on the result of the refined search, the student information in the group registered student table having the corresponding group ID is rewritten (step 585). Further, the number of students belonging to the group management table is rewritten (step 586). This batch process is performed for all group management tables whose group management type names indicate variable groups.

FIG. 85 shows the processing executed when the narrowing-down condition management processing (FIG. 78, step 22) is selected on the menu screen. In the narrow-down condition management process shown in FIG. 85,
After the same processing as the narrowing-down condition management processing shown in FIG. 19 is performed, the narrowing-down screen as shown in FIG. 88 is displayed on the client 5 (6).
(Step 144A). From this screen, in addition to the narrowing-down process (step 21) and the narrowing-down condition storing process (step 86A), the process can proceed to a new changing group creating process (step 104) and a changing group updating process (step 124).

FIG. 92 shows the procedure of group management processing in another embodiment. In the group operation screen shown in FIG. 89, the process can proceed to the recruiter team registration process (step 165), the download process (step 167), and the batch data registration process (step 168).

When the user selects group management on the menu screen (FIG. 11) (FIG. 9, step 23), a message to that effect is transmitted from the client 5 (6) to the corporate web server 1. In response, the server 1 searches the group management table (FIG. 74 (A)), and finds out the group names and update dates and times of all the groups that have already been created (update date: year, month, day, time). , Minutes, and seconds), usage classification (no classification, selection process, e-mail), and the number of students (number of respondents)
Is created (step 151), the group management screen including this list is modified and transmitted to the client 5 (6) (step 152).

In the client 5 (6), a group management screen as shown in FIG. 98 is displayed on the display device (step 161A). This screen displays the above list.

[0449] On the group management screen, pulling down the upper box of the upper and lower two boxes at the top, lists the application category (selection process, mail, etc.), and pulling down the lower box, the group management type name (fixed group) , Fluctuating group) appears. The user selects a desired use category or group management type name from this list (step 162), and presses a "select" button on the right side of the box of the selected row, and the fact is transmitted to the server 1 (step 162). Step 163). The server 1 reads out data on the corresponding group (step 153),
Since the read operation screen of the group is transmitted to the client 5 (6) (step 154), the group operation screen of FIG. 89 is displayed (step 164A).

In the download process (step 167), the user selects a specific data item of the specific student information,
That is, data of the selected student item is downloaded from the server 1 to the client 5 (6) as a CVS format file. The user can save the selected data item or combination thereof under a specific name.

The following data items can be selected.

Personal information such as student ID, Yomigana (surname), Yomigana (first name), last name, first name, gender, date of birth, mail address, current address, current address telephone number, home address, home address. School information such as school name, undergraduate school, department, and humanities division. Corporate information such as reception media, selection process name, evaluation, evaluation comment, and recruiter team name.

In this case, the data of the downloaded item can be corrected and then uploaded to the server 1 to correct the student information master.

FIG. 93 shows the procedure of the group storing process (step 87 in FIG. 92) in another embodiment. In the group storing process of FIG. 93, the user inputs a group name and selects a use category (step 181A). Client 5 (6) displays information on the usage category along with the group name
Is transmitted to the server 1 (step 182A).

[0455] The server 1 issues a new group ID for the input group name, creates a new group management table and a group registration student table including data relating to groups such as use classifications, and stores them in the sub database 9. (Step 171A). The group management type name is a fixed group.

After that, the server 1 creates a group operation screen including data on the registered group and transmits it to the client 5 (6) (step 172A).

As a result, the group operation screen shown in FIG. 89 is displayed on the display device of the client 5 (6) (step 183A), and the user operates the recruiter team registration processing (step 165) on this screen to register the collective data. Processing (step 168), download processing (step 167)
), It is possible to proceed to other processing.

The user can change only the purpose of use. In this case, call the group for which you want to change the usage category, enter a check in the box of the category that you want to change in the box of no category, selection process and e-mail, and press the “Overwrite category” button. Good.

FIG. 94 shows the procedure of the applicable person list processing in another embodiment. The hit list processing in FIG. 94
Basically, the process is the same as that of the hit list shown in FIG. 27, and the process can proceed to the flag setting process (step 209) in the hit list display (FIG. 99) (step 201A).

[0460] On the display screen of the client 5 (6),
The hit list screen as shown in 99 is displayed (step
201A). On this screen, the names (first and last names), school names, departments, departments, and telephone numbers of the students belonging to a specific group are displayed in the form of a list.

A flag setting box and a "GO" button are arranged at the top of the corresponding person list screen.

FIG. 95 shows a flag setting processing procedure.

The flag setting registers the flag information in the student information master (FIG. 72). As shown in FIG. 77 (B), the flags represent information of all 12 colors (black, red, blue, green, yellow, pink, light blue, yellow green, purple, brown, orange, and gray). Before setting the flag, a black flag (default) is set.

[0464] The user can use the student ID as a criterion for recruiting students by coloring the student ID according to information on the selection process. For example, a student whose flag is set to red is an important candidate for a recruitment candidate, a student whose flag is set to blue has already been offered to another company, and a student whose flag is set to green has a particularly high degree of desire.

In the applicable person list screen shown in FIG. 99, a check is made in the box of the first cell in the column (line) of each student for whom a flag is to be set. Then, when pulling down the flag setting box of the information in the list, a list of flags appears as shown in FIG. The user selects a desired flag from this list, and selects “G” on the right side of the flag setting box.
The button "O" is pressed (step 601). The information of the selected student and the flag is transmitted to the corporate web server 1 (step 602).

The server 1 reads the flag information selected from the flag table (step 611), and sets (registers) the flag information in the corresponding student information master (steps 612, 613). After that, a corresponding person list with the flag set is created, and together with the corresponding person list, the client 5
It is transmitted to (6) (step 614).

The display screen of the client 5 (6) shows
A corresponding person list screen as shown in 101 is displayed (step 603). On the displayed screen, the student ID displayed to the left of the student's name is displayed in the set flag color. Note that the color of the flag can be used as a condition for the refined search.

FIG. 96 shows the procedure of the group combining process in another embodiment. The same process as the group combining process shown in FIG. 28 is performed, and then the group operation screen shown in FIG. The display can be displayed on the display device (6) (step 183A), and the process can proceed to recruiter team registration processing (step 165), batch data processing (step 168), download processing (step 167), and other processing.

In the above embodiment, the group combining process is performed by 2
A new group is formed by associating two groups with AND, OR, and NOT. By specifying three or more groups, these are combined by AND, OR, and NOT to form a new group. Is also good.

FIG. 97 shows a batch data registration process (step 168).
).

[0471] The batch data registration process is for selecting a pertinent person for each group for students belonging to the group of the company.
This is to register specific data in the student information master of the selected student in a lump. The specific data to be registered collectively includes the reception media (telephone, postcard, DM, etc.)
Registration and selection process (primary interview, secondary interview, final interview, etc.)
Application, evaluation (S, A, B, etc.), evaluation comment,
Interviewer's comment, submission documents (resume, transcript, graduation certificate, etc.) registration, free comment (free field), job offer notification date, decline, entry sheet (S, A,
B ... etc.) Forcible non-display of evaluation and selection process.

In the group operation screen display (FIG. 89) in step 183A of FIG. 96, the user calls a desired group for which data is to be registered collectively (the called group is displayed at the top of this screen). Thereafter, when the character of the batch data registration is clicked, data indicating that the user has selected the batch data registration is transmitted from the client 5 (6) to the server 1.

[0473] In response, the server 1 transmits an item selection screen to the client 5 (6) (step 621).
). The client 5 (6) displays an item selection screen as shown in FIG. 102 (step 631).

[0474] On this screen, there are items of reception media, documents to be submitted, free fields, notification date of job offer, decline, entry sheet evaluation, and compulsory selection process non-display. Items included in the selection process include selection process application, evaluation input,
There are rating comments and interviewer comments. There is a selection process box that shows a list of primary interviews, secondary interviews, final interviews, etc. when further pulled down. The user selects an item to be registered as a batch data from these items, selects a selection process (stage) from the list in the selection process box,
Press the "select" button (step 632). The selected item of the batch registration data is transmitted to the corporate web server 1 (step 633). Here, it is assumed that the selection stage is the primary interview and the selection process application is selected.

In response to the selection of the item of the batch registration data, the server 1 changes the selection process name of the primary interview already created from the selection process code indicating the selection stage of the selection process master (FIG. 4 (G)). Readout, briefing session with selection process name read out /
The information of the selection process name is read from the interview table (FIG. 6A), and a primary interview list (selection process name list) is created (step 622). Then, a selection process name list screen including this list is created and transmitted to the client 5 (6) (step 623).

In the client 5 (6), a selection process name list screen as shown in FIG. 103 is displayed on the display device (step 634). This screen shows the selection process name, date and time of the event (year, month, day, hour, minute), venue, number of applicants,
The number of applications and the status are displayed.

[0477] The user presses the "select" button of the cell on the rightmost side of the column of the selection process name for which the user wishes to perform batch data registration (selection process application) (step 635). Then, the selected selection process name is transmitted from the client 5 (6) to the server 1 (step 636).

The server 1 refers to the group registration student table for the students belonging to the group called in the group operation screen display (FIG. 89) shown in FIG. 96 and reads the student information (name, school name, undergraduate, (Department, telephone number, etc.) to create a list (step 624),
The data is transmitted to the client 5 (6) together with the batch data registration screen (step 625).

In the client 5 (6), a batch data registration screen as shown in FIG. 104 is displayed on the display screen (step 637). On the batch data registration screen, information on the selection process name at the top (selected in step 635)
And the corresponding person list at the bottom (the list created in step 623), and "Check all", "Clear all", "Batch application", and "Batch application" displayed between them
Buttons and included.

The user checks the box of the leftmost cell in the column (row) of the student for a desired student who wants to perform batch data registration (here, batch data application). The user will consider whether to check each of all the students displayed on the hit list. Lastly, the user presses the "batch application" button (step 638). Then, the information of the corresponding person's batch data registration (application for selection process) is transmitted to the server 1 (step 63).
9).

In the screen shown in FIG. 104, "Check all"
Pressing the button will select all the students displayed in the applicable person list, and pressing the "Clear All" button will cancel all selections. Further, when the “all application at once” button is pressed, all the students belonging to the called group in the operation screen display of FIG. 96 (FIG. 86) are registered collectively (application for the selection process).

The server 1 must apply to the student information master of the selected student in the student information master for the primary interview selection process (specifically, the primary interview and the briefing session as the selection process name). / Interview ID) is registered (step 626).

In the student information master, if an item that has already been registered is registered again by batch registration, an error occurs (step 627).

If there is no error, a batch data registration end confirmation screen is transmitted to the client 5 (6) (step 628), and the client 5 (6) displays the batch data registration end confirmation screen shown in FIG. (Step
641).

When an error occurs (Y in step 627)
In ES), a list of applicable students is created, and an error screen is transmitted to the client 5 (6) together with an error message (step 629).

In the client 5 (6), if the screen transmitted from the server 1 is an error screen (error screen in step 640), an error screen is displayed (step 640).
642) (not shown). On the error screen, a list of students for whom batch data cannot be registered is displayed, and the user can select the relevant student (step 643) and perform a download process (step 167). Thereby, the user can confirm why the batch data registration could not be performed.

In the item selection screen (FIG. 96), when the reception media, selection process application (evaluation comment, interviewer comment), submission document, free field, job offer notification date, refusal and selection process forced non-display are selected. Also, the same processing as described above is performed.

Recruiter team registration processing, recruiter team minor classification creation processing, recruiter team (major classification) quick reference table display processing, recruiter team (small classification) progress table processing, recruiter team user setting processing

FIG. 106 shows the recruiter team registration processing procedure. When the user selects the recruiter team registration process (FIG. 78, step 165), or clicks on the recruiter team registration character from the group operation screen of FIG. 89, the fact is transmitted from the client 5 (6) to the enterprise web server 1. Is done. Server 1 responds by
Search the recruiter team table (Fig. 75 (A)) to create a list of the recruiter team major categories that have already been created, the creation date and time (date created: year, month, day, hour, minute) and the number of students belonging Then, the recruiter team large classification list screen including this list is edited and transmitted to the client 5 (6) (step 652).

In the client 5 (6), a recruiter team large classification list screen as shown in FIG. 110 is displayed on the display device (step 661). On this screen,
The above list is displayed. The user inputs the desired new recruiter team major classification name in the box to the right of the character of the recruiter team major classification name arranged above the list on the screen shown in FIG. 110, and presses the “Create” button (step 662). The input new recruiter team major classification name is transmitted to the server 1 (step 663).

In the enterprise web server 1, the above step 66 is performed.
Give the recruiter team major classification name entered in 2 and issue a recruiter team major classification ID (step 653).
A new recruiter team table is created using the data on these recruiter teams (major categories) and stored in the sub database 9 (step 654).

[0492] Thereafter, the server 1 creates a recruiter team large classification list screen including data on the recruiter team (major classification) registered in step 654, and transmits it to the client 5 (6) (step 655).

In the client 5 (6), a list including the newly registered (created) recruitment team (major category) is added (a new recruiter team (major category) is added to the bottom line of the list in FIG. 110). Is displayed (step 664). In this screen, if the user checks the box on the left side of the list and presses the "Delete" button, the checked recruiter team (major category) is deleted from the recruiter team table. When you press the "Reverse" button located below the list, the check is cleared from the checked boxes, and the unchecked boxes are automatically checked. Clicking on the recruiter team major classification name displayed in the list will lead to a recruiter team minor classification creation process (step 665), which will be described later. ) It is possible to proceed to the quick reference table display processing (step 666).

FIG. 107 shows the procedure of the recruiter team minor classification creation process (FIG. 106, step 665).

When the user wants to create a recruiter team (small category) belonging to the recruiter team (major category) displayed in FIG. 110, the user clicks a desired recruiter team major category name in the list, and the client 5 ( From 6), a request to create a recruiter team minor classification and data representing the recruiter team major classification are transmitted to the corporate web server 1.

The server 1 reads out the recruiter team (major category) selected from the recruiter team table (step 671), and retrieves all recruiter teams (small category) already created as belonging to the recruiter team (major category). ) Recruiter team minor category ID, recruiter team minor category name, creation date and time (creation date: year, month,
A list of the day, hour, and minute) and the number of affiliated students is created (step 672), and the recruiter team small classification list screen including this list is edited and transmitted to the client 5 (6) (step 673) (recruiter newly) Team (major classification)
If you want to create a recruiter team (small classification) may not exist.)

In the client 5 (6), a recruiter team small classification list screen as shown in FIG. 111 is displayed on the display screen (step 681). The list is displayed on this screen. The user arbitrarily determines and inputs a four-digit ID to the right of the ID character in the recruiter team sub-category creation column arranged above the list on the screen shown in FIG. 111, and enters the desired ID in the box to the right of the name character. Enter a new recruiter team minor category name and press the "Create" button on the right (step 682). Then, the recruiter team minor category name and the recruiter team minor category ID are transmitted from the client 5 (6) to the corporate web server 1 (step 683).

The server 1 edits the narrowing-down condition input screen and transmits it to the client 5 (6) (step 674).

FIG. 112 is displayed on the display device of client 5 (6).
Is displayed (step 684). In FIG. 112, when the "call" button of the condition call item displayed at the top is pressed, the process proceeds to a narrowing condition calling process (step 85A, FIG. 82) to call the narrowing condition. In the box on the left side of the “register” button in the recruiter sub-category section, the recruiter team sub-classification ID and the recruiter team sub-classification name that have been input earlier are displayed. Also, the narrowing-down conditions displayed in FIG. 112 are the same as the narrowing-down conditions displayed in FIG.

The user inputs a narrowing-down condition calling process (step 85A) or a narrowing-down condition (step 685).
After confirming the displayed recruiter team minor category ID and recruiter team minor category name, the "register" button is pressed (step 686). If it is desired to change, the recruiter team minor category ID and the recruiter team minor category name may be rewritten, and the “register” button may be pressed. Then, the recruiter team small category registration information is transmitted from the client 5 (6) to the server 1 (step 687).

The server 1 receives the narrowing-down condition, the recruiter team minor classification name, and the recruiter team minor classification ID.
To create a recruiter team table (FIG. 75A) and store it in the sub-database 9 (step 675).
).

[0502] Thereafter, the server 1 creates a recruiter team minor classification list screen including data on the newly registered (created) recruiting team (minor classification) and transmits it to the client 5 (6) (step 676).

In the client 5 (6), information on the newly registered (created) recruiter team (small category) is displayed on the display screen of the recruiter team (small category) list shown in FIG. (Step 688). Figure
In step 111, when the "quick reference" button on the right side of the recruiter team major classification column displayed at the top is pressed, the recruiter team (major classification) quick reference table display processing (step 666)
Then, if the "progress" button on the right side of the recruiter team (small classification) list is pressed, the process can proceed to the recruiter team (small classification) progress table display processing (step 690).

If a check is entered in the box on the left and the “Delete” button is pressed, the checked recruiter team (small classification) is deleted from the recruiter team table. When you press the "Reverse" button in the list, the check is cleared from the checked boxes and the unchecked boxes are checked.

FIG. 108 shows the procedure of the recruiter team (small classification) progress table display processing.

In the list of recruiter teams (small categories) displayed on the screen of FIG. 111, when the “progress” button on the right side of the column of the desired recruiter team (small categories) is pressed (step 701), the fact is indicated. The data is transmitted from the client 5 (6) to the corporate web server 1 (step 702).

In the server 1, the recruiter team small classification ID of the selected (desired) recruiter team (small classification)
Is read from the recruiter team table (step 711).
), And reads out the narrowing-down condition ID of the corresponding recruiter team (small classification). The sub-database 9 (student information master) is searched according to the narrowing condition based on the read narrowing condition ID, and a student matching the narrowing condition is extracted (step 712). The extracted student ID, student name, school name, undergraduate school, contact status, selection process name, date (year, month, day), interviewer, evaluation, etc. are read from the student information master and the briefing / interview table. A list is created (step 713), and the recruiter team (small classification) progress table (table showing the progress of the selection of the students in charge of the recruiter team) including this list is edited and transmitted to the client 5 (6). (Step 714).

In the client 5 (6), a recruiter team (small classification) progress display screen as shown in FIG. 113 is displayed on the display device (step 703).

FIG. 109 shows the procedure of the recruiter team (major classification) quick reference table display processing. The recruiter team (major classification) quick reference table display process refers to the current application status of students to a specific company (registration status) and the status of applicants progressing to recruitment (progress status) (for example, seminars). (A person in charge of the company) for the recruiter team to quickly grasp the number of persons who participated in the program, the number of persons who participated in the interview, and the number of persons who passed the primary interview.

When the “quick look-up” button is pressed on the recruiter team major classification list screen shown in FIG. 110 or the recruiter team minor classification list screen shown in FIG. 111, the fact is transmitted from the client 5 (6) to the server 1. You.

The server 1 reads the recruiter team major classification ID from the recruiter team table (step 1).
731) The recruiter team (small category) belonging to the read recruiter team (major category) is read (step 73).
2). The narrowing-down condition ID of the recruiter team (small classification) thus read out is read, and the sub-database 9 (student information master) is searched according to the narrowing-down condition based on this.
Students matching the narrowing conditions are extracted (step 733).
Register (rewrite) the extracted students in the recruiter team table. Registered students with student information master (Fig. 72)
In the selection process, a recruiter team quick look-up table is created by counting the number of persons for each name (step 734).
Server shows recruiter team quick reference to client 5
It is transmitted to (6) (step 735).

At the client 5 (6), the recruiter team quick reference screen shown in FIG. 114 is displayed (step 741).

FIG. 115 shows the procedure for the recruiter team user setting process.

[0514] The recruiter team user setting process issues a user ID and a user password to a person in charge on the company side, sets an authority level for this person in charge, and restricts the management of the recruiter team according to the authority level. is there.
For example, a person with a low authority level manages one recruiter team minor classification, and a person with a high authority level manages three recruiter team major classifications. With this process, a recruiter user account table is created.

When the user selects the recruiter team user setting process (step 750 in FIG. 78), the fact is transmitted from the client 5 (6) to the corporate web server 1 (step 751).

At the client 5 (6), the user setting screen shown in FIG. 116 is displayed on the display device (step 761). The user enters the user ID, name, department, authority level, password, etc. of the person who wants to make user settings, and presses the "register" button (step 762). Then, the client 5 (6) transmits the input information to the server 1
(Step 763).

The server 1 creates a new recruiter user account table (FIG. 73 (D)) and stores it in the sub database 9 with data relating to the user ID, name, user password, and user authority level (step 752).
). Further, the server 1 retrieves the already created user ID, name,
A list of authority levels is created, and a user list screen including this list is edited and transmitted to the client 5 (6) (step 753).

At the client 5 (6), a user list screen as shown in FIG. 117 is displayed on this display device.

When the user presses the “execute” button on the right side of the authority level of the person who wants to make user settings on the screen shown in FIG. 117 (step 765), the client 5
The message is transmitted from (6) to the server 1 (step 766).

[0520] If the "stop" button on the right side of the "execute" button is pressed here, the person who is currently set as a user cannot use the recruitment management system, and the "resurrection" button.
Pressing the button will allow those who could not currently use the recruitment system to use the system. The "Stop" button and the "Resurrection" button are interchangeable. When the “new registration” button arranged above the list is pressed, the process returns to step 761.

When the authority level of the person who wants to make user settings is i or higher (for example, i = 4), the server 1 reads the recruiter team major classification name from the recruiter team table, creates a list, and creates a list. It is transmitted to the client 5 (6) together with the classification charge setting screen (step 755).

If the authority level is lower than i, the recruiter team minor classification name is read from the recruiter team table, a list is created, and the list is transmitted to the client 5 (6) together with the recruiter team minor classification charge setting screen (step 756). .

If the recruiter team large classification charge setting screen is transmitted from the server, the screen shown in FIG. 118 is displayed on the display device of the client 5 (6) (step 76).
8) If the recruiter team minor classification charge setting screen is sent from the server, the recruiter team minor classification charge screen is displayed (step 769) (not shown). In FIG. 118, the user checks the box on the left side of the recruitment large classification to be set, and presses the “register” button at the top (step 770). Is transmitted (step 771). If the "return to list" button is pressed on the right side of the "register" button, the process returns to step 764. Furthermore, when the user box is pulled down, a list of user names (here, the authority level is i or higher) displayed on the user list screen appears. When the user selects a user name and presses the “copy” button,
The recruiter team major category that is the same as the selected user name will be selected.

In the recruiter team minor classification charge screen, the recruiter team major classification list in FIG. 118 is a recruiter team minor classification list.

When the server 1 receives the notification that the recruiter team has been selected from the client 5 (6), the selected recruiter team major category (small category) ID is registered in the recruiter user account table (step 75).
7).

As a result, the person in charge of the user setting can browse the quick reference table and the progress table of the set recruiter team. That is, it is not possible to browse a quick reference table and a progress table of recruiter teams other than the set recruiter team.

[Brief description of the drawings]

FIG. 1 shows an overall configuration of a recruitment management system.

FIG. 2 shows a database.

FIG. 3 shows a student information master.

Fig. 4 (A) is a prefecture master, (B) is a school master, (C) is an undergraduate master, (D) is a desired job master,
(E) shows the desired work location master, (F) shows the desired course master, and (G) shows the selection process master.

FIG. 5A shows a group management table, and FIG. 5B shows a group registration student table.

6 (A) shows a briefing session / interview table, FIG. 6 (B) shows a briefing session / interview applicant table, and FIG. 6 (C) shows a briefing session / interview venue master.

FIG. 7A shows a transmission mail table, and FIG. 7B shows a reception mail table.

FIG. 8A shows a narrowing-down condition table, FIG. 8B shows a quick-reference table data table, and FIG. 8C shows a delivery table.

FIG. 9 is a flowchart showing an overall process of the web server.

FIG. 10 is a flowchart showing processing related to logon and menu selection.

FIG. 11 shows a menu screen for a company representative.

FIG. 12 shows a student menu screen.

FIG. 13 is a flowchart showing the number-of-items lookup table processing.

FIG. 14 shows a number reference table condition selection screen.

FIG. 15 shows a case number reference screen.

FIG. 16 is a flowchart illustrating a narrowing process.

FIG. 17 is a flowchart illustrating a narrowing condition saving process.

FIG. 18 is a flowchart illustrating a narrowing-down condition calling process.

FIG. 19 is a flowchart illustrating a narrowing condition management process.

FIG. 20 shows a narrowing-down screen.

FIG. 21 shows a search result display screen.

FIG. 22 shows a narrowing-down screen.

FIG. 23 shows a narrow-down condition selection screen.

FIG. 24 shows a refinement condition management screen.

FIG. 25 is a flowchart showing a group management process.

FIG. 26 is a flowchart showing a group saving process.

FIG. 27 is a flowchart showing an applicable person list process.

FIG. 28 is a flowchart showing group combination processing.

FIG. 29 shows a group management screen.

FIG. 30 shows a group operation screen.

FIG. 31 shows a group operation screen.

FIG. 32 shows an applicable person list screen.

FIG. 33 shows a profile screen.

FIG. 34 shows a group combination screen.

FIG. 35 is a flowchart showing a briefing session / interview situation table process.

FIG. 36 is a flowchart showing a briefing session / interview reception condition setting / storing process.

FIG. 37 is a flowchart showing a briefing session / interview setting process.

FIG. 38 is a flowchart showing a briefing session / interview application process.

FIG. 39 is a flowchart showing a briefing session / interview application process.

FIG. 40 is a flowchart showing a briefing session / interview application process.

FIG. 41 is a flowchart showing a briefing session / interview application process.

FIG. 42 shows a situation table condition selection screen.

FIG. 43 shows a status table screen.

FIG. 44 shows an explanatory session / interview details display screen.

FIG. 45 shows a briefing session / interview reception condition setting / save screen.

FIG. 46 shows an explanatory meeting / interview reception condition management screen.

FIG. 47 shows an explanatory meeting / interview setting screen.

FIG. 48 shows an explanatory meeting / interview setting screen.

FIG. 49 shows an explanatory meeting / interview list screen.

FIG. 50 shows an explanatory meeting / interview list screen.

FIG. 51 shows an explanatory meeting / interview list screen.

FIG. 52 is a flowchart showing a mail management process.

FIG. 53 is a flowchart showing transmission content confirmation processing.

FIG. 54 is a flowchart showing a received mail confirmation process.

FIG. 55 is a flowchart showing transmission mail confirmation processing.

FIG. 56 is a flowchart showing a received mail list process.

FIG. 57 is a flowchart showing an unknown mail confirmation process.

FIG. 58 is a flowchart showing an unknown mail association process.

FIG. 59 is a flowchart showing a mail update process.

FIG. 60 is a flowchart showing a mail transmission process.

FIG. 61 shows a mail management screen.

FIG. 62 shows a transmission content screen.

FIG. 63 shows a mail creation screen.

FIG. 64 shows a received mail confirmation screen.

FIG. 65 shows a reception content screen.

FIG. 66 shows a mail creation screen.

FIG. 67 shows a transmitted mail confirmation screen.

FIG. 68 shows a received mail list screen.

FIG. 69 shows an unknown mail confirmation screen.

FIG. 70 shows an unknown mail list screen.

FIG. 71 shows a mail creation screen.

FIG. 72 shows a student information master according to another embodiment.

FIG. 73 shows a contact status table.

74A shows a group management table according to another embodiment, and FIG. 74B shows a group registration student table according to another embodiment.

FIG. 75 (A) shows a recruiter team table;
(B) shows the recruiter user account table,
(C) shows a user setting table.

76A shows a narrowing-down condition table according to another embodiment, FIG. 76B shows a quick-reference table data table according to another embodiment, and FIG. 76C shows a delivery table according to another embodiment.

77A shows an evaluation table, and FIG. 77B shows a flag table.

FIG. 78 is a flowchart showing overall processing of a web server in another embodiment.

FIG. 79 is a flowchart showing a narrowing down process according to another embodiment.

FIG. 80 is a flowchart showing a narrowing-down condition storing process in another embodiment.

FIG. 81 is a flowchart showing a variable group new creation process.

FIG. 82 is a flowchart showing a narrowing-down condition calling process in another embodiment.

FIG. 83 is a flowchart showing a variable group update process.

FIG. 84 is a flowchart showing a variable group batch process.

FIG. 85 is a flowchart showing a narrowing-down condition management process in another embodiment.

FIG. 86 shows a narrowing-down screen in another embodiment.

FIG. 87 shows a search result display screen according to another embodiment.

FIG. 88 shows a narrowing-down screen in another embodiment.

FIG. 89 shows a change group management screen.

FIG. 90 shows a narrowing-down screen in another embodiment.

FIG. 91 shows a change group update screen.

FIG. 92 is a flowchart showing a group management process in another embodiment.

FIG. 93 is a flowchart showing group combination processing in another embodiment.

FIG. 94 is a flowchart showing a relevant person list process in another embodiment.

FIG. 95 is a flowchart showing a flag setting process.

FIG. 96 is a flowchart showing group combination processing according to another embodiment.

FIG. 97 is a flowchart showing batch data registration processing.

FIG. 98 shows a group management screen according to another embodiment.

FIG. 99 shows an applicable person list screen in another embodiment.

FIG. 100 shows an applicable person list screen in another embodiment.

FIG. 101 shows an applicable person list screen in another embodiment.

FIG. 102 shows an item selection screen.

FIG. 103 shows a selection process name list screen.

FIG. 104 shows a batch data registration screen.

FIG. 105 shows a batch data registration end confirmation screen.

FIG. 106 is a flowchart showing a recruiter team registration process.

FIG. 107 is a flowchart showing a recruiter team minor classification creation process.

FIG. 108 is a flowchart showing a recruiter team progress table display process.

FIG. 109 is a flowchart showing a recruiter team quick reference table display process.

FIG. 110 shows a recruiter team large classification list screen.

FIG. 111 shows a recruiter team minor classification list screen.

FIG. 112 shows a narrow-down condition input screen.

FIG. 113 shows a recruiter team minor classification progress table screen.

FIG. 114 shows a recruiter team quick reference screen.

FIG. 115 shows a recruiter team user setting process.

FIG. 116 shows a user setting screen.

Fig. 117 shows a user list screen.

FIG. 118 shows a recruiter team major classification setting screen.

[Explanation of symbols]

 1 Corporate Web Server 2 Student Web Server 3 Mail Server 4 Database Server 5 Corporate Client 6 Agency Client 7 Student Client 8 Database 9 Subdatabase

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Toshifumi Kosai 191 Shinjuku-dori Karasuma Nishiiri Higashi-Sakamachi, Shimogyo-ku, Kyoto-shi Kyoto Tokyo Seikatsukan Shinka Co., Ltd. 191 Kyoto Tokyo Seimeikan Shinka Co., Ltd. 191 Higashisakaicho Kyoto Tokyo Life Hall Shinka Co., Ltd.

Claims (78)

[Claims] At least one of a job seeker information master storing at least identification information, a name, an address, and educational background of a job seeker and selection information including a selection process, and registration information in the job seeker information master. For each combination of the condition that determines the range of the item and the type of the number table, the number of applicable persons stored in the job applicant information master is searched in advance, and this search result is used for each combination of the above condition and type. A quick-reference data table that stores the numerical values in the cell of the quick-reference table in response to a request for processing the quick-reference table from the client. Means for transmitting the data to be displayed, and responding to the specification of the condition and the type entered in the number reference table condition selection screen. Means for transmitting data for displaying the number-of-counts quick-view screen to the client based on the data of the corresponding quick-reference table data table. 2. The server according to claim 1, wherein the condition includes a section related to an address in the registration information and a section related to an educational background. 3. The server according to claim 1, wherein the types of the number reference table include types of educational background, types of addresses, and types of a selection process. 4. The job seeker information master further includes, as registration information, job seeker's desired information on occupation or work location, and the type of the number reference table includes a desired category. The server according to claim 1. 5. The information processing apparatus according to claim 1, further comprising: means for updating a quick look-up table data table based on the latest job seeker information master information in response to an update request from a client. Server. 6. A job seeker corresponding to the specified cell is searched in the job seeker information master in response to designation of any cell of the count reference table displayed on the client. Means for forming a group of applicants and creating a list of job seekers belonging to the group, and means for transmitting data for causing the client to display an applicable person list screen including the created list. The server according to claim 1. 7. A briefing session / interview table in which data relating to a briefing session / interview for a job seeker is set, and an identification code of the job seeker who applied for the briefing session / interview corresponding to the identification code of the briefing session / interview. / Interview applicant table storing the information, means for transmitting data for displaying a screen for selecting the range of the briefing session / interview to the client, and the range according to the selection of the range of the briefing session / interview at the client 7. A means for creating a list of briefing sessions / interviews belonging to the group and transmitting data for causing a client to display a briefing session / interview management screen including the list.
A server according to any one of the preceding claims. 8. In response to designation of a briefing / interview in the list displayed on the briefing / interview management screen,
Means for reading a job applicant applying for the specified briefing session / interview from the briefing session / interview applicant table, forming a group of obtained applicants, and creating a list of applicants belonging to the group; and 8. The server according to claim 7, further comprising: means for transmitting data for causing a client to display an applicable person list screen including the created list. 9. The server according to claim 6, further comprising means for giving a group name to the formed group and creating a group table for storing data on job seekers constituting the group. 10. A means for reading information of a designated job seeker from a job seeker information master in response to designation of a job seeker in a list on a corresponding person list screen and transmitting the information in a form displayable to a client. The server according to any one of claims 6 to 8, further comprising: 11. The job seeker's at least identification code, name,
A job seeker information master that stores registration information including an address and educational background and selection information including a selection process, and a narrowing-down screen for prompting a client to select or specify a plurality of items for information in the job seeker information master. Means for transmitting data, in response to the transmission of a narrowing condition including one or a plurality of search conditions defined by one or a plurality of items selected or specified on the narrowing screen, the job seeker according to the narrowing condition; A search means for searching for the job information master and forming a group of job seekers satisfying the narrowing-down condition; and a means for creating and transmitting a screen for displaying a result obtained by the search on a client. 12. The job seeker information master further includes, as registration information, the job seeker's request regarding the occupation or work location, and an item relating to the job seeker's request can be selected or specified on the narrowing-down screen. Server as described in. 13. The search result displayed on the client is the number of persons concerned or a list of persons concerned.
The server described in 11 or 12. 14. The apparatus according to claim 11, further comprising: means for giving a group name to the formed group, and creating a group table for storing data on job seekers constituting the group. The server described. 15. The method according to claim 15, wherein the means for creating the group table stores, in the group table, a use category indicating a use assigned to the formed group.
14. The server according to 14. 16. A means for creating a group table,
15. The server according to claim 14, wherein data representing a group management type is stored in a group table. 17. The server according to claim 16, wherein the data representing the group management type includes data representing a variable group. 18. The job searcher information master is searched again according to the narrowing-down condition used to form a group for a group in which data representing a variable group is stored in the group table, and a group of job-seekers satisfying the narrowing-down condition is searched. 18. The server according to claim 17, further comprising: a group updating unit that updates the group. 19. A first means for prompting selection of a group to be subjected to collective data registration, a second means for prompting selection of an item for which collective data registration is to be performed, and referring to the group table, the selected group is referred to. A means for creating and displaying a list of job seekers to belong to, and a means for registering data relating to the above selected items in the job seeker information master of the job seeker for all of the job seekers selected from the displayed list 15. The server according to claim 14, comprising: 20. A means for reading out information of a designated job seeker from a job seeker information master in response to designation of a job seeker in a list of applicable persons and transmitting the information in a form displayable to a client. 14. The server according to claim 13, comprising a server. 21. The method according to claim 11, wherein when a group to be narrowed down has already been determined, the search means executes a search within a range of job seekers belonging to the already determined group. Server as described in section. 22. The server according to claim 11, further comprising: means for creating a narrow-down condition table for storing the one or more search conditions together with their identification codes. 23. A system further comprising means for transmitting data for displaying a screen for inputting a narrowing condition name to a client,
23. The server according to claim 22, wherein the narrowing condition table creating means stores the narrowing condition name transmitted from the client in the narrowing condition table. 24. The server according to claim 22, wherein an identification code of a group formed by a search according to the narrowing condition is stored in the narrowing condition table. 25. The server according to claim 22, wherein data relating to a search target is stored in the narrowing-down condition table. 26. In response to a request from a client,
A means for creating a list of narrowing condition names stored in the narrowing condition table, transmitting data for displaying the list to the client, and selecting one narrowing condition name from the narrowing condition name list displayed on the client 24. The server according to claim 23, further comprising: means for reading a search condition of a corresponding narrowing condition table in response to the search, and transmitting data for displaying a narrowing screen including the search condition to a client. 27. A recruiter team table associating one or a plurality of narrowing conditions used to form a group and a recruiter team permitted to access a group satisfying the narrowing condition,
The server according to claim 11. 28. The server according to claim 27, wherein the recruiter team is specified by a major category and a minor category. 29. The server according to claim 27, further comprising a person in charge table for storing information on persons in charge belonging to the recruiter team. 30. In response to a request from a client,
15. The server according to claim 9, further comprising means for creating a list of groups stored in the group table and transmitting data for displaying a group list screen on the client. 31. In response to designation of a group on the group list screen, a list of job seekers constituting the corresponding group is created, and screen data for displaying the list to the client is transmitted. 31. The server according to claim 30, further comprising means. 32. A group combination screen including an area for specifying a plurality of groups and an area for specifying the type of logical operation, including a list of group names for which a group table has been created. Means for transmitting data to be displayed to the client, and a job application belonging to the plurality of specified groups in response to transmission of data indicating the plurality of specified groups and data indicating the type of logical operation from the client 15. A means according to claim 9, further comprising means for performing a specified logical operation on a user, forming a new group based on the result of the logical operation, assigning a group name to the group, and creating a new group table. Server. 33. A plurality of group tables each storing a group name of a group and identification codes of persons belonging to the group, a list of group names for which the group table is created is displayed, and designation of a plurality of groups is included. Means for transmitting data for causing a client to display a group combination screen having an area for performing and an area for specifying the type of logical operation, and indicating data indicating a plurality of specified groups and the type of logical operation In response to the transmission of the data and the data from the client, a specified logical operation is performed on persons belonging to a plurality of specified groups, a new group is formed based on the result of the logical operation, and a group is identified for the group. Means for creating a new group table with a code. 34. A means for transmitting data for causing a client to display a group name input screen for the formed group, and a means for storing the group name transmitted from the client in a corresponding group table.
34. The server according to claim 33, comprising: 35. A mail address of a job seeker is registered in the job seeker information master, a destination area including a list of group names for which the group table is created, an area for inputting a subject, and A means for sending data to the client to display a mail creation screen with an area to enter the mail text, and in response to the transmission of the mail creation screen in which the group name, subject and mail text as the destination have been input And means for creating and transmitting an e-mail including the mail address of the job seeker belonging to the group for each job seeker belonging to the group with reference to the group table and the job seeker information master. 33. The server according to any one of the above. 36. A received mail request for a job seeker is input in a received mail table storing an identification code of the job seeker and data relating to an e-mail from the job seeker, and a screen displaying information of the job seeker. 21. The server according to claim 10, further comprising: means for reading out data relating to the e-mail of the job seeker from the received mail table in response to the e-mail and transmitting the data to the client. 37. A transmission mail table storing an identification code of a job seeker and data relating to an electronic mail to the job seeker,
Means for reading out the e-mail data of the job seeker from the above-mentioned sent mail table and transmitting the data to the client in response to the input of the send mail request for the job seeker on the screen displaying the information of the job seeker The server according to claim 10, comprising: 38. Data relating to an e-mail sent for each individual person or for each group including a plurality of persons, wherein the transmitted mail ID, the group ID, and the identification code of the person to be transmitted are stored. And at least one of a destination mail address, a subject, a transmission date and time, and a transmission mail table storing a text, and data relating to a received e-mail. Received mail table that stores the mail address, the transmitted mail ID of the transmitted mail corresponding to the received mail, unknown classification data indicating whether there is a corresponding transmitted mail, the identification code of the sender, the subject, the reception date and time, and the text , In response to the mail management request from the client, refer to the above sent mail table and received mail table Means for creating a sent mail list including, for each sent mail ID, the subject of the sent mail, the sent date and time, data on the destination, the number of sent mails, and the number of replies indicating the number of received mails corresponding to the sent mail; Means for transmitting data for displaying the sent mail list to the client. 39. In response to a request from a client indicating that a specific outgoing mail is specified in the outgoing mail list, data of the specified outgoing mail can be read from the outgoing mail table and displayed on the client. 39. The server of claim 38, comprising means for transmitting in form. 40. In response to a request from a client indicating that the contents of a received mail corresponding to a specific sent mail should be acquired in the sent mail list, the data of the received mail is read from the received mail table. 40. The server according to claim 38, further comprising means for transmitting the data in a form displayable to a client. 41. For one or a plurality of received mails transmitted from the mail server, the received mails and the transmitted mails are associated with each other, and the association result is transmitted mail ID.
39. The server according to claim 38, further comprising: means for storing data relating to the received mail in a received mail table, expressed as data of an unknown category. 42. A subject information master storing at least a mail address of the subject, a group table storing, for each group, a subject belonging to the group with a group ID, and a list of group names in which the group table is created. A means for sending data to display a mail creation screen on the client with an area for the destination including the display, an area for entering the subject, and an area for entering the body of the mail, and the group name, subject, and body of the destination as the destination In response to the transmitted mail creation screen being sent, an e-mail including the e-mail address of the subject belonging to the group is created for each subject belonging to the group with reference to the group table and the subject information master. 39. The server according to claim 38, further comprising: means for transmitting data. 43. A data for displaying on a client a mail creation screen having a subject information master storing at least a subject's mail address, an area for inputting a destination, an area for inputting a subject, and an area for inputting a mail text. In response to the sending of the mail creation screen with the sending means and the destination, subject and email text entered,
39. The server according to claim 38, further comprising: means for creating and transmitting an e-mail including the mail address of the target person with reference to the target person information master. 44. Explanatory meeting / interview identification code, explanatory meeting / interview table, data describing the venue and date and time of the briefing session / interview, selection process, capacity, and range of applicants who can apply The briefing session corresponding to the code /
Briefing session that stores the identification code of the job applicant who applied for the interview /
Interview applicant table, in response to access to the application for the briefing / interview including the identification code of the job seeker from the client, referencing the data indicating the range of applicants who can apply for the briefing / interview table and accessing the application. A means for creating a list of briefing sessions / interviews that can be applied by the job seeker who has applied, a means for transmitting data for displaying the briefing session / interview application screen including the created list to the client, and a briefing session / interview application Means for writing the identification code of the job seeker in the corresponding briefing / interview applicant table in response to the client sending a notification indicating that the application has been made by specifying the briefing / interview on the screen The server according to any one of claims 1, 11, 33 and 38, comprising: 45. A briefing session / interview identification code, a briefing session / interview table storing data indicating the venue and date and time of the briefing session / interview, the selection process, the capacity and the range of applicants who can apply, and the briefing session / interview identification The briefing session corresponding to the code /
Briefing session that stores the identification code of the job applicant who applied for the interview /
Interview applicant table, in response to access to the application for the briefing / interview including the identification code of the job seeker from the client, referencing the data indicating the range of applicants who can apply for the briefing / interview table and accessing the application. A means for creating a list of briefing sessions / interviews that can be applied by the job seeker who has applied, a means for transmitting data for displaying the briefing session / interview application screen including the created list to the client, and a briefing session / interview application Means for writing the identification code of the job seeker in the corresponding briefing / interview applicant table in response to the client sending a notification indicating that the application has been made by specifying the briefing / interview on the screen , A server equipped with. 46. The briefing session / interview table also includes data on briefing sessions / interviews that do not limit the range of eligible persons who can apply, and these briefing sessions / interviews that limit the range of eligible persons who can apply. 46. The server of claim 45, wherein the server is also added to the list. 47. Upon receipt of a notice of an application from a client, it is checked whether or not the application for the job seeker who applied has been approved. If so, the identification code of the job seeker is entered in the briefing session / interview applicant table. The server of claim 45, wherein the server writes. 48. The server according to claim 45, wherein the data indicating the range of target persons who can apply is data indicating a group, and the group table includes a group table storing job seekers belonging to the group for each group. 49. At least identification code, name,
A job applicant information master that stores the registration information including the address and educational background and the selection information including the selection process, and the reception condition specified by specifying one or more items of the information in the job applicant information master as the reception condition name A reception condition table stored in association with the data is provided, and data representing a range of target persons who can apply is indicated by the reception condition name.
The server according to claim 45. 50. The server according to claim 49, wherein the data indicating the range of applicants who can apply is one in which a predetermined item in the reception conditions is further restricted in the number of persons. 51. At least identification code, name,
The client displays a job applicant information master storing registration information including an address and educational background and selection information including a selection process, and a reception condition selection screen for prompting selection or designation of a plurality of items for information in the job applicant information master. Means for transmitting data for receiving the information and one or more conditions specified by one or more items selected or specified on the reception condition selection screen. 46. The server according to claim 45, further comprising: means for creating a reception condition table in correspondence with the reception condition name. 52. Data for displaying a briefing session / interview setting screen for inputting data representing the name of the briefing session / interview, venue, date and time, selection process, capacity and the range of applicants who can apply, to the client. In response to receiving the data entered in the means and the briefing / interview setting screen from the client, the briefing /
46. The server according to claim 45, further comprising: means for creating an interview table. 53. At least the identification code, name,
A job applicant information master that stores registration information including the address and educational background and selection information including the selection process is provided. For each combination with the type, the number of applicable persons stored in the job applicant information master is searched in advance, and this search result is stored as a numerical value in the cell of the cell count table for each combination of the above condition and type. Create a quick-reference table data table to be stored in advance, and respond to a request for processing the number of quick-reference tables from the client. In response to the specification of the condition and type entered in the number reference table selection screen, the corresponding reference table data Transmits the data for displaying the number Chart screen to the client on the basis of the data of Buru, Recruitment method using a server. 54. In response to designation of any cell of the count reference table displayed on the client, a job applicant corresponding to the designated cell is searched in the job applicant information master, and 54. The method according to claim 53, wherein a group of applicants is formed, a list of job seekers belonging to the group is created, and data for causing the client to display a hit list screen including the created list is transmitted to the client. 55. An explanation / interview table in which data relating to a briefing session / interview for job seekers is set, and identification of job seekers who applied for the briefing / interview corresponding to the identification code of the briefing session / interview A description session / interview applicant table storing codes is provided, and data for displaying a screen for selecting a range of the description session / interview to the client is transmitted. Create a list of briefing sessions / interviews that belong to the range, send data that causes the client to display the briefing / interview management screen including this list, and explain in the list displayed on the briefing / interview management screen. In response to the designation of the meeting / interview, job applicants applying for the designated briefing / interview are read from the briefing / interview applicant table, and the obtained group of applicants is formed. 54. The method according to claim 53, wherein a list of applicants belonging to the group is created, and data for causing the client to display a hit list screen including the created list is transmitted to the client. 56. The method according to claim 54, wherein the formed group is given a group name, and a group table for storing data on job seekers constituting the group is created. 57. The method according to claim 53, wherein a use table indicating a use of the group is stored in the group table. 58. A recruiter team table for associating one or more narrowing conditions used for forming a group with a recruiter team permitted to access a group satisfying the narrowing condition. Server. 59. The server according to claim 58, wherein the recruiter team is specified by a major classification and a minor classification. 60. A person in charge table for storing information about persons in charge belonging to the recruiter team is further created.
60. The server according to claim 58 or 59. 61. The server according to claim 56, wherein data indicating a group management type is stored in the group table. 62. The server according to claim 61, wherein the data representing the group management type includes data representing a variable group. 63. A group in which data representing a variable group is stored in the group table is searched again according to the narrowing conditions used to form a group, and the job seeker information master is searched again by a job seeker who satisfies the narrowing conditions. 62. The server of claim 61, wherein the server updates a group. 64. At least identification code, name,
A job applicant information master that stores registration information including address and educational background and selection information including the selection process is provided, and a narrowing-down screen for prompting the client to select or specify a plurality of items in the job applicant information master is displayed on the client. In response to the transmission of the refinement condition including one or more search conditions defined by one or more items selected or specified on the refinement screen, and in accordance with the refinement condition, Searches the job applicant information master, forms a group of job applicants that meet the narrowing conditions, creates and sends a screen that displays the results obtained by the search on the client, assigns a group name to the formed group, Create a group table that stores data about job seekers that make up a group. Recruitment method using. 65. A group combination screen including an area for specifying a plurality of groups and an area for specifying the type of logical operation, including displaying a list of group names for which a group table has been created. Sending data to be displayed to the client, and responding to the client sending data indicating the specified groups and data indicating the type of logical operation, the job applicant belonging to the specified groups. 65. The method according to claim 56, wherein the specified logical operation is performed, a new group is formed based on the result of the logical operation, and the group is given a group name to create a new group table. 66. A plurality of group tables each storing a group name of a group and identification codes of persons belonging to the group, including displaying a list of group names for which the group table is created, Transmits data for causing a client to display a group combination screen having an area for specifying and an area for specifying the type of logical operation, and indicates data indicating a plurality of specified groups and the type of logical operation In response to the transmission of the data from the client, a specified logical operation is performed on persons belonging to the plurality of specified groups, and a new group is formed based on the logical operation result.
A group management method using a server, wherein a new group table is formed by attaching a group identification code to the group. 67. A mail address of a job seeker is registered in the job seeker information master, a destination area including a list of group names in which the group table is created, an area for inputting a subject, and Sends data to display a mail creation screen with an area for entering the mail body on the client, and responds to the transmission of the mail creation screen in which the group name, subject, and mail body as the destination are sent. 67. Any one of claims 56, 64 and 66, wherein an e-mail including the e-mail address of the job seeker belonging to the group is created and transmitted for each job seeker belonging to the group with reference to the group table and the job seeker information master. The method described in. 68. A storage section for storing data relating to an e-mail transmitted for each individual person or for each group including a plurality of persons, and includes an outgoing mail ID, a group ID, and an identification code of the person to be transmitted. , A transmission mail table storing the mail address of the transmission destination, the number of transmissions, the subject, the transmission date and time, and the text, and the data relating to the received e-mail.
The sender's mail address, the outgoing mail ID of the outgoing mail corresponding to the received mail, unknown classification data indicating whether there is a corresponding outgoing mail, the identification code of the sender's target person, the subject, the received date and time, and the text are stored. A received mail table is provided, and in response to a mail management request from the client, referring to the above-mentioned sent mail table and received mail table, for each sent mail ID, the subject of the sent mail, the date and time of transmission, the data on the destination, and the number of transmissions. And a server-based mail management method for creating a sent mail list including the number of replies indicating the number of received mails corresponding to the sent mail and transmitting data for displaying the sent mail list on a client. 69. A subject information master that stores at least a mail address of a subject, and a group table that stores, for each group, a subject belonging to the group together with a group ID, and a group name in which the group table is created. Sends data to the client to display a mail creation screen with an area for the destination including the list display of the list, an area for entering the subject, and an area for entering the body of the mail. The group name, subject, and body of the destination as the destination In response to the input mail creation screen being sent, an e-mail containing the e-mail addresses of the subjects belonging to the group is created for each subject belonging to the group with reference to the group table and the subject information master. 69. The method according to claim 68, wherein the transmission is performed. 70. Explanation session / interview identification code, explanation session / interview venue and date and time, selection process, capacity and data indicating the range of applicants who can apply, and explanation session / interview table, and explanation session / interview A briefing session / interview applicant table that stores the identification code of the job applicant who applied for the briefing session / interview corresponding to the identification code is provided, and the client accesses the briefing session / interview including the identification code of the job seeker from the client In response to, by referring to the data indicating the range of candidates who can apply for the briefing / interview table, create a list of briefing sessions / interviews that the job seeker who accessed the application can apply, and create the list And send data to the client to display a briefing / interview application screen containing
In response to the notification from the client indicating that the application was made by specifying the briefing / interview on the interview application screen, the identification code of the job seeker was written in the corresponding briefing / interview applicant table. Claim 53 or comprising:
64. The method according to 64. 71. A briefing session / interview table storing data indicating the briefing session / interview identification code, the venue and date and time of the briefing session / interview, the selection process, the capacity and the range of applicants who can apply, and the briefing session / interview A briefing session / interview applicant table storing the identification code of the job seeker who applied for the briefing session / interview corresponding to the identification code is provided, and the client accesses the briefing session / interview including the identification code of the job seeker from the client. In response to, by referring to the data indicating the range of candidates who can apply for the briefing / interview table, create a list of briefing sessions / interviews that the job seeker who accessed the application can apply, and create the list To send the client to display the briefing / interview application screen containing
In response to the client notifying that the application was made by specifying the briefing / interview on the interview application screen, the identification code of the job seeker was written in the corresponding briefing / interview applicant table. Recruitment management method using server. 72. At least the identification code, name,
A job applicant information master that stores registration information including the address and educational background and selection information including the selection process is provided, and a reception condition selection screen for prompting the client to select or specify a plurality of items in the job applicant information master is provided to the client. In response to the transmission of the data to be displayed and the transmission of the reception condition including one or more conditions specified by one or more items selected or specified on the reception condition selection screen, the reception condition 72. The method according to claim 71, wherein a reception condition table is created in correspondence with the reception condition name. 73. Data for displaying a briefing session / interview setting screen for inputting data representing the name of the briefing session / interview, venue, date and time, selection process, capacity, and the range of applicants who can apply, is transmitted to the client. 72. The method of claim 71, wherein in response to receiving data entered on the briefing / interview setting screen from the client, the briefing / interview table is created using the data. 74. At least the identification code, name,
For each combination of the condition that defines the range of at least one item of the registration information in the job applicant information master that stores the registration information including the address and educational background and the selection information including the selection process, and the type of the number reference table, A quick-reference table data table in which the number of applicable persons stored in the job applicant information master is searched in advance and the search result is stored as a numerical value in the cell of the number-of-cases quick-reference table for each combination of the above conditions and types. In response to a request from the client to process the count reference table, the client sends the data to display the count reference table selection screen for inputting the above conditions and types. In response to the specification of the above condition and type input in the above, the number of cases is checked based on the data of the corresponding quick reference table data table. Medium recording Recruitment program for controlling a computer to transmit data for displaying a screen on the client. 75. At least identification code, name,
Data for displaying a narrowing screen for prompting a client to select or specify a plurality of items for information in the job applicant information master storing registration information including the address and educational background and selection information including the selection process, and transmitting the data to the client, In response to the transmission of the narrowing condition including one or more search conditions defined by one or more items selected or specified on the narrowing screen, the job seeker information master is searched according to the narrowing conditions. ,
Form a group of job seekers who meet the narrowing conditions, create and send a screen to display the results obtained by the search on the client, assign a group name to the formed group, and data on the job seekers constituting the group Recording a recruitment management program for controlling a computer so as to create a group table for storing information. 76. A reference to a plurality of group tables each storing a group name of a group and identification codes of persons belonging to the group, including displaying a list of group names for which the group table has been created, Creates a group combination screen having an area for specifying a group and an area for specifying the type of logical operation, transmits data to be displayed on the client, and displays data and logic indicating a plurality of specified groups. In response to the data indicating the type of operation being transmitted from the client, a specified logical operation is performed on persons belonging to the specified groups, and a new group is formed based on the logical operation result. A group that controls the computer to create a new group table with the group identification code assigned to the group Medium on which management programs are recorded. 77. A storage unit for storing data relating to an e-mail transmitted for each individual person or for each group including a plurality of persons, and includes a transmission mail ID, a group ID, and an identification code of a person to be transmitted. , A transmission mail table storing the transmission destination mail address, the number of transmissions, the subject, the transmission date and time, and the text, and the data relating to the received e-mail.
The sender's mail address, the outgoing mail ID of the outgoing mail corresponding to the received mail, unknown classification data indicating whether there is a corresponding outgoing mail, the identification code of the sender's target person, the subject, the reception date and time, and the text are stored. A received mail table is provided, and in response to a mail management request from the client, the transmitted mail table and the received mail table are referred to, for each transmitted mail ID, the subject of the transmitted mail, the date and time of transmission, the data relating to the destination, and the number of transmissions. Mail management for controlling a computer so as to create a sent mail list including the number of replies indicating the number of received mails corresponding to the sent mail and to transmit the data for displaying the sent mail list to a client. Medium on which the program is recorded. 78. Explanation session / interview identification code, explanation session / interview venue and date and time, selection process, capacity and data representing the range of applicants who can apply, and explanation session / interview table A briefing session / interview applicant table storing the identification code of the job seeker who applied for the briefing session / interview corresponding to the identification code is provided, and the client accesses the briefing session / interview including the identification code of the job seeker from the client. In response to, by referring to the data indicating the range of candidates who can apply for the briefing / interview table, create a list of briefing sessions / interviews that the job seeker who accessed the application can apply, and create the list To send the client to display the briefing / interview application screen containing
In response to the client notifying that the application was made by specifying the briefing / interview on the interview application screen, the identification code of the job seeker was written in the corresponding briefing / interview applicant table. A medium in which an employment management program for controlling a computer to be inserted is recorded.