How mehadi-trackrep/event-registration works
Main Components
• Tally Form Registration: Representing the user input on the tally form (registration data).
• Google Sheet Database: The central data repository where registration data is stored and updated.
• Google Cloud Service Account: This is set up through the credentials.json file and is used for programmatically accessing the Google Sheets data.
• Google Apps Script Web API: (app_scripts_web_api.js) that provides an interface for retrieving events from the Google Sheet.
• Chart and Analytics Generator: The Python script (generate_charts.py) that fetches data from the Google Sheet and creates visualizations.
• SMS Android Application: Located in the SMS-App directory, developed using MIT App Inventor, which fetches event data via the Apps Script Web API.
• Supporting Documentation/Configuration: Files like sheet_queries.md (for translated/instructional info on querying) and tally-form-images for assets.
Relationships and Data Flow
• Registration Process: The tally form collects user registration data and inserts it into the Google Sheet.
• Data Access Layer: The Google Cloud Service Account, via credentials.json, ensures secure access so that both the chart generator and the web API pull data from the Google Sheet.
• API Interaction: The Google Apps Script Web API interfaces directly with the Google Sheet to offer event data needed by the SMS Android application.
• Analytics and Reporting: The Python script (generate_charts.py) periodically queries the Google Sheet (with the help of the service account) to generate analytical charts.
• Mobile Interaction: The SMS Android App communicates with the Web API to fetch the event data, then utilizes this information for messaging or display purposes.
• SMS Sending Caution: Although not shown as a component in the file tree, the README informs you that for sending bulk SMS, a licensed third party service is advised and should be thought of as an external service integration.
Architectural Patterns or Design Principles
• Integration-Based Architecture: The system integrates multiple services (Google Sheets, Google Cloud, and an external mobile app) that communicate via APIs.
• Separation of Concerns: There is a clear division between user registration, data storage, analytics processing, and mobile SMS delivery.
• API-Driven Interaction: The use of a dedicated Google Apps Script Web API allows for a decoupled interface between the central data store (Google Sheets) and the SMS application.
• Every component includes a clear label, such as “Tally Form (Registration Interface)”, “Google Sheet (Database)”, “Google Cloud Service Credentials (credentials.json)”, “Google Apps Script Web API (app_scripts_web_api.js)”, “Analytics Generator (generate_charts.py)”, and “SMS App (MIT App Inventor)”.
• Incorporate any supporting elements described in documentation (for example, references to sheet queries from sheet_queries.md or asset directories like tally-form-images if they play a role in UI design or documentation).