Build Instance of Drupal and Limesurvey!

Hi Summit !

I think your module has lots of potential!

Yes, I think so !

Are you willing to build an instance with drupal and limesurvey configured for use already?

It is not planned, it could interesting, it would be a drupal installation profile release. But I would have to release a new file on every new version of LimeSurvey or Drupal and the admin user would still have to configure the database connexion information for both softwares. He would not gain much time.

May be also input already the examples as in your demowebsite.

Yes it is a good idea ! I could add an exemple module (some module provide examples, as modal Frame API).
For your information, I did not created the survey demonstrating all questions : is already include into the LimeSurvey release, it is the 'limesurvey/docs/demosurveys/SAMPLE_SURVEY_191_EN_DE_FR.lss' file. I may include it within monthes, because it is not a priority task.

Hi - am looking forward to seeing more development here = a very interesting project in tandem with quexml and such = merci!

Hi alibama,

Yes, thanks to the qxml schema, this module increases the compatibility and import/export capacities of surveys (or any form) for a Drupal site.

Aloha thedut
Is there any way to use feeds to import quexml data? use feeds xpath parser?
http://drupal.org/project/feeds_xpathparser
i guess that would get the data ingested, however perhaps with rules one might be able to ingest the feed of xml and create cck fields from it? It's possible, then use features to redistribute the recipe

interesting..

There is no need to import datas with feeds : LimeSurvey already take care of importing datas from the LimeSurvey admin interface and it is doing it well.
The LimeSurvey synchronization module purpose is to make surveys available for a Drupal Site but not to import surveys single datas into Drupal as CCK (or fields) : because doing this would break drupal performance if there is too many fields (aproximatively more than 50 fields and there are a lot of surveys that need 50 questions or more).
As it is designed, the LimeSurvey synchronization module preserves Drupal performances, even for heavy survey : It have tested my module with a survey containing 700 questions and it works still very fast !

Actually, there is another module importing LimeSurvey surveys single datas into cck fields using feeds. This is the LimeSurvey Importer module. Unfortunatelly, it is only a sandbox, and it seems to be abandoned by its author, since there is no activity for monthes. This is an interesting approch but IMHO, the LimeSurvey Importer module could break Drupal performance for surveys with too many questions.

-------------------------
For information, some references about Too many fields and Drupal performance :
Too many fields crashes pages like /admin/config/people/accounts
How many CCK fields is too many?
Using 71 Fields breaks my view (Too many Joins)
Custom content with many fields (over fifty) and the manage display Ajax takes longer than a raw page load
And an interesting thread about fields and Drupal performance : Field Structure

LimeSurvey Importer project owner intends to continue developing but the owner had other issues to attend to. Said it may be a few months before that.