Skip to content

Latest commit

 

History

History
58 lines (38 loc) · 2.44 KB

README-Attendance.md

File metadata and controls

58 lines (38 loc) · 2.44 KB

Attendance & Check In

Attendance is one of the basic metrics that needs to be tracked in movement building. Its useful for tracking the impact of your outreach, the growth of your group over time, and individual participation tracking. Its also incredibly useful for fundraising, considering many grants will accept volunteer hours as their matching funding requirement.

We've built a platform for your Brigade to start tracking attendance.

Brigade members can checkin at:

We recommend making a short link of the checkin url for your group.

Attendance Data

Brigade Leadership can find the attendance data for their groups at https://people.codeforamerica.org/brigade/

To get access talk to Hannah or Andrew

Build your own Brigade attendance tools

Attendance data can be pulled from the Code for America API.

Checkins can be posted

The schema expected for checkins is:

fieldname - type - default - optional - example
name - string - None - Yes - `Margaret Hamilton`
email - string - None - Yes - `[email protected]`
event - string - None - Yes - `Moon Landing`
date - datetime - datetime.now() - Yes - `1969-07-20`
cfapi_url - string - None - No - `https://www.codeforamerica.org/api/organizations/Code-for-Houston`
question - string - None - Yes - "What did you do today?"
answer - string - None - Yes - "I invented software engineering and sent the first people to the moon."

Testing Checkins

We made a simple testing route to POST to at https://www.codeforamerica.org/brigade/test-checkin/. It won't save anything, but it will return the correct error codes if you get the cfapi_url wrong. It will return your POSTed data back to you if you get succeed with a 200.