Re: "gateway" surveys

Easiest is to keep it all in one survey. One suggestion here would be 
trying out the IMPORT tag and populate a LIST with elements from a 
database for course names/ids. However, keeping separate lists of 
passwords might be tricky this way.

You can accept values passed to a survey on the GET string through the use 
of perl snippets. You could use a CONSTANT somewhat like this (not tested)

<SURVEY ...>

   <CONSTANT NAME="userid" VALUE="{&
     print $argument->ArgByName("userid");
   &} />

</SURVEY>

Calling the survey page and adding ?action=display&userid=somebody to the 
GET string would then set the constant to "somebody".

   // Joel


On Thu, 3 Nov 2005, Todd Slater wrote:

> We'd like to deploy end-of-course surveys. I imagine a student going
> to a page and selecting a course. That would pass on three variables:
> the course id, the password file to use, and the type of course (questions
> and routing would depend on course type) and send them to the survey.
> They would then have to authenticate, checking against the specified
> password file.
>
> Does that sound logical? How can I pass variables from the gateway
> survey on the "real" survey? Or is it all one big survey?
>
> Recommendations appreciated!
>
> Best,
>
> Todd
> Skickat av Todd Slater <[email protected]>
> till survey-discussion
>
Skickat av Joel Palmius <[email protected]>
till survey-discussion