Return to Navigation

Researching Duplicate Records

In the search dialog page of the External Test Score Suspense component, enter the test ID that you want to review, Complete in the Edit Process Option field, and Perform in the Search/Match Process Option field. Then click the Search button. The search process finds only those suspense records that went through the search/match/post process but did not get posted. The reason the search/match/post process did not post the records is because it found a possible duplicate record in the database. Upon entering the component, the Test Score Suspense Data page displays the search/match level involved in the possible match and the number of individuals in the database that match the criteria in the Search/Match Results group box.

For example, let's suppose that the Order Number field in the Search/Match Results group box displayed 40, and that three matches appear. At PSUNV, Order Number of 40 means that the process is checking for a matching name and gender. Therefore, you know that there are three people in your database with the same name and gender as the person in the suspense record. Use the Search/Match component to look up the name and gender that match the suspense record, and compare the other information (such as address) to determine whether the person in the database is the same as the person in the suspense record. Select Student Recruiting, External Test Score Processing, Search/Match or Student Admissions, External Test Score Processing, Search/Match to access this page.

If the person from the suspense record is not the same as a person in your database, set the Search field to Complete and the Post field to New ID Add.

If the person from the suspense record is the same as a person in your database, set the Search field to Complete and the Post field to Update Existing ID. Then go to the Personal Information page and enter the ID that you want to update. Note, however, that the search/match/post process only updates test score and candidate data information. The process does not update bio/demo data because some bio/demo data may have already been verified.