Volunteer/Attendee count incorrectly displayed as zero

[ilen]

Steps to reproduce:

1. Go to: https://www.bridgetroll.org/events/441
2. Note presence of attendee and volunteer lists.

RESULT: Attendee and volunteer count is zero
EXPECTED: Attendee and volunteer count should match list displayed

(Count is also zero on export of workshop data as csv)

[siruguri]

The code doesn't match the expectation above - it shows number of attendees who have checkins in the DB, if the event is in the past.

Did this event not do check-ins? Or are you expecting past events to not use the check-ins count filter?

[ilen]

No idea whether the event had check ins; I'm trying to get participation totals for the annual report and was not involved in the event.

I think it would make sense to assume that if an event is in the past, the best count of attendees is whoever was registered.

Here is the list of all workshops in a similar state in case it's helpful:

https://www.bridgetroll.org/events/433
https://www.bridgetroll.org/events/437
https://www.bridgetroll.org/events/441
https://www.bridgetroll.org/events/438
https://www.bridgetroll.org/events/442
https://www.bridgetroll.org/events/440
https://www.bridgetroll.org/events/449
https://www.bridgetroll.org/events/454

[rachelober]

This is an interesting situation to be in. The idea behind the check-ins is to record as accurately as possible who are being served by our free workshops. If we aren't accurately checking-in people it is actually doing us a disservice whenever we pull reports to try and make a case for our efficacy to potential donors.

Additionally, having zero people pulled now after an event that happened in the past can't be fixed now and I see your concern that you want at least SOMETHING to show that your workshop happened.

I propose a few resolutions to this to clarify this situation:

1. Don't do the extra work on the event page to distinguish check-ins. In reality, the question is who is served by having that information on the main page? Regular attendees don't need to know. Organizers should expect to see that on their dashboard.
2. We should give the option of exporting user data with check-ins or just all attendees. I can't seem to see where that export option is right now, @ilen, so I don't know what the current messaging around the export looks like. I'll continue to investigate to see what kind of additional feature could be added.

[ilen]

To export the workshop stats csv, Bridge Troll global admins, can access URL: http://bridgetroll.org/events.csv The column in question is the "attended" column which appears to be the sum of the checked in volunteers and students. We're using this number to provide updates to donors on the impact of the workshops. So maybe another solution is to change just the csv to ignore the "checked in" status for past events? (I'm afraid I don't know enough about how Bridge Troll is being used at events, I should remedy that!)

…

On Wed, May 1, 2019 at 4:05 AM Rachel Ober ***@***.***> wrote: This is an interesting situation to be in. The idea behind the check-ins is to record as accurately as possible who are being served by our free workshops. If we aren't accurately checking-in people it is actually doing us a disservice whenever we pull reports to try and make a case for our efficacy to potential donors. Additionally, having zero people pulled now after an event that happened in the past can't be fixed now and I see your concern that you want at least SOMETHING to show that your workshop happened. I propose a few resolutions to this to clarify this situation: 1. Don't do the extra work on the event page to distinguish check-ins. In reality, the question is who is served by having that information on the main page? Regular attendees don't need to know. Organizers should expect to see that on their dashboard. 2. We should give the option of exporting user data with check-ins or just all attendees. I can't seem to see where that export option is right now, @ilen <https://github.com/ilen>, so I don't know what the current messaging around the export looks like. I'll continue to investigate to see what kind of additional feature could be added. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#643 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAALJXFANQRXHWRHXYV2RN3PTF2P7ANCNFSM4HJHCC5A> .