Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attendance count needs to be more than just one number #514

Open
maneesha opened this issue Oct 1, 2015 · 10 comments

Comments

Projects
None yet
7 participants
@maneesha
Copy link
Contributor

commented Oct 1, 2015

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 registered, attendance_day_1, and attendance_day_2 may work as most workshops are just two days, but some are spread out over three, and instructor training may be over a few weeks. Maybe registered, attendance_day_1, and attendance_day_n?

@pbanaszkiewicz

This comment has been minimized.

Copy link
Contributor

commented Oct 6, 2015

This is another reason why I'm missing PostgreSQL. With it we would have an option to store a list (array) of attendance figures within one field.

@gvwilson any thoughts on switching?

@gvwilson

This comment has been minimized.

Copy link
Contributor

commented Oct 8, 2015

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.

@maneesha

This comment has been minimized.

Copy link
Contributor Author

commented Oct 9, 2015

Sounds good @gvwilson

@shubhsingh594

This comment has been minimized.

Copy link
Contributor

commented Mar 4, 2016

We could use a JSON object to store an array list, and then convert it into a String to store it into the SQLite database. This way we can use one field to store the attendance for all the days of the workshop individually.

@pbanaszkiewicz

This comment has been minimized.

Copy link
Contributor

commented Mar 4, 2016

@shubhsingh594 technical solution is not an issue – having people send us the data for specific days is one.

@pbanaszkiewicz pbanaszkiewicz modified the milestone: v1.5.3 Apr 7, 2016

@pbanaszkiewicz pbanaszkiewicz modified the milestones: v1.5.3, v1.5.4 Apr 20, 2016

@maneesha

This comment has been minimized.

Copy link
Contributor Author

commented Apr 26, 2016

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.

@gvwilson gvwilson removed this from the v1.9 milestone Sep 28, 2016

@maneesha

This comment has been minimized.

Copy link
Contributor Author

commented Jun 24, 2019

@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?

  1. Would like to see this fixed as soon as possible, in the next 1-2 development cycles (i.e., by September 2019)
  2. Would like to see this fixed later (by the end of 2019)
  3. Would like to see this fixed, but possibly as part of a larger project that needs more planning
  4. Not sure
  5. No longer relevant - OK to close

@maneesha maneesha assigned Talishask and sheraaronhurt and unassigned maneesha Jun 24, 2019

@Talishask

This comment has been minimized.

Copy link
Collaborator

commented Jul 6, 2019

3 - I think we are still thinking about how we want to collect attendance and what information we want. I believe this is a part of a larger conversation among SherAaron, Kari & Tracy.

@sheraaronhurt

This comment has been minimized.

Copy link
Collaborator

commented Jul 9, 2019

agreed. 3

@kariljordan

This comment has been minimized.

Copy link
Member

commented Jul 10, 2019

I am in agreement with 3 as well. If we collect and track this data, we are not in a position to take action or use the information to inform changes in curriculum or workshop administration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.