fix: extract company/location from JD file instead of using filename - #66
Open
jaimax0401 wants to merge 1 commit into
Open
fix: extract company/location from JD file instead of using filename#66jaimax0401 wants to merge 1 commit into
jaimax0401 wants to merge 1 commit into
Conversation
Issue: BPMSoftwareSolutions#57 - Fix Resume-Job Linking & Data Consistency Issues Problem: job_listing_id was null because title was derived from filepath stem instead of parsed from JD content. Company was always empty since it was never extracted. Fix: Parse markdown JD file to extract title, company, location using regex before creating JobListing entry. AI agent contribution (bounty work)
7 tasks
This file contains hidden or 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
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.
Fix Resume-Job Linking & Data Consistency Issues (Item 1)
Issue: #57 — Fix Resume-Job Linking & Data Consistency Issues
Problem
job_listing_idwas alwaysnullbecause job title was derived from the filepath stem (e.g.,job_listing.md→ "job_listing") instead of the actual job title in the JD contentFix
Parse the saved JD markdown file (after fetching) to extract:
# headingline**Company:** company_nameline**Location:** locationlineThen create the
JobListingentry with actual parsed metadata instead of empty defaults.Files Changed
src/tailor_from_url.py: Added JD file parsing step before creatingJobListingentryAcceptance Criteria
# headingin markdown)**Company:**in markdown)**Location:**in markdown)job_listing_idis no longer null when resumes are saved