Lessons from #EJC2015

Search posts
Forum index

 

Dee -

Lessons from #EJC2015

This will be a small series of posts [which, individually, may be quite long] on some of the transferable lessons from the EJC just gone.

Registration:

This went remarkably smoothly, but I think that some efficiencies can be achieved. The combined single queue that split at the last minute worked well in ensuring that no one was stuck in the “wrong” queue.

The QR system worked really well in enabling fast processing, without requiring bar-code scanners. I would, however, have called it a ticket rather than an e-ticket, as the organisers wanted people to print out the ticket and sign the disclaimer. In my head, an e-ticket is not something that needs to be printed.

Having sufficient floor space really made a difference. This meant that the queue could be managed in a less frenzied manner [especially in comparison to Toulouse] and people had room to manoeuvre.

I would like to have a few (perhaps 2) express desks: adults pre-registered for the full week only. This reduces the number of options required for the desk and could speed-up the process [enabling you to use your volunteers with more languages for more complex interactions]. Under 18s require a range of different permission slips, making the process slightly slower and more complicated.

Another desk (note that this desk would also take standard pre-registrations) for those arriving with a large number of youths [e.g. youth circuses] – rather than splitting to individual desks; this is because those working at the desks must check ID etc. from those acting in loco parentis – often a limited number of people that then need to go from one desk to another if split out, slowing up all desks.

The passes this year were great: sufficiently long to go around the leg, with a sufficiently generous metal clamping bit to allow the pass to be easily reassembled if someone wanted to put it on their leg – this has been an issue in the past – the passes were long enough to go around the ankle, but could not fit across the heal without coming undone and then were almost impossible to reassemble in situ. To make this process more efficient, I would have a clamping station away from the registration desks – mainly for those wanting it on the leg [the wrist clamping didn’t cause any delays]. The name of the manufacturer and the specification of the passes should be passed on to other organising teams.

The six-odd hours of making up the registration packs on the Friday before the convention started was worthwhile when it came to speeding up the registration queues. There are always people onsite on the last day that aren’t really in a fit state for heavy lifting – this is a highly practical use for those bodies.

I would also note that those working on registration desks should not put gala show tickets into these packs; rather that they should physically hand over the gala show ticket to the person registering [more likely to be put into a safe location].

The day ticket passes this year were difficult to work and caused confusion for volunteers on badge control points. The day passes were also a woven wrist/ankle band, with those clamping the pass required to alter the point of the clamping bit to indicate the validity of the pass. This is surprisingly tricky when done on the wrist and really tricky on the ankle. Then those on badge control weren't sure if the clamping point indicated the last day of validity or the day after the last day [with some slippage when clamping, it could possibly have meant either].

If possible (not sure how compatible this is with Andi’s system), I would have those paying for more than a single day enter their own details into the system [would require more computers, but not necessarily ones able to scan and process QR codes] to avoid someone having to do this at a later point. This is particularly important if someone then wants an official receipt [which could be issued later in the week, when registration is quieter] as their details of when they arrived and how much they paid would be already on the computer system.

Orinoco - - Parent

Great work Dee. Lots of useful stuff in there for convention organisers.

Handing over the show ticket separately is a great example of engineering a problem out of the system (lost show tickets are a real pain to handle for reg desk volunteers). I always make sure I put my show ticket in my wallet straight away, it's annoying when I have to open an envelope & fish around for it.

There have been many studies on queueing theory. The single queue that splits is almost always the most efficient solution. The only instance that I remember where it isn't is when they number of kiosks desk at the end is so many that people fail to spot when a desk becomes free. Not a situation likely to happen at a juggling festival.

I wonder if a self service prereg kiosk could be built? Attendees insert their card or type in their prereg number which queries the prereg database & prints a colour coded ticket. They then take the colour coded ticket which volunteers swap for a corresponding coloured pack of goodies.

^Tom_ - - Parent

Such as at Karlsruhe (2008) gala show (2 doors, people queuing for door 1 blocking access to the deserted door 2), or Munich EJC registration.

The problem in both cases was that people only saw the alternative when they were sufficiently close to the front to think "ah well, I'm nearly there now", and deprive the system of running at full efficiency. I'm pretty sure that it would have been fixed in both cases with a steward, and would have almost certainly have saved volunteer-hours overall.

Dee - - Parent

Having the space available for a single queue that splits last minute [with enough space between desks that it is obvious which desk is free and easy to access the free desk] is a bonus.

I also like Tom's suggestion of smart phone enabled "register on site" option to reduce the amount of information needed to be entered by the team of volunteers [but this would need a separate wifi system to avoid causing overburden on the registration system wifi - as lots would access this system in the queue just to check emails / facebook etc].

^Tom_ - - Parent

As to the final point, you've just given me an excellent idea, which would be to have a smartphone based form where all non-preregistered information could be pre-completed by people standing in the queue, and then the desk tablets would then be able to pick up the registration by scanning a qr code on the phone with the tablet, which tells them which forms to get signed, which ID to check, how much cash is required, and what tickets to assign.

As you suggest, this is mostly about a transfer of the burden of effort, it also helps people to know before reaching the desk what to expect (cost etc), which would certainly help out those on the desk.

If you want to make your suggestion to Andi's system, there is an issues/feature request section on the github page, otherwise I'll try to remember to mention it to him next time I see him.

Dee - - Parent

Can you send me the github link [by other means available...] I have a few feature requests that are quite system specific that don't really need to clutter up this discussion

Orinoco - - Parent

I'd be interested in having a poke around the code too. I did a quick search & found this which looks interesting.

Little Paul - - Parent

If you google for "EJC Registration" you end up at https://prereg.eja.net

If you look in the bottom right hand corner of that page, there's a link to https://github.com/inbaz/ers/issues which is the issue tracker for the https://github.com/inbaz/ers project, which looks very much like the code you're looking for?

Orinoco - - Parent

Err... yeah! I did say it was a quick search!

Dee - - Parent

Another piece of good practice implemented by the onsite registration team was the decision not to try to distribute merchandise during the crazy initial rush. This year this was because there was a separate merchandise shop for the entire week; however, others should consider the same.

 

Subscribe to this forum via RSS
1 article per branch
1 article per post

Forum stats