View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
05005Bug reportsImport/Exportpublic2012-01-21 12:14
ReporterMazi Assigned Tomdekker  
PrioritynormalSeveritypartial_block 
Status closedResolutionfixed 
Product Version1.91RC4 
Target Version1.91RC5 
Summary05005: Exporting timings isn't possible
Description

The new timings feature at 1.91 is really great for experiments but the big problem is that exporting these timing - together with the answer data - currently isn't possible/enabled at 1.91 which makes this feature more or less useless.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)191
I will donate to the project if issue is resolvedNo
BrowserFirefox 3.6
Database type & versionMySQL 5
Server OS (if known)Win 7
Webserver software & version (if known)Apache 2.2
PHP Version5.3.1

Relationships

related to 04975 closedDenisChenu Question Code for Array (Texts) is exported incorrectly. 

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2011-03-08 17:07

administrator   ~14341

Menno, when you rewrote the timings to use their own function you happened to remove these fields from the export, too.
Can you have a look at it - I think it should not be too hard to let them show up there again.

mdekker

mdekker

2011-03-09 09:30

reporter   ~14354

Not really... the fields come from a different table so they where never really there. Shouldn't be to hard to implement as we just need another join and a merge of two arrays with fieldmap, but i think we need to think about it a little more first.

In 'normal' export (excel/word/etc) I would say an option 'include/exclude' ALL timings would be enough, not sure what to do for export to r/spss, maybe the same?

Pretty busy at the moment, doing a photography course when the dev meetings are and shooting and printing in between but i can give it a look when we agree on how to implement.

Mazi

Mazi

2011-03-09 17:11

updater   ~14357

for the normal export it would be nice to have a selectable list of timing, similar to the question and token data list. Often when performing experiments using timings you are only interested in the time for answering some certain questions so I think having a list of available timer data would be best.
As for the SPSS/R export I'm no expert, if the same is possible we should make it that way to similar to the current export of token data for example.

In general I think this should be solved before releasing 1.91 stable because timings are a great new feature.

c_schmitz

c_schmitz

2011-03-09 18:55

administrator   ~14361

I agree to Mazi. Menno, would be awesome if you can take a shot at it.

mdekker

mdekker

2011-03-10 09:04

reporter   ~14369

I think spss / r export should be integrated in the regular export so funcionality is the same. For now I will go for the quick fix... auto-include all in spss/r and adding the selectable fields to the other exports.

Thinking a bit more in the future it would be cool if you could save your export settings as a preset... so when you select only half the timings (or any other field) you don't have to make the selection over and over.

mdekker

mdekker

2011-03-17 21:53

reporter   ~14458

Gave it a try but current export results code is too crappy to fix. Can take a look at the dev branch, but as the code is completely different in both it would take too much (wasted) effort to fix the current branch

Mazi

Mazi

2011-03-18 12:43

updater   ~14462

This might be a stupid question but don't we just need a simple JOIN to present result AND token data AND timings?
If we are not able to add this feature at 1.91 we should think about removing the timings as well because they are pretty much useless if you can't export the data.

Is there any way I can help you adding this to 1.91?

mdekker

mdekker

2011-03-21 09:30

reporter   ~14496

I was hoping a simple join on the select and merge of the two fieldmaps would do the trick but in reality the select is done twice and there is also some overhead in selecting question titles etc.

If the export was making better use of the fieldmap function it would have been easier I think. I am maybe 60% in the process of making it work but the fix would only be for the 1.91 branch and could have some glitches that have been fixed in the 1.92 (dev) branch already. It just feels like a waste of time to redesign for 1.91 while 1.92 has a redesigned export already. Maybe we can port export-functionality from 1.92 to 1.91 but I don't know about dependencies.

Mazi

Mazi

2011-03-22 16:32

updater   ~14512

In general I agree, Menno.

Problem is that 1.92 will probably be released after this years GSoC so this will take about half a year. Offering the great new timing feature without a working export for such a long time will look strange to our users.

I can't estimate the total effort of adding this export feature to 1.91 but I think we should give it a try. Please let me know if I can help you anyhow.

mdekker

mdekker

2011-03-27 18:37

reporter   ~14561

Ok, I'm done with the 1.91 i think, but not for spss / r
committed today, please give it a try

Patch can not be ported to dev version as export is rewritten there so will leave the bug open

Mazi

Mazi

2011-03-27 23:04

updater   ~14567

I tested the Excel export using a simple test survey and it works like a charm.

Great work, Menno!

mdekker

mdekker

2011-03-28 12:24

reporter   ~14584

Last edited: 2011-03-28 12:27

