<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: GenCon Registration 2009: RUBI System = Best Reg So Far</title>
	<atom:link href="http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far/feed" rel="self" type="application/rss+xml" />
	<link>http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far</link>
	<description>The Game Mastering Blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 00:00:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alan De Smet</title>
		<link>http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far/comment-page-1#comment-5401</link>
		<dc:creator>Alan De Smet</dc:creator>
		<pubDate>Mon, 27 Apr 2009 19:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnomestew.com/?p=3162#comment-5401</guid>
		<description>Wishlists were a great addition.  You could fill your wishlist before registration when things were relaxed.  Then during the crush you could log in, mash two or three buttons, and it tried to buy one of everything in your wishlist.  Not perfect if you need multiple tickets for one event, and while it let you try for conflicting events the fallback system was crude (you got the lowest numbered event available, later conflicts were dropped).  Still, a serious step forward.

I have some sympathy for the scaling problem for the initial crush.  Gen Con is, relatively speaking, a little company.  Scaling up your entire system what I&#039;m guessing is an order of magnitude for 30 minutes a year is hard for anyone.&lt;div class=&quot;comment-remix-meta&quot;&gt;&lt;a href=&quot;#&quot; class=&quot;replyto&quot; onclick=&quot;replyto(&#039;5401&#039;,&#039;Alan De Smet&#039;); return false;&quot;&gt;Reply&lt;/a&gt; &lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Wishlists were a great addition.  You could fill your wishlist before registration when things were relaxed.  Then during the crush you could log in, mash two or three buttons, and it tried to buy one of everything in your wishlist.  Not perfect if you need multiple tickets for one event, and while it let you try for conflicting events the fallback system was crude (you got the lowest numbered event available, later conflicts were dropped).  Still, a serious step forward.</p>
<p>I have some sympathy for the scaling problem for the initial crush.  Gen Con is, relatively speaking, a little company.  Scaling up your entire system what I&#8217;m guessing is an order of magnitude for 30 minutes a year is hard for anyone.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('5401','Alan De Smet'); return false;">Reply</a> </div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Benson</title>
		<link>http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far/comment-page-1#comment-5316</link>
		<dc:creator>Patrick Benson</dc:creator>
		<pubDate>Mon, 20 Apr 2009 17:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnomestew.com/?p=3162#comment-5316</guid>
		<description>It is an improvement, yes, but it is still not a good system. Maybe I&#039;m just being too harsh because of my profession, but a good system doesn&#039;t slow down during the high impact periods. And a good system wouldn&#039;t require that I go to another site in order to search for information about Gen Con events.

Yes, it is better. It still isn&#039;t the gold standard and Gen Con should be at the gold standard. A for effort, C- for the site.&lt;div class=&quot;comment-remix-meta&quot;&gt;&lt;a href=&quot;#&quot; class=&quot;replyto&quot; onclick=&quot;replyto(&#039;5316&#039;,&#039;Patrick Benson&#039;); return false;&quot;&gt;Reply&lt;/a&gt; &lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>It is an improvement, yes, but it is still not a good system. Maybe I&#8217;m just being too harsh because of my profession, but a good system doesn&#8217;t slow down during the high impact periods. And a good system wouldn&#8217;t require that I go to another site in order to search for information about Gen Con events.</p>
<p>Yes, it is better. It still isn&#8217;t the gold standard and Gen Con should be at the gold standard. A for effort, C- for the site.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('5316','Patrick Benson'); return false;">Reply</a> </div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt "Telas" Schneider</title>
		<link>http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far/comment-page-1#comment-5314</link>
		<dc:creator>Kurt "Telas" Schneider</dc:creator>
		<pubDate>Mon, 20 Apr 2009 15:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnomestew.com/?p=3162#comment-5314</guid>
		<description>Anyone can criticize (and if the internet proves anything, they usually will), but it&#039;s a rare individual who will publicly praise something they once criticized.  As a Gen Con attendee who has to deal with both the frustration of registration, and the (well earned) complaining from the users, I think your series of &quot;registration reviews&quot; is an example of how to provide solid feedback, both negative and positive.

