CN107004167B

CN107004167B - Publication recruitment normalization and deduplication

Info

Publication number: CN107004167B
Application number: CN201580064463.7A
Authority: CN
Inventors: D.哈德克; G.B.马丁; J.博林格尔; L.M.沃尔; J.维姆布纳拉延; S.卡马特; P.戈文达拉简; A.D.迪尔; O.索尔森
Original assignee: 微软技术许可有限责任公司
Current assignee: Microsoft Technology Licensing LLC
Priority date: 2014-09-30
Filing date: 2015-03-25
Publication date: 2022-04-19
Anticipated expiration: 2035-03-25
Also published as: CN107004167A; WO2016053382A1

Abstract

Techniques for standardizing and deduplicating unpaid job placements obtained from third-party systems are described. Obtaining the unpaid job posting from the third-party system through the social networking service. The positions and descriptions of the unpaid job postings are standardized and combined into a standardized unpaid job postings. Performing a deduplication process to prevent the standardized unpaid job posting from replacing a paid job posting within the social networking service and to prevent the standardized unpaid job posting from replacing a more authoritative unpaid job posting within the social networking service.

Description

Publication recruitment normalization and deduplication

Priority requirement

This PCT application claims the benefit of priority from U.S. patent application No. 14/502,224 entitled "open recruitment STANDARDIZATION AND DEDUPLICATION (JOB publication STANDARDIZATION AND DEDUPLICATION)" filed on 9, 30 days 2014 AND the benefit of priority from U.S. patent application No. 14/502,261 entitled "open recruitment STANDARDIZATION AND DEDUPLICATION (JOB publication STANDARDIZATION AND DEDUPLICATION)" filed on 9, 30 days 2014, both of which are incorporated herein by reference in their entirety.

Technical Field

The present invention relates generally to data processing systems for hosting a job posting and, in some embodiments, to techniques for standardizing and deduplicating job postings that exist on different third-party systems.

Background

In a typical job hosting service, a company representative posts a job posting to the job hosting service so that users of the job hosting service can search, browse, and, in some cases, apply for work associated with a particular job posting. In exchange for presenting a job posting to a user of the work hosting service, the company that issued the job posting will typically pay some fee.

Drawings

Some embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

FIG. 1 is a network diagram illustrating a network environment suitable for social networking services, according to some example embodiments.

Fig. 2 is a block diagram illustrating components of a social networking system, according to some example embodiments.

Fig. 3A is a flow diagram illustrating operation of the work capture module and the work normalization module in performing a method for normalizing a job posting obtained from a third-party system, according to some example embodiments.

Fig. 3B is a flow diagram illustrating optional operations of the job normalization module in performing a method for normalizing a job posting obtained from a third-party system, according to some example embodiments.

Fig. 4A is a flow diagram illustrating operation of a work deduplication module, and optionally a work capture module and/or a work standardization module, in performing a method for deduplication of a publicly available recruit obtained from a third party system, according to some example embodiments.

Fig. 4B is a flowchart illustrating optional operation of the operational deduplication module in performing a method for deduplication of a publicly available recruit obtained from a third party system, according to some example embodiments.

FIG. 5 is a block diagram illustrating an example of a machine on which one or more embodiments may be implemented.

Detailed Description

Methods, systems, and computer program products are described that separately provide work hosting services that provide different levels of service to paid and unpaid publicly recruits (sometimes referred to as work posts). In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various aspects of the disclosed subject matter. It will be apparent, however, to one skilled in the art that the presently disclosed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the disclosed subject matter.

According to some embodiments, a job hosting service (e.g., associated with a social networking system) hosts both paid and unpaid publicly recruited. For example, through the job posting module of the job hosting service, users of the job hosting service can provide information about specific job openings and generate paid job postings. The job publication typically consists of the name of the company or organization from which the job opening is available, the job name of the job opening, a description of the job function, required or suggested skills, education level, and certificates and/or expertise, etc. In exchange for paying some fee, the paid publicly recruited will be eligible to be presented to the user (e.g., a person working on a social networking system with which the hosted service is integrated).

In some embodiments, the job hosting service may host paid and unpaid job recruitment. In some cases, the paid job posting may be listed directly on the job hosting service, while the unpaid job posting may be received from a third-party system. However, the data format for the job posting received from the third-party system may not match the data format for its job hosting service's job posting usage. In addition, the job posting received from the third-party system can represent a job posting that has been listed by the work hosting service.

In addition to paid job recruitment, the job hosting service may ingest job recruits from a different externally hosted third-party job site. In some embodiments, an automated computer program (e.g., "bot" or "spider") automatically "crawls" related internet websites and finds a job for ingestion. In some embodiments, the job posting is obtained from a data feed maintained by one or more third party partners. The job hosting service stores both paid and unpaid job recruits or has another entity store both paid and unpaid job recruits on its behalf, i.e., job recruits that have been generated by the job recruiting module and have paid a fee to the social networking system and job recruits that are obtained from third party websites and have not paid a fee to the social networking system.

In some embodiments, the unpaid job recruitment is only eligible for presentation to people of the social networking service through the work search interface. As a result, unpaid or free publicly recruited will typically only be presented to social networking service personnel, which may be referred to as "active job candidates" or "active job seekers". These active job seekers are people who are often actively involved in finding new employment opportunities. The paid publication recruitment also qualifies for presentation to the persons of the social networking service through the search interface, but also to such persons through a variety of other channels. For example, the work recommendation engine may match a person profile with a job application with the goal of presenting a relevant job application (i.e., a job application that may be of interest to the person) to the person of the social networking service based on the person's profile data.

