Vugraph country flags

[DVH1]

Could you add one of those small flags to the names when players represent a country on vugraph. It would make it more interesting for those of us kibs that do not know all the players in the world. It would also help to identify the paired tables when multiple games are in progress. Thanks.

[helene_t]

Usually the player profiles on vugraph have flags, especially when the represent countries.

[barmar]

I think the flag is normally shown in VuGraph. If it doesn't, I think it means that the VuGraph operator didn't select the countryy.

[Walddk]

I think the flag is normally shown in VuGraph.  If it doesn't, I think it means that the VuGraph operator didn't select the countryy.

Only the vugraph operator can edit player profiles, e.g. name, country and useful information. Many do, some don't. Experienced operators have plenty of time to do it, perhaps not before play begins if they are in a spot of time trouble, but if not, then soon afterwards.

 

Less experienced people have plenty to do with following the play and do not edit the profiles, not even when encouraged through a private chat message. Finally, some don't even know that they have the option.

 

It is of course desirable that flags are shown. We do not have specific rules with regard to this issue, but recently I added the following to our standard vugraph guidelines:

 

"Please make sure that the operator edits the player profiles and inserts name and flag. The same applies to the operator, who should put full name an country in her or his profile.

 

As far as players are concerned, we also recommend that operators use surnames only. The software only allows 10 characters. Example: Versace is fine, but Alfredo Ve is not. That is what you will see if you try it type first names too."

 

Roland

[barmar]

Roland, how long has it been since you operated a Vugraph? The country is a menu you select from in the same window where you type the player's name. It takes 5-10 seconds. The only problem is if the operator doesn't know the player's country.

 

I think there's little excuse for skipping this in team games. In pair games, where new players have to be entered each round, time can be short. It's helpful if the organizers provide the incoming players for the round ahead of time, so the operator can fill this information in when they're not also rushing to follow the auction.

[ahollan1]

I don't recall ever seeing Fred or Uday responding to a forum entry that suggested software changes geared toward vugraph issues. However, if/when they decide to allocate resources, this is one of many situations where a software approach could:

 

a) reduce reliance upon operator training

:) minimize/eliminate operator typing tests

c) improve the accuracy of the historical record

 

If they'd be used, I would be happy to supply requirements, design options and/or testing.

[barmar]

I think the main thing on their to-do list regarding Vugraph operating is adding it to the Flash client. Hopefully when they do this they'll address the usability issues.

 

I'm not sure what you mean by "typing tests", as I don't recall having to do any complicated typing when I've done Vugraphs. But maybe I don't notice because I'm a touch typist.

[ahollan1]

My use of "typing tests" refers to anything that the operator must manually enter even though the information is already known in a way that could be captured and retrieved electronically. Examples will take us beyond the scope of the current thread, but will include that specific use case so I'll list some here:

 

In World Championships, Zonals, Team Trials where pre-registration is required, all of the following is known before the tournament begins. Very little if any manipulation would be needed to parse the data in a form that could either be read/remembered/recalled by BBO.

 

1) Team Name

2) Team Roster

3) Player Nationality

 

The first 2 eliminate the need for operator to

* determine correct spelling

* enter correctly

* ask first name of player [no more confusion about Steve vs Howie Weinstein]

 

When pre-registration is not used, the tournament officials still get to a point where there is an electronic capture of team/player information. Since this data is likely to be less rigidly formatted, then some careful data manipulation might be required.

 

We should even be able to go outside the confines of a specific tournament to build a "database" of frequent fliers. i.e. players often seen on vugraph. Creating this bank of vugraph player profiles could then [always] include such goodies as:

 

* player's BBO handle

* link to official copies of partnership convention cards

* player's web page/blog [only with their permission]

* usually sits in direction X

* etc

 

There are many elegant scenarios that could be played out at this point, but the key issue is that the worst case scenario would be that the operator would just need to copy/paste info into the table or place a pre-defined bbo vugraph player account in the proper seat.

 

The idea is that when electronic solution(s) are available, eliminate the randomness of vugraph data based upon operator: training, familiarity with players, spelling, typing, flag selection ....

 

Since operator would always have the ability to override any data that was grabbed electronically, I don't see a downside to the concept. [note: design/implementation impact on diskspace, cpu usage, processing speed, etc is a different matter]