I had a chance to review the code for the Registration entity module and how we're currently doing event and registration handling with the current version of COD.

Current Major Issues

  • Single event. Multiple events can exist, but sessions, rooms, timeslots, etc have no reference to these events, and thus its not really usable for a multiple-event site
  • A particular event cannot have multiple registration types. We see this with paid vs free events. I invision that an event can have n registration types, where n is a 5-day pass, a training ticket, a 'expo hall' pass, a free pass, etc.
  • Workflows for different event types are handled differently. These should all follow the same workflow, in both creation and in execution. We should hook where needed to add additional steps (aka Commerce), but in general they are additions not deviations.

Solutions to said issues

  • Review patches and fixes suggested here #1084462: Support for multiple events in one cod site (next generation feature)
  • Use OG to organize users and permissions for events
  • Attach OG fields to Sessions, Bofs, Schedule Items, Rooms, and Time Slots to reference events
  • Make the event node also the hub for configuration for an event. This includes moving timeslot configuration from the admin page to the event page, and scheduling admin views. I've created a new admin view that does show up under conference configuration that lists all the events and related admin actions
  • Refactor the registration entity module to allow for multiple types per event. This deserves its own thread

This is a meta ticket. It should be closed when the tickets above are closed. But conceptual conversations around the system should exist in this ticket

CommentFileSizeAuthor
#3 registration-event.png65.84 KBjaperry
#3 registration-tickets.png84.5 KBjaperry
#3 registration-advanced.png96.58 KBjaperry
#2 cod_registration_lfnw_module.patch50.23 KBjaperry

Comments

kclarkson’s picture

kclarkson commented

@japerry

Thanks for taking the time to write this out. You are right on when it comes to multiple registration types for the same event. Hopefully the guys working on the registration module will be able to help with that.

The patch I provided #1084462: Support for multiple events in one cod site (next generation feature) already addresses a couple of the bullet points you posted;

Attach OG fields to Sessions, Bofs, Schedule Items, Rooms, and Time Slots to reference events
I have already added the groups audience fields to the content types.

Make the event node also the hub for configuration for an event. This includes moving timeslot configuration from the admin page to the event page, and scheduling admin views.
The event node is the main organic group content type that allows for Multiple events to work. All other content has a group audience field that would reference the "event" content type.

The "special event" content type replaces the old event type and also has a field to reference the new "event" type. The "special event" content type is used for the VIP parties and excursions that has a separate registration so that organizers can add a price or take RSVP's.

PANELS VS DISPLAY SUITE and how to incorporate CONTEXT
We need to have some sort of consensus regarding how to show the Organic Group posts / content.

Here are my suggestions:
PANELS - Use to override the relevant nodes. -I know many people are against panels but IMHO we should plan for the future and it looks like Panels is going to be a staple in D8 with all of the emphasis on the content editor's experience.
DISPLAY SUITE - Use for Teasers
CONTEXT - Use for all sidebars and menus

japerry’s picture

japerry
Location KOMK
commented
StatusFileSize
new cod_registration_lfnw_module.patch50.23 KB

LFNW cod_registration patch. Not meant for production use, will need some editing.

japerry’s picture

japerry
Location KOMK
commented
StatusFileSize
new registration-advanced.png96.58 KB
new registration-tickets.png84.5 KB
new registration-event.png65.84 KB

Bringing this back alive. Looking at the most recent MOSCOW, there are the following important user stories:

  • Organizer can decide if users can register for the website and register for the event at once, or register for the website only. (Useful for Call-for-papers when registration isn't open yet)
  • User can use existing credentials on the website to login and register for an event
  • Organizer can setup different registration types (Example:)
  • Organizer can view which users have which type of registration.
  • User can view registration types, select desired registration, and become registered for that event
  • User can view registration types, register for other users based upon email addresses, and register them for the event
  • Organizer can limit the number of attendees for an event
  • For paid events, user will be directed to pay for event before they become registered.
  • Users that are registered by other users will see on their account that they are registered for the event.

Looking at some other registration systems, I mocked up a few wireframes. Some can probably guess where I borrowed the UI ideas from. The main goal here is to illustrate whats needed, not what it'll look like.

It seems like this should be attached to the event CT, it definitely makes sense for a multi-event site, and its where entity_registration by default saves a registration reference.



There is some re-work on entity registration that would be needed to get these user stories done. I'll see if we can get that team looped in here.

kclarkson’s picture

kclarkson commented

This looks nice and clean !! Great Job !

japerry’s picture

japerry
Location KOMK
commented
Issue summary: View changes
Issue tags: +cod_paloalto_sprint
jyee’s picture

jyee commented

See issue #2127459: Add Venue and Organizer fields to Events for the additional fields on events shown in the first wireframe above.

We should probably discuss implementation of registration types. Are these products or is it something Entity Registration provides?

japerry’s picture

japerry
Location KOMK
commented

There is a new cod_registration module, which will provide the COD glue where ticket module stops. Ticket is supposed to provide an underlying framework to build upon, its our responsibility to get that framework into COD.

Features

  • Ticket field for event CT

    • - DONE

  • Provides a wizard for registration (/register)

    • 80%

  • Manages registration workflow and ticket states

    • 60%

  • Works with cod_paid_events for commerce related items

    • 10%

  • Sets flags to give users group membership when a certain ticket status is set.

    • 0%

  • Provides check-in functionality for organizers at the event

    • 0%

  • Commit 0c5d7aa on 7.x-1.x by japerry: 
    Issue #1854590: Move registration fields from cod_events to...
japerry’s picture

japerry
Location KOMK
commented
Status: Active » Fixed

Marking this meta issue as fixed, we should make a new issue for a feature to make private events later on.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.