How kwaknit69/qualimeat-web-portal works
QualiMeat is represented by two browser portals sharing Firebase-backed records: administrators authenticate, review inspection and stall data, and manage reporting, while vendors scan or enter a stall identifier to validate registration and view inspection-derived certificates. The admin’s inspected dashboard and information modules show direct Firestore reads; the vendor scanner and certificate modules show registry validation and inspection reads. Other listed admin capabilities are retained, but their specific data interactions are not inferred from filenames. Evidence for unsampled modules is limited to the source index.
Main entry points: auth-guard.js Admin session guard · firebase-config.js Vendor Firebase setup · stall-validation.js Stall registry validation · dashboard.js Dashboard analytics
Components 22
Admin access
- Sign in / register
Admin-Portal-main/js/auth.js - Admin session guard
Admin-Portal-main/js/auth-guard.js
Admin operations
- Dashboard analytics
Admin-Portal-main/js/dashboard.js - Inspection management
Admin-Portal-main/js/inspections.js - Inspection history
Admin-Portal-main/js/inspection_history.js - Stalls and inspectors
Admin-Portal-main/js/information.js - Compliance review
Admin-Portal-main/js/compliance.js - Reports
Admin-Portal-main/js/reports.js - Administrator profile
Admin-Portal-main/js/profile.js - General history
Admin-Portal-main/js/history.js - Table pagination
Admin-Portal-main/js/table-pagination.js
Vendor portal
- Scan or enter stall
QualiMeat-Vendor-Portal-main/js/index.js - Stall registry validation
QualiMeat-Vendor-Portal-main/js/stall-validation.js - Inspection sessions
QualiMeat-Vendor-Portal-main/js/certificates.js - Certificate detail
QualiMeat-Vendor-Portal-main/js/certificate.js - Vendor warnings
QualiMeat-Vendor-Portal-main/js/warnings.js
Shared data
- Admin Firebase setup
Admin-Portal-main/js/firebase-config.js - Vendor Firebase setup
QualiMeat-Vendor-Portal-main/js/firebase-config.js - Firebase Authentication
- Firestore
Other components
- Administrator
- Vendor
Connections 37
- Administrator → Sign in / register: signs in
Admin-Portal-main/js/auth.js - Sign in / register → Firebase Authentication: authenticates
Admin-Portal-main/js/auth.js - Sign in / register → Firestore: reads and writes profiles
Admin-Portal-main/js/auth.js - Admin session guard → Admin Firebase setup: uses configuration
Admin-Portal-main/js/auth-guard.js - Admin session guard → Firestore: checks admin profile
Admin-Portal-main/js/auth-guard.js - Admin session guard → Firebase Authentication: checks session
Admin-Portal-main/js/auth-guard.js - Dashboard analytics → Admin session guard: requires session
Admin-Portal-main/js/dashboard.js - Dashboard analytics → Firestore: reads inspections
Admin-Portal-main/js/dashboard.js - Dashboard analytics → Table pagination: paginates rows
Admin-Portal-main/js/dashboard.js - Stalls and inspectors → Admin session guard: requires session
Admin-Portal-main/js/information.js - Stalls and inspectors → Firestore: reads and deletes records
Admin-Portal-main/js/information.js - Stalls and inspectors → Table pagination: paginates tables
Admin-Portal-main/js/information.js - Inspection management → Admin session guard: requires session
Admin-Portal-main/js/inspections.js - Inspection management → Firestore: uses records
- Inspection history → Admin session guard: requires session
Admin-Portal-main/js/inspection_history.js - Inspection history → Firestore: reads inspection history
Admin-Portal-main/js/inspection_history.js - Compliance review → Admin session guard: requires session
Admin-Portal-main/js/compliance.js - Compliance review → Firestore: uses records
- Reports → Admin session guard: requires session
Admin-Portal-main/js/reports.js - Reports → Firestore: uses records
- Administrator profile → Admin session guard: requires session
Admin-Portal-main/js/profile.js - Administrator profile → Firestore: uses profile data
- General history → Admin session guard: requires session
Admin-Portal-main/js/history.js - General history → Firestore: uses records
- Vendor → Scan or enter stall: scans or enters
QualiMeat-Vendor-Portal-main/js/index.js - Scan or enter stall → Stall registry validation: validates stall
QualiMeat-Vendor-Portal-main/js/index.js - Stall registry validation → Vendor Firebase setup: uses configuration
QualiMeat-Vendor-Portal-main/js/stall-validation.js - Stall registry validation → Firestore: queries stall registry
QualiMeat-Vendor-Portal-main/js/stall-validation.js - Inspection sessions → Stall registry validation: validates direct visits
QualiMeat-Vendor-Portal-main/js/certificates.js - Inspection sessions → Vendor Firebase setup: uses configuration
QualiMeat-Vendor-Portal-main/js/certificates.js - Inspection sessions → Firestore: streams inspections
QualiMeat-Vendor-Portal-main/js/certificates.js - Certificate detail → Vendor Firebase setup: uses configuration
QualiMeat-Vendor-Portal-main/js/certificate.js - Certificate detail → Firestore: reads certificate and inspector
QualiMeat-Vendor-Portal-main/js/certificate.js - Vendor warnings → Vendor Firebase setup: uses configuration
QualiMeat-Vendor-Portal-main/js/warnings.js - Admin Firebase setup → Firebase Authentication: configures client
Admin-Portal-main/js/firebase-config.js - Admin Firebase setup → Firestore: configures client
Admin-Portal-main/js/firebase-config.js - Vendor Firebase setup → Firestore: configures client
QualiMeat-Vendor-Portal-main/js/firebase-config.js