In some embodiments, the data format for the job posting received from the third-party system may not match the data format for its job hosting service for job posting use by the social networking system. In such embodiments, the work hosting service standardizes the job placements received from third-party systems so that the job placements can be integrated into the work hosting service.

In some embodiments, the recruitment received from the third-party system represents a recruitment of a job that has been integrated into the work hosting service. In such embodiments, the job hosting service performs a job posting deduplication and replaces the integrated job posting with the new job posting if it is determined that the new job posting is better (e.g., more authoritative) than the integrated job posting.

The various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., by software instructions) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such a processor may constitute a processor-implemented module or article for performing one or more operations or functions. In some example embodiments, the modules and objects referred to herein may comprise processor-implemented modules and/or objects.

Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of the method may be performed by one or more processors or processor-implemented modules. The execution of certain operations may be distributed among one or more processors, not only residing within a single machine or computer, but also being deployed across multiple machines or computers. In some example embodiments, one or more processors may be located in a single location (e.g., within a home environment, office environment, at a server farm, etc.), while in other embodiments, processors may be distributed across multiple locations.

The one or more processors may also be used to support performance of related operations in a "cloud computing" environment or within the context of software as a service ("SaaS"). For example, at least some of the operations may be performed by a group of computers (e.g., of machines including processors), which may be accessed over a network (e.g., the internet) and through one or more suitable interfaces (e.g., Application Program Interfaces (APIs)).

Fig. 1 is a network diagram illustrating a network environment 100 suitable for social networking services, according to some example embodiments. The network environment 100 includes a server machine 110, a database 115, and a device 150 for a user 152, all communicatively coupled to each other through a network 190. The server machine 110 may form all or a portion of the network-based system 105 (e.g., a cloud-based server system configured to provide one or more services to the devices 130 and 150). The database 115 can store a job posting for a social networking service. The server machine 110, the first device 130, and the second device 150 may each be fully or partially implemented in a computer system, as described below with respect to fig. 5.

Also shown in FIG. 1 is a user 152. The user 152 may be a human user (e.g., a human), a machine user (e.g., a computer configured by a software program to interact with the apparatus 150), or any suitable combination thereof (e.g., a human assisted by a machine or a machine supervised by a human). The user 152 is not part of the network environment 100, but is associated with the device 150. In some embodiments, the device 150 is a desktop computer, a vehicle computer, a tablet computer, a navigation device, a portable media device, a smartphone, or a wearable device (e.g., a smart watch or smart glasses) operated by the user 152.

Any of the machines, databases, or devices shown in fig. 1 may be implemented in a general-purpose computer modified (e.g., configured or programmed) by software (e.g., one or more software modules) to perform one or more of the functions described herein for the machine, database, or device. For example, a computer system capable of implementing any one or more of the methods described herein is discussed below with respect to fig. 5. As used herein, a "database" is a data storage resource and may store data structured as text files, tables, spreadsheets, relational databases (e.g., object relational databases), triple stores, hierarchical data stores, or any suitable combination thereof. Further, any two or more of the machines, databases, or devices illustrated in fig. 1 may be combined into a single machine, and the functions described herein for any single machine, database, or device may be subdivided among multiple machines, databases, or devices.

Network 190 may be any network that enables communication between or among machines, databases, and devices (e.g., server machine 110 and device 130). Thus, the network 190 may be a wired network, a wireless network (e.g., a mobile or cellular network), or any suitable combination thereof. Network 190 may include one or more portions that form a private network, a public network (e.g., the internet), or any suitable combination thereof. Thus, the network 190 may include one or more portions that incorporate a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, a mobile telephone network (e.g., a cellular network), a wired telephone network (e.g., a Plain Old Telephone System (POTS) network), a wireless data network (e.g., WiFi or WiMax @) or any suitable combination thereof. Any one or more portions of network 190 may communicate information over a transmission medium. As used herein, "transmission medium" refers to any intangible (e.g., transitory) medium that is capable of transmitting (e.g., transmitting) instructions for execution by a machine (e.g., by one or more processors of such machine), and includes digital or analog communication signals or other intangible medium to facilitate communication of such software.

Fig. 2 is a block diagram illustrating components of social-networking system 210, according to some example embodiments. Social-networking system 210 is an example of network-based system 105 of FIG. 1. In some embodiments, the social networking system 210 includes a work capture module 202, an application server module 204, a work normalization module 206, and a work deduplication module 208, all configured to communicate with each other (e.g., via an interconnect, a bus, a shared memory, a switch, etc.).

Although fig. 2 illustrates the job publication database 220 as a single database, the job publication database 220 can comprise multiple databases, which can be located in one location or multiple locations. Similarly, although fig. 2 illustrates the job publication database 220 as distinct from the social networking system 210, in some embodiments, the job publication database 220 is incorporated within the social networking system 210.

In some embodiments, the job capture module 202 captures, receives, or otherwise obtains the job posting from the third-party system 170. As depicted in fig. 3A and 3B, in some embodiments, the job normalization module 206 normalizes the job application prior to integrating the job application into the job application database 220. As depicted in fig. 4A and 4B, if this integration does not result in a poor job placement instead of a good job placement, the job deduplication module 208 integrates the job placement into the job placement database 220.

