data sources - Andre-asn/Quack-Campus-Event-Coordinator GitHub Wiki

OAuth Provider

Students sign in through Google or Microsoft.

The OAuth provider authenticates that the user controls a school email account.

User profile information used by Quack! includes:

  • email
  • display_name
  • avatar_url
  • provider
  • provider_subject_id

Membership of the school domain is checked by Quack!.

User Input

Event data is provided directly by authenticated users.

Event information includes:

  • title
  • description
  • category
  • location
  • location_label
  • starts_at
  • visibility

The location label is typed by the host.

No geocoding is used.

Map Interaction

The client loads tiles from Mapbox directly.

Mapbox provides map tiles and rendering.

The viewport bounding box drives every query.

Requests are debounced while panning and hit our API, not Mapbox.

Application Database

PostgreSQL with the PostGIS extension stores application data.

The database stores:

  • users
  • events
  • event locations
  • event attendance
  • event views
  • visibility information
  • timestamps
  • category information

Pins are stored as PostGIS geography(Point, 4326).

Seed Data

Seeded users are flagged is_seed and cannot sign in.

The deployed demo environment will include seeded demo data.