Le 23/09/2011 11:12, Marcel Minke (Limesurvey) a écrit :
Hi everybody,

I totally agree that we should add a check for unique question codes. Can somebody open a ticket for this?

I also see the long term consequences of redesigning the fieldmaps, but that's nothing I would like to touch soon. Better get the CI version stable first. So how about adding the uniqueness check at the current CI version without an update procedure so far? Since we are planning to name the next release "Limesurvey 2.0 alpha" the user should expect some major changes so it should not be too hard to argue "The new EM will rely on unique question codes so there is a check for it when creating new surveys. If you want to use EM for old, existing surveys, please check the uniqueness yourself (either manually or by a function which the user could call from the admin backend)".
I consider this the easier way which also takes care of the tough time line to release a first Limesurvey 2.0 version at mid October.

I feel the same about this Mazi.

Thibault



Just my 2 cents...

Have a nice weekend everybody,
Marcel

Am 23.09.2011 09:25, schrieb Carsten Schmitz:

Enforcing a unique question code across the survey should not be too hard.
But if we enforce it we have to make sure that all existing surveys don't have duplicate codes so there needs to be an upgrade procedure which takes care of that.
Especially in the case of active surveys this will be a great mess.

If we start doing changes like that we should go the whole nine yards and redesign the fieldnames completely (same great mess) but only once.




Am 23.09.2011 09:13, schrieb Thibault Le Meur:
Le 23/09/2011 09:07, Menno Dekker a écrit :
>From export (SPSS/R) perspective I always advice people to have unique question codes. The SGQA if is a pain for portability so I would love to see some kind of check for a unique question code. On activate would be enough and the easiest to do, but a check on question save would be much better. This unique code can then be used as ID in the javascript too. Makes porting custom js a lot easier.


I fully agree with you Menno.
Morover, in order to avoid a potential SGQA collision between "SGQ" and "SGQA" fieldnames, I strongly recommend to use question code beginning with a Letter (not a number).

I would propose a new global setting "$enforce_question_code_consistency = true" that would enforce these 2 points:
* a question code must be unique within the survey
* a question code begins with a char other than a number

My 2 cents,
Thibault


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2


_______________________________________________
limesurvey-developers mailing list
limesurvey-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/limesurvey-developers
    

------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ limesurvey-developers mailing list limesurvey-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/limesurvey-developers


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2


_______________________________________________
limesurvey-developers mailing list
limesurvey-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/limesurvey-developers