In some cases, the work capture module 202, the work normalization module 206, and/or the work deduplication module 208 are configured to process data offline and/or periodically. For example, the job capture module 202 can include a server that periodically obtains a job posting from an associated third-party internet website. Standardizing and de-duplicating third party job placements can be computationally intensive; thus, work standardization and/or deduplication may be done offline.

As will be further described with respect to fig. 3A-3B, the work capture module 202, in conjunction with the work normalization module 206, can obtain and normalize the unpaid job recruitment for integration into the job recruitment database 220.

Any one or more of the modules described herein may be implemented using hardware (e.g., one or more processors of a machine) or a combination of hardware and software. For example, any of the modules described herein may configure a processor (e.g., among one or more processors of a machine) to perform the operations described herein for the module. Further, any two or more of these modules may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Further, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices, according to different example embodiments.

In some embodiments, the job recruitment database 220 contains a set of predefined job titles identified by the job hosting service. For example, the set of predefined job names may include job names such as "customer manager," "system engineer," "sales manager," and the like. In some embodiments, the job recruitment database 220 contains a set of predefined job seniority levels identified by the job hosting service. For example, the set of predefined work seniority levels may include seniority levels such as "intern," "junior," "intermediate," "senior," "manage," "manager," and the like.

Fig. 3A is a flow diagram illustrating the operation of the work capture module 202 and the work normalization module 206 when performing the method 300 for normalizing a job posting obtained from a third-party system, according to some example embodiments. The operations in method 300 may be performed by network-based system 105 using the modules described above with respect to fig. 2. As shown in fig. 3A, method 300 includes

operations

302, 304, 306, 308, and 310.

By obtaining and standardizing the job placements from third-party systems, the job hosting service of the social networking system 210 may present job placements to its users from other job sources in addition to job placements that the social networking system pays to present to its users.

At operation 302, a first entity (e.g., a work hosting service of the social networking system 210) obtains (e.g., using the work capture module 202) data representing a publicly recruited on a third-party system 170. The job posting includes a job name and a job description. In some embodiments, the publicly recruiting further comprises at least one of: name of the employment unit, industry of recruitment, geographic location of work and required skills.

At operation 304, the job name for the job recruit is standardized (e.g., using the job standardization module 206) to match the predefined job name identified by the first entity. In some embodiments, one or more operations 352-362 of the method 350 illustrated in fig. 3B are performed as part of a job title normalization process.

At operation 306, the job description is standardized to conform to a data format identified by the first entity. In some embodiments, normalizing the job description includes performing spell checking/correction and/or grammar checking/correction on the job description.

At operation 308, the standardized job title and the standardized job description are combined into a standardized job publication. In some embodiments, additional information, such as metadata, is also included in the standardized job posting.

At operation 310, standardized publication recruitment is integrated into a recruitment system (e.g., a work hosting service) of a first entity (e.g., the social networking system 210). In some embodiments, a job deduplication process is performed for the standardized job recruitment prior to integration of the standardized job recruitment (e.g., the method 400 of fig. 4A).

Fig. 3B is a flow diagram illustrating optional operations of the job normalization module 206 in performing a method 350 for normalizing a job posting obtained from a third-party system, according to some example embodiments. The operations in method 350 may be performed by network-based system 105 using the modules described above with respect to fig. 2. As shown in fig. 3B, method 350 includes

operations

352, 354, 356, 358, 360, 362, 364, and 366.

At operation 352, the undesired characters appearing in the job title are cleared. For example, in some embodiments, periods are undesirable in job titles. If the job title in the post job is "s.e.in San Francisco, c.a.", clearing the period will result in a modified job title of "SE in San Francisco, CA". In some embodiments, undesirable characters are cleared by a regular expression applied to the job title.

At operation 354, the geographic location is determined to be within and cleared from the job title. For example, if the job name entered for this operation is "SE in San Francisco, CA", then the job name output will be "SE".

At operation 356, when representing the abbreviation, the abbreviation within the job title is replaced with the word or phrase recognized by the first entity. For example, if the job name entered for this operation is "SE", the job name will be "Systems Engineer".

In some embodiments, the abbreviations are disambiguated using context within the job names and/or context within the job descriptions. In some embodiments, the abbreviations are disambiguated by reference to words that occur multiple times within the job description. For example, the abbreviation "SE" may represent a predefined job title such as "system engineer", "sales engineer", "sports news editor", "cleaner", "construction engineer", "senior engineer", etc. In some embodiments, if a potential match to a predefined job title occurs within the job description, this increases the probability of a correct match at this potential match.

At operation 358, the words of the job title are broken into a list of words. For example, if the job name entered for this operation is "system engineer", then the output for this operation would be a list of the words "system" and "engineer".

At operation 360, all possible permutations of words in the word list are generated. For example, if the list of words is "system" and "engineer", then it is likely that the arrangement will be "system engineer" and "engineer system".

At operation 362, the arrangement of words is selected as the standardized job title that most closely matches the at least one predefined job title identified by the first entity. For example, if the possible permutations are "system engineer" and "engineer system," then "system engineer" would select as the standardized job title.

At operation 364, a job name number corresponding to the standardized job name is determined. For example, if the standardized job name is "system engineer," then the corresponding job name number within a particular job hosting service may be 525.

Further, at operation 364, a job seniority level corresponding to the job title number is determined. For example, the job seniority level corresponding to the job title number 525 of "system engineer" may be "intermediate".

At operation 366, the job title number and the job seniority level are included in the standardized post job. In some embodiments, the position name number and the work seniority level are included in the standardized job application prior to integrating the standardized job application into the job application database 220.

