Hello all,
I am the developer for a top 20 trade show and have built a custom registration system for us that we have used for the past three years. I have some free time over the next several weeks, and I was considering making it into a full-fledged module (group of modules) that I could contribute back to Drupal that would be more integrated with Drupal, rather than just being a sort-of app-next-to-Drupal that it is now. I am also helping to organize an open source conference (shameless plug to mosscon.org, we'd love to have you!) which is where I was introduced to COD, which has led me here. I was hoping to throw out a brief outline of what our requirements are and see if they line-up with the future of COD; if so, I'll start digging through how I can begin contributing to make it something that we can use as well. My main concern is: are our registration needs outside the intended scope of COD? I know the event/session/seminar set-up is right up COD's alley.
- We have an Event.
- Event has 0 or more RegistrationTypes.
- Registration may or may not be free.
- Registration may have different rates for different time periods (“early-bird”).
- Registration may or may not be created by anonymous user (general attendee = anonymous, vip = authorized user)
- Registration by anonymous user may or may not create a User account
- User account can own several registrations
- An Event has ChildEvents (give-a-way, press conference, Fleet Forum, etc.)
- ChildEvents can be owned by EventParticipants (exhibitors, sponsors)
- ChildEvents may inherit (usually do) registration from Event
- ChildEvents may or may not require additional registration.
- ChildEvents can have ChildEvents
- ChildEvents can have 0 or more EventParticipants::Sponsors
- An Event and ChildEvents can have EventParticipants (Exhibitor, Sponsor, for example)
- EventParticipants can have 1 or more classification (Exhibitor, Advertiser, Sponsor)
- SponsorLevel can be assigned to Sponsors
- An Event and ChildEvents can have 1 or more Sessions
- Independent of Tracks
- ChildEvents can have 0 or more Tracks
- Tracks can span multiple days but restricted by parent::ChildEvents
- Tracks inherit parent::ChildEvent registration
- Tracks may or may not require additional registration
- Tracks can have Breaks
- Tracks can own 1 or more Rooms
- Tracks can have 1 or more Sessions
- Sessions cannot have Sessions
- Sessions are assigned Rooms
I would appreciate some feedback on this as I would rather be contributing to COD in a way that helps us and that allows us to contribute to the community, if it's feasible given our needs. Also, I don't have much, if any, interest in working on Drupal 6 (unless it's backporting as we build).
Thanks much!
Comments
Comment #1
rootworkI'm sorry no one ever responded to you, but I think a lot of this work would be great to do within the COD development. The only trick would be finding the relevant issues that are already being worked on in the issue queue. I think some of the things you've mentioned definitely exist in the 7.x alpha2 version, and more work has happened since then in the dev version.
So this may be far too late at this point (and I'm not a maintainer or a core developer for this distribution) but I think it would be great if you got involved.
Comment #2
japerryHi clrockwell,
Thanks for your interest in COD. Its great to get a varying number of use cases.
The idea of doing multiple events is being currently worked on in the 7.x-1.x branch of COD. its not complete, and there is a separate debate of how exactly we should move forward with it.
If you are doing one major event per site, you could use the multi-event setup to house your child events. These would essentially be OG groups with their own registrations, session workflow, etc. Multiple events with multiple child events on one site is not possible with COD at this time. OG subgroups is fairly experimental and has various management and scalability issues.
The other issues you're asking about (registration earlybird, tracks, who can register, etc) are either already included in COD or is on our roadmap for 1.0
Comment #2.0
japerryTrying to make requirements more concise
Comment #3
ishmael-sanchez commentedThis thread is a couple years old I say let's move to close this out or make a more concise list that's a bit more actionable. If you disagree with the status change jump in.