API data schema

Current inferred structure

Users

is_admin

profile

email

password

Profiles

user

full_name

display_name

phone

has_ticket

Departments

name = ‘DPW’

description = ‘Deparment of Public Works’

active_lead = None

active_liaison = None

Shifts

department

start_time

shift_length

owner (user)

code

requires code

locked

is_midnight_spanning

Proposed MVP structure

Users

is_admin

email

password

user

full_name

display_name

phone

has_ticket

Departments

name = ‘DPW’

description = ‘Deparment of Public Works’

active_lead = None

active_liaison = None

Shifts

department

start_time

shift_length

owner (user)

requirements

Requirements

code

requires code

locked

is_midnight_spanning

Proposed ideal structure

Users

user_id:number,

user_name:String, //not everyone has a [realistically typed]

playa name

real_name:String,

playa_name:String,

email:String,

phone:Number

emergency_contact:String,

user_notes:String

has_ticket

under21

dob:Date

Departments

name

lead_id:Number|Array,

liaison_id:Number|Array,

admin_ids:[uid],

shifts:[shiftObj],

Roll

role_id

name

description

requirements

Shift

dept_id:Number,

role_id:Number

shift_id

start_time:Date,

duration:Number,

requirements:String

Requirements

name:String

description:String

requires_code:String,

requires_confirmation:Bool,

confirmation_status:Number,

confirmation_ttl:Datetime,

confirmation_id:number

search requirements

Search types:

Time range

playa name

department

shift type