[Inpycon] Ticket cancellation/refund policies.

[Bibhas Ch Debnath]

On 20 June 2012 14:48, Kiran Jonnalagadda <jace at pobox.com> wrote:

> On Wed, Jun 20, 2012 at 4:12 AM, Sreekanth S Rameshaiah <sree at mahiti.org>wrote:
>
> Checked the refund future of doAttend. This is simple enough to manage.
>> Also, there is a edit functionality for booking, do you use this for
>> transfer?
>>
>
> Yes, when someone asks for a transfer, we use this to send it to the new
> person.
>
> We also ask people to NOT print tickets (the default DoAttend ticket
> template says DO print). It's easy enough to export the attendee list, sort
> it and keep a printout at the registration counter.
>
> When an attendee walks in, ask them to show some form of id and check
> their name off the list. Don't bother with their ticket printouts. This
> solves all problems with verifying tickets.
>
> We've automated all this with an open source app:
> https://github.com/hasgeek/peopleflow (repo is missing BSD license
> declaration and setup instructions since we're the only users so far).
>
> In Peopleflow, if you check a name off the list at one counter, it goes
> away from all other counters because it runs as a web app. This allows
> having registration desks that are physically separated from each other.
>
>
A small app like this makes sense. Easier to keep track of attendees. I
built one for a local event here. Something similar was also there at Open
hack. Easier to search through the list. Or else, if done manually, it
takes around 5-10 seconds per person to find them in the list.


> Kiran
>
> _______________________________________________
> Inpycon mailing list
> Inpycon at python.org
> http://mail.python.org/mailman/listinfo/inpycon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20120620/d7f0800b/attachment-0001.html>