How mcrence/church-monitoring-system works
Church Monitoring System is a staff-facing web application for participant records, event attendance, sponsorship and child-care follow-up, with separate guardian and church-goer access. The principal workflow is staff use of the web client to manage records or check-ins, with the server enforcing access and persisting data; staff can then review attendance and participation reports. The graph also preserves import, history, audit, access, and attendance-risk capabilities documented in the README. Several relationships are grounded only in README descriptions or imports; unsampled handler details are not inferred.
Main entry points: index.js HTTP API and workflows · App.jsx Church web app · app.py Risk scoring API · offlineCheckinQueue.js Offline check-in queue
Components 21
Web experience
- Church web app
client/src/App.jsx - Offline check-in queue
client/src/offlineCheckinQueue.js
Application services
- HTTP API and workflows
server/index.js - Church monitoring database
church_monitoringdb.sql - Schedule and record import
server/utils/import-file.js - Guardian passcodes
server/utils/participant-passcode.js - Staff permissions and audit
server/index.js - Email and SMS delivery
server/utils/gmail-api.js - SMS integration
server/utils/semaphore-sms.js
Monitoring domains
- Participant records
server/utils/participant-utils.js - Attendance and check-in
server/index.js - Participation summaries
server/utils/participation.js - Education history
server/utils/education-history.js - Sponsorship operations
server/utils/sponsorship-tables.js - Church-goer access
server/utils/goer-access.js - Attendance analytics
server/utils/attendance-analytics.js - At-risk summaries
server/utils/at-risk-summary.js - Attendance prediction
server/utils/attendance-prediction.js
Risk analytics
- Risk scoring API
analytics-service/app.py - Risk score function
analytics-service/risk_scoring.py
Other components
- Staff and guardians
Connections 19
- Staff and guardians → Church web app: uses
README.md - Church web app → HTTP API and workflows: requests
- Church web app → Offline check-in queue: queues check-ins
client/src/App.jsx - HTTP API and workflows → Church monitoring database: queries
server/index.js - HTTP API and workflows → Schedule and record import: inspects files
server/index.js - HTTP API and workflows → Participant records: uses
server/index.js - HTTP API and workflows → Attendance and check-in: handles check-ins
README.md - HTTP API and workflows → Participation summaries: uses
server/index.js - HTTP API and workflows → Education history: serves history
server/index.js - HTTP API and workflows → Sponsorship operations: initializes
server/index.js - HTTP API and workflows → Church-goer access: checks access
server/index.js - HTTP API and workflows → Guardian passcodes: verifies portal access
server/index.js - HTTP API and workflows → Attendance analytics: serves reports
README.md - HTTP API and workflows → At-risk summaries: provides follow-up
server/index.js - HTTP API and workflows → Attendance prediction: scores attendance
server/index.js - HTTP API and workflows → Staff permissions and audit: manages permissions and audit
README.md - HTTP API and workflows → Email and SMS delivery: sends email
server/index.js - HTTP API and workflows → SMS integration: sends SMS
server/index.js - Risk scoring API → Risk score function: calls
analytics-service/app.py