Scraped position data incorrect when user has more than one position in same company
See original GitHub issueThe profile shown here has multiple roles at the same company, “Excelian | Luxoft Financial Services”.
In the scraped profile, both of these roles are collapsed into a single one, where the company name is listed as the title and no companyName field is present. The dates shown are from the first role, but the description is from the second.
positions: [
{
title: 'Excelian | Luxoft Financial Services',
link: 'https://www.linkedin.com/company/excelian/',
url: 'https://www.linkedin.com/company/excelian/',
location: 'Sydney, Australia',
description: 'Mxml developer focused on confirmation work',
date1: 'Sep 2016 – Present',
date2: '3 yrs 10 mos'
},
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
python - I get the same job title for multiple jobs when using ...
The scraper works well, however for different job positions it returns the same title, whereas they should be different pending on the job...
Read more >How do I stop Indeed from scraping my job postings?
If you know that Indeed is scraping your Lever-hosted jobs and you would like them to stop, you can do so by contacting...
Read more >Your Approach to Hiring Is All Wrong - Harvard Business Review
Cappelli explores what's wrong with today's recruiting and hiring and how to ... data indicates that the most common reason employees consider a...
Read more >Job posting ( JobPosting ) structured data for Job Search
Improve the job seeking experience on Google by reviewing how you can markup your job posting web pages with structured data.
Read more >Reporting Jobs on LinkedIn | LinkedIn Help
If you come across a job on LinkedIn that you find to be inappropriate, broken, or incorrect, you can flag the job to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@grapevineai all of the scrapping is based on profileScraperTemplate.js:
template
is an array of LinkedIn sections object, each object will be translated to be the final scrapedin result to the user, it has basically 2 properties:selector
: a css selector which is an HTML container element which represents a LinkedIn section, such as Education or About.fields
: it can be two options:String
: a CSS selector that will actually scrap an HTML element value to store and return to the user. It can be two options:Object
: will do recursively do the same job in the current section. It’s necessary when we have “elements inside other elements” such as roles from LinkedIn’s positions/experiencesIt’s all based on CSS selectors as you can see, it’s not hard. The rest of the code is mostly to read that template and it barely has bugs. Thank you for your contribution, I spend my time here doing this project without earning a single penny so it’s good to have help, thank you 😄
That was fixed on v
1.0.20
please update your version, feedback is appreciated! Thanks for reporting that @web-goddess