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.

Sign up for GitHub

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

Jump to bottom

Modify the Guest List CSV #144

Closed
yarunluon opened this issue May 10, 2024 · 12 comments · Fixed by #176
Closed

Modify the Guest List CSV #144

yarunluon opened this issue May 10, 2024 · 12 comments · Fixed by #176
Assignees
@kigster @beingmattlevy
Labels
feature-request New feature or request work-in-progress
Milestone
M2: TicketBooth P...

Comments

@yarunluon
Copy link
Contributor

yarunluon commented May 10, 2024 •
edited

Is your feature request related to a problem? Please describe.
Gate needs a list of attendees that is formatted to expeditiously check-in attendees. They will be printing out the Guest List so need a quick way to scan for names.

Describe the solution you'd like
Modify the Guest List CSV to use these columns per @mrwilldehaan 's comment

  • Name first last: alphabetical ascending (a-z) order, concatenated
  • role
  • early access (EA)
  • email: used as a backup to verify attendance if name can't be found. People use DJ names or Playa/FnF names. Can also be used as secondary verification.

FYI: Gate will add these columns which will help Gates and Tickets post-event for auditing tasks

  • arrival time
  • tent/car/rv + payment status

The Guest List CSV can be found under the "Guest List" tab in the Admin view
image

Describe alternatives you've considered
Taken from Slack thread:

  1. Tickets team will write some spreadsheet equations to generate a “Gate List” using the “Ticket Requests CSV”.
  2. Gate does the work instead of Tickets and reformats the “Ticket Requests CSV” or the “Guest List CSV” to their needs.
  3. We do nothing and Gate needs to look up the attendee by Sponsor -> Guest name using the current “Guest List CSV”.

Additional context
The current format of the Guest List is

  • Name (aka Sponsor or Ticket Requester)
  • n-Guest names

Format of Guest Names

image

The guest list can be up to 4 pages long when printed. The majority of attendees will be in the "Guest" columns. Scanning a 4 page document to find guest names is time consuming. This will generate long queues of people in their cars.
@yarunluon yarunluon added the feature-request New feature or request label May 10, 2024
@mrwilldehaan
Copy link

Gotta rule out #3 as not useful since guests and hosts show up in different vehicles

Gate list columns look like:
Name first last, role, early access (EA), arrival time, tent/car/rv + payment status, email

Gate can do data-entry to populate the database after the event if desired. Good job for a ravey intern

@yarunluon
Copy link
Contributor Author

Thanks! Updated Issue description based on @mrwilldehaan 's comment.

@kigster
Copy link
Collaborator

kigster commented May 13, 2024

I don't understand how we can print the guest list if at no point in the flow we are requiring the guests to be filled out. Either make up your mind about guest list or remove them from the CSV. What's the point of neither here nor there solution?

@yarunluon
Copy link
Contributor Author

yarunluon commented May 13, 2024 •
edited

In the version of TicketBooth that was < v1.0.1, the names of the guest list were required to enter the payment flow. This was enforced by disabling the link and displaying a message saying all guest names had to be filled out.

@mrwilldehaan
Copy link

mrwilldehaan commented May 13, 2024 via email

@beingmattlevy beingmattlevy linked a pull request May 14, 2024 that will close this issue
Flatten the guest list in CSV dowload and disable the delete ticket request button (why?) #174
Closed
@beingmattlevy beingmattlevy self-assigned this May 14, 2024
@kigster
Copy link
Collaborator

kigster commented May 15, 2024

I am super confused.

After the requirement to fill out the guest names was nuked, and now at no point in the ticket request flow is the ticket buyer required to fill out this info, what is the value of even including the guests when only a small portion of ticket holders would go back and fill that out?

@kigster
Copy link
Collaborator

kigster commented May 15, 2024

Having said that, for those TRS that do have guests, adding them on separate rows is a trivial change.

@yarunluon
Copy link
Contributor Author

After the requirement to fill out the guest names was nuked, and now at no point in the ticket request flow is the ticket buyer required to fill out this info, what is the value of even including the guests when only a small portion of ticket holders would go back and fill that out?

I am now seeing this comment and would have responded earlier. See this comment. The old version of TicketBooth enforced Guest Names before entering the payment flow. When old Ticketbooth was migrated to new Ticketbooth, it was assumed this validation would remain the same. My fault. I should have explicitly called out that Guest Names are enforced before entering the payment flow.

@yarunluon
Copy link
Contributor Author

yarunluon commented May 17, 2024 •
edited

Name first last, role, early access (EA), arrival time, tent/car/rv + payment status, email

@mrwilldehaan , when you mention "tent/car/rv + payment status", are you referring to the payment status for Car Camping, Tickets, or both? I was assuming Car Camping.

If it's the former, Tickets doesn't have Payment Status for tent/car/rv so I'm thinking that will be merged later? Also Arrival Time will be recorded by Gate?

@mrwilldehaan
Copy link

mrwilldehaan commented May 17, 2024 via email

@mrwilldehaan
Copy link

mrwilldehaan commented May 17, 2024 via email

@kigster
Copy link
Collaborator

kigster commented May 17, 2024

I am going to shortly paste the version of the CSV we are currently exporting.

Then it will be much easier to make changes having seen an example.

@kigster kigster self-assigned this May 17, 2024
@kigster kigster linked a pull request May 17, 2024 that will close this issue
Ticket Request logical delete + CSV generation #176
Merged
@yarunluon yarunluon mentioned this issue May 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kigster kigster

@beingmattlevy beingmattlevy

Labels
feature-request New feature or request work-in-progress
Projects
None yet
Milestone
M2: TicketBooth Passed the Acceptance...
4 participants
@kigster @beingmattlevy @yarunluon @mrwilldehaan