How skilledgamer101/job_notifiers_public works
Input Layer
• User Credentials (McMaster Email, Password)
• Notification Email Address
• Chromedriver Path
• Configuration Files (*.txt files for job tracking)
Core Components
• Main Notifier (notifier.py)
• Job Board Scrapers:
• OscarPlus Scraper (oscarplus.py)
• SSC Scraper (ssc.py)
• Mosaic SWP Scraper (mosaic_swp.py)
• Mosaic TA Scraper (mosaic_ta.py)
External Services
• Chrome WebDriver
• McMaster Authentication System (with 2FA)
• Job Board Websites
• Gmail API (EZGmail)
• [User Input/Config] → [Core System] → [External Services] → [Output]
Component Relationships
Specific Instructions for Drawing:
Top Layer (Input)
• Configuration files (*.txt) as persistent storage
Middle Layer (Core)
• Notifier.py in the center as the main orchestrator
• Four scraper modules (oscarplus.py, ssc.py, mosaic_swp.py, mosaic_ta.py) in a horizontal line below it
• Connections to their respective .txt files
External Services Layer
• Chrome WebDriver and McMaster Auth system on the left
• Job Board websites in the middle
• Gmail API on the right
Important flows
• Authentication flow through McMaster's 2FA
• Web scraping flow through ChromeDriver
• Data persistence flow to .txt files
• Email notification flow through Gmail API
Key Technical Details to Highlight:
Dependencies
• Selenium for web automation
• BeautifulSoup4 for HTML parsing
• EZGmail for email notifications
• PyInputPlus for user input handling
State Management
• How .txt files store job states
• Comparison logic between stored and new jobs
Authentication Flow
• 2FA phone call verification process
• Secure credential handling
Remember to:
• Notes about critical requirements (Chrome v117, 2FA setup)
• Error handling paths
• Automated scheduling capability through Windows Task Scheduler