When using “software-as-a-service” offerings, a user often has a problem of matching records stored by the different services and determining if they refer to the same entity (person, account, order
When using “software-as-a-service” offerings, a user often has a problem of matching records stored by the different services and determining if they refer to the same entity (person, account, order, etc.) The ICPC is no exception. While each participant has a record in the central ICPC registration system, additional “outside” applications may be used to collect and process information for functionality not provided by the central system. Once an “outside” application is used, it becomes necessary to match the entries from both systems. Unfortunately, in spite of careful directions, sometimes it is not clear if records correspond to the same person. The primary sorts of mis-matches that occur are these: E-mail addresses do not match. This could be due to a misspelling, such as .eud.eud.eud instead of .edu.edu.edu, or different e-mail addresses that a participant used in the central ICPC system and the outside system. Exact names do not match. This could be due to a typing error, or varying use of legal names and nicknames. Your team is to write a program that will read lists of people from the ICPC system and an outside system and determine which records in each system do not match a record in the other system. Two entries are considered matched if either the e-mail addresses are an exact match or the last name and first name are an exact match
