Author Topic: Event rego - interface for additional people is counter-intuitive (Read 9667 times)

Dave Greenberg · December 08, 2009, 03:45:42 pm

Kirk - Very exciting to see this moving forward. I agree that the counts need to be exposed. The places that I think this should happen are:

1. Reports >> Attendee Listing and Event Participant Report (List)
We could add an optional 'Count' column to these reports. For participants in events that don't use price sets, or where price set count is 0, the column would always show 1 - but for the new use cases, it would show the total count for that participant. This would be the price set field count property TIMES the number of count units assigned to that field. So if price set field was for a 'Table of 8', and Jane Doe bought 2 Tables - her row would show a count of 2 x 8 = 16. If she purchased 2 Single Tickets and the 2 Tables, her row count would be 18.

2. Participant View and Edit
Here we already break down price set line items - so we can add a Count column for each line item row and then total the count in the line item table footer.

3. Find Participants (search result listing)
This is a bit harder, since it won't make sense to add a 'Count' column given that most sites don't use price sets / this feature. We could potentially append a "Total Count: 18" after the text we already display in the Fee Level column.

Adult Tickets - 2Child Tickets (12 and under) - 3Total Count - 5

Dave Greenberg · December 08, 2009, 03:47:15 pm

Another screenshot, current Participant "View" with line items listed (we'd add Count column).

ken · December 09, 2009, 01:52:01 am

Nice, Dave.

kmarkley · December 10, 2009, 11:32:32 am

Quote from: Dave Greenberg on December 08, 2009, 03:45:42 pm

Kirk - Very exciting to see this moving forward.

I'm very excited too. Everything seems to be moving forward at this point. The project will incorporate both the attachment of participant counts to price set fields and the changes to reports/lists suggested above. It will be built on the 3.1 code base and should be done by the end of the month.

I really appreciate your help on this. I'm thrilled that the changes we need are things that seem useful to the core development team - both for my selfish desire to future-proof the solution and as a chance to give a little something back to the community.

The project will also include the creation of a new module to allow linking to multiple registration pages from a regular drupal node kind of vaguely like this:

--------------------------------------------------------------------------------
Wednesday MM/DD/YYYY Too Late
--------------------------------------------------------------------------------
Thursday MM/DD/YYYY »Buy Tickets
--------------------------------------------------------------------------------
Friday MM/DD/YYYY SOLD OUT!
--------------------------------------------------------------------------------
Saturday MM/DD/YYYY »Buy Tickets
--------------------------------------------------------------------------------

Where:

"Too Late" is user-defined text for events whose "Registration End Date" has passed
"»Buy Tickets" links to the registration page for each (date-specific) event
"SOLD OUT!" is the "Message if Event Is Full" text for each (date-specific) event.

I will also make this module available to anyone else who might find it useful.

Dave Greenberg · December 10, 2009, 12:58:36 pm

Kirk - kudos for pushing this forward AND the add-on module with links looks awesome too!

CiviCRM Community Forums (archive)

News:

Author Topic: Event rego - interface for additional people is counter-intuitive (Read 9667 times)

Dave Greenberg

Re: Event rego - interface for additional people is counter-intuitive

Dave Greenberg

Re: Event rego - interface for additional people is counter-intuitive

ken

Re: Event rego - interface for additional people is counter-intuitive

kmarkley

Re: Event rego - interface for additional people is counter-intuitive

Dave Greenberg

Re: Event rego - interface for additional people is counter-intuitive