Recruitment data management system and recruitment data management method
The recruitment data management system addresses inefficiencies by ensuring complete job data registration across multiple databases, enhancing recruitment efficiency and job seeker engagement through data matching and operational status analysis.
Patent Information
- Application Number
- JP2023081993
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-18
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2043-05-18
AI Technical Summary
In scenarios where job data is registered in one job database but not in another, leading to inefficiencies in recruitment activities due to incomplete job postings viewed by job seekers.
A recruitment data management system and method that utilizes a management device to access both job databases, determining matching job data based on similarity and operational status to ensure comprehensive registration across databases.
Enhances recruitment efficiency by identifying and registering missing job data, linking databases, and promoting active use of high-potential job postings, thereby improving job seeker engagement.
Smart Images

Figure 2024165633000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a recruitment data management system and a recruitment data management method. [Background technology]
[0002] In recent years, systems have become known that support the recruiting activities of companies and other employers by managing the application status of job seekers for job data posted on recruitment media such as Internet recruitment sites. Such systems are sometimes called ATS (Applicant Tracking System).
[0003] For example, a management device has been proposed that works in conjunction with multiple recruitment media to collect and centrally manage the application status of job seekers for job data posted on each of the multiple recruitment media (for example, Patent Document 1). [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2017-16298 A Summary of the Invention [Problem to be solved by the invention]
[0005] Here, it is conceivable that a recruiter may use two or more recruitment databases (for example, a first recruitment database and a second recruitment database) as recruitment databases in which to register (or post) recruitment data. The recruitment databases may be considered to be databases corresponding to the recruitment media, or may be considered to be databases corresponding to the ATS (the management device described above).
[0006] In such a case, a situation may occur where job data is registered in the first job database but not in the second job database. Conversely, a situation may occur where job data is registered in the second job database but not in the first job database.
[0007] If the above situation occurs, the created job data cannot be registered in the job database, which could result in the job not being published in job media viewed by job seekers, making the employer's recruitment activities inefficient.
[0008] SUMMARY OF THE PRESENT EMBODIMENTS Accordingly, an object of the present invention is to provide a recruitment data management system and a recruitment data management method that enable recruiters to increase the efficiency of their recruiting activities. [Means for solving the problem]
[0009] One aspect of the disclosure is a vacancy data management system that includes a first vacancy database that manages first vacancy data registered by a target employer, a second vacancy database that manages second vacancy data registered by the target employer, and a management device that can access both the first vacancy database and the second vacancy database, wherein the management device determines whether vacancy data corresponding to the first vacancy data is managed as the second vacancy data in the second vacancy database based on the degree of match between the first vacancy data and the second vacancy data.
[0010] One aspect of the disclosure is a vacancy data management method comprising: a step A in which a first vacancy database manages first vacancy data registered by a target employer; a step B in which a second vacancy database manages second vacancy data registered by the target employer; and a step C in which a management device that can access both the first vacancy database and the second vacancy database determines, based on the degree of match between the first vacancy data and the second vacancy data, whether vacancy data corresponding to the first vacancy data is managed as the second vacancy data in the second vacancy database. Effect of the Invention
[0011] According to the present invention, it is possible to provide a recruitment data management system and a recruitment data management method that enable recruiters to increase the efficiency of their recruiting activities. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram showing a job offer data management system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating the management device 30 according to the embodiment. [Diagram 3] FIG. 3 is a diagram for explaining an operation example according to the embodiment. [Figure 4] FIG. 4 is a diagram for explaining an operation example according to the embodiment. [Diagram 5] FIG. 5 is a diagram for explaining an operation example according to the embodiment. [Figure 6] FIG. 6 is a diagram showing a job offer data management system according to the embodiment. [Figure 7] FIG. 7 is a diagram for explaining generation of a learning model according to the first modification. [Figure 8] FIG. 8 is a diagram for explaining calculation of the score according to the first modification example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, embodiments will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.
[0014] However, it should be noted that the drawings are schematic and the ratios of the dimensions may differ from the actual ones. Therefore, the specific dimensions should be determined with reference to the following explanation. In addition, the drawings may of course include parts with different dimensional relationships or ratios.
[0015] [Disclosure Summary] The job data management system according to the disclosure summary comprises a first job database that manages first job data registered by a target employer, a second job database that manages second job data registered by the target employer, and a management device that can access both the first job database and the second job database, and the management device determines whether job data corresponding to the first job data is managed as the second job data in the second job database based on the degree of match between the first job data and the second job data.
[0016] The job data management method according to the disclosed summary includes step A in which a first job database manages first job data registered by a target employer, step B in which a second job database manages second job data registered by the target employer, and step C in which a management device that can access both the first job database and the second job database determines whether job data corresponding to the first job data is managed as the second job data in the second job database based on the degree of match between the first job data and the second job data.
[0017] In the summary of the disclosure, the management device determines whether or not the recruitment data corresponding to the first recruitment data is managed as the second recruitment data in the second database based on the degree of match between the first recruitment data and the second recruitment data. With this configuration, by taking advantage of the fact that the management device can access both the first database and the second database, recruitment data that is managed in the first database but not managed in the second database can be identified, thereby improving the efficiency of the recruiter's recruitment activities.
[0018] [Embodiment] (Recruitment Data Management System) A job offer data management system according to an embodiment will be described below. Fig. 1 is a diagram showing a job offer data management system 100 according to an embodiment.
[0019] As shown in Fig. 1, the job offer data management system 100 includes a first terminal 10, a second terminal 20, a management device 30, a first DB 40, and a second DB 50. The first terminal 10, the second terminal 20, the management device 30, the first DB 40, and the second DB 50 are connected by a network 200. Although not particularly limited, the network 200 may be configured by the Internet. The network 200 may include a local area network, a mobile communication network, or a VPN (Virtual Private Network).
[0020] The first terminal 10 is a terminal used by a job seeker. For example, the first terminal 10 may be a personal computer, a smartphone, or a tablet terminal. The job seeker may use the first terminal 10 to view job offer data registered in at least one of the first DB40 and the second DB50.
[0021] The second terminal 20 is a terminal used by the recruiter. The second terminal 20 may be a personal computer, a smartphone, or a tablet terminal. The recruiter may use the second terminal to register job data in at least one of the first DB40 and the second DB50.
[0022] The management device 30 is a device that can access both the first DB 40 and the second DB 50. The management device 30 may be read as an ATS (Applicant Tracking System). Details of the management device 30 will be described later (see FIG. 2).
[0023] The first DB40 is a database that manages job data registered by the target recruiter (hereinafter, the first job data). The first DB40 may manage job data registered by recruiters other than the target recruiter. In the embodiment, the first DB40 is an example of a first job database that manages the first job data. The first DB40 may be read as a first job medium. The first job medium includes a job site or job advertisement on the Internet, a job advertisement in paper media, and the recruiter's own website (recruitment website). The first DB40 may also include an ATS. The ATS is linked to other job mediums, and the recruiter may post the job data created in the ATS on other job mediums linked to the ATS. The first job data is data related to a job posting created by the recruiter to recruit personnel, and may include the name of the target recruiter, the job type, job title, annual salary, and text of the job posting. The job type, job title, and annual salary for which personnel are recruited may be considered as category information of the first job data. The category information is information selected or input from among predetermined items. The text of the job posting may be considered to be text information such as the job content, the employer's mission, and the recruitment background.
[0024] The second DB50 is a database that manages job data registered by the target recruiter (hereinafter, second job data). The second DB50 may manage job data registered by recruiters other than the target recruiter. In the embodiment, the second DB50 is an example of a second job database that manages the second job data. The second DB50 may be read as a second job medium. The second job medium includes a job site or job advertisement on the Internet, a job advertisement in paper media, and the recruiter's own website (recruitment website). The second DB50 may also include an ATS. The ATS is linked to other job mediums, and the recruiter may post the job data created in the ATS on other job mediums linked to the ATS. The second job data is data related to a job posting created by the recruiter to recruit personnel, and may include the name of the target recruiter, the job type, job title, annual salary, and the text of the job posting. The job type, job title, and annual salary for which personnel are recruited may be considered as category information of the second job data. The category information is information selected or input from among predetermined items. The text of the job posting may be considered to be text information such as the job content, the employer's mission, and the recruitment background.
[0025] Here, the recruiter may be any entity that creates or registers recruitment data, and may be a recruiter at a company level, or a recruiter at a department level of a company. The recruiter may also be an intermediary such as an agent. The target recruiter refers to a recruiter that checks whether recruitment data corresponding to the first recruitment data managed in the first DB40 is managed in the second DB50 as second recruitment data.
[0026] (Management device) The management device according to the embodiment will be described below. Fig. 2 is a diagram showing a management device 30 according to the embodiment. As shown in Fig. 2, the management device 30 includes a communication unit 31, a management unit 32, and a control unit 33.
[0027] The communication unit 31 is configured by a communication module. The communication module may be a wireless communication module conforming to a standard such as IEEE802.11a / b / g / n / ac / ax, LTE, 5G, or 6G, or may be a wired communication module conforming to a standard such as IEEE802.3.
[0028] For example, the communication unit 31 may receive the first job offer data from the first DB 40. The communication unit 31 may receive the second job offer data from the second DB 50.
[0029] The management unit 32 is configured with a storage medium such as an SSD (Solid State Drive) or an HDD (Hard Disk Drive), and stores various information.
[0030] For example, the management unit 32 may manage a score indicating the possibility of employing a job seeker for the first job vacancy data. The score may be calculated by the control unit 33, which will be described later.
[0031] The management unit 32 may manage data indicating the operating status of the first job offer data. The data indicating the operating status may include a history of sending and receiving scout emails related to the first job offer data, a history of applications from job seekers related to the first job offer data, a history of interviews between recruiters and job seekers related to the first job offer data, and the like.
[0032] The management unit 32 may manage data indicating the operating status of the second job offer data. The data indicating the operating status may include a history of sending and receiving scout emails related to the second job offer data, a history of applications from job seekers related to the second job offer data, a history of interviews between recruiters and job seekers related to the second job offer data, and the like.
[0033] The control unit 33 may include at least one processor. The at least one processor may be configured by a central processing unit (CPU), a micro processing unit (MPU), a graphics processing unit (GPU), one or more integrated circuits, one or more discrete circuits, or a combination thereof.
[0034] In an embodiment, the control unit 33 may perform the following operations.
[0035] First, the control unit 33 determines whether or not the job data corresponding to the first job data is managed as the second job data in the second DB 50 based on the degree of agreement between the first job data and the second job data. Such a determination process may be referred to as a name matching determination process. The degree of agreement between the first job data and the second job data may be read as a degree of similarity.
[0036] For example, the control unit 33 calculates the degree of match between the first job data and the second job data, which indicates the degree to which the first job data and the second job data match (degree of match), by comparing the text data of the first job data and the text data of the second job data. If the degree of match between the first job data and the second job data is equal to or greater than a threshold, the control unit 33 determines that the job data corresponding to the first job data is managed as the second job data in the second DB 50. If the degree of match between the first job data and the second job data is less than the threshold, the control unit 33 determines that the job data corresponding to the first job data is not managed as the second job data in the second DB 50.
[0037] Specifically, the name matching determination process may include the following steps.
[0038] In the first step, the control unit 33 determines whether the name of the employer in the first job data matches the name of the employer in the second job data. Specifically, it determines whether the company name, etc., described as the name of the employer in the first job data matches the company name, etc., described as the name of the employer in the second job data. The control unit 33 proceeds to the next step when the name of the employer in the first job data matches the name of the employer in the second job data. When the name of the employer in the first job data does not match the name of the employer in the second job data, the control unit 33 determines that the job data corresponding to the first job data is not managed as second job data in the second DB50. When the name of the employer in the first job data does not match the name of the employer in the second job data, the control unit 33 may determine that the degree of match between the text of the job posting in the first job data and the text of the job posting in the second job data is 0%.
[0039] Here, the names of the recruiters in the first recruitment data and the second recruitment data may be considered to be an example of text data. The names of the recruiters may include the official name and may include the abbreviated name. The official name and the abbreviated name may be determined to match. For example, "XX Co., Ltd." and "XX" may be determined to match.
[0040] In the second step, the control unit 33 determines whether the job type advertised by the first job data matches the job type advertised by the second job data. Specifically, it determines whether the job type name described as the job type advertised by the first job data matches the job type name described as the job type advertised by the second job data. The control unit 33 proceeds to the next step when the job type advertised by the first job data matches the job type advertised by the second job data. When the job type advertised by the first job data does not match the job type advertised by the second job data, the control unit 33 determines that the job data corresponding to the first job data is not managed as the second job data in the second DB50. When the job type advertised by the first job data does not match the job type advertised by the second job data, the control unit 33 may determine that the degree of match between the text of the job advertisement of the first job data and the text of the job advertisement of the second job data is 0%.
[0041] Here, the job types in the first job data and the second job data may be considered to be an example of text (character string) data. The job types may be determined to match not only when the entire character string of the job type matches, but also when a part of the job type matches. For example, "data scientist" and "data analyst" may be determined to match. This allows the job types to be determined to match because they are essentially the same job type even if there are spelling variations or typos in the job type text.
[0042] In the third step, the control unit 33 judges whether the job title advertised by the first job data matches the job title advertised by the second job data. Specifically, it judges whether the job title name described as the advertised job title in the first job data matches the job title name described as the advertised job title in the second job data. The control unit 33 proceeds to the next step when the job title advertised by the first job data matches the job title advertised by the second job data. When the job title advertised by the first job data does not match the job title advertised by the second job data, the control unit 33 judges that the job title corresponding to the first job data is not managed as the second job title in the second DB50. When the job title advertised by the first job data does not match the job title advertised by the second job data, the control unit 33 may judge that the degree of agreement between the text of the job posting of the first job data and the text of the job posting of the second job data is 0%.
[0043] Here, the job titles in the first job data and the second job data may be considered as an example of text (character string) data. The job titles may be determined to match not only when the entire character string of the job title matches, but also when a part of the character string matches. In addition, the job titles may be associated with categories in advance, and the job titles may be determined to match when the categories associated with the job titles match. For example, if "section chief" and "department manager" are associated with the "management" category in advance, "section chief" and "department manager" may be determined to match. This allows the job titles to be determined to match as being substantially the same, even if there are spelling variations or typos in the job title text.
[0044] In the fourth step, the control unit 33 determines the degree of agreement between the text of the job posting of the first job posting data and the text of the job posting of the second job posting data. The degree of agreement between the text of the job posting of the first job posting data and the text of the second job posting data may be read as the similarity between the text of the job posting of the second job posting data. The degree of agreement (similarity) between the text of the job posting of the first job posting data and the text of the second job posting of the second job posting data may be calculated by performing morphological analysis on the text, vectorizing the text by a known method such as BOW (Bag Of Words), TF-IDF (Term Frequency-Inverse Document Frequency), SCDV (Sparse Composite Document Vectors), or distributed representation, and calculating the degree of agreement (similarity) between the text of the job posting of the first job posting data and the text of the job posting of the second job posting data, respectively, calculating the distance between the respective feature vectors by cosine similarity or the like, and outputting the degree of agreement (similarity). If the similarity between the text of the job posting of the first job posting data and the text of the second job posting of the second job posting data is equal to or greater than a threshold value, the text of the job posting of the second ... The threshold value may be a value of 40%, 50%, etc. Even if the content of job data is the same, the specifications and formats may differ depending on the job medium that publishes the job data and the DB that stores the job data, so even if the similarity of the text of the job advertisement is not 100%, if it is equal to or exceeds a threshold value such as 40%, 50%, etc., the text of the job advertisement may be determined to match.
[0045] In addition, when there are multiple second job data, the control unit 33 may determine that the second job data with the highest degree of match or similarity with the text of the job advertisement of the first job data matches the text of the job advertisement of the first job data. In addition, when there are multiple second job data in which the degree of match or similarity of the text included in the job advertisement is equal to or greater than a threshold, the control unit 33 may determine that the second job data with the highest degree of match or similarity matches the text of the job advertisement of the first job data. This makes it possible to determine that the text of substantially identical job advertisements matches even if the expression of the text of the job advertisement is partially different or the order of items included in the text is different.
[0046] Finally, in the fourth step, if it is determined that the text of the job advertisement matches, the control unit 33 determines that the job data corresponding to the first job advertisement data is managed as the second job advertisement data in the second DB 50. On the other hand, if it is determined that the text of the job advertisement does not match, the control unit 33 determines that the job data corresponding to the first job advertisement data is not managed as the second job advertisement data in the second DB 50.
[0047] In the name identification determination process, at least one of the second step and the third step may be omitted, and the order of the second step and the third step may be changed.
[0048] As described above, the control unit 33 may execute a process (cut-off process) to determine second job data that may correspond to the first job data based on whether or not category information such as the name of the target recruiter and the job type and job title match, and then, for the second job data that may correspond to the first job data, determine whether or not the job data corresponding to the first job data is managed as second job data in the second DB 50 based on whether or not text information such as the text of the job advertisement matches. According to such a configuration, by cutting off job data whose contents are obviously different in advance, the number of job data that is the subject of calculation and determination of the degree of match (similarity) can be reduced, and the load on the system and the time required for these processes can be reduced.
[0049] In other words, the control unit 33 extracts one first job data from the first DB 40, and searches and extracts second job data having a name of a recruiter that matches the name of the recruiter of the extracted first job data (matching target) from the second DB 50. The control unit 33 searches and extracts second job data having a job type that matches the job type of the matching target from the searched second job data. The control unit 33 searches and extracts second job data having a job title that matches the job title of the matching target from the searched second job data. The control unit 33 calculates the degree of agreement or similarity of the searched second job data to the text of the matching target job posting, and arranges and lists the second job data in order of the degree of agreement or similarity. The control unit 33 determines that the second job data whose degree of agreement or similarity to the text of the matching target job posting is equal to or greater than a threshold corresponds to the matching target.
[0050] In addition, when there are multiple second job data, the control unit 33 may determine that the second job data with the highest degree of agreement or similarity to the text of the job advertisement of the matching target corresponds to the matching target. Alternatively, when there are multiple second job data in which the degree of agreement or similarity of the text included in the job advertisement is equal to or greater than a threshold, the control unit 33 may determine that the second job data with the highest degree of agreement or similarity matches the text of the job advertisement of the first job data. In addition, when there are multiple first job data registered by the target recruiter in the first DB40, the control unit 33 repeats the above process for each of the multiple first job data, and calculates the degree of agreement or similarity between the text of the job advertisement of each of the multiple first job data and each of the multiple second job data. Then, the control unit 33 may identify the second job data with the highest degree of agreement or similarity for the text of each of the multiple first job data, and determine that the second job data corresponds to each of the multiple first job data. This makes it possible to assign the corresponding second job data to each of the multiple first job data, and to identify the first job data that is not managed as second job data.
[0051] Secondly, the control unit 33 identifies non-operating job data from the second job data based on data indicating the operating status of the second job data. Such identification processing may be referred to as non-operating identification processing. As described above, the data indicating the operating status of the second job data may include a history of sending and receiving scout emails related to the second job data, a history of applications from job seekers related to the second job data, a history of interviews between recruiters (including intermediaries such as agents) and job seekers related to the second job data, and the like. Here, interviews between recruiters and job seekers include interviews conducted online and interviews conducted offline.
[0052] For example, the control unit 33 may identify non-operating job offer data based on whether or not a scout email has been sent, whether or not a reply email to the scout email has been received, the frequency of sending scout emails, the frequency of receiving reply emails to the scout emails, etc. In detail, the control unit 33 may identify second job offer data for which no scout email has been sent as non-operating job offer data, may identify second job offer data for which no reply email has been received as non-operating job offer data, may identify second job offer data for which the frequency of sending scout emails is lower than a threshold as non-operating job offer data, and may identify second job offer data for which the frequency of receiving reply emails is lower than a threshold as non-operating job offer data.
[0053] For example, the control unit 33 may identify non-operating vacancy data based on the presence or absence of applications from job seekers and the number of applications from job seekers. In particular, the control unit 33 may identify second vacancy data for which there are no applications from job seekers as non-operating vacancy data, or may identify second vacancy data for which the number of applications from job seekers is less than a threshold as non-operating vacancy data. Note that, in the case where the target employer has multiple second vacancy data registered in the second DB 50, the login history to the second DB 50 does not provide a basis for determining whether a specific second vacancy data included therein is in operation, and therefore may not be used to determine the operation status of the second vacancy data.
[0054] For example, the control unit 33 may identify non-operating vacancy data based on the presence or absence of an interview between the recruiter and the job seeker, and the number and frequency of interviews with the job seeker. In particular, the control unit 33 may identify second vacancy data in which there is no interview with the job seeker as non-operating vacancy data, or may identify second vacancy data in which the number and frequency of interviews with the job seeker are less than a threshold value as non-operating vacancy data.
[0055] Third, the control unit 33 identifies operating job vacancy data from the first job vacancy data based on data indicating the operating status of the first job vacancy data. Such identification processing may be referred to as an operating identification processing. As described above, the data indicating the operating status of the first job vacancy data may include a history of sending and receiving scout emails related to the first job vacancy data, a history of applications from job seekers related to the first job vacancy data, a history of interviews with job seekers related to the first job vacancy data, etc.
[0056] For example, the control unit 33 may identify the operating job offer data based on whether or not a scout email has been sent, whether or not a reply email to the scout email has been received, the frequency of sending the scout email, the frequency of receiving a reply email to the scout email, etc. In detail, the control unit 33 may identify the first job offer data for which a scout email has been sent as the operating job offer data, may identify the first job offer data for which a reply email has been received as the operating job offer data, may identify the first job offer data for which the frequency of sending scout emails is higher than a threshold as the operating job offer data, and may identify the first job offer data for which the frequency of receiving reply emails is higher than a threshold as the operating job offer data.
[0057] For example, the control unit 33 may identify the active job offer data based on the presence or absence of applications from job seekers and the number of applications from job seekers. In particular, the control unit 33 may identify the first job offer data to which a job seeker has applied as the active job offer data, or may identify the first job offer data to which the number of applications from job seekers is greater than a threshold as the active job offer data. Note that, in the case where the target employer has registered multiple first job offer data in the first DB 40, the login history to the first DB 40 does not provide a basis for determining whether a specific first job offer data included therein is active or not, and therefore may not be used to determine the active status of the first job offer data.
[0058] For example, the control unit 33 may identify the operating job offer data based on whether or not there is an interview with a job seeker, and the number and frequency of interviews with a job seeker. In particular, the control unit 33 may identify the first job offer data in which there is an interview with a job seeker as the operating job offer data, or may identify the first job offer data in which the number and frequency of interviews with a job seeker are greater than a threshold value as the operating job offer data.
[0059] Fourth, the control unit 33 identifies high score job vacancy data, which has a score indicating the possibility of hiring a job seeker higher than a predetermined score, from at least one of the first job vacancy data and the second job vacancy data. Such an identification process may be referred to as a high score job vacancy identification process.
[0060] For example, as in operation examples 1 and 3 described below, for posted job data in which job data corresponding to the first job data is managed as second job data in the second DB50, the job data used to determine the score may be the second job data corresponding to the posted job data. The job data used to determine the score may be the first job data corresponding to the posted job data.
[0061] For example, as in operation examples 2 and 4 described below, for non-posted job data in which job data corresponding to the first job data is not managed as second job data in the second DB50, the job data used to determine the score may be the first job data corresponding to the non-posted job data.
[0062] For example, the control unit 33 may calculate a score related to evaluation elements for evaluating the first job recruitment data. The evaluation elements may include one or more elements selected from the amount of information included in the first job recruitment data (hereinafter, information amount), the expression of the sentences included in the second job recruitment data (hereinafter, expression), and the terms included in the first job recruitment data (hereinafter, expertise). The terms included in the first job recruitment data are terms that represent the job content of the personnel desired by the employer. A score indicating the possibility of hiring the job seeker may be calculated based on the scores of the amount of information, expression, and expertise.
[0063] The information score may be calculated using the options below.
[0064] In option 1-1, the score for the amount of information may be calculated based on the result of comparing the number of characters contained in the entire first job data with the appropriate range. For example, the score for the amount of information may be calculated lower if the number of characters contained in the entire first job data is smaller than the lower limit of the appropriate range. The score for the amount of information may be calculated lower if the number of characters contained in the entire first job data is larger than the upper limit of the appropriate range.
[0065] In option 1-2, the score for the amount of information may be calculated based on the amount of information for each item. For example, the score for an item may be calculated based on a comparison result between the number of characters included in the item and the appropriate range for the item, and the score for the overall amount of information for the first job vacancy data may be calculated based on the score for each item. In such a case, the appropriate range for the item may differ for each item. The score for the overall amount of information for the first job vacancy data may be calculated based on the score for each item and the weighting value for each item.
[0066] The score for an expression may be calculated according to the options listed below.
[0067] In option 2-1, the expression score may be calculated based on whether or not grammatically inappropriate expressions are included by analyzing the expressions of sentences included in the first job data. For example, the more grammatically inappropriate expressions there are, the lower the expression score may be calculated. The expression analysis may be performed using a tool such as morphological analysis. The expression analysis may be performed using machine learning represented by AI (Artificial Intelligence).
[0068] In Option 2-2, the score for expression may be calculated based on the consistency between the item and the sentences contained in the item. For example, if the "specific job content" item contains sentences other than the specific content of the industry or job type that the employee desired by the employer actually works in (for example, sentences about the desired personality type), the score for expression may be calculated low. The consistency analysis may be performed using a tool such as morphological analysis. The consistency analysis may be performed using machine learning represented by AI.
[0069] In option 2-3, the score for the expression may be calculated based on the consistency between sentences included in each of two or more items. For example, if a sentence included in the "Mission" item is inconsistent with a sentence included in the "Charm" chasing tree, the score for the expression may be calculated to be low. The analysis of the consistency may be performed using a tool such as a morphological analysis. The analysis of the consistency may be performed using machine learning represented by AI.
[0070] Expertise scores may be calculated using the options below.
[0071] In option 3-1, the score for expertise may be calculated by referring to a database in which terms that describe the job content of the personnel desired by the recruiter are registered. For example, if a term registered in the database is included in the first recruitment data, the score for expertise may be calculated to be high.
[0072] Here, the database may be considered as a dictionary that associates terms expressing job content with jobs. The terms expressing job content may include not only terms actually used in the first job data, but also terms generally used in jobs. The terms expressing job content may be registered by the recruiter, or may be registered by a third party other than the recruiter. The database may be provided in the above-mentioned management unit 32, or may be provided in an external device provided separately from the management device 30.
[0073] In option 3-2, the expertise score may be calculated based on the similarity to the first job data determined to have a higher expertise score than a threshold. The similarity may be determined using machine learning such as AI. For the first job data determined to have a higher expertise score than a threshold, the first job data calculated by option 3-1 and having a higher score than the threshold may be used, or the first job data selected by the employer may be used.
[0074] Although not particularly limited, the above-mentioned processes may be executed in the following order: name matching determination process, non-working identification process, working identification process, and high-score job offer identification process. The order of the non-working identification process and the working identification process may be reversed. However, the high-score job offer identification process may be executed before the name matching determination process. The non-working identification process and the working identification process may be executed before the name matching determination process.
[0075] (Example of operation) An operation example according to the embodiment will be described below. The operation example may be the following. In the following, a case will be described in which the job data corresponding to the first job data managed in the first DB40 includes the second job data (posted job data) managed in the second DB50 and the job data (non-posted job data) that is not managed in the second DB50.
[0076] In operation example 1, as shown in FIG. 3, the management device 30 identifies posted job data in which job data corresponding to the first job data is managed in the second DB 50 as second job data. The management device 30 identifies high score job data from the job data corresponding to the posted job data. The job data used to identify the score may be the second job data corresponding to the posted job data. The job data used to identify the score may be the first job data corresponding to the posted job data. The management device 30 outputs information (hereinafter, operation promotion information) encouraging the target recruiter to actively operate the posted job data corresponding to the high score job data. The operation promotion information may be information encouraging the sending of scout emails to job seekers, or information encouraging an interview with a job seeker.
[0077] In other words, when the management device 30 determines that the job data corresponding to the high score job data is managed in the second DB 50 as second job data, it outputs information to the target employer encouraging them to actively operate the job data corresponding to the high score job data.
[0078] The management device 30 may identify low-score job data from the job data corresponding to the posted job data. The management device 30 may output information (hereinafter, improvement promotion information) to the recruiter to encourage improvement of the posted job data corresponding to the low-score job data. Low-score job data is job data in which the score indicating the possibility of hiring a job seeker is lower than a predetermined score.
[0079] In operation example 2, as shown in FIG. 3, the management device 30 identifies non-posted job data in which job data corresponding to the first job data is not managed in the second DB50 as second job data. The management device 30 identifies high score job data from the job data corresponding to the non-posted job data. The job data used to identify the score may be the first job data corresponding to the non-posted job data. The management device 30 outputs information (hereinafter, registration promotion information) that encourages the non-posted job data corresponding to the high score job data to be registered in the second DB50. The registration promotion information may be information that notifies the user that job data corresponding to the high score job data is not registered in the second DB50.
[0080] The management device 30 may identify low score job posting data from job posting data corresponding to non-posted job posting data. The management device 30 may output information (improvement promotion information) to the employer to encourage review and improvement of the content of the job posting of the non-posted job posting data corresponding to the low score job posting data. Low score job posting data is job posting data with a score indicating the possibility of hiring a job seeker that is lower than a predetermined score.
[0081] In other words, when it is determined that the job data corresponding to the high score job data is not managed as second job data in the second DB50, the management device 30 outputs information prompting the user to register the job data corresponding to the high score job data in the second DB50.
[0082] In operation example 3, as shown in FIG. 4, the management device 30 identifies posted job data in which job data corresponding to the first job data is managed in the second DB 50 as second job data. The management device 30 identifies non-operating job data from the second job data corresponding to the posted job data. The management device 30 identifies high score job data from the job data corresponding to the non-operating job data. The job data used to identify the score may be the second job data corresponding to the non-operating job data. The job data used to identify the score may be the first job data corresponding to the non-operating job data. The management device 30 outputs information (operation promotion information) that encourages active operation of the non-operating job data corresponding to the high score job data. The operation promotion information may be information that encourages the sending of a scout email, or may be information that encourages an interview.
[0083] In other words, when the management device 30 determines that job data corresponding to the high score job data is managed in the second DB 50 as non-operating job data, it outputs information (operation promotion information) that encourages actively operating the non-operating job data corresponding to the high score job data.
[0084] In operation example 4, as shown in FIG. 5, the management device 30 identifies non-posted job data in which job data corresponding to the first job data is not managed in the second DB50 as second job data. The management device 30 identifies operating job data from the first job data corresponding to the non-posted job data. The management device 30 identifies high score job data from the job data corresponding to the operating job data. The job data used to identify the score may be the first job data corresponding to the non-posted job data. The management device 30 outputs information (registration promotion information) that encourages the job data corresponding to the high score job data to be registered in the second DB50. The registration promotion information may be information that notifies that job data corresponding to the high score job data is not registered in the second DB50.
[0085] In other words, when the management device 30 determines that job data corresponding to the operating job data and high score job data is not managed as second job data in the second DB50, it outputs information (registration promotion information) encouraging registration of the job data corresponding to the operating job data and high score job data in the second DB50.
[0086] (Recruitment data management method) The job data management method according to the embodiment will be described below. Fig. 6 is a diagram showing the job data management method according to the embodiment.
[0087] As shown in Fig. 6, in step S10, the management device 30 determines whether or not the job data corresponding to the first job data is posted job data managed as second job data in the second DB50. If the job data corresponding to the first job data is posted job data, the management device 30 executes processing of step S11. If the job data corresponding to the first job data is non-posted job data, the management device 30 executes processing of step S14. Step S10 is an example of a name matching determination process.
[0088] In step S11, the management device 30 determines whether the job data corresponding to the posted job data is non-working job data. If the job data corresponding to the posted job data is non-working job data, the management device 30 executes the process of step S12. If the job data corresponding to the posted job data is working job data, the management device 30 ends the series of processes. Step S11 is an example of a non-working identification process.
[0089] In step S12, the management device 30 determines whether the job data corresponding to the non-operating job data is high score job data. The job data used to identify the score may be second job data corresponding to the posted job data. The job data used to identify the score may be first job data corresponding to the posted job data. The management device 30 executes the process of step S13 when the job data corresponding to the non-operating job data is high score job data. The management device 30 ends the series of processes when the job data corresponding to the non-operating job data is low score job data. Step S12 is an example of a high score job identification process.
[0090] In step S13, the management device 30 outputs information (operation promotion information) that encourages active operation of the non-operating vacancy data corresponding to the high score vacancy data (for example, the above-mentioned operation example 3).
[0091] In step S14, the management device 30 determines whether the job data corresponding to the non-posted job data is working job data. If the job data corresponding to the non-posted job data is working job data, the management device 30 executes the process of step S15. If the job data corresponding to the non-posted job data is non-working job data, the management device 30 ends the series of processes. Step S14 is an example of an operation identification process.
[0092] In step S15, the management device 30 determines whether the job data corresponding to the operating job data is high score job data. The job data used to identify the score may be the first job data corresponding to the unpublished job data. The management device 30 executes the process of step S16 when the job data corresponding to the operating job data is high score job data. The management device 30 ends the series of processes when the job data corresponding to the operating job data is low score job data. Step S15 is an example of a high score job identification process.
[0093] In step S16, the management device 30 outputs information (registration promotion information) that prompts the user to register the operating recruitment data corresponding to the high score recruitment data in the second DB 50 (for example, the above-mentioned operation example 3).
[0094] 6 illustrates a case where the process of step S11 is executed, but the process of step S11 may be omitted as in the above-mentioned Operation Example 1. Similarly, while FIG. 6 illustrates a case where the process of step S14 is executed, the process of step S14 may be omitted as in the above-mentioned Operation Example 2.
[0095] 6, the management device 30 may output information (improvement promotion information) to the recruiter to encourage improvement of the recruitment data determined to be low-score recruitment data in step S12. Similarly, the management device 30 may output information (improvement promotion information) to the recruiter to encourage improvement of the recruitment data determined to be low-score recruitment data in step S15.
[0096] 6, the high-score job offer identification process (steps S12 and S15) may be executed before the name matching determination process (step S10). In such a case, the job offer data used to identify the score may be the entire first job offer data and the entire second job offer data.
[0097] 6, the non-operating identification process (step S11) may be executed before the name matching determination process (step S10). In such a case, the job offer data used to determine non-operating status may be the first job offer data and the second job offer data in their entirety.
[0098] 6, the operation determination process (step S14) may be executed before the name matching determination process (step S10). In such a case, the job data used to determine the operation may be the first job data and the second job data in their entirety.
[0099] (Action and Effects) In the embodiment, the management device 30 judges whether the job offer data corresponding to the first job offer data is managed as the second job offer data in the second DB 50 based on the degree of agreement (or similarity) between the first job offer data and the second job offer data. With this configuration, job offer data that is managed in the first DB 40 but not in the second DB 50 can be identified, and the efficiency of the recruiter's recruitment activities can be improved. In detail, even if the target recruiter uses multiple DBs (recruitment media), such as the first DB 40 and the second DB 50, it is possible to prevent a situation in which certain job offer data is registered or published only in some DBs or recruitment media, and the opportunity to catch the attention of a job seeker is missed. Furthermore, by identifying the second job offer data corresponding to the first job offer data, the first job offer data and the second job offer data can be linked and centrally managed using the same ID or the like.
[0100] For example, even if the recruiter initially registers the same recruitment data in the first DB 40 and the second DB 50, there is a possibility that a mismatch may occur between the first recruitment data registered in the first DB 40 and the second recruitment data registered in the second DB 50 when updating the recruitment data. When a mismatch occurs in the recruitment data, it is difficult for the recruiter's hiring manager to recognize that the data is the same recruitment data, and it is possible that the application status for the first recruitment data and the second recruitment data cannot be managed in a centralized manner. In the embodiment, even if a discrepancy occurs between the first recruitment data and the second recruitment data, it is possible to determine that the data are corresponding recruitment data based on the degree of match, thereby improving the efficiency of the recruiter's recruitment activities.
[0101] In the embodiment, when it is determined that the job offer data corresponding to the high score job offer data is managed in the second DB 50 as the second job offer data, the management device 30 outputs information (operation promotion information) that encourages the active operation of the job offer data corresponding to the high score job offer data. With this configuration, it is possible to actively utilize the second job offer data that is likely to employ a job seeker among the second job offer data managed in the second DB 50. As a result, particularly for recruiters who manage a large amount of job offer data and have limited resources such as recruiters, it is possible to allocate resources to job offer data that is likely to lead to a contract and efficiently operate the job offer data.
[0102] In the embodiment, when it is determined that job offer data corresponding to the high score job offer data is not managed as second job offer data in the second DB 50, the management device 30 outputs information (registration promotion information) that encourages the job offer data corresponding to the high score job offer data to be registered in the second DB 50. With this configuration, the possibility of successful recruitment can be increased by expanding the media for posting job offer data that is likely to be able to hire a job seeker to the second DB 50.
[0103] In the embodiment, when it is determined that job offer data corresponding to the high score job offer data is managed as non-operating job offer data in the second DB 50, the management device 30 outputs information (operation promotion information) that encourages active operation of the non-operating job offer data corresponding to the high score job offer data. With this configuration, it is possible to actively utilize the second job offer data that is not in operation despite having a high possibility of hiring a job seeker among the second job offer data managed in the second DB 50.
[0104] In the embodiment, when it is determined that job data corresponding to the operating job data and the high score job data is not managed as second job data in the second DB 50, the management device 30 outputs information (registration promotion information) that encourages registration of the job data corresponding to the operating job data and the high score job data in the second DB 50. With this configuration, the possibility of successful recruitment can be increased by expanding the media for posting job data that is operating in the first DB 40 and has a high possibility of hiring a job seeker to the second DB 50.
[0105] [Change Example 1] Modification 1 of the embodiment will be described below. Differences from the embodiment will be mainly described below.
[0106] Specifically, in the embodiment, the score indicating the possibility of hiring the job seeker is calculated based on the scores regarding the evaluation elements of the amount of information, the expression, and the expertise. In contrast, in the first modification, the score indicating the possibility of hiring the job seeker is determined using a learning model. In this case, the control unit 33 includes an artificial intelligence unit having the learning model.
[0107] The learning model may be a learning model such as a language model such as a transformer including GPT (Generative Pretrained Transformer, including GPT-1, GPT-2, and GPT-3), BERT (Bidirectional Encoder Representations from Transformers), or BART (Bidirectional and Auto-regressive Transformer), etc. An artificial intelligence unit equipped with such a learning model may be referred to as AI.
[0108] The learning model may be a learning model based on a machine learning algorithm. Specific examples of machine learning algorithms include nearest neighbor methods, naive Bayes methods, decision trees, and support vector machines. The learning model may also be deep learning that uses a neural network to generate features and connection weighting coefficients for learning. The artificial intelligence unit can apply the above algorithms as appropriate.
[0109] The artificial intelligence unit may perform machine learning using teacher data. Teacher data refers to learning data, and is composed of pairs of input data for learning and output data (correct answer data). Note that a trained model refers to a model that has been trained (learned) in advance using appropriate teacher data (learning data) for a learning model that follows any machine learning algorithm such as deep learning.
[0110] However, the trained model may include not only a model for which appropriate training data has been obtained in advance but for which no further training is performed, but also a model for which additional training is performed. Additional training may also be performed after the device is installed at the site of use.
[0111] The artificial intelligence unit may also perform machine learning by so-called unsupervised learning to construct a trained model. Unsupervised learning is a method of learning a process by providing a large amount of input data alone without providing output data corresponding to the input data.
[0112] First, the generation of the learning model will be described. As shown in FIG. 7, the model generation unit 33A generates a learning model by learning the correlation between the job data and the contract data. The job data may include job data registered by the target recruiter, as well as job data registered by recruiters other than the target recruiter. In other words, the job data may include job data managed in the first DB 40, and may include job data managed in the second DB 50. The job data may be job data managed in association with contract data. The contract data is data indicating whether or not the recruitment of personnel has been successful in the job posting of the job data. The job data and contract data input to the model generation unit 33A may be referred to as learning data. The model generation unit 33A may be provided in the control unit 33. The contract data may be received from the first DB 40 or the second DB 50, and may be managed by the management unit 32. The learning model (trained model) may be managed by the management unit 32. In addition, the artificial intelligence unit equipped with the learning model may be an external configuration of the management device 30. In this case, the artificial intelligence unit may be configured to be connected to the management device 30 or the like via the network 200, receive input from the management device 30, and return instructed output to the management device 30.
[0113] Secondly, the specification of a score indicating the possibility of employing a job seeker will be described. As shown in FIG. 8, the score specification unit 33B inputs job offer data to a learning model (trained model) to obtain a score indicating the possibility of employing a job seeker from the learning model. Here, the learning model is a learning model that is trained to input job offer data and output a score indicating the possibility of employing. The job offer data input to the score specification unit 33B may be read as job offer data to be identified in order to distinguish it from job offer data that is learning data. The score specification unit 33B may be provided in the control unit 33. In the above-mentioned operation example 1 or 3, the job offer data to be identified in the score may be the second job offer data. In the above-mentioned operation example 2 or 4, the job offer data to be identified in the score may be the first job offer data. In addition, when the artificial intelligence unit is an external configuration of the management device 30, the management device 30 may input the job offer data to the learning model by transmitting the job offer data to the artificial intelligence unit that is an external configuration.
[0114] For example, as in the above-mentioned operation example 1 or 3, for posted job data in which job data corresponding to the first job data is managed as the second job data in the second DB50, the learning model may be generated by learning the correlation between the job data and the contract data managed in the second DB50. By generating a learning model by learning the correlation between the job data and the contract data managed in the second DB50, the job data in the second DB50 that is more likely to be able to employ a job seeker can output a higher value as a score indicating the possibility of employment. This makes it possible to actively operate job data that is more likely to be able to employ a job seeker by using the second DB50. However, the correlation between the job data and the contract data managed in the first DB40 may be used in generating the learning model.
[0115] For example, as in the above-mentioned operation example 2 or 4, even for unposted job data in which job data corresponding to the first job data is not managed as second job data in the second DB50, the learning model may be generated by learning the correlation between the job data and the contract data managed in the second DB50. By generating a learning model by learning the correlation between the job data and the contract data managed in the second DB50, the higher the job data in the second DB50 is likely to be able to employ a job seeker, the higher the score indicating the employability can be output. This makes it possible to encourage the use of the second DB50 to register job data that is likely to employ a job seeker in the second DB50. However, the correlation between the job data and the contract data managed in the first DB40 may be used in generating the learning model.
[0116] [Other embodiments] Although the present invention has been described by the above-mentioned embodiment, the description and drawings forming a part of this disclosure should not be understood as limiting the present invention. From this disclosure, various alternative embodiments, examples and operating techniques will become apparent to those skilled in the art.
[0117] In the above embodiment, the management device 30 performs various storage and control, but multiple external devices may be used instead of the management device 30. In other words, various information and programs may be distributed and stored in multiple external devices using block chain technology or the like.
[0118] In the above disclosure, a case has been described in which the management device 30 is separate from the first DB 40 and the second DB 50. However, the above disclosure is not limited to this. The management device 30 may be a device integrated with the first DB 40, or may be a device integrated with the second DB 50. In such a case, the management unit 32 may constitute the first DB 40, or may constitute the second DB 50.
[0119] In the above disclosure, a case has been described in which the job data corresponding to the first job data managed in the first DB40 includes the second job data (posted job data) managed in the second DB50 and the job data (non-posted job data) not managed in the second DB50. However, the above disclosure is not limited to this. The job data corresponding to the second job data managed in the second DB50 may include the first job data (posted job data) managed in the first DB40 and the job data (non-posted job data) not managed in the first DB40. In such a case, the above disclosure may be read by replacing the first job data with the second job data.
[0120] Although not specifically mentioned in the above disclosure, a program may be provided that causes a computer to execute each process performed by the management device 30. The program may also be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
[0121] Alternatively, a chip may be provided that is configured by a memory that stores a program for executing each process performed by the management device 30 and a processor that executes the program stored in the memory.
[0122] [Note] The above disclosure may be expressed as follows:
[0123] The first feature is a vacancy data management system comprising a first vacancy database that manages first vacancy data registered by a target employer, a second vacancy database that manages second vacancy data registered by the target employer, and a management device that can access both the first vacancy database and the second vacancy database, wherein the management device determines whether or not vacancy data corresponding to the first vacancy data is managed as the second vacancy data in the second vacancy database based on the degree of match between the first vacancy data and the second vacancy data.
[0124] A second feature is a job data management system in which, in the first feature, the management device identifies high score job data from at least one of the first job data and the second job data, the high score job data having a score indicating the possibility of hiring a job seeker that is higher than a predetermined score, and when it is determined that the job data corresponding to the high score job data is managed in the second job database as the second job data, the management device outputs information encouraging the proactive operation of the job data corresponding to the high score job data.
[0125] A third feature is a job data management system in which, in the first or second feature, the management device identifies high score job data from the first job data, the high score job data indicating the possibility of hiring a job seeker being higher than a predetermined score, and if it is determined that the job data corresponding to the high score job data is not managed in the second job database as the second job data, it outputs information to encourage the registration of the job data corresponding to the high score job data in the second job database.
[0126] A fourth feature is a job data management system in which, in at least one of the first to third features, the management device calculates a degree of similarity between the first job data and the second job data by comparing text data of the first job data and text data of the second job data.
[0127] A fifth feature is a recruitment data management system in which, in at least one of the first to fourth features, the management device determines that the first recruitment data and the second recruitment data do not match when the job type or position advertised in the first recruitment data does not match the job type or position advertised in the second recruitment data.
[0128] A sixth feature is a job data management system in at least one of the first to fifth features, wherein the management device determines whether a name of an employer in the first job data and a name of an employer in the second job data match, and if the name of the employer in the first job data and the name of the employer in the second job data match, calculates a degree of match between the first job data and the second job data by comparing a sentence in the first job data and a sentence in the second job data.
[0129] A seventh feature is a job data management system in which, in at least one of the first to sixth features, the management device calculates a degree of matching between each of the multiple second job data and the first job data, and determines that the second job data among the multiple second job data having the highest degree of matching is the job data corresponding to the first job data.
[0130] An eighth feature is a job data management system in which, in at least one of the first feature to the seventh feature, the management device identifies non-operating job data from the second job data based on data indicating the operation status of the second job data, identifies high score job data from at least one of the first job data and the second job data, the high score job data having a score indicating the possibility of hiring a job seeker higher than a predetermined score, and when it is determined that the job data corresponding to the high score job data is managed in the second job database as the non-operating job data, outputs information encouraging the non-operating job data corresponding to the high score job data to be actively operated.
[0131] A ninth feature is the job data management system of the eighth feature, wherein the data indicating the operating status includes one or more data selected from a history of sending and receiving scout emails related to the second job data, a history of applications from job seekers related to the second job data, and a history of interviews with job seekers related to the second job data.
[0132] A tenth feature is a job data management system in which, in at least one of the first to ninth features, the management device identifies operating job data from the first job data based on data indicating the operation status of the first job data, identifies high score job data from the first job data having a score indicating the possibility of hiring a job seeker that is higher than a predetermined score, and when it is determined that the operating job data and job data corresponding to the high score job data are not managed as the second job data in the second job database, outputs information to encourage the registration of the operating job data and the job data corresponding to the high score job data in the second job database.
[0133] An eleventh feature is the job data management system of the tenth feature, wherein the data indicating the operating status includes one or more pieces of data selected from a history of sending and receiving scout emails related to the first job data, a history of applications from job seekers related to the first job data, and a history of interviews with job seekers related to the first job data.
[0134] A twelfth feature is a recruitment data management system in accordance with the second, eighth or tenth feature, wherein the management device generates a learning model by learning the correlation between recruitment data managed in at least one of the first recruitment database and the second recruitment database and data indicating whether or not the recruitment data has resulted in a successful recruitment, and uses the learning model to identify a score indicating the possibility of recruiting the job seeker.
[0135] A thirteenth feature is a vacancy data management method comprising: a step A in which a first vacancy database manages first vacancy data registered by a target employer; a step B in which a second vacancy database manages second vacancy data registered by the target employer; and a step C in which a management device that can access both the first vacancy database and the second vacancy database determines whether vacancy data corresponding to the first vacancy data is managed as the second vacancy data in the second vacancy database based on a degree of match between the first vacancy data and the second vacancy data. [Explanation of symbols]
[0136] 10...first terminal, 20...second terminal, 30...management device, 31...communication unit, 32...management unit, 33...control unit, 33A...model generation unit, 33B...score determination unit, 40...first DB, 50...second DB, 100...job data management system, 200...network
Claims
1. A first job vacancy database that manages first job vacancy data registered by target employers; A second job vacancy database that manages second job vacancy data registered by the target job vacant employer; A management device that can access both the first job vacancy database and the second job vacancy database, The management device determines whether or not job data corresponding to the first job data is managed as the second job data in the second job database based on the degree of match between the first job data and the second job data.
2. The management device includes: Identifying high-score job vacancy data, which has a score indicating a possibility of employing a job seeker that is higher than a predetermined score, from at least one of the first job vacancy data and the second job vacancy data; A job data management system as described in claim 1, which outputs information encouraging active operation of the job data corresponding to the high score job data when it is determined that the job data corresponding to the high score job data is managed as the second job data in the second job database.
3. The management device includes: Identifying high-score job vacancy data from the first job vacancy data, the high-score job vacancy data having a score indicating a possibility of employing the job seeker higher than a predetermined score; A job data management system as described in claim 1, which outputs information encouraging registration of job data corresponding to the high score job data in the second job database when it is determined that job data corresponding to the high score job data is not managed as the second job data in the second job database.
4. The job data management system according to claim 1 , wherein the management device calculates a degree of agreement between the first job data and the second job data by comparing text data of the first job data and text data of the second job data.
5. The job data management system of claim 1, wherein the management device determines that the first job data and the second job data do not match when the job type or position advertised in the first job data does not match the job type or position advertised in the second job data.
6. The management device includes: Determining whether the name of the recruiter in the first recruitment data and the name of the recruiter in the second recruitment data match; A job data management system as described in claim 1, wherein when the name of the employer in the first job data and the name of the employer in the second job data match, the degree of match between the first job data and the second job data is calculated by comparing the text of the first job data and the text of the second job data.
7. The management device includes: Calculating a degree of match between each of the plurality of second job vacancy data and the first job vacancy data; The job data management system according to claim 1 , wherein the second job data having the highest degree of matching among the plurality of second job data is determined to be the job data corresponding to the first job data.
8. The management device includes: Identifying non-operating job data among the second job data based on data indicating the operation status of the second job data; Identifying high-score job vacancy data, which has a score indicating a possibility of employing a job seeker that is higher than a predetermined score, from at least one of the first job vacancy data and the second job vacancy data; A job data management system as described in claim 1, which outputs information encouraging a proactive operation of the non-operating job data corresponding to the high score job data when it is determined that the job data corresponding to the high score job data is managed in the second job database as the non-operating job data.
9. The job data management system of claim 8, wherein the data indicating the operating status includes one or more pieces of data selected from a history of sending and receiving scout emails related to the second job data, a history of applications from job seekers related to the second job data, and a history of interviews with job seekers related to the second job data.
10. The management device includes: Identifying operating job vacancy data among the first job vacancy data based on data indicating the operation status of the first job vacancy data; Identifying high-score job vacancy data from the first job vacancy data, the high-score job vacancy data having a score indicating a possibility of employing the job seeker higher than a predetermined score; The job data management system of claim 1, which outputs information encouraging registration of the operating job data and the job data corresponding to the high score job data in the second job database when it is determined that the operating job data and the job data corresponding to the high score job data are not managed as the second job data in the second job database.
11. The job data management system of claim 10, wherein the data indicating the operating status includes one or more pieces of data selected from a history of sending and receiving scout emails related to the first job data, a history of applications from job seekers related to the first job data, and a history of interviews with job seekers related to the first job data.
12. The management device includes: Generate a learning model by learning a correlation between recruitment data managed in at least one of the first recruitment database and the second recruitment database and data indicating whether or not the recruitment data has been successfully employed; The recruitment data management system of claim 2, claim 8 or claim 10, further comprising: determining a score indicating the likelihood of employing the job seeker using the learning model.
13. A step A in which a first job vacancy database manages first job vacancy data registered by a target job vacant; A step B in which a second job vacancy database manages second job vacancy data registered by the target job vacant; A job data management method comprising: a step C in which a management device capable of accessing both the first job vacancy database and the second job vacancy database determines, based on the degree of match between the first job vacancy data and the second job vacancy data, whether job data corresponding to the first job vacancy data is managed in the second job vacancy database as the second job vacancy data.
Citation Information
Patent Citations
Applicant management system
JP2017016298A