Fig. 4A is a flow diagram illustrating the operation of the job deduplication module 208, and optionally the job capture module 202 and/or the job normalization module 206, when performing the method 400 for deduplication of a job posting obtained from a third-party system, according to some example embodiments. The operations in method 400 may be performed by network-based system 105 using the modules described above with respect to fig. 2. As shown in fig. 4A, method 400 includes

operations

402, 404, 406, 408, 410, and 412.

By de-duplicating the job posting from the third-party system, the job hosting service of the social networking system 210 may organize repeated job postings that present the same job to its users.

At operation 402, optionally, a first entity (e.g., a work hosting service of the social networking system 210) obtains (e.g., using the work capture module 202) data representing a job posting on the third-party system 170. In some embodiments, the job posting comprises at least one of: job title, job description, name of the employment entity, recruitment industry, geographic location of the job, and required skills. In some embodiments, operation 402 of method 400 is substantially similar to operation 302 of method 300.

At operation 404, optionally, the job name for the job recruit is standardized (e.g., using the job standardization module 206) to match the predefined job name identified by the first entity. In some embodiments, one or more operations 352-362 of the method 350 illustrated in fig. 3B are performed as part of a job title normalization process.

At operation 406, a first source value is assigned to the standardized job publication. In some embodiments, the first source value is determined at least in part by a source type of the third-party system. For example, in some embodiments, three third party source types are identified: a website of a job-taker entity, an electronic job seeker tracking system (ATS), and an electronic recruitment website. The ATS examples comprise Taleo, ADP and the like. Examples of electronic recruiting websites comprise Monster. com @, Inded @, Craigsist @, and the like.

In some embodiments, there is a hierarchy of source types. For example, a website of a job-taker unit is considered highest in the source type hierarchy, an electronic ATS is considered second highest in the source type hierarchy, and an electronic recruitment website is considered lowest in the source type hierarchy. Therefore, the recruitment obtained from the personal website has a higher source value than the recruitment obtained from the electronic ATS, and the recruitment obtained from the electronic ATS has a higher source value than the recruitment obtained from the electronic recruitment website.

Further, the source values can be different for a job publication obtained from a source within the same source type. Com may have higher source values than those obtained from Craigslist. In some embodiments, an administrator of the work hosting service can assign source values to different types of sources (e.g., through a user interface).

At operation 408, a hash value for the standardized job publication is generated and assigned to the standardized job publication. In some embodiments, the hash value is generated based on a standardized job name, a geographic location, and a human organization name.

In some embodiments, methods of comparing data other than hashing are used, for example, checksums, statistical analysis methods, and machine learning methods, such as neural networks or other supervised learning methods.

At operation 410, it is determined whether a job posting substantially similar to the standardized job posting is present in a work hosting service of the social networking system 210. In some embodiments using hashing, this determination is made by comparing the hash value to a plurality of hash values for a job placement within the work hosting service of the social networking system 210, which hash values are generated for a standardized job placement at operation 408.

In some embodiments using hashing, the standardized recruitment and the integrated recruitment are considered substantially similar if the hash value of the standardized recruitment sufficiently matches the hash value of the recruitment integrated into the work hosting service. In some embodiments, the comparison of the text of the job descriptions for the two job placements is performed if the hash value for the standardized job placement sufficiently matches the hash value for the job placement that has been integrated into the work hosting service. In some embodiments, the comparison involves calculating or comparing a calculated similarity measure for the two job placements. For example, the Jacard similarity factor can be used to compare the similarity between two job placements.

In some embodiments that use comparison methods other than hashing, different comparison techniques can be used to determine a large number of similarities between job placements. For example, a comparison of similar attributes of the job publication and/or keywords within the job publication can be performed to determine a number of similarities.

In some embodiments, if the standardized job application and the integrated job application are substantially similar, the job application with the highest sourcing value is stored in the job hosting service, and the job applications with lower sourcing values are discarded. In the event that two job placements have the same source value, the earliest job placement will be saved.

In some embodiments, if the standardized job application and the integrated job application are substantially similar, then both job applications are saved and the job application displayed to the user is determined at the time of or just prior to displaying the job application. For example, if at the time of display of a specific job of job recruitment, the paid job recruitment has expired and the paid job recruitment has not been previously displayed to the user, then a standardized job recruitment will actually be displayed. The due paid publicly recruitment is displayed to the user as a job-specific publication recruitment if the due paid publicly recruitment has been previously displayed to the user.

In some embodiments, the standardized job application is integrated into the work hosting service if it is determined that a substantially similar job application does not exist in the work hosting service.

At operation 412, a substantially similar job placement is replaced with the standardized job placement within the work hosting service. In some embodiments, the replacement is performed in response to the substantially similar job posting having been identified as not being a paid job posting and the source value for the standardized job posting is greater than the source value for the substantially similar job posting in the work hosting service. The substitution when these conditions are met prevents the non-paid publicly recruitment from engaging paid publicly recruitment within the alternative work escrow service and prevents less authoritative non-paid publicly recruiting more authoritative non-paid publicly recruitment within the alternative work escrow service.

Fig. 4B is a flowchart illustrating optional operations of the job deduplication module 208 in performing a method 450 for deduplication of a publicly available recruit obtained from a third party system, according to some example embodiments. The operations in method 450 may be performed by network-based system 105 using the modules described above with respect to fig. 2. As shown in fig. 4B, method 450 includes

operations

452 and 454.

