Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Attendance count needs to be more than just one number #514
To accurately track and assess our impact, I'd like to have more than just one number to reflect attendance count. I've gotten a few reports back where attendance on day 2 was lower than attendance day 1 -- sometimes by just a couple of people, sometimes significantly lower. Actual attendance is also often lower than registered attendance especially for free workshops.
This speaks to a larger need to assess SWC's impact & effectiveness but to do so we need to track this data.
Something like counts for
I think we should defer switching to multi-valued attendance figures until we know that people will actually provide them - if admins start asking now, and archive answers (e.g. in a Google doc) for 2-3 months, and we see that we're actually getting data, then it's worth complicating things. If they don't give us data, then there's no point.
I've been tracking this & have put it in a github repo. We've gotten attendance by day for 30 workshops in eight months without even trying. I think this shows us it's worth it for us to more explicitly ask instructors/hosts for attendance broken down like this and track it in AMY.
referenced this issue
Jun 28, 2016
@sheraaronhurt @Talishask How important is it that we track retention/attrition? Do we want to know if attendance count changed over the event? Is it more important for DC, where curriculum is continuous vs SWC where it's more modular? Will having this data tell us if the two day model is effective? Can we compare it to workshops that are spread out over days/weeks? Will instructors/hosts share this data?
We have this scale in place to prioritize things. Since this isn't a well defined fix yet, I'd suggest option 3. Let me know what you think.
Which of the following applies to when you want to see this fixed?