Ignore duplicates in CSV upload
Bug #731647 reported by
Kristina Hoeppner
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Invalid
|
Low
|
Unassigned |
Bug Description
When an institution wants to upload their users via a csv file, but some of their users already have a Mahara account, i.e. the email address already exists in Mahara, an error message is returned and no new user accounts are created.
Instead, only these duplicates should be ignored and all other accounts should be created. Thus, when a csv file is uploaded and existing accounts / email addresses are encountered, convert the error message into a warning that is printed to the screen and keep going with the account creation.
tags: | removed: bite-sized |
Changed in mahara: | |
milestone: | 1.4.0 → none |
tags: |
added: csvupload removed: csvimport |
Changed in mahara: | |
status: | In Progress → Fix Committed |
milestone: | none → 1.9.0 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.