mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #02935
[Bug 731647] Re: Ignore duplicates in CSV upload
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 test@xxxxxxxx already exists and belongs to Student Test
- existing record is kept without any change
- new accounts are created
- warning is issued that test@xxxxxxxx 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 test@xxxxxxxx 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 test@xxxxxxxx for Student Test-QA
- because the admin approved the setting to update duplicates, the test@xxxxxxxx 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.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/731647
Title:
Ignore duplicates in CSV upload
Status in Mahara ePortfolio:
Confirmed
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.
References