Data for Good Calgary — Volunteer Platform
Data for Good Calgary
Data for Good Calgary matches volunteer data scientists, analysts and engineers with non-profits that need help making sense of their data. Demand was never the chapter’s constraint. Coordination was: running a volunteer organisation across a stack of disconnected tools.
Two applications, one database
The platform runs on Oracle AI Database 26ai with Oracle APEX 26.1 in front of it: a staff application for the core team, project leads and administrators, and a public site that volunteers, partners and visitors use without an account. Both read and write one schema of 112 tables, with 24 PL/SQL packages written for the system.
All application source is kept in APEXlang (.apx) rather than binary exports, so pages are reviewable in a diff and deployable through SQLcl like any other code.
Automating the onboarding chain
The work that used to be manual is now driven from PL/SQL:
For NextCloud, the database calls the OCS API to create accounts and keep project group membership in step as volunteers join and leave projects. Account passwords are generated with DBMS_CRYPTO.RANDOMBYTES rather than a pseudo-random source, because those accounts give access to partner data.
DocuSeal is driven over REST, issuing NDAs from managed templates and pulling submission status back every night. The signed-field JSON is unpivoted into queryable views, so compliance reporting is a SQL question rather than a folder audit.
HubSpot is pulled every six hours and each run stores HubSpot’s own total beside the local count; Mautic is mirrored nightly and new volunteers are pushed back. A discrepancy surfaces the next morning instead of at the next audit.
Engineering details that mattered
The NextCloud OCS API returns two status codes: the HTTP status, and an OCS status inside the response JSON. An HTTP 200 with an OCS 102 means “user already exists,” not success. Every call checks both. An integration that checks only the HTTP status quietly does nothing.
The same lesson shaped the job monitor. A scheduler job can report success without doing its work, so the monitor checks results (rows pulled, totals reconciled) as well as exit status, and raises one alert per problem rather than one per run.
Live
- Public hub: yyc-hub.dataforgood.ca
- Resource Library: browse the catalogue
- Volunteer position interest: interest form
This platform is one of three connected pieces of work for the chapter. See also the marketing automation migration and the cloud infrastructure underneath it.