|
Stichting Festival Aangeschoten Wild
|
March 30, 2014 at 4:22 am
Dear EventEspresso,
I’m currently analysing the data of an event we held a few days ago, so we can better predict next years ticket sales and check-in peaks. However, I can across a discrepancy between the Excel-export of all the event attendees, and the event_attendee_checkin table in the EE-database. The former shows 1161 check-in’s, whereas the table contains 896.
Can you assist in explaining this?
Thanks, and with kind regards,
Bram
|
|
Josh
|
April 1, 2014 at 12:31 pm
Hi there,
We might if can take a look at the data. Can you attach an export of each to and email and send to support@eventespresso.com?
|
|
Josh
|
April 3, 2014 at 9:53 am
Hi Bram,
I took a look at the attendee list exports and there are duplicate entries. This is a known issue where if there are multiple entries in the checkins table the corresponding entries in the attendee list will be duplicated. We have a fix for this, and the fix will be released in Event Espresso 3.1.37. You can manually apply the fix to the version of Event Espresso that you have now by downloading this file and upload it to replace the existing export.php file in /plugins/event-espresso/includes/functions/export.php.
|
|
Stichting Festival Aangeschoten Wild
|
April 3, 2014 at 2:03 pm
Ah, I see! So – just to get things straight – say a ticket with ID 123 is valid for two attendees. If it is scanned for the first time, the particular ticket gets updated to ‘scanned = 1’. If it’s scanned the second time, the ticket then gets an update to ‘scanned = 2’, AND is duplicated (with the scanned = 2). Or am I misinterpreting your explanation? Does it also do this if the two attendees enter simultaneously?
Spending some more thought on this, it might also be considered a feature. Now, it is possible to track all scans (i.e., scanning dates/times) of a particular ticket, rather than only the last one. The column ‘ticket scanned’, however, should than only reflect the amount of tickets scanned at that particular moment. Might also be an interesting way to look at things…
Thanks for your reply, and looking forward to confirmation (or denial) on the analysis above.
Bram
|
|
Stichting Festival Aangeschoten Wild
|
April 3, 2014 at 2:11 pm
And to follow up on my previous thoughts: in the database, the last scanning date overwrites the first, doesn’t it? Then, it would still not be possible to (accurately) analyze the busier moments at the door, for which we wanted to use the data. For instance, if 10 tickets for 6 attendees are sold, and of this tickets, the first 5 arrive at 15:00h, and the last persons on the tickets arive at 18:00h, it will show as if 60 attendees arrived at 18:00h, right?
Thanks for your reply!
|
|
Josh
|
April 3, 2014 at 3:07 pm
I think you’ve misunderstood my explanation. This is a bug where when the export loops through the data from the check ins table, the entries in the check ins table with a value greater than one get duplicated, which they shouldn’t be. So if there were two checkins, the attendee exported shows both of the 2 checkins twice instead of once each. The file I linked to fixes the issue.
|