There have been changes to the way the question / abbreviated question / question code is handled. If you can confirm all still works that would be great.(I did some small tests myself so I don't expect anything but just to make sure)

Will see when I have time to port the changes to the dev branch

Maybe checking this one would be good too:
http://bugs.limesurvey.org/view.php?id=4975

Mazi

Mazi

2011-04-04 20:04

updater   ~14665

Assigning this back to you...

Should we wait for the porting to codeigniter before working on this for other exports?

mdekker

mdekker

2011-04-05 14:02

reporter   ~14676

Yeah, for 1.91 I don't want to move the fix to other areas (R/SPSS) but when it is ported to the 1.92 version from there it should be included in all exports. And I would strongly support having SPSS/R integrated in the normal export screen. Much easier for code maintainability.

So for 1.91 i would call it closed and a todo for 1.92 (did not port the 1.91 changes yet)

c_schmitz

c_schmitz

2011-09-11 09:35

administrator   ~16253

Last edited: 2011-09-11 09:35

the CI port is done now. Can you have a look at this issue for 1.92 please?

Mazi

Mazi

2011-09-11 10:27

updater   ~16261

I tried to import a test survey which uses timings but it failed. Error was reported here: http://bugs.limesurvey.org/view.php?id=5458

Will check later when the problem above was solved.

mdekker

mdekker

2011-09-12 10:32

reporter   ~16268

Will have a look when i have time... it's on my list

Mazi

Mazi

2011-11-04 15:11

updater   ~16597

Some forum feedback: Exporting timings to SPSS as well isn't supported yet. This makes the statistic nerds a little sad.
Maybe worth a Google Code in idea?

mdekker

mdekker

2011-11-07 09:55

reporter   ~16602

No more new features in 1.91 and not happy to jump in CI with the licence troubles so I think we have to leave it the way it is.

With the new export system that is in the ci port it should be easier to integrate in all exports but I will only do that when we know how it is going to work out with the framework. I think it is too essential to make it a GCI task, it is best if I or some other core member does it so at least someone in the team has knowledge about how it was done and why.

Quickfix for the spss people: export a csv with only the timings and token and/or response ID and import that in SPSS and link both files with SPSS using the unique token / response ID.

Issue History

Date Modified Username Field Change
2011-03-08 16:53 Mazi New Issue
2011-03-08 16:53 Mazi Status new => assigned
2011-03-08 16:53 Mazi Assigned To => mdekker
2011-03-08 17:07 c_schmitz Note Added: 14341
2011-03-09 09:30 mdekker Note Added: 14354
2011-03-09 17:11 Mazi Note Added: 14357
2011-03-09 18:55 c_schmitz Note Added: 14361
2011-03-10 09:04 mdekker Note Added: 14369
2011-03-17 21:53 mdekker Note Added: 14458
2011-03-18 12:43 Mazi Note Added: 14462
2011-03-21 09:30 mdekker Note Added: 14496
2011-03-22 16:32 Mazi Note Added: 14512
2011-03-27 18:37 mdekker Note Added: 14561
2011-03-27 18:37 mdekker Assigned To mdekker => Mazi
2011-03-27 18:37 mdekker Status assigned => feedback
2011-03-27 23:04 Mazi Note Added: 14567
2011-03-27 23:04 Mazi Status feedback => assigned
2011-03-28 12:24 mdekker Note Added: 14584
2011-03-28 12:27 mdekker Note Edited: 14584
2011-03-28 12:27 mdekker Relationship added related to 04975
2011-04-04 20:04 Mazi Note Added: 14665
2011-04-04 20:04 Mazi Assigned To Mazi => mdekker
2011-04-04 20:04 Mazi Status assigned => confirmed
2011-04-05 14:02 mdekker Note Added: 14676
2011-06-16 14:38 c_schmitz Category Import/Export => RemoteControl
2011-09-11 09:35 c_schmitz Note Added: 16253
2011-09-11 09:35 c_schmitz Note Edited: 16253
2011-09-11 09:35 c_schmitz Status confirmed => feedback
2011-09-11 10:26 Mazi Relationship added related to 05458
2011-09-11 10:27 Mazi Note Added: 16261
2011-09-11 10:27 Mazi Status feedback => assigned
2011-09-11 10:55 c_schmitz Relationship deleted related to 05458
2011-09-12 10:32 mdekker Note Added: 16268
2011-10-20 18:29 c_schmitz Category RemoteControl => (No Category)
2011-11-04 15:11 Mazi Note Added: 16597
2011-11-07 09:55 mdekker Note Added: 16602
2012-01-21 12:13 c_schmitz Status assigned => closed
2012-01-21 12:14 c_schmitz Category (No Category) => Import/Export
2012-01-21 12:14 c_schmitz Resolution open => fixed