Comment 1 for bug 731647

Preferably, there's also a check box for the admin to decide whether existing user details (name, password, login) are updated from the csv file or not. I.e.:

Scenario 1: Ignore duplicates in CSV file
- email <email address hidden> already exists and belongs to Student Test
- existing record is kept without any change
- new accounts are created
- warning is issued that <email address hidden> already existed and no change was made

Scenario 2: Update duplicates with CSV file information
- admin clicks the setting to update existing accounts with new information from the CSV file
- before admin continues he sees a pop-up message asking whether he is sure that he wants to proceed because if duplicates are detected, the information from the CSV file will overwrite them (username, name, ...)
- email <email address hidden> already exists and belongs to Student Test
- existing record shall be updated to reflect the correct name of the user as it appears in an external directory, e.g. Student Test-QA
- the CSV file <email address hidden> for Student Test-QA
- because the admin approved the setting to update duplicates, the <email address hidden> account is updated with the new information
- new accounts are created
- after the upload is complete, admin receives warning messages on the screen alerting him to which accounts have been updated
- admin can save these warning messages as txt file for future reference, e.g. if a user has a question why his login details changed.