|
FAQs for the xDUID
PRINT
|
| How does this product generate the unique id’s? |
|
The core of the xDUID application is the xDUID Match Engine. The xDUID Match Engine is used to evaluate attributes to determine if a student already exists in the system. New identifiers are only created for students when processed through the xDUID Match Engine. The same identifier is retrieved as students change schools, change districts, or exit and re-enter the education system. The matching technology contained in the Match Engine uses a two-pass system to quickly eliminate dissimilar records from consideration. The few remaining records are examined in detail for similarity. In some cases, a character-by-character review of each field is initiated. The component determines a normalized match score and applies the result to thresholds set for confidence limits among matches. This approach allows the system to determine their levels of for the special characteristics of text, numeric, and date elements. The xDUID Match Engine will return one of three possible results:
- Where the input data probability exceeds the match threshold a single existing student, the application will return the UID and details of that student.
- Where the input data probability does not exceed possible match thresholds for any student, the application will return a no match condition with the ability to create and assign a new UID.
- Where the input data probability matches multiple students, or is similar enough that it may match one or more records a list of the matching students will be returned. Authorized users can resolve the UID online from a list of multiple matches is generated for resolution.
In cases where the xDUID Match Engine cannot discern whether two or more records describe the same student, users are presented with the information needed to make a correct determination. If no existing record describes the student in question, a new identifier can be created and assigned.
|
| How configurable is the unique id generator? |
|
The xDUID application is configurable with regard to the type and nature of attributes stored and used to describe students. Configurable weighting factors are used in calculations. An administrator can tune system threshold ranges that determine whether records are considered a match or need further review. The Administrator can configure aspects of the attribute fields through XML configuration files and web UI screens. The user interface will allow the selection of weights, the type of attribute fields, and match thresholds for custom attributes. Certain aspects of default attributes and the nature of the default attributes can also be configured by the Administrator. User configuration will not modify the number of supported attribute fields, but will allow for assignment of comparison fields, adjust weights, and provide display/use information.
|
| How does the xDUID address possible duplicates? |
| Periodic de-duplication of the xDUID master database is an important operational function. The process for a system wide de-duplication process is built into the xDUID framework and it is suggested that de-duplication be processed whenever large batch loads of data are engaged or mass changes are made in the system. The xDUID system recognizes the dynamic nature of the unique identification process and provides a web user interface to manage and evaluate potential duplicates in the master identifier database. Duplicates may arise, without regard to the accuracy of the CPSI Match Engine, when errors are made in data entry or erroneous information is provided to the system. A key element in the successful implementation of a unique identification system is the process of preventing and managing duplicates. |
| How does the xDUID handle UID’s that have been inadvertently assigned to the same student by users? |
| When duplicates are identified, the xDUID provides a linking mechanism to link one student to another to accommodate the duplicate while maintaining the integrity of historical records. Once a student is established with a UID, the student cannot be deleted nor the UID reassigned. An Administrator can link students that have different attribute information, but are known to be the same individual. Linking records establishes a method to define multiple records as the same student and preserving the existing UID’s. Among linked records, only one record is designated as primary at any given time, however, all of the historical information is retained to support retrieval of information without the requiring districts to edit or alter data. The system will maintain an audit trail of linked students. |
| What is the format of the UID number in the xDUID System? |
|
The xDUID has the ability to generate its own pool of UID’s. UID’s can be configured to be any length between 7 and 12 digits. xDUID UID’s are randomly generated and have the following characteristics:
- Contain random numbers – not sequential.
- Do not begin with a zero (0) or end with a zero (0).
- Do not contain a sequence of 3 or more repeating numbers.
- Use only numbers.
- The check digit is constructed using Modulus 11 calculation in accord with National Serials Data Program methods.
|