matthusby / brewcompetitiononlineentry

Automatically exported from code.google.com/p/brewcompetitiononlineentry
0 stars 0 forks source link

In judging, stewards can't be assigned to more than one table #187

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Build a comp with non-queued judging
2. Assign a steward to a table
3. Try to assign a steward to a second table

What is the expected output? What do you see instead?
IMHO the analogy is like this: A steward in a non-queued judging comp is like a 
restaurant server. A steward in a queued judging comp is like a bartender. A 
server runs around to multiple tables, a bartender handles one. They don't 
stand at one table waiting to do something. The system should allow us the 
flexibility of indicating multiple table assignments per round for a steward in 
this kind of comp.

What version of the product are you using? On what operating system?
1.2.1.2

Please provide any additional information below.
This seems to be a result of what seems to be that the preferred comp design 
using BCOEM is queued judging. There are some other walls we've run into that 
seem to stem from this as well. Hopefully these styles of comp can be 
differentiated more in BCOEM?

Original issue reported on code.google.com by ted.as...@gmail.com on 25 Oct 2012 at 6:03

GoogleCodeExporter commented 9 years ago
In general, the program is meant to be useful for both types of judging. 
Admittedly, the queued judging components were easier to program due to the 
smaller set of variables involved. In the spirit of your analogy above, let me 
offer this one about the program. 

BCOE&M is a tool, much like a hammer. Each competition that uses the program is 
a nail. Each competition is unique because the particular set of resources for 
the competition vary from other competitions (entries, participants, staff, 
etc.). There are also many commonalities among all competitions (entries, 
judges, stewards, etc.). 

The software can only account for the commonalities among competitions and 
cannot account for all variances and idiosyncrasies. 

So, continuing the analogy, one competition could be a finishing nail, another 
a 10 penny, and yet another a railroad spike. BCOE&M is just a plain old claw 
hammer. It will get the job done on each, but the degree of hammering will 
depend upon the user.

In the case of stewards, I agree with your suggestion and will look at a 
solution.

Cheers,

Geoff

Original comment by gpzhumphrey on 29 Oct 2012 at 8:28

GoogleCodeExporter commented 9 years ago
Thanks Geoff! Just tossing them out there, you control the destiny of the
app.

Ted

On Mon, Oct 29, 2012 at 1:28 PM,
<brewcompetitiononlineentry@googlecode.com>wrote:

Original comment by ted.as...@gmail.com on 29 Oct 2012 at 8:51

GoogleCodeExporter commented 9 years ago
No worries, Ted. Thanks for being so diligent and forward-thinking.

Geoff

Original comment by gpzhumphrey on 30 Oct 2012 at 3:31