[limesurvey-developers] Introduction

[Patrick Clochesy]

Hi folks,

I would like to quickly introduce myself... my name is Patrick and I am the
general manager of an market research/incentivized marketing company. We
recently began using LimeSurvey for our internal user experience surveys to
gather feedback on our operation, however we hope to also expand this to
include generating our own supply directly to interested firms.

I am not sure at this point how much we will be contributing, however in
integrating LimeSurvey via the API we have found a few things "missing" for
our uses, as well as a tiny bug fix in the API, and would like to
contribute these fixes when and where we believe they would be useful to
others.

Nothing major, but three things to immediately contribute:

1. get_token function for looking up a token ID from a token. This is
important for us and others to query participants in the future, as
external systems do not use LimeSurvey's token IDs but their own token.

2. Simple bugfix to list_participants. This routine is currently broken.

3. If people believe it is a useful addition, we have also added completion
status filtering to list_participants so you can get only completed tokens.
This is an option in the CSV token export, so I think it would make sense
to have it here.

Hopefully in the future, we will be using LimeSurvey more and more and be
able to contribute more things. I'm sure in the near future we will find
more API additions to make.

-Patrick

[Marcel Minke]

Hi Patrick,

every help extending the API is welcome and we are also happy about each
bug fix.

@1: Please send us a pull request via Github based on the latest 2.05
Limesurvey code. We can then check your code and add the new feature
after review.

@2: Please file a bug report at http://bugs.limesurvey.org (this
requires setting up an account at www.limesurvey.org first). We are
happy if you can attach a fix right away. If not, we will look into the
problem.

@3: That definitely makes sense. Again, feel free to send us a pull
request and contact us if you have any questions or need help
implementing this.

Thanks for getting in touch with us!

Best regards,
Marcel
--
Dr. Marcel Minke

Head Consultant at Limesurvey-Consulting.com
<http://www.limesurvey-consulting.com>
Owner of the Limesurvey Template Shop <http://www.limesurvey-templates.com>
Head of Support at Limesurvey <http://www.limesurvey.org>

Feel free to add me at LinkedIn <http://de.linkedin.com/in/marcelminke>
| Xing <https://www.xing.com/profile/DrMarcel_Minke> | Google+
<https://plus.google.com/u/0/102812116525985282322/about>

Post by Patrick Clochesy
Hi folks,
I would like to quickly introduce myself... my name is Patrick and I
am the general manager of an market research/incentivized marketing
company. We recently began using LimeSurvey for our internal user
experience surveys to gather feedback on our operation, however we
hope to also expand this to include generating our own supply directly
to interested firms.
I am not sure at this point how much we will be contributing, however
in integrating LimeSurvey via the API we have found a few things
"missing" for our uses, as well as a tiny bug fix in the API, and
would like to contribute these fixes when and where we believe they
would be useful to others.
1. get_token function for looking up a token ID from a token. This is
important for us and others to query participants in the future, as
external systems do not use LimeSurvey's token IDs but their own token.
2. Simple bugfix to list_participants. This routine is currently broken.
3. If people believe it is a useful addition, we have also added
completion status filtering to list_participants so you can get only
completed tokens. This is an option in the CSV token export, so I
think it would make sense to have it here.
Hopefully in the future, we will be using LimeSurvey more and more and
be able to contribute more things. I'm sure in the near future we will
find more API additions to make.
-Patrick
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
limesurvey-developers mailing list
https://lists.sourceforge.net/lists/listinfo/limesurvey-developers

[Denis Chenu]

Hi Patrick,

Great to have some fix for remote control, not using it a lot for me :).

Post by Patrick Clochesy
1. get_token function for looking up a token ID from a token. This is
important for us and others to query participants in the future, as
external systems do not use LimeSurvey's token IDs but their own token.

This is not included actually ? Really, this is needed !!!

Post by Patrick Clochesy
2. Simple bugfix to list_participants. This routine is currently broken.

Bug fix in pull request i think ?

Post by Patrick Clochesy
3. If people believe it is a useful addition, we have also added
completion status filtering to list_participants so you can get only
completed tokens. This is an option in the CSV token export, so I
think it would make sense to have it here.

Seems great too !

Thank you :)