View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
11627Feature requestsOtherpublic2016-09-21 12:02
Reporterlemonbrain Assigned To 
PrioritynoneSeverityfeature 
Status newResolutionopen 
Summary11627: Import .csv to update participant data
DescriptionI'd like to be able to update participant data on a live survey via .csv import. This would primarily be to change existing records rather than add new. Say, to update `firstname` via a .csv import with two fields: `email` (the key) and `firstname`.

Thanks for considering the request.
Additional InformationAs mentioned in the forum 'Can I do this with LimeSurvey?' https://www.limesurvey.org/forum/can-i-do-this-with-limesurvey/106946-update-participants-data-on-live-survey#141366
TagsNo tags attached.
Bug heat4

Users monitoring this issue

User List There are no users monitoring this issue.

Activities

jelo

jelo

2016-09-20 23:30

partner   ~40866

The real issue with dataoperations like this is that LimeSurvey has no pause mode.
A pause mode which e.g let no new probands on the survey, but let the others finish their interviews.

The time gap between exporting and importing can cause change of data which is lost.

Currently there is only an importmode under "Create Entries".
Since there is an Export Button, I would favor an Import Button for the other import modes. Update and Replace. Replace overwrites everything with the CSV content. Update will only replace nonempty cells.
That way you can update data without overwriting everything else.
lemonbrain

lemonbrain

2016-09-21 12:02

reporter   ~40879

Thanks for the comment. The use-case that brought me here (my first survey): a mistake with the original Create->Import->.csv - where only the first 50 records had a valid `firstname` (the `lastname` field wasn't used) - the rest were populated with "O". So, in this case, I'd want the import/update to overwrite a non-empty field.

(Luckily, or by great design, the bounces suggest that the single character names were not used in the To header - they went as "To: invitee51@example.com" rather than "To: O <invitee51@example.com>").

Issue History

Date Modified Username Field Change
2016-09-06 14:42 lemonbrain New Issue
2016-09-20 23:30 jelo Note Added: 40866
2016-09-21 12:02 lemonbrain Note Added: 40879