Parsing/identifying sections in job descriptions












0















I'm trying to solve quite a difficult problem - building a generic parser for job descriptions. The idea is, given a job description, the parser should be able to identify and extract different sections such as job title, location, job description, responsibilities, qualifications etc. The job description will basically be scraped from a web page.



A rule based approach (such as regular expressions) doesn't work since the scenario is too generic. My next approach was to train a custom NER classifier using SpaCy; I've done this numerous times before. However, I'm running into several problems.




  1. The entities can be very small in size (location, job title etc.) or very large (responsibilities, qualifications etc.). I'm not sure how well NER works if the entities are several lines or a paragraph long? Most of the use cases I've seen are those in which the entities aren't longer than a few words max. Does Spacy's NER work well if the text of the entities I want to identify is quite long in size? (I can give examples if required to make it clearer).


  2. Is there any other strategy besides NER that I can use to parse these job descriptions as I've mentioned?



Any help here would be greatly appreciated. I've been banging my head along different walls for a few months, and I have made some progress, but I'm not sure if I'm on the right track, or if a better approach exists.










share|improve this question























  • Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

    – Alex L
    Jan 3 at 21:41











  • @AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

    – Azfar Imtiaz
    Jan 4 at 14:50
















0















I'm trying to solve quite a difficult problem - building a generic parser for job descriptions. The idea is, given a job description, the parser should be able to identify and extract different sections such as job title, location, job description, responsibilities, qualifications etc. The job description will basically be scraped from a web page.



A rule based approach (such as regular expressions) doesn't work since the scenario is too generic. My next approach was to train a custom NER classifier using SpaCy; I've done this numerous times before. However, I'm running into several problems.




  1. The entities can be very small in size (location, job title etc.) or very large (responsibilities, qualifications etc.). I'm not sure how well NER works if the entities are several lines or a paragraph long? Most of the use cases I've seen are those in which the entities aren't longer than a few words max. Does Spacy's NER work well if the text of the entities I want to identify is quite long in size? (I can give examples if required to make it clearer).


  2. Is there any other strategy besides NER that I can use to parse these job descriptions as I've mentioned?



Any help here would be greatly appreciated. I've been banging my head along different walls for a few months, and I have made some progress, but I'm not sure if I'm on the right track, or if a better approach exists.










share|improve this question























  • Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

    – Alex L
    Jan 3 at 21:41











  • @AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

    – Azfar Imtiaz
    Jan 4 at 14:50














0












0








0








I'm trying to solve quite a difficult problem - building a generic parser for job descriptions. The idea is, given a job description, the parser should be able to identify and extract different sections such as job title, location, job description, responsibilities, qualifications etc. The job description will basically be scraped from a web page.



A rule based approach (such as regular expressions) doesn't work since the scenario is too generic. My next approach was to train a custom NER classifier using SpaCy; I've done this numerous times before. However, I'm running into several problems.




  1. The entities can be very small in size (location, job title etc.) or very large (responsibilities, qualifications etc.). I'm not sure how well NER works if the entities are several lines or a paragraph long? Most of the use cases I've seen are those in which the entities aren't longer than a few words max. Does Spacy's NER work well if the text of the entities I want to identify is quite long in size? (I can give examples if required to make it clearer).


  2. Is there any other strategy besides NER that I can use to parse these job descriptions as I've mentioned?



Any help here would be greatly appreciated. I've been banging my head along different walls for a few months, and I have made some progress, but I'm not sure if I'm on the right track, or if a better approach exists.










share|improve this question














I'm trying to solve quite a difficult problem - building a generic parser for job descriptions. The idea is, given a job description, the parser should be able to identify and extract different sections such as job title, location, job description, responsibilities, qualifications etc. The job description will basically be scraped from a web page.



A rule based approach (such as regular expressions) doesn't work since the scenario is too generic. My next approach was to train a custom NER classifier using SpaCy; I've done this numerous times before. However, I'm running into several problems.




  1. The entities can be very small in size (location, job title etc.) or very large (responsibilities, qualifications etc.). I'm not sure how well NER works if the entities are several lines or a paragraph long? Most of the use cases I've seen are those in which the entities aren't longer than a few words max. Does Spacy's NER work well if the text of the entities I want to identify is quite long in size? (I can give examples if required to make it clearer).


  2. Is there any other strategy besides NER that I can use to parse these job descriptions as I've mentioned?



Any help here would be greatly appreciated. I've been banging my head along different walls for a few months, and I have made some progress, but I'm not sure if I'm on the right track, or if a better approach exists.







python parsing nlp spacy ner






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 3 at 13:41









Azfar ImtiazAzfar Imtiaz

12




12













  • Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

    – Alex L
    Jan 3 at 21:41











  • @AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

    – Azfar Imtiaz
    Jan 4 at 14:50



















  • Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

    – Alex L
    Jan 3 at 21:41











  • @AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

    – Azfar Imtiaz
    Jan 4 at 14:50

















Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

– Alex L
Jan 3 at 21:41





Exactly how much variation is in these job descriptions since you say they come from "a" (singular) web page? You could probably pull out location with NER, but you might have more success getting something like job responsibilities with dependency parsing.

– Alex L
Jan 3 at 21:41













@AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

– Azfar Imtiaz
Jan 4 at 14:50





@AlexL The job descriptions are not coming from a singular web page. It can be different job sites such as Indeed, Monster, Google Jobs etc. Location isn't that hard since there are APIs for that, and NER works better for that too. Can you elaborate more on how I can get job responsibilities via dependency parsing?

– Azfar Imtiaz
Jan 4 at 14:50












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023471%2fparsing-identifying-sections-in-job-descriptions%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023471%2fparsing-identifying-sections-in-job-descriptions%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas