Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Survey attributes (as opposed to attributes attached to respondents)

  • Leithy
  • Leithy's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
3 years 5 months ago #223519 by Leithy
Please help us help you and fill where relevant:
Your LimeSurvey version: [see right hand bottom of your LimeSurvey admin screen] 3.x and 5.x
Own server or LimeSurvey hosting: Own
Theme: Vanilla extended

==================

Hiya - has anyone attempted or found a way to implement survey level attributes or custom fields (as opposed to the current custom attributes for users)?

My use case for this is that I have a single survey that serves different questions and reports based on hidden variables. However these are based on attributes common to a particular instance of the survey as a whole, rather than a particular user. In my current set-up therefore, there's a lot of redundant data stored- ie every survey response contains the values of these hidden questions even though they aren't used for the data analysis.

The solution would probably look like a plugin that allows setting for {surveyfield:attributex}, probably in the UI for each survey, and could be accessed via expression manager in the usual places (questions, email templates, text areas).

Before I go ahead and look at implementing this, has anyone done anything on this they'd be happy to share?


 
The topic has been locked.
More
3 years 5 months ago #223525 by jelo
If I get your idea right, you ask for a way to define surveywide variables without having to create a hidden question inside the survey, right?

Your idea could be mixed with the panel integration feature.

Variablename
Variabledescription
Value external (url parameter name)
Value internal / Defaultvalue
Saved in results (yes/no).

As the "workaround" with the hidden questions works, I remember no feature requests or plugins around static variables.

I recommend to open one and start collecting a few ideas and screenshots from other tools.

Another missing part are static and dynamic lists, which can be applied in different ways.
bugs.limesurvey.org/view.php?id=11688

The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The following user(s) said Thank You: Leithy
The topic has been locked.
  • Leithy
  • Leithy's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
3 years 5 months ago - 3 years 5 months ago #223534 by Leithy
Hi Jelo, yes, the idea is exactly as you describe, will open a feature request.

While I'm here, are the standard existing custom attributes considered done? I note there's an open feature/bug request: bugs.limesurvey.org/view.php?id=11204 as currently the various types only work in the CPDB interface, not the survey custom attributes page. I think there's also a legacy page (by Marcel?) that talks about adding radio button and checkbox versions, but I can't find it just now.

Edit: Found the link -  www.limesurvey.org/manual/Central_partic...r_panel)_Development , section Attribute control.

 
Last edit: 3 years 5 months ago by Leithy.
The topic has been locked.
  • Leithy
  • Leithy's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
3 years 5 months ago #223823 by Leithy
The following user(s) said Thank You: jelo
The topic has been locked.
More
3 years 5 months ago #223835 by jelo
I never used the CPDB part. Consider your request as a more sophisticated one. No feature is considered done, but the feature set of LimeSurvey is unbalanced. I don't see much traction around CPDB. The main force to keep ideas in play are bug and feature tickets. They stay long after forum and wiki entries are gone. If you really need a feature, you have to code it on your own or hire a developer.

The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The topic has been locked.
  • Leithy
  • Leithy's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
3 years 5 months ago #223847 by Leithy
I mainly use the CDPB part for two things:
* Hold the test accounts that I import into every survey - this is really handy!
* Create custom attributes that I import into every survey -

Agree, these are far off the likely intended use of having a bank of users you invite to different surveys. I guess the main users of such features would be professional survey companies? Guess they're not the majority of the userbase!
The topic has been locked.
Moderators: tpartnerholch

Lime-years ahead

Online-surveys for every purse and purpose