<div dir="ltr"><div>Thx Alan.<br><br>I think their driving hope was to get away from the last name partitioning. I agree the robot aspect could be failure-prone. Of course if I were building it it'd probably have big giant flashing screens.like that selection system in Starship Troopers. <br>
<br></div><div>If they had a local copy of the db on each machine or local network they could handle the just-in-time print with mitigating the network concerns.<br><br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jan 29, 2014 at 12:18 PM, Alan Gardner <span dir="ltr"><<a href="mailto:alanctgardner@gmail.com" target="_blank">alanctgardner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">The idea of using a robot to dispense pre-printed materials is alluring, but it seems like it might be more failure-prone than print-on-demand. My low(ish)-cost proposal:<div><br></div><div>- Partition your attendees by last name, so each last name can only use one terminal. Put the attendee list for each terminal on a USB key (maybe a SQLite database?).</div>
<div>- Have n terminals, each with a range of last names, with a B&W laser printer attached directly</div><div>- Attendees check-in on the terminal with a unique code from an email, and the local printer prints on demand and updates the database on the USB key.</div>
<div><br></div><div>Each terminal is stand-alone, so there's no risk of network issues. You might want to have n+1 terminals, so you can move the USB key to a new terminal in the event of a printer/computer failure. </div>
<div><br></div><div>Just a thought.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jan 29, 2014 at 12:07 PM, Jamie <span dir="ltr"><<a href="mailto:jamie@steppinofftheedge.com" target="_blank">jamie@steppinofftheedge.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div>Hello,<br><br></div>I'm working on web site component of a conference with Carleton U and the organizer mentioned a desire to improve the registration check-in process. Thought maybe someone on this list might have seen a solid solution or have an idea on creating one?<br>
<br></div><b>The Details<br></b><ul><li>Most conferences default to having pre-printed schedules, name badges and materials available through a volunteer base co-ordinating people into lines based on last name to get their materials.<br>
<br></li><li>Some use QR code or kiosk to input email and on-demand print of same name badges, materials, etc.<br><br></li><li>They would like to find a balance between the two which have the pros of each and none of the cons - no lines, small need for volunteer army to checkin but not at-risk of printer malfunction or network issue from on-demand print.</li>
</ul><p>My brain went to grocery store self-checkout change return system concept. Some kind of setup that allows:</p><ul><li> pre-printed materials placed into envelopes that are numbered and/or QR coded</li><li>When person arrives they provide email or QR code</li>
<li>The system drops their envelope out for pickup.</li><li>If network goes down, volunteers only need to check name to # to numerically find an envelope.</li></ul><p> No idea of budget - but I'd be happy to connect the dots for anyone interested in pursuing.</p>
<span><font color="#888888">
<p>Jamie<br></p></font></span></div>
<br></div></div>_______________________________________________<br>
Lab mailing list<br>
1. subscribe <a href="http://artengine.ca/mailman/listinfo/lab" target="_blank">http://artengine.ca/mailman/listinfo/lab</a><br>
2. then email <a href="mailto:Lab@artengine.ca" target="_blank">Lab@artengine.ca</a> to send your message to the list<br></blockquote></div><br></div>
</blockquote></div><br></div>