Follow Operator

[ahollan1]

[i submitted this a couple weeks ago to "Suggestions for the Software" but haven't had any responses. Didn't know how to 'cross post' so just doing copy paste to see if followers of "Vugraph Issues" are interested]

 

There are a number of scenarios in vugraph where spectators & commentators would like to avoid the need for rejoining a table that they've been watching. In some cases the issue is the tournament format more often a technical issue. Either way, it would be very helpful and user friendly if there was a mechanism to automatically rejoin when the table becomes available again.

 

Examples

 

A) Pairs Event, all players change after a round

B) Paris Event, on pair changes, one pair stays but may rotate seats

 

In these cases, the room must be closed after each round to handle the change in Player Names.

 

If there was a hook to "Follow Vugraph Operator", reopening of the modified table could pull in all subscribers. The relationship should only last through

 

1) life of the event + session

2) bbo account not leaving the room while it is still functioning

 

C) Room Crashes - true, this almost never happens :o but again it seems ability to attach to vugraph operator would benefit all

 

D) Operator account unexpectedly logged off

If specs/commentators have established hook to operator, this relationship should be preserved -- but only through the particular event+session. That would cove

 

D) Session planned but not yet game time

This situation may be more important for Commentators who have been assigned to specific tables, but maybe spectators could also benefit if there was a way to signup for the event + room. This would facilitate timely entry into the room AND help commentators get into the correct room.

 

D1) Perhaps this functionality could be extended so that the Vugraph Commentator COORDINATOR could [manually or via some input file] establish the registration per communicated assignments

 

 

Note: Even without this functionality, it might be helpful if the BBO announcement that is broadcast when new vugraph room is opened was modified to include not just name of the event - but also the name of the room [i.e. did open or closed room just open]

 

D2) As with tables with pre-assigned seating, the new functionality would best serve if it pulled registrant into an already open vugraph room. This covers 2 situations

(a) Later arrival of registrant

(B) registrant account loses BBO connection while in still functioning room

 

D3) It is easy to imagine a non-commentator registering for a future event, who is logged in, but not available or decides not to go to vugraph room. So - perhaps the registration form can include options of the type

(a) automatically take me to the vugraph table

(B) ask if i want to go to the vugraph table

 

 

D4) [this one is huge stretch] If registered for "next session" of a vugraph event, perhaps the automatic logoff timer could be adjusted so that there is no need to log back on in time for the after meal break restart. This is unreasonable when next session is next day, but if break is known to be no more than 2-3 hours, then it would be very user friendly if the auto-logoff could be avoided

 

 

I'm sure there are other scenarios that could be considered and adjustments that could be suggested but feel this is more than a good start at presenting a solution for a very common problem

 

Al Hollander

[ahollan1]

[Rain]

This will help only in the scenario where vugraph crashed, and the same vugraph operator comes back and reopens table.

 

-VOs use a wide variety of names. The names are recycled often. Unless you turn "follow VO#5 off", in 2 months you may be following an entirely different VO#5 in his vugraphed event.

 

-Different sessions may have different vugraph operators, even in the same event.

 

Kibbing commentators and following a certain commentator makes more sense than following vugraph, and to achieve that, just mark the commentator you want as friend and join his table.

[ahollan1]

I think you missed a key point in the original post

 

"The relationship should only last through

 

1) life of the event + session

2) bbo account not leaving the room while it is still functioning"