At operation 452, it is determined that the substantially similar job application is a paid job application. In some embodiments, this determination is made by at least one client of the social networking system 210 based at least in part on whether the social networking system 210 is compensated to present a substantially similar job posting to at least one user 152 of the work hosting service of the social networking system 210. In some embodiments, this determination is made to prevent the unpaid publication recruitment from replacing a paid publication recruitment within the work hosting service of the social networking system 210.

At operation 454, the standardized job posting is presented to the user 152 of the social networking system 210 after receiving the related work search submitted by the user 152. In some embodiments, the user 152 of the social networking system 210 submits a work search within the social networking system 210. In such a system, the social networking system 210 presents a set of job postings to the user 152 that are relevant to the submitted work search. In some embodiments, the presented job posting may include a paid job posting, an unpaid job posting, or some combination thereof.

Fig. 5 illustrates a block diagram of an example machine 500 on which any one or more of the techniques (e.g., methods) discussed herein may be executed. In alternative embodiments, the machine 500 may act as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 500 may operate in the capacity of a server machine, a client machine, or both server and client network environments. In an example, the machine 500 may operate as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 500 may be a Personal Computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions that specify actions to be taken by that machine (whether sequentially or otherwise). Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, and (e.g., cloud computing, software as a service (SaaS), other computer cluster configurations).

As described herein, an instance may contain, or be operated by, logic or multiple components or mechanisms. A circuit group is a collection of circuits implemented in a tangible entity that includes hardware (e.g., simple circuits, gates, logic, etc.). The circuit group members may be flexible over time and underlying hardware variability. The circuit group contains members that can perform specified operations, either individually or in combination, when operated. In an example, the hardware of a circuit group may be permanently designed to perform a particular operation (e.g., hard-wired). In an example, the hardware of the circuit set may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include instructions that are physically modified (e.g., magnetic, electrically movable placement of invariant centralized particles, etc.) to encode a particular operation. When physical components are connected, the underlying electrical characteristics of the hardware formation change, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., an execution unit or load mechanism) to generate members of a circuit group in the hardware via a variable connection to perform portions of a particular operation when in operation. Thus, the computer readable medium is communicatively coupled to other components of the circuit group member while the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuit group. For example, in operation, the execution unit may be used in a first circuit of a first circuit group at one point in time and reused at a different time by a second circuit in the first circuit group or by a third circuit in the second circuit group.

A machine (e.g., a computer system) 500 may include a hardware processor 502 (e.g., a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a hardware processor core, or any combination thereof), a main memory 504 and a static memory 506, some or all of which may communicate with each other via an interconnect (e.g., a bus) 508. The machine 500 may further include a display unit 510, an alphanumeric input device 512 (e.g., a keyboard), and a User Interface (UI) navigation device 514 (e.g., a mouse). In an example, the display unit 510, the input device 512, and the UI navigation device 514 may be a touch screen display. The machine 500 may additionally include a storage device (e.g., drive unit) 516, a signal generation device 518 (e.g., a speaker), a network interface device 520, and one or more sensors 521, such as a Global Positioning System (GPS) sensor, compass, accelerometer, or other sensor. The machine 500 may include an output controller 528, such as a serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., Infrared (IR), Near Field Communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, card reader, etc.).

The storage 516 may include a machine-readable medium 522 on which is stored one or more sets of data structures or instructions 524 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504, within static memory 506, or within the hardware processor 502 during execution thereof by the machine 500. In an example, one or any combination of the hardware processor 502, the main memory 504, the static memory 506, or the storage device 516 may constitute machine-readable media.

While the machine-readable medium 522 is illustrated as a single medium, the term "machine-readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 524.

