RidgeStar
About
Locations
Manual
Preface
Introduction
Versions
Concepts
Construction
Usage
Operations
Assignment
Bulk Load
Data Prep...
Direct Deposit
Finances
Mail
Options
Messaging
Notification
Privacy
Reset Password
Schedule
UID Allocation
UID and SRC
User-Agent
USSF_API
Welcome
Questions
Features
Settings
Internals
Appendices
Reference
Service
Logon
RidgeStar

Manual: Operations-UID and SRC

Logontranslateoff
Get Started |Calendar |Locations

Feature=UIDFeature 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.

When a Site Administrator that has Feature=UID active would like to maintain the connection between a User and the UID mechanism for the purposes of contacting the Washington State Referee Committee (the SRC), the following steps outline the most common sequences to establish the UID value in the User's profile:

At Administrator: RidgeStar-UID in your Site, put LastName into the criteria and click Show.
Basically, utilize the necessary combination of criteria elements to confirm that the individual you are seeking is (or is not) already defined with a UID (it's important that every individual has ONE and ONLY ONE UID entry!). Your fellow Webmasters are counting on you to use appropriate care when manipulating the contents of the UID table.

Once you have established whether the individual is already defined in the UID table (or not), you should be able to determine which of the following approaches you should utilize.

If you see the desired individual and s/he has a defined StateRefID in their UID Table entry
  1. Place the value you see in the UID column into his/her User Profile in your Site (usually located on the Administrator tab of the User Profile).

Do NOT place the StateRefID value into the Users entry, place the UID value (the UID entry will, in turn, identify the StateRefID for the purposes of contacting the SRC). Many of the Referees registered prior to March 2013 will have a UID value that is the same as the StateRefID, but it remains the UID that should be placed into your Users table.

If you see the desired individual and s/he does NOT have a defined StateRefID in their UID entry
  1. At Administrator: Tools-SRC on your Site, put the FirstName+LastName into the criteria and click Display
  2. If the individual is defined to the SRC, the API Response should report [UNIQUEID] with a value (the value is the SRC's StateRefID)
  3. Return to Administrator: RidgeStar-UID and place the SRC's StateRefID into the UID entry for the individual
  4. Place the UID value into your Site's User Profile for the individual (usually, in the Administrator tab).
If you do NOT see the desired individual at all
  1. Obtain the SRC's StateRefid (see steps 1-2 above) for the individual
  2. At Administrator: RidgeStar-UID on your Site, click the Add symbol (Add) after the Show action (this should provide a FORM for you to fill in)
  3. Put in the FirstName, MiddleName, LastName, and StateRefID and click Update (USSFNumber and BirthDate are optional, but intended to help other webmasters determine if the individual is the same one they're trying to add, so we don't end up with multiple entries defining the same individual).
  4. Place the UID value into your Site's User Profile for the individual (usually, in the Administrator tab).

Note that the combination of FirstName+MiddleName+LastName MUST be unique within the UID mechanism, BUT the name does NOT have to match what's on file as the "common name" within the Chapter sites (and, in fact, there are multiple individuals that do this - different names in different sites...).

Updated: 8 January 2014