JobsNMore - Team 9

Transcript

1. JobsNMore Team 9 Jesus Munoz-Castaneda, Javier Ramirez, Willy Resendiz, Cade Taylor
2. Team Willy Resendiz Full-Stack 107 Commits 24 Issues 3 Unit Test Jesus Munoz Castaneda Backend 7 Commits 3 Issues 3 Unit Test Javier Ramirez Backend 60 Commits 18 Issues 3 Unit Test Cade Taylor Backend 17 Commits 2 Issues 2 Unit Test
3. Our Goal ◈ Compile resources for people seeking employment Jobs is the main model ◈ Courses to gain skills. ◈ Information about locations.
4. Tools and Software ◈ Tools Frontend (JS) ◈ React ◈ Bootstrap-react ◈ Font-awesome ◈ Prettier Backend (Python) ◈ Pytest ◈ Black ◈ Requests ◈ Flask ◈ Flask-SqlAlchemy Slack GitLab GCP PostgresSQL
5. ◈ CareerOneStop Information regarding courses, jobs, and occupations ◈ BLS Used as part of CareerOneStop API Statistics on occupations ◈ Onet Courses Information of Industries ◈ RoadGoat Information on locations APIs Documentation
6. Models ◈ Industries Used ONET cluster code ◈ Occupations Used ONET code ◈ Locations Top 30 locations based off population ◈ Jobs Used ONET Code to scrape jobs off Career One Stop ◈ Courses Used ONET Code to scrape courses off Career One Stop
7. ER Diagram
8. Functionality (A) Pagination (B) Sorting (C) Searching A B C
9. JobsnMore Critique ◈ What did we do well? Design Search and sorting was fast and responsive ◈ What did we learn? What not to do with GCP
10. JobsnMore Critique ◈ What can we do better? Setting up python virtual environment to the same as GCP ◈ What puzzles us? GCP is very confusing Getting the website to run on all our machines
11. CsMailman Critique ◈ What they did well Clear and defined navigation Sorting for all 3 models was fast and effective ◈ What did we learn from their website? Google as API integration for Gmail You can categorize the types of emails through Google API You can see information about people who sent you emails and analytics of the emails
12. CsMailman Critique ◈ What could they do better? Could be built-in functionality to add personal gmail data Design looks plain GitLab information looks incomplete Information could be displayed better ◈ What puzzles us? The meaning of the models and labels are confusing Navigation from senders and labels models are not done Search function only searches through one specific arbitrary column