LinkedIn Job Extractor - Job data extraction tool from the web using Scrapy #375 #391
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👋 Thank you for opening this pull request! We appreciate your contribution to improving this project. Your PR is under review, and we'll get back to you shortly. To help move the process along, please tag @UppuluriKalyani, @Neilblaze, and @SaiNivedh26 for a faster review! |
github-actions
bot
requested review from
Neilblaze,
SaiNivedh26 and
UppuluriKalyani
|
@UppuluriKalyani @Neilblaze kindly review my pr :) |
UppuluriKalyani
approved these changes
Oct 16, 2024
|
🎉🎉 Thank you for your contribution! Your PR #391 has been merged! 🎉🎉 |
|
@UppuluriKalyani thank you :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues or bug
This PR addresses issues related to the scraping of job postings from LinkedIn, including challenges with rate limits and IP blocking.
Fixes: #375
Proposed Changes
Implemented the Octoparse proxy middleware to manage requests and avoid IP bans.
Optimized the CSS selectors for improved accuracy in extracting job details.
Enhanced error handling and logging for better monitoring of scraping performance.
Added support for dynamic content scraping.
Additional Info
The Octoparse proxy middleware helps in rotating IPs and reduces the chances of getting blocked by LinkedIn during scraping.
This implementation allows for more efficient and reliable data extraction from LinkedIn job postings.
Screenshots