feat: Add Scholarship & Mentorship scoring category and fix provider … #122
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.
Resolves #76
New Feature: Scholarship & Mentorship Scoring
This PR adds a new scoring category for scholarships and mentorships as requested in issue #76.
Scholarship
andScholarshipsSection
tomodels.py
.scholarship_mentorship
score to theScores
model.scholarships.jinja
prompt for data extraction.pdf.py
,transform.py
, andtemplate_manager.py
to use the new prompt.score.py
to display the new category in the final report.Bug Fixes Included
llm_utils.py
andprompt.py
where theLLM_PROVIDER
environment variable was being ignored, ensuring the correct provider is now used.requirements.txt
to resolve a deep dependency conflict with Google's libraries that was preventing the Gemini provider from working correctly.Testing Note
The feature has been fully implemented and tested with the default Ollama provider. From a code perspective, the feature is complete.
However, the local
gemma3:4b
model was not consistently powerful enough to pass the validation test (i.e., extract the scholarship data correctly). Furthermore, a persistent cloud configuration issue (404 Publisher Model not found
) prevented successful validation with the Gemini/Vertex AI provider, even after a full environment overhaul and multiple debugging attempts. The included bug fixes for provider selection and dependencies were discovered during this process.