How spidy20/smart_resume_analyser_app works
Project Type & Purpose
• The project is a Python-based web application built using Streamlit for analyzing and scoring resumes.
• Its purpose is to extract key information from user-uploaded PDFs (using tools like PyResparser and PDFMiner), evaluate resumes, and provide recommendations on careers, courses, skills, resume writing tips, and even suggest YouTube videos.
• There are roles for both Users and Admins (with preset admin credentials), so the application caters to different user journeys.
Analysis of the File Structure
• Top-level files include:
• App.py: The main entry point that runs the Streamlit web application UI.
• Courses.py: Houses information for course and YouTube video recommendations.
• requirements.txt: Lists all the dependencies (including PyResparser, PDFMiner, etc.).
• Logo and README.md: Branding/Documentation.
• Directory:
• Uploaded_Resumes: Contains sample PDF uploads representing user-submitted resumes.
• The README also mentions a "Classifier.py" that implements a KNN algorithm (even though it isn’t in the file tree); this suggests an additional module concerned with scoring or classification.
• There is mention of XAMP/Apache & SQL services, indicating that while the Python app handles the UI and resume parsing, there is also an underlying database (or service) component that might be used for storing analysis results or managing admin/user data.
Main Components
• Frontend (Streamlit UI):
• Represented by App.py, this component manages user interactions, resume uploads, and displaying results.
• Different sections for user and admin operations should be indicated.
• Resume Upload & File Management:
• The component that handles receiving resumes from the user and storing them in the Uploaded_Resumes folder.
• Resume Parsing & Extraction Module:
• Uses tools like PyResparser and PDFMiner to extract text and meaningful data from the resumes.
• Recommendation and Classification Engine:
• Consists of:
• The KNN-based classification module (even if referenced only in the README as Classifier.py), which calculates the resume score.
• Recommendation logic from Courses.py for career, courses, skills, and video suggestions.
• Backend/Database Layer:
• Even if minimal, show the connection to an SQL-based datastore as required by the instructions (using XAMP/Apache suggests MySQL or similar).
• Flow of storing and retrieving user analysis data.
• External Libraries & Dependencies:
• From the User Interface to the Resume Upload Module.
• From the Resume Upload Module to the Resume Parsing Module.
• From the Parsing Module to the Recommendation/Classification Engine.
• From both the UI and the Recommendation Engine to the Database (if storing/retrieving data).
• Bi-directional flows where needed (for example, results from the Recommendation Engine being displayed in the UI).
Architectural Patterns & Design Principles
• Separation of Concerns:
• Clearly separate UI (Streamlit front end) from the backend analytics (parsing, classification, and recommendations).
• Modularity:
• Each component (upload handler, parser, classification engine, and recommendation system) should be treated as a distinct module.
• Extensibility:
• The design should make it clear how one might extend or replace modules (e.g., changing the recommendation strategy or parser library).