|Performing Server Maintenance / Checking Data|
When checking names, the Data Check is looking for situations which result in ambiguous choices when a user issues a voice command.
This can include either of the following situations:
Two (or more) badge users with the same first name in the same department, when "First Name and Department" is enabled as a System Preference.
For example, if Seymour Krelborn and Seymour Puddle work in the Produce department, and the "First Name and Department" setting is enabled in System Preferences, a voice command to "Call Seymour in Produce" would result in two possible targets for the call.
This is an ambiguous choice, as further clarification from the caller is required when calling "Seymour in Produce" (the user can respond to the full name of each possible choice when the Genie asks for clarification).
The Data Check would flag this item with Low Severity, as having a spoken name in common. Fixing Low Severity items can wait until you have time to investigate and resolve them, as they do not prevent communication from occurring. However, they do result in annoying "Do you mean so-and-so?" questions for system users, which may lower their satisfaction and reduce the overall usage level of the system.
Similarly, any two non-user entities with the same Spoken Name will be flagged with Low Severity. For example, if two groups, "Info Services" and "I T" share the spoken name "I T", they will be flagged with Low Severity (again, when the Genie asks for clarification the user can distinguish between the possibilities using the full name of each group).
Two (or more) names (users, buddies, and address book entries) with the exact same spoken name (first and last names for people).
When two users have the same first and last names (e.g. "Joe Fox"), they will be flagged with High Severity, as there is no way for a user calling Joe to tell them apart.
If you have enabled calling by first name and department on the Preferences page of the System screen, the Data Check report may display a large number of conflicts. For example, the users Seymour Glass and Seymour Franklin may have the spoken name "Seymour in Produce" in common. Depending on the size of your departments, your report may display many speech recognition conflicts in this form.
If your data check report contains many first name and department conflicts, you can fix the problem in either of the following ways:
Temporarily uncheck "First Name & Department" in the System Preferences tab and run the report to filter these speech recognition errors. Turn the feature on again immediately, because turning it off for more than a few moments on a production system may confuse users.
After fixing other speech recognition conflicts, run the report again and fix the "First Name & Department" conflicts.
Permanently disable the call by first name and department feature.
If this feature results in too many errors, disable it and require users to call by first name, last name, and department.