Your article above (and your previous ones) expresses my sentiments exactly: This year&#039;s registration was the best ever, and by a goodly margin, but there&#039;s still room for improvement.&lt;div class=&quot;comment-remix-meta&quot;&gt;&lt;a href=&quot;#&quot; class=&quot;replyto&quot; onclick=&quot;replyto(&#039;5314&#039;,&#039;Kurt \&quot;Telas\&quot; Schneider&#039;); return false;&quot;&gt;Reply&lt;/a&gt; &lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Anyone can criticize (and if the internet proves anything, they usually will), but it&#8217;s a rare individual who will publicly praise something they once criticized.  As a Gen Con attendee who has to deal with both the frustration of registration, and the (well earned) complaining from the users, I think your series of &#8220;registration reviews&#8221; is an example of how to provide solid feedback, both negative and positive.</p>
<p>Your article above (and your previous ones) expresses my sentiments exactly: This year&#8217;s registration was the best ever, and by a goodly margin, but there&#8217;s still room for improvement.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('5314','Kurt \&quot;Telas\&quot; Schneider'); return false;">Reply</a> </div>
]]></content:encoded>
	</item>
	<item>
		<title>By: DNAphil</title>
		<link>http://www.gnomestew.com/gaming-conventions/gencon-registration-2009-rubi-system-best-reg-so-far/comment-page-1#comment-5309</link>
		<dc:creator>DNAphil</dc:creator>
		<pubDate>Mon, 20 Apr 2009 11:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnomestew.com/?p=3162#comment-5309</guid>
		<description>I have to agree.  While I did have some problems in the first 12 minutes, after that the system was much faster than any of the previous years.  I also really liked the Watchlist feature, and the ability to buy tickets for everything on your watchlist all at once. I also liked that you could buy tickets for friends, and that the schedule showed you where you had conflicts when you looked at other events.  All in all, RUBI was a big improvement over past systems.

But on one bit of criticism, and this is meant to be positive.  With a few years of online registration under their belts, the GenCon registration team, knows what the initial volume of transactions are going to be in the first 15 min of opening registration for both True Dungeons and the rest of the events.  Efforts should be taken to scale the system up to handle that level of volume.  While the system seemed to recover after 15 min, those first few minutes after the opening of registration felt like years past.  

So, in your post mortem analysis of the 2009 registration, please set a goal for next year to scale RUBI to handle more than the volume of transactions in those first 15 min.

Otherwise...good job, and far less painful than years past.&lt;div class=&quot;comment-remix-meta&quot;&gt;&lt;a href=&quot;#&quot; class=&quot;replyto&quot; onclick=&quot;replyto(&#039;5309&#039;,&#039;DNAphil&#039;); return false;&quot;&gt;Reply&lt;/a&gt; &lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>I have to agree.  While I did have some problems in the first 12 minutes, after that the system was much faster than any of the previous years.  I also really liked the Watchlist feature, and the ability to buy tickets for everything on your watchlist all at once. I also liked that you could buy tickets for friends, and that the schedule showed you where you had conflicts when you looked at other events.  All in all, RUBI was a big improvement over past systems.</p>
<p>But on one bit of criticism, and this is meant to be positive.  With a few years of online registration under their belts, the GenCon registration team, knows what the initial volume of transactions are going to be in the first 15 min of opening registration for both True Dungeons and the rest of the events.  Efforts should be taken to scale the system up to handle that level of volume.  While the system seemed to recover after 15 min, those first few minutes after the opening of registration felt like years past.  </p>
<p>So, in your post mortem analysis of the 2009 registration, please set a goal for next year to scale RUBI to handle more than the volume of transactions in those first 15 min.</p>
<p>Otherwise&#8230;good job, and far less painful than years past.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('5309','DNAphil'); return false;">Reply</a> </div>
]]></content:encoded>
	</item>
</channel>
</rss>

