How sungodemk/msu-engineering-engagement-hub works
This repository appears to implement an engineering engagement hub: staff browse company and person records, inspect activity and relationships, follow companies, edit entities, and review duplicate matches. The frontend routes and API helper are shown, and backend route modules are registered by the Flask app; sampled route excerpts show database-backed company, profile, edit, and stewardship behavior. Other listed pages and ingestion/matching scripts are represented as capabilities from the source index, but their internal calls were not inspected, so uncertain links are omitted.
Main entry points: App.jsx App routes · app.py Flask app · database.py PostgreSQL access · api.js API client
Components 27
Hub interface
- App routes
frontend/src/App.jsx - Company view
frontend/src/pages/company_page.jsx - Person views
frontend/src/pages/persons_page.jsx - Dashboard
frontend/src/pages/dashboard.jsx - Activity timeline
frontend/src/graphs/temporal.jsx - Relationship graph
frontend/src/graphs/relationship.jsx - Match review
frontend/src/pages/stewardship_queue.jsx - Portfolio
frontend/src/pages/portfolio.jsx - User profile
frontend/src/pages/profile_page.jsx - API client
frontend/src/api.js
Backend API
- Flask app
backend/app.py - Company API
backend/routes/company.py - Person API
backend/routes/person.py - Matching API
backend/routes/matching.py - Entity edits
backend/routes/edits.py - Profile API
backend/routes/profile.py
Engagement data
- PostgreSQL access
backend/database.py - Date calculation
backend/days_calculator/days_calculator.py - Edit history
backend/scripts/entity_edits.py - Entity merging
backend/scripts/merge_entities.py - Match rescoring
backend/scripts/rescoring.py - Company matching
backend/scripts/company_matcher.py - Person matching
backend/scripts/person_matcher.py - Data ingestion
backend/scripts
Identity and access
- Login authorization
backend/auth.py - Firebase identity
frontend/src/firebase.js
Other components
- Hub user
Connections 37
- Hub user → App routes: navigates
frontend/src/App.jsx - App routes → Company view: routes to
frontend/src/App.jsx - App routes → Person views: routes to
frontend/src/App.jsx - App routes → Dashboard: routes to
frontend/src/App.jsx - App routes → Portfolio: routes to
frontend/src/App.jsx - App routes → Match review: routes to
frontend/src/App.jsx - App routes → User profile: routes to
frontend/src/App.jsx - Company view → Activity timeline: renders
frontend/src/pages/company_page.jsx - Dashboard → Activity timeline: renders
frontend/src/pages/dashboard.jsx - Dashboard → Relationship graph: renders
frontend/src/pages/dashboard.jsx - Company view → API client: requests data
frontend/src/pages/company_page.jsx - Person views → API client: requests data
frontend/src/pages/persons_page.jsx - User profile → API client: requests data
frontend/src/pages/profile_page.jsx - Match review → API client: requests data
frontend/src/pages/stewardship_queue.jsx - API client → Firebase identity: gets token
frontend/src/api.js - API client → Flask app: sends HTTP
- Flask app → Company API: registers routes
backend/app.py - Flask app → Person API: registers routes
backend/app.py - Flask app → Matching API: registers routes
backend/app.py - Flask app → Entity edits: registers routes
backend/app.py - Flask app → Profile API: registers routes
backend/app.py - Company API → PostgreSQL access: reads and writes
backend/routes/company.py - Company API → Date calculation: calculates days
backend/routes/company.py - Person API → PostgreSQL access: reads data
backend/routes/person.py - Matching API → PostgreSQL access: reads and writes
backend/routes/matching.py - Matching API → Entity merging: merges entities
backend/routes/matching.py - Entity edits → PostgreSQL access: reads and writes
backend/routes/edits.py - Entity edits → Entity merging: resolves entity
backend/routes/edits.py - Entity edits → Match rescoring: rescores company
backend/routes/edits.py - Entity edits → Edit history: uses edit history
backend/routes/edits.py - Profile API → PostgreSQL access: reads and writes
backend/routes/profile.py - Profile API → Entity merging: resolves entity
backend/routes/profile.py - Profile API → Edit history: resolves source
backend/routes/profile.py - Match rescoring → Company matching: uses matcher
backend/scripts/rescoring.py - Match rescoring → Person matching: uses matcher
backend/scripts/rescoring.py - Login authorization → PostgreSQL access: updates login
backend/auth.py - Company API → PostgreSQL access: queries records
backend/routes/company.py