The term "machine-readable medium" may include any medium that is capable of storing, encoding or carrying instructions for execution by the machine 500 and that cause the machine 500 to perform any one or more of the techniques of this disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. In an example, a centralized machine-readable medium includes a machine-readable medium having a plurality of particles with an invariant (e.g., static) mass. Thus, the centralized machine-readable medium is a non-transitory propagating signal. Specific examples of a centralized machine-readable medium may include: non-volatile memories such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 524 may further utilize any of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), hypertext transfer protocol (HTTP), etc.) to transmit or receive over the communication network 526 using a transmission medium via the network interface device 520. Example communication networks may include a Local Area Network (LAN), a Wide Area Network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards known as Wi-Fi, the IEEE 802.16 series of standards known as WiMax), the IEEE 802.15.4 series of standards, a peer-to-peer (P2P) network, among others. In an example, the network interface device 520 may include one or more physical jacks (e.g., ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 526. In an example, the network interface device 520 may include multiple antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 500, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

Additional notes and example embodiments:

example 1 includes subject matter (e.g., a method, means for performing an action, or a machine-readable medium comprising instructions that, when executed by a machine, cause the machine to perform the action) comprising: obtaining, by a first entity, data representing a job publication on a third-party recruitment system, the data comprising a job title and a job description; standardizing the job title to match at least one of a plurality of predefined job titles identified by the first entity; standardizing the job description to conform to a data format recognized by the first entity; combining the standardized job title and the standardized job description into a standardized publicly recruited job; and integrating the standardized publication recruitment into a recruitment system of the first entity.

Example 2 may include the subject matter of example 1, or may optionally be combined with the subject matter to include, wherein the standardized job name includes clearing occurring undesirable characters, the clearing performed using at least one regular expression.

Example 3 may include the subject matter of one or any combination of examples 1-2, or may optionally be combined with the subject matter to include, wherein the standardized job title includes at least one of: determining a geographic location within the job title and eliminating the determined geographic location from the job title; or determining a person name within the job name and eliminating the determined person name from the job name.

Example 4 may include the subject matter of one or any combination of examples 1-3, or may optionally be combined with the subject matter to include, wherein the standardized job name includes an abbreviation within the job name replaced with a word or phrase recognized by the first entity when representing the abbreviation.

Example 5 may include the subject of one or any combination of examples 1-4, or may optionally be combined with the subject to include, wherein substituting includes disambiguating the abbreviation using at least one of context within the job title and context within the job description.

Example 6 may include the subject matter of one or any combination of examples 1-5, or may optionally be combined with the subject matter to include, wherein the standardized job title includes: dividing the job title comprising a plurality of words in order into a list of words; generating a plurality of permutations of words from the list of words; and selecting a ranking from the plurality of rankings of words that most closely matches at least one of the plurality of predefined job titles identified by the first entity.

Example 7 can include the subject matter of one or any combination of examples 1-6, or can optionally be combined with the subject matter to include, wherein normalizing the position name further comprises determining a position name number and a work seniority level corresponding to the normalized position name, and wherein the position name number and the work seniority level are included in the normalized public recruitment.

Example 8 can include the subject matter of one or any combination of examples 1-7, or can optionally be combined with the subject matter to include, wherein the standardized publication recruitment includes at least one of a geographic location, a human unit name, a recruitment industry, and an identification of a work skill.

Example 9 can include the subject matter of one or any combination of examples 1-8, or can optionally be combined with the subject matter to include, the subject matter (e.g., an apparatus, device, or system) comprising: a machine comprising a memory and at least one processor; a machine-executable job capture module configured to obtain, by a first entity, data representing a job publication on a third-party recruitment system, the data comprising a job title and a job description; and a work normalization module executable by the machine and configured to: standardizing the job title to match at least one of a plurality of predefined job titles identified by the first entity; standardizing the job description to conform to a data format recognized by the first entity; combining the standardized job title and the standardized job description into a standardized publicly recruited job; and integrating the standardized publication recruitment into a recruitment system of the first entity.

Example 10 may include the subject matter of example 9, or may optionally be combined with the subject matter to include, wherein the standardized job name includes clearing occurring undesirable characters, the clearing performed using at least one regular expression.

Example 11 may include the subject matter of one or any combination of examples 9-10, or may optionally be combined with the subject matter to include, wherein the standardized job title includes at least one of: determining a geographic location within the job title and eliminating the determined geographic location from the job title; or determining a person name within the job name and eliminating the determined person name from the job name.

Example 12 may include the subject matter of one or any combination of examples 9-11, or may optionally be combined with the subject matter to include, wherein the standardized job name includes an abbreviation within the job name replaced with a word or phrase recognized by the first entity when representing the abbreviation.

Example 13 may include the subject of one or any combination of examples 9-12, or may optionally be combined with the subject to include, wherein the substituting includes disambiguating the abbreviation using at least one of context within the job title and context within the job description.

Example 14 may include the subject matter of one or any combination of examples 9-13, or may optionally be combined with the subject matter to include, wherein the standardized job title includes: dividing the job title comprising a plurality of words in order into a list of words; generating a plurality of permutations of words from the list of words; and selecting a ranking from the plurality of rankings of words that most closely matches at least one of the plurality of predefined job titles identified by the first entity.

Example 15 can include the subject matter of one or any combination of examples 9-14, or can optionally be combined with the subject matter to include, wherein normalizing the position name further comprises determining a position name number and a work seniority level corresponding to the normalized position name, and wherein the position name number and the work seniority level are included in the normalized public recruitment.

Example 16 can include the subject matter of one or any combination of examples 9-15, or can optionally be combined with the subject matter to include, wherein the standardized publication recruitment includes at least one of a geographic location, a human unit name, a recruitment industry, and an identification of a work skill.

Example 17 may include the subject matter of one or any combination of examples 1-16, or may optionally be combined with the subject matter to include, subject matter (e.g., a method, means for performing an action, or a machine-readable medium including instructions that when executed by a machine cause the machine to perform an action) comprising: obtaining, by a first entity, data representing a job publication on a third-party system; standardizing the data to produce a standardized job posting; assigning a first source value to the standardized job posting, the first source value determined at least in part by a source type of a third-party system; generating a first hash value of the standardized job posting and assigning the first hash value to the standardized job posting; determining that a substantially similar job publication having the second source value and the second hash value exists in the recruitment system of the first entity; and replacing the substantially similar job placement with the standardized job placement within the recruitment system of the first entity, the replacement performed in response to: a substantially similar job application has been identified as not being a paid job application and the first source value is greater than the second source value.

Example 18 may include the subject matter of example 17, or may optionally be combined with the subject matter to include, wherein the data representative of the job publication on the third-party system includes a job title, a geographic location, and a employment unit title, wherein the standardized job publication includes a standardized job title, and wherein the first hash value for the standardized job publication is generated based on the standardized job title, the geographic location, and the employment unit title.

Example 19 may include the subject matter of one or any combination of examples 17-18, or may optionally be combined with the subject matter to include, wherein the source type of the third-party system is at least one of a website of a human entity, an electronic job seeker tracking system, and an electronic recruitment website.

Example 20 may include the subject matter of one or any combination of examples 17-19, or may optionally be combined with the subject matter to include wherein the source value of the website in the employment unit is greater than the source value of the electronic job seeker tracking system, and wherein the source value of the electronic job seeker tracking system is greater than the source value of the electronic recruitment website.

Example 21 can include the subject matter of one or any combination of examples 17-20, or can optionally be combined with the subject matter to include wherein determining that a substantially similar publication recruitment exists in the recruitment system of the first entity includes comparing the first hash value to a plurality of hash values for the publication recruitment within the recruitment system of the first entity, the plurality of hash values including the second hash value.

Example 22 can include the subject matter of one or any combination of examples 17-21, or can optionally be combined with the subject matter to include determining, by at least one customer of the first entity, a substantially similar job placement is a paid job placement based on whether the first entity is compensated to present the substantially similar job placement to at least one user of the recruitment system of the first entity.

Example 23 can include the subject matter of one or any combination of examples 17-22, or can optionally be combined with the subject matter to include presenting the standardized publication recruitment to the user after receiving a related work search submitted by the user of the recruitment system of the first entity.

Example 24 can include the subject matter of one or any combination of examples 1-23, or can optionally be combined with the subject matter to include, the subject matter (e.g., an apparatus, device, or system) comprising: a machine comprising a memory and at least one processor; a machine-executable job capture module configured to obtain, by a first entity, data representing a job publication on a third-party recruitment system; a work standardization module executable by the machine and configured to standardize job posting; and a work deduplication module executable by the machine, configured to: assigning a first source value to the standardized job posting, the first source value determined at least in part by a source type of a third-party system; generating a first hash value for the standardized job posting and assigning the first hash value to the standardized job posting; determining that a substantially similar job publication having the second source value and the second hash value exists in the recruitment system of the first entity; and replacing the substantially similar job placement with the standardized job placement within the recruitment system of the first entity, the replacement performed in response to: a substantially similar job application has been identified as not being a paid job application and the first source value is greater than the second source value.

Example 25 may include the subject matter of example 24, or may optionally be combined with the subject matter to include, wherein the data representative of the job publication on the third-party system includes a job title, a geographic location, and a employment unit title, wherein the standardized job publication includes a standardized job title, and wherein the first hash value for the standardized job publication is generated based on the standardized job title, the geographic location, and the employment unit title.

Example 26 can include the subject matter of one or any combination of examples 24-25, or can optionally be combined with the subject matter to include, wherein the source type of the third-party system is at least one of a website of a human entity, an electronic job seeker tracking system, and an electronic recruitment website.

Example 27 can include the subject matter of one or any combination of examples 24-26, or can optionally be combined with the subject matter to include wherein the source value of the website in the employment unit is greater than the source value of the electronic job seeker tracking system, and wherein the source value of the electronic job seeker tracking system is greater than the source value of the electronic recruitment website.

Example 28 may include the subject matter of one or any combination of examples 24-27, or may optionally be combined with the subject matter to include, wherein the work deduplication module is configured to determine, at least in part, that a substantially similar recruitment exists in the recruitment system of the first entity by comparing the first hash value to a plurality of hash values for the recruitment within the recruitment system of the first entity, the plurality of hash values including the second hash value.

Example 29 may include the subject matter of one or any combination of examples 24-28, or may optionally be combined with the subject matter to include, wherein the work deduplication module is configured to determine, by the at least one customer of the first entity, that the substantially similar job posting is a paid job posting based at least in part on whether the first entity is compensated for, to present the substantially similar job posting to the at least one user of the recruitment system of the first entity.

The instance 30 can include the subject matter of one or a combination of the instances 24-29, or can optionally be combined with the subject matter to include, the presentation module is configured to present the standardized publication recruitment to the user of the recruitment system of the first entity after receiving the related work search submitted by the user.

Each of these non-limiting examples can exist independently, or can be combined in various permutations or combinations with one or more of the other examples.

Conventional terminology used in the field of computer networks and computer systems is used herein. Such terms are known in the art and are provided as non-limiting examples only for convenience. Accordingly, unless otherwise specified, the interpretation of corresponding terms in the claims is not limited to any particular definition. Thus, the terms used in the claims should be given the broadest reasonable interpretation.

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. Many modifications will be apparent to those of ordinary skill in the art. Accordingly, this application is intended to cover any adaptations or variations.

The foregoing detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that can be practiced. These embodiments are also referred to herein as "examples". Such examples may include elements in addition to those illustrated or described. However, the inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the inventors also contemplate examples (or one or more aspects thereof) using any combination or permutation of those elements shown or described with respect to a particular example (or one or more aspects thereof) or with respect to other examples (or one or more aspects thereof) shown or described herein.

All publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as if individually incorporated by reference. In the event of inconsistent usages between this document and those incorporated by reference, the usage in the incorporated reference should be considered to supplement the usage of this document; for irreconcilable inconsistencies, the usage in this document plays a dominant role.

In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, regardless of any other instances or uses of "at least one" or "one or more. In this document, the term "or" is used to refer to a non-exclusive or, such that "a or B" includes "a instead of B", "B instead of a", and "a and B" unless otherwise indicated. In this document, the terms "comprising" and "in which" are used as the colloquial equivalents of the respective terms "comprising" and "in wheein". Furthermore, in the following claims, the terms "comprising" and "including" are open-ended, that is, a system, apparatus, article, or process that includes elements in addition to those listed in the claims after this term is still considered to be within the scope of the claims. Furthermore, in the appended claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The method examples described herein may be implemented at least in part by a machine or computer. Some examples may include a computer-readable medium or machine-readable medium encoded with instructions that may be used to configure an electronic device to perform a method as described in the above examples. Embodiments of such methods may include code, such as microcode, assembly language code, a high-level language code, and the like. This code may contain computer readable instructions for performing various methods. The code may form part of a computer program product. Further, in an example, the code can be tangibly stored on one or more volatile, non-transitory, or non-volatile tangible computer-readable media, e.g., during execution or at other times. Examples of such tangible computer-readable media may include, but are not limited to, hard disks, removable magnetic disks, removable optical disks (e.g., compact disks and digital video disks), magnetic cassettes, memory cards or sticks, Random Access Memories (RAMs), Read Only Memories (ROMs), and the like.

The above description is intended to be illustrative and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. For example, one of ordinary skill in the art, after reviewing the above description, may use other embodiments. The abstract is provided to comply with 37c.f.r. § 1.72 (b) to allow the reader to quickly ascertain the nature of the technical disclosure and is submitted with an understanding that it is not intended to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, various features may be grouped together to simplify the present invention. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments may be combined with each other in various combinations or permutations. The scope of the embodiments should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

1. A method for hosting a job posting, comprising:

obtaining, by a first entity, data representing a job publication on a third-party system;

standardizing the data to produce a standardized job publication;

assigning a first source value to the standardized job posting, the first source value determined at least in part by a source type of the third-party system;

generating a first hash value for the standardized job posting and assigning the first hash value to the standardized job posting;

determining that a substantially similar job posting with a second source value and a second hash value exists in a recruitment system of the first entity; and

replacing, within the recruitment system of the first entity, the substantially similar job posting with the standardized job posting, the replacing performed in response to:

the substantially similar job posting has been identified as not being a paid job posting and

the first source value is greater than the second source value,

wherein the source type of the third-party system is at least one of a website of a human employment unit, an electronic job seeker tracking system, and an electronic recruitment website, and

wherein a source value of a website of a employment unit is greater than the source value of the electronic job seeker tracking system, and wherein the source value of the electronic job seeker tracking system is greater than the source value of the electronic recruitment website.

2. The method of claim 1, wherein the data representative of the job publication on the third-party system includes a job title, a geographic location, and a employment unit title, wherein the standardized job publication includes a standardized job title, and wherein the first hash value for the standardized job publication is generated based on the standardized job title, the geographic location, and the employment unit title.

3. The method of claim 1, wherein the determining that the substantially similar recruitment exists in the recruitment system of the first entity includes comparing the first hash value to a plurality of hash values for a recruitment within the recruitment system of the first entity, the plurality of hash values including the second hash value.

4. The method of claim 1, comprising:

determining, by at least one client of the first entity, that the substantially similar job placement is the paid job placement based on whether the first entity receives payment to present the substantially similar job placement to at least one user of the recruitment system of the first entity.

5. The method of claim 1, further comprising:

presenting the standardized job posting to a user of the recruitment system of the first entity after receiving a related work search submitted by the user.

6. A system for hosting a job posting, comprising:

a machine comprising a memory and at least one processor;

a job capture module executable by the machine and configured to obtain, by a first entity, data representing a job publication on a third-party recruitment system;

a job normalization module executable by the machine and configured to normalize the job posting; and

a work deduplication module executable by the machine, configured to:

assigning a first source value to the standardized job posting, the first source value determined at least in part by a source type of the third-party recruitment system;

the first source value is greater than the second source value,

wherein the source type of the third party recruitment system is at least one of a website of a human-using entity, an electronic job seeker tracking system, and an electronic recruitment website, and

7. The system of claim 6, wherein the data representative of the job publication on the third-party recruitment system comprises a position name, a geographic location, and a employment unit name, wherein the standardized job publication comprises a standardized position name, and wherein the first hash value for the standardized job publication is generated based on the standardized position name, the geographic location, and the employment unit name.

8. The system of claim 6, wherein the work deduplication module is configured to determine, at least in part, that the substantially similar job posting is present in the recruitment system of the first entity by comparing the first hash value to a plurality of hash values for job posting within the recruitment system of the first entity, the plurality of hash values including the second hash value.

9. The system of claim 6, wherein the work deduplication module is configured to determine, by the at least one client of the first entity, that the substantially similar job posting is the paid job posting based at least in part on whether the first entity is compensated for, to present the substantially similar job posting to the at least one user of the recruitment system of the first entity.

10. The system of claim 6, further comprising a presentation module configured to present the standardized publication recruitment to a user of the recruitment system of the first entity after receiving a related work search submitted by the user.

11. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising:

standardizing the data to produce a standardized job publication;

the first source value is greater than the second source value,

12. The non-transitory machine-readable storage medium of claim 11, wherein the data representative of the job publication on the third-party system includes a job title, a geographic location, and a vocational name, wherein the standardized job publication includes a standardized job title, and wherein the first hash value for the standardized job publication is generated based on the standardized job title, the geographic location, and the vocational name.

13. The non-transitory machine-readable storage medium of claim 11, wherein the determining that the substantially similar recruitment is present in the recruitment system of the first entity includes comparing the first hash value to a plurality of hash values for a recruitment within the recruitment system of the first entity, the plurality of hash values including the second hash value.

14. The non-transitory machine-readable storage medium of claim 11, comprising instructions for determining, by at least one customer of the first entity, that the substantially similar job placement is the paid job placement based on whether the first entity is compensated to present the substantially similar job placement to at least one user of the recruitment system of the first entity.

15. The non-transitory machine-readable storage medium of claim 11, further comprising instructions for presenting the standardized job posting to a user of the recruitment system of the first entity after receiving a related work search submitted by the user.