Manual: Operations-UID Allocation

Feature=UID provides an operational mechanism that permits the unique identification of an individual (a "User") across sites and operational systems. The UID mechanism recognizes that individuals, using "Common Names" may not be known by the same name in different places (Sites, Databases, etc.) and is designed to eliminate the ambiguity associated with uniquely identifying an individual.

To activate this mechanism, each defined individual in a Site (a "User") is connected to an entry in the RidgeStar UID table via the UID table's primary Key (named the "UID"). This "UID Table" is maintained by all cooperating Administrators from within their own Site at Administrator: RidgeStar-UID.

The Administrator can manually search the UID database for a suitable entry when a new User enters the system. If found, the ersulting can be manually copied to the Users table. If not found, other processes can be used to manually allocate a new UID entry, etc.

For those sites with the UID Allocation mechanism implemented (represented by the persence of a in a results listing related to a User), a single click requests that the site search the UID database for an exact match to the User using FirstName, MiddleName, LastName, and BirthDate.

If an exact Match is located...

The Site will store the located UID into the Users table entry of the related Users table entry identifying the individual.

If an exact match is not located..,

The Site will query the UID database for any entry that has the same LastName and BirthDate and display the results. If one of the listed entries can be identified as the same individual (e.g. a slightly different FirstName), the Administrator can manually place the UID into the Users' table UID data field (thereby manually creating the linkage between the User and the UID table)

If there are no Lastname+BirthDate matches located...

The Site will allocate a new UID entry in the UID Database, placing the FirstName, MiddleName, LastName, and BirthDate into it. The resulting UID is then placed into the Users table UID data field.

Note that the UID mechanism is useful in multiple cross-site situations. If you are seeking information about how the UID relates to the Washington State Referee Committee's API, please see Manual: Operations-UID and SRC.

Updated: 14 January 2014