View Issue Details

IDProjectCategoryView StatusLast Update
14944Development [All Projects] Import/Exportpublic2019-08-06 09:17
ReporterDenisChenu Assigned ToDenisChenu  
PrioritynoneSeverityminor 
Status assignedResolutionopen 
Product Version3.x 
Target VersionFixed in Version 
Summary14944: Adding id and related_id in TSV export make it complicated to edit
Description

TSV is made for Export : update manually, import.
Have id and related_id make it complex to editing
Remove this 2 columns : still working

What is the usage of this 2 columns ?

Additional Information

In 2.X : import/export as roughly tested and working with multilingual, survey.

User just have to put subquestion after question : it's clear enough

@dominikvitt : i think you add this id , related_id : for user it make it complex to use TSV. Did you remind the reason ? Then related mantis ?
Currenlty : using TSV for quick edit of survey seems broken (for example for translation).

I use it for :

  1. Translation
  2. Make 4 subgroups with same questions in a group

Removing this 2 columns : TSV can be imported.
With this 2 columns : i must set random number …

TagsNo tags attached.

Relationships

related to 06502 closedmfaber Development  Unable to import exported multi lang survey 
related to 14403 feedbackLouisGac Feature requests Survey Export sorting by question_order 

Activities

DenisChenu

DenisChenu

2019-05-27 19:47

developer   ~52123

I can find and fix : but speediest if i know usage of this 2 columns :)

dominikvitt

dominikvitt

2019-05-28 13:41

developer   ~52128

id and related id columns are required for export and import of quotas.
Quotas are too complex to reconstruct without those columns.
See here:
https://github.com/LimeSurvey/LimeSurvey/blob/206c3aa12673d54f204d363082f1c86536fb52fd/application/helpers/export_helper.php#L2596

All other objects aren't required to have those columns set, it would work without them.

DenisChenu

DenisChenu

2019-05-28 14:04

developer   ~52129

Last edited: 2019-05-28 14:05

View 2 revisions

OK, for quota only.

Because quota table use qid and not question/answer code in export (and import).

Terribly boring since TSV is a really good tool but broken here …

dominikvitt

dominikvitt

2019-05-28 14:06

developer   ~52130

Three tables need to be connected, so it's not so easy.

DenisChenu

DenisChenu

2019-05-28 14:14

developer   ~52131

I check it when i found times :)

DenisChenu

DenisChenu

2019-06-25 14:56

developer   ~52543

@dominikvitt : what do you think if we don't add this 2 columns if there are no quota ?

DenisChenu

DenisChenu

2019-07-12 14:48

developer   ~52863

@dominikvitt id and related_id are not used for Question and answers ? Right ?

Then i think we can use another column for quota is and related id.

For Group we use G1,G2 etc … Why not QTA1, QTA2 etc …

I have an issue currently with quota , i check if it was a plugin before report …

dominikvitt

dominikvitt

2019-07-12 14:52

developer   ~52864

@DenisChenu:
Those columns are used only for Quotas.
Number of columns in TSV export should always be the same or it would be very confusing.

DenisChenu

DenisChenu

2019-07-12 15:50

developer   ~52866

I see you remove the number in export for Group : we add it for import group with multiple language : there are an old issue somewhere …

For id and related id, clearly

  1. Don't put it if not used , needed : just set it to "" for qid and gis (and assessmeents).
  2. Since ii's not a major columns : add it after other column (maybe just after relevance ) : this one is easy.
DenisChenu

DenisChenu

2019-07-12 15:51

developer   ~52867

If it's used only for quota : why not name it quota_id and related_quota_id ?

Unsure on this point : if we need it another id elsewhere …

pnickel

pnickel

2019-08-05 00:21

reporter   ~53085

After extensive testing, I discovered that any "text" column data that includes a non-standard ASCII character (as get copied out of Word and include things like en-dash and em-dash and the slanted versions of the single and double quotation marks) creates a crash in the import with no error message. It seems that you can copy formated Word text into the Limesurvey survey creator, but the importer cannot handle such text.

I've now cleaned up my Excel pseudo-database of survey questions and can start generating new forms.

DenisChenu

DenisChenu

2019-08-06 09:17

developer   ~53121

@pnickel : totally unrelated to this issue … please report another bug …

Issue History

Date Modified Username Field Change
2019-05-27 19:46 DenisChenu New Issue
2019-05-27 19:46 DenisChenu Status new => assigned
2019-05-27 19:46 DenisChenu Assigned To => dominikvitt
2019-05-27 19:46 DenisChenu Additional Information Updated View Revisions
2019-05-27 19:47 DenisChenu Note Added: 52123
2019-05-28 11:08 DenisChenu Relationship added related to 14403
2019-05-28 13:41 dominikvitt Note Added: 52128
2019-05-28 14:04 DenisChenu Note Added: 52129
2019-05-28 14:05 DenisChenu Note Edited: 52129 View Revisions
2019-05-28 14:06 dominikvitt Note Added: 52130
2019-05-28 14:14 DenisChenu Assigned To dominikvitt => DenisChenu
2019-05-28 14:14 DenisChenu Note Added: 52131
2019-06-25 14:56 DenisChenu Note Added: 52543
2019-07-12 14:48 DenisChenu Note Added: 52863
2019-07-12 14:52 dominikvitt Note Added: 52864
2019-07-12 15:50 DenisChenu Note Added: 52866
2019-07-12 15:51 DenisChenu Note Added: 52867
2019-07-13 18:33 DenisChenu Relationship added related to 06502
2019-08-05 00:21 pnickel Note Added: 53085
2019-08-06 09:17 DenisChenu Note Added: 53121