Event based inventory

[bethlakshmi]

MARCUS - I assigned this to you, because IMO it's easiest to start with the data, and then design the GUI after... when you have a data layer ready, reassign it to me.

We want to have an inventory that shows the sum totals of sales for limited inventory items. For example

• the conference is our most limited item - we can only really sell 100 or so seats, so space is at a premium
• we'd like to know how many tickets are sold for a show - so we know how many seats to set up.
• we'd like to know how many people will be at Mina's Tea Party so we don't run out of tea sandwiches.

That doesn't translate directly to sold items, but it IS mapped to Events under the cover in the Edit Ticket Types area.

What we want is to turn the view around and show:

• Events as the rows
• for each Event the number of relevant sales across ALL ticket types as a single value

This may include adding some invisible event id types, like "the conference" which lasts for 3 days.

Action items:

• Marcus - create a data layer API to pull the data from the database
• Betty - create a view of the data as a report for Scratch, create additional invisible events to map to particularly important event types (the conference days)

[markcockrum]

API Complete. See the menu option Ticketing -> Attendance Report for an example of how it can be used. The API functionality can be found in gbe_ticketing.inc at the bottom.

Here is the header for the API function to be used.

/* function get_valid_transactions_for_event

• Used to obtain an array of Transaction objects in the system that allow
• the purchaser to attend the given event. Limbo Transactions are transactions
• in the temporary table associated with an unregistered user. *
• $EventId - the Event ID to query for
• $Transactions - array of Transaction records per above.
• $LimboTrans - array of LimboTransactions (unregistered trans.) per above.
• Returns: nothing. */

function get_valid_transactions_for_event($EventId, &$Transactions, &$LimboTrans)

This function returns an array of Transaction objects, and an array of LimboTransaction objects, as defined in the gbe_ticketing.inc file. The last two parameters are call by reference.

The function show_transactions_by_event() just below gives an example of how to use the API function.

-Marcus

[bethlakshmi]

Why is it reopened? I'm thinking of doing a code port soon, should I hold off on ticketing related php? (that's OK if it's true, I still get some good stuff in with Scheduling.php and some legacy *.inc updates.

[markcockrum]

Let's close it. I've imported all the ticketing stuff to Live. :)

[bethlakshmi]

awesome!

On Wed, Jan 15, 2014 at 7:35 PM, Marcus DeBoyz notifications@github.comwrote:

Let's close it. I've imported all the ticketing stuff to Live. :)

— Reply to this email directly or view it on GitHubhttps://github.com/bethlakshmi/GBE/issues/128#issuecomment-32431426 .