https://manual.limesurvey.org/api.php?action=feedcontributions&user=Ddrmoscow&feedformat=atomLimeSurvey Manual - User contributions [en]2024-03-29T04:51:29ZUser contributionsMediaWiki 1.35.10https://manual.limesurvey.org/index.php?title=Survey_quotas/ru&diff=63320Survey quotas/ru2014-09-29T17:30:31Z<p>Ddrmoscow: Created page with "__ОГЛАВЛЕНИЕ__"</p>
<hr />
<div><languages /><br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=General explanation=<br />
<br />
A quota is used to set a limit on responses from defined groups of people on an active survey. Some common attributes used in defining quotas are things like gender, age, race, province/state. A quota can be added, edited or deleted by opening the quota window. Select the quota [[File:button-quota.png]] button on the '''Survey''' administration toolbar.<br />
<br />
An english sample survey demonstrating the use of quotas at LimeSurvey is available for download. You can import this survey at your LimeSurvey system for testing ("import" tab at survey creation page): [[Media:LimeSurvey_sample_survey_Quotas.lss|LimeSurvey_sample_survey_Quotas.lss]]<br />
<br />
=Quotas are not automatically exclusive=<br />
<br />
Quotas are not comprehensive and automatically exclusive. To explain, let's imagine a survey that has a simple "Yes or No" question at the beginning.<br />
<br />
You set a quota on this survey that contains a restriction of 20 users who have answered "Yes" to this question. The quota will be checked everytime somebody answers "Yes" to that question, and completes the whole survey. If the person answers the quota question but doesn't complete the survey, that answer-id is not going to be counted towards the quota. Once 20 people have done so, the quota action will be triggered by anyone else choosing "Yes".<br />
<br />
However, if "No" is chosen, the quota system is never triggered. The survey will never restrict anyone who chooses no.<br />
<br />
To set a limit on the number of "No" responses, you need to add an additional quota, restricting the number of participants who choose "No".<br />
<br />
=Supported question types=<br />
<br />
Currently only the following question types can have a quota defined for it:<br />
*Gender<br />
*Multiple Choice<br />
*Array - 5 Point Choice<br />
*Array - 10 Point Choice<br />
*Language Switch<br />
*Yes/No<br />
*List (Radio)<br />
*List (Dropdown)<br />
*List with comments<br />
<br />
=Example of a quota=<br />
<br />
You might have to conduct a survey where you want to limit it to 25 male and 30 female respondents. You could then define a quota with a limit of 25 for the answer "Male" from your gender question in the survey. Another quota for the answer "Female" with a limit of 30 could be added as well. This will give you a maximum of 25 males who will be able to complete the survey, and a maximum of 30 females who can complete the survey.<br />
<br />
A survey participant has to match all answers under the quota for it to apply to that response.<br />
<br />
=Adding a new Quota=<br />
<br />
Adding a new quota is really adding a framework for set of quota conditions. For a fully working quota you must firstly "Add a quota", and then "Add Answers" to that quota (see next section).<br />
<br />
When adding a quota, you will be asked for a "Quota Name", the "Quota Limit", and a "Quota Action".<br />
<br />
From version 1.85RC you will also have the option of setting your own unique quota "Quota Message", "url" and "URL Description" for each language used in your survey. You can also set "Autoload URL" so that the survey redirects users to the quota URL when the quota action is triggered.<br />
<br />
All new quotas are assigned to the Survey you were viewing when you clicked "Set Survey Quotas".<br />
*'''Quota Name:''' This is a name to reference the quota by, generally it should describe the quota it will represent.<br />
*'''Quota Limit:''' This is maximum number of completed surveys to allow for the quota. This sets a limit that will be check when quota selected questions are answered during the survey.<br />
*'''Quota Action:''' This is an action to perform when a participant is filling out a survey and lands up being part of a quota that has become full.<br />
**'''Terminate Survey:''' This immediately terminates the survey, and closes the interview.<br />
**'''Terminate Survey With Warning:''' This warns the participant and allows them to go back<br />
*'''Autoload URL:''' This tells LimeSurvey to automatically redirect the participant to the URL when the quota action occurs. (Only In Version 1.85RC)<br />
*'''Quota Message:''' The text displayed to your survey participant if the quota action is triggered (ie: the quota is full). (Only In Version 1.85RC)<br />
*'''URL:''' The URL displayed to survey participants after the quota message, or the URL participants are automatically redirected to if 'Autoload URL' is turned on. You can use [[URL fields]] in this section. (Only in Version 1.85RC)<br />
*'''URL Description:''' The text displayed for the URL. (Only in Version 1.85RC)<br />
<br />
Once a quota is added, you will be able to add answers under the quota.<br />
<br />
=Adding an answer=<br />
*'''Select Question:'''<br />
<br />
+When adding a answer under the quota, you will be shown a list of all available quota questions which are in your survey. If a question does not show up on the list, then its not yet supported with quotas. After you have chosen the question you want, press "Next" to move on to answer selection.<br />
*'''Select Answer:'''<br />
<br />
+Once selecting your question, you will be show a list of answers under that question. Here you will select an answer you would like to add to you quota, then press "Next".<br />
<br />
=Adding multiple quotas for the same question & subquestion=<br />
<br />
Adding multiple quotas for the same question is surely possible - but know that quotas are checked with a logical 'AND' operator - so to meet the quota the user has to answer both subquestion in that question like in your quota.<br />
<br />
This means also that multiple quotas for the same '''subquestion''' or the same single choice question can never come true.<br />
<br />
=Quota and response data=<br />
<br />
All data is saved when the participant clicks the "Next" button. Even if the quota is full, the data submitted until the survey is terminated will be recorded. Nevertheless, such id is marked as "No Completed".<br />
<br />
=Quota and tokens=<br />
<br />
When tokens are used in a survey and the user is screened out due to a quota, then the according token entry is marked with the letter "Q" in the Completed column. That way the token is invalidated and the survey participant can't re-start the survey.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_quotas/1/ru&diff=63319Translations:Survey quotas/1/ru2014-09-29T17:30:28Z<p>Ddrmoscow: Created page with "__ОГЛАВЛЕНИЕ__"</p>
<hr />
<div>__ОГЛАВЛЕНИЕ__</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/Page_display_title/ru&diff=63318Translations:QS:Location mapheight/Page display title/ru2014-09-29T17:28:25Z<p>Ddrmoscow: Created page with "QS:Location mapheight"</p>
<hr />
<div>QS:Location mapheight</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/371/ru&diff=63317Translations:QS:Location mapheight/371/ru2014-09-29T17:26:41Z<p>Ddrmoscow: Created page with "Category:Question SettingsCategory:Advanced Question Settings"</p>
<hr />
<div>[[Category:Question Settings]][[Category:Advanced Question Settings]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/370/ru&diff=63316Translations:QS:Location mapheight/370/ru2014-09-29T17:26:35Z<p>Ddrmoscow: Created page with "</onlyinclude>"</p>
<hr />
<div></onlyinclude></div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=QS:Location_mapheight/ru&diff=63315QS:Location mapheight/ru2014-09-29T17:26:29Z<p>Ddrmoscow: Created page with "высота карты в пикселях (по умолчанию: 300px)"</p>
<hr />
<div><languages /><br />
<onlyinclude><br />
<br />
===Высота карты (location_mapheight)===<br />
<br />
высота карты в пикселях (по умолчанию: 300px)<br />
<br />
</onlyinclude><br />
<br />
[[Category:Question Settings]][[Category:Advanced Question Settings]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/369/ru&diff=63314Translations:QS:Location mapheight/369/ru2014-09-29T17:26:29Z<p>Ddrmoscow: Created page with "высота карты в пикселях (по умолчанию: 300px)"</p>
<hr />
<div>высота карты в пикселях (по умолчанию: 300px)</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=QS:Location_mapheight/ru&diff=63313QS:Location mapheight/ru2014-09-29T17:25:56Z<p>Ddrmoscow: Created page with "===Высота карты (location_mapheight)==="</p>
<hr />
<div><languages /><br />
<onlyinclude><br />
<br />
===Высота карты (location_mapheight)===<br />
<br />
height of the map in pixels (default: 300px)<br />
<br />
</onlyinclude><br />
<br />
[[Category:Question Settings]][[Category:Advanced Question Settings]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/368/ru&diff=63312Translations:QS:Location mapheight/368/ru2014-09-29T17:25:56Z<p>Ddrmoscow: Created page with "===Высота карты (location_mapheight)==="</p>
<hr />
<div>===Высота карты (location_mapheight)===</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=QS:Location_mapheight/ru&diff=63311QS:Location mapheight/ru2014-09-29T17:25:35Z<p>Ddrmoscow: Created page with "<languages /> <onlyinclude>"</p>
<hr />
<div><languages /><br />
<onlyinclude><br />
<br />
===Map height (location_mapheight)===<br />
<br />
height of the map in pixels (default: 300px)<br />
<br />
</onlyinclude><br />
<br />
[[Category:Question Settings]][[Category:Advanced Question Settings]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:QS:Location_mapheight/1/ru&diff=63310Translations:QS:Location mapheight/1/ru2014-09-29T17:25:35Z<p>Ddrmoscow: Created page with "<languages /> <onlyinclude>"</p>
<hr />
<div><languages /><br />
<onlyinclude></div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Installation_-_LimeSurvey_CE/ru&diff=63309Installation - LimeSurvey CE/ru2014-09-29T17:23:32Z<p>Ddrmoscow: Created page with "=Общее="</p>
<hr />
<div><languages /><br />
<br />
<div class="simplebox"> Note: These installation instructions are for version 2.0 or later. Older instructions for 1.92 can be found [[Installation Version 1.92 or older|here]] </div><br />
<br />
=Общее=<br />
<br />
The LimeSurvey project offers two ways of installating LimeSurvey:<br />
*On your webserver:<br />In that case just follow the instructions on this page starting with step 1.<br />
<br />
*On your local Windows PC:<br />You usually only want to install LimeSurvey on your local PC if you want to create surveys locally (mainly for speed or test reasons) and upload them later to your live LimeSurvey installation on a web server. For this we have prepared a special package for LimeSurvey which includes the web server, the database and the LimeSurvey application and [[Installation of the LimeSurvey XAMPP package|instructions how to install it]].<br />
<br />
=Make sure you can use LimeSurvey on your website=<br />
<br />
Make sure your server meets the following additional requirements. Most of these requirements will also be checked during the installation.<br />
<br />
Required:<br />
* Minimum 80 MB disk space<br />
* MySQL 4.1.0 or later '''OR''' Microsoft SQL Server 2005 or later '''OR''' Postgres 8.1 or later<br />
* '''PHP 5.3 or later''' with the following modules/libraries enabled:<br />
** mbstring (Multibyte String Functions) extension library (see also [[Installation FAQ#What is this mbstring (Multibyte String Functions) library?|Installation FAQ]])<br />
** PDO database driver for MySQL (pdo_mysql or pdo_mysqli) or Postgres (pdo_pgsql) or MSSQL ([http://php.net/manual/en/ref.pdo-sqlsrv.php pdo_sqlsrv] for Windows and [http://www.php.net/manual/en/ref.pdo-dblib.php pdo_dblib] for Linux)<br />
** Also we assume in general that all PHP default libraries are enabled (like hash, session, etc.).<br />
<br />
<div class="simplebox"> Please note that LimeSurvey 2.x uses different database drivers than 1.x . If you get a message not No DBO driver was found during the installation you will have to contact your webspace provider and ask them to activate one of the aforementioned database driver libraries. </div><br />
<br />
<br />
Optional PHP Extensions:<br />
* '''GD-Library''' '''with FreeType support''' installed is needed for captchas or nice charts in statistics - see [http://de3.php.net/manual/en/image.setup.php PHP GD-Library Extension documentation]<br />
* '''IMAP''' (pretty standard) is needed for the [[Email bounce tracking system]] - see [http://www.php.net/manual/en/imap.setup.php PHP IMAP Extension documentation]<br />
* '''LDAP''' installed is needed to import tokens using LDAP - see [http://de.php.net/manual/en/ldap.installation.php PHP LDAP Documentation]<br />
* '''Zip''' (pretty standard) for template upload and import resources Zip archives - see [http://www.php.net/manual/en/zip.setup.php PHP Zip Extension documentation]<br />
* '''Zlib''' (pretty standard) is needed for the [[ComfortUpdate]] - see [http://www.php.net/manual/en/zlib.setup.php PHP Zlib Extension documentation]<br />
<br />
In most cases your webspace provider or system administrator will be able to help you out on these optional components.<br />
<br />
If you want to try LimeSurvey on your local machine we recommend [http://www.apachefriends.org/en/xampp.html XAMPP] which is an easy to install software package containing a complete web server with Apache, MySQL, PHP and Perl. LimeSurvey will run on XAMPP with no configuration needed.<br />
<br />
If you want to run Microsoft's IIS server taking a look at "[[Installation on XP with IIS]] might also help.<br />
<br />
When using database sessions, make sure MySQL '''max_allowed_packet''' setting is large enough, some surveys generate over 2 MB of session data.<br />
<br />
===Browser compatibility===<br />
For the survey taking side we currently support IE7 and all newer comparable browsers like FF, Chrome, Opera, etc.<br />
For the administration part we currently support IE9 and all newer comparable browsers like FF, Chrome, Opera, etc.<br />
We do not support any IE version running in Intranet-mode or Compatibility-mode!<br />
<br />
===Hosting for LimeSurvey===<br />
<br />
LimeSurvey should work with most hosting companies which provide PHP and MYSQL. If you want a ready-installed version of LimeSurvey consider using [http://www.limeservice.com LimeService], else check out our [[LimeSurvey-compatible hosting companies|list of LimeSurvey-compatible hosting companies]].<br />
<br />
=Download the LimeSurvey package=<br />
<br />
[http://www.limesurvey.org/en/download Download] the latest stable LimeSurvey zip package (there are also gzip, bz2 and 7zip packages available for your convenience) and save it to your local disk.<br />
<br />
=Unpack the LimeSurvey package=<br />
<br />
Uncompress the zip file into a dedicated directory/folder using your preferred compression software. When you uncompress the file make sure that you uncompress the directory structure with the files (this is default behavior for most compression programs). The path name for the installation directory should not include '''(''' or ''')''' characters, but may include the '''space''' character<br />
<br />
=Collect information about your server=<br />
<br />
You will need to know the following things to install LimeSurvey on your web server correctly:<br />
*Your intended website URL where your scripts will reside (e.g: ''http://my.domain.com/limesurvey'')<br />
*The physical disk location on your server where your scripts will reside (ie: ''/home/usr/htdocs/limesurvey'')<br />
*The IP/net location of your database server (ie: ''localhost'')<br />
*If your database server uses a non-standard port find out which port it is.<br />
*Your username and password for your database server<br />
*With most providers you can't let the script create the database but have to do it yourself. If you are using such a provider please create a database (for example ''limesurvey'') yourself.<br />
<br />
=Upload the files to your web server=<br />
<br />
Using your FTP program, connect to your web server and create a directory to store your scripts. Then upload the files using the directory structure they are in. Make sure you '''upload the files in binary mode''' (check the settings of your FTP program). Please note that uploading in ASCII mode can lead to uncommon errors (e.g. 'class not found' error during installation), also images may not be uploaded correctly.<br />
<br />
=Set Directory permissions=<br />
<br />
For the script to work properly it needs certain access to some directories - this applies especially to Linux/*nix systems.<br />
*The '''"/limesurvey/tmp"''' directory and all its subdirectories and files are used for imports & uploads and should be set to ''Read & Write'' for your webserver.<br />
*The '''"/limesurvey/upload/"''' directory and all its subdirectories and files must also have ''Read & Write'' for your webserver in order to enable picture and media files upload.<br />
*The '''"/limesurvey/application/config/"''' directory also needs ''Read & Write'' permissions for your webserver.<br />
*The other directories can be set to ''Read Only'' or in Linux/Unix. You may wish to set the permissions on each file within the /limesurvey/admin directory to ''Read Only''.<br />
<br />
{{Hint|Text=If you are using Linux then depending on your webserver configuration you will have to chmod the rights on the writable folders to 755 or 777. Try 755 first - if it does not work 'upgrade' to 777.}}<br />
<br />
=Create a database user=<br />
<br />
LimeSurvey will create a database and the tables inside it. To be able to do this it will need the username and password of a database user. In general we recommend to create a database user with the following permissions:<br />
<br />
- MySQL: SELECT, CREATE, INSERT, UPDATE, DELETE, ALTER, DROP, INDEX<br />
<br />
- PostgreSQL: SELECT, INSERT, UPDATE, DELETE, TRUNCATE, TRIGGER<br />
<br />
- Microsoft SQL Server:<br />
<br />
=Run the installation script=<br />
<br />
'''Go to "http://your.domain.com/limesurvey/admin"'''. If you configured everything correctly the LimeSurvey installer should be starting - just follow the instructions. You will be asked if to create the database and/or create the tables inside the database. LimeSurvey then creates the needed tables in the database.<br />
<br />
=Connect to the administration script for the first time=<br />
<br />
After the installer has finished you are done! Open your browser and enter the URL of your admin.php script. Assuming you used LimeSurvey as the directory name to store the files in, this will be something like "http://your.domain.com/limesurvey/admin".<br />
<br />
You should get a login screen. The default login credentials (if not changed during in the installation) are<br />
<br />
<div class="simplebox"> User: admin<br />
<br />
Password: password<br />
<br />
</div><br />
<br />
You will be prompted to change the default password after you logged in. Have fun!<br />
<br />
=What if I have problems...=<br />
<br />
Like all computer programs, most of the time things will work just like the instructions say, but sometimes they just won't. There are too many possible reasons for things not going according to plan to describe here. If you have trouble, first check out the [[Installation FAQ]]. If you don't find your answer there please post your problem and any error messages in the [http://www.limesurvey.org/en/forum LimeSurvey forums] on limesurvey.org or join the [irc://irc.freenode.net/limesurvey|LimeSurvey IRC channel]:<br />
<br />
<div class="simplebox"><center>'''[http://www.limesurvey.org/en/community-services/live-chat Direct link to the official LimeSurvey IRC Channel]'''</center></div></div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Installation_-_LimeSurvey_CE/3/ru&diff=63308Translations:Installation - LimeSurvey CE/3/ru2014-09-29T17:23:31Z<p>Ddrmoscow: Created page with "=Общее="</p>
<hr />
<div>=Общее=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/Page_display_title/ru&diff=63307Translations:Survey settings/Page display title/ru2014-09-29T17:19:27Z<p>Ddrmoscow: Created page with "=Настройки опроса="</p>
<hr />
<div>=Настройки опроса=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63306Survey settings/ru2014-09-29T17:19:06Z<p>Ddrmoscow: Created page with "=Дополнительные языки="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Установки=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Импорт==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Копировать==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Ресурсы==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Дополнительные языки=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/25/ru&diff=63305Translations:Survey settings/25/ru2014-09-29T17:19:04Z<p>Ddrmoscow: Created page with "=Дополнительные языки="</p>
<hr />
<div>=Дополнительные языки=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63304Survey settings/ru2014-09-29T17:18:44Z<p>Ddrmoscow: Created page with "==Ресурсы=="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Установки=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Импорт==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Копировать==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Ресурсы==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/21/ru&diff=63303Translations:Survey settings/21/ru2014-09-29T17:18:42Z<p>Ddrmoscow: Created page with "==Ресурсы=="</p>
<hr />
<div>==Ресурсы==</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63302Survey settings/ru2014-09-29T17:18:27Z<p>Ddrmoscow: Created page with "==Копировать=="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Установки=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Импорт==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Копировать==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/16/ru&diff=63301Translations:Survey settings/16/ru2014-09-29T17:18:26Z<p>Ddrmoscow: Created page with "==Копировать=="</p>
<hr />
<div>==Копировать==</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63300Survey settings/ru2014-09-29T17:18:07Z<p>Ddrmoscow: Created page with "==Импорт=="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Установки=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Импорт==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Copy==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/14/ru&diff=63299Translations:Survey settings/14/ru2014-09-29T17:18:07Z<p>Ddrmoscow: Created page with "==Импорт=="</p>
<hr />
<div>==Импорт==</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63298Survey settings/ru2014-09-29T17:17:56Z<p>Ddrmoscow: Created page with "=Установки="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Установки=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Import==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Copy==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/5/ru&diff=63297Translations:Survey settings/5/ru2014-09-29T17:17:56Z<p>Ddrmoscow: Created page with "=Установки="</p>
<hr />
<div>=Установки=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63296Survey settings/ru2014-09-29T17:06:24Z<p>Ddrmoscow: Created page with "==Ключи доступа=="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Settings=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Ключи доступа==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Import==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Copy==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/13/ru&diff=63295Translations:Survey settings/13/ru2014-09-29T17:06:23Z<p>Ddrmoscow: Created page with "==Ключи доступа=="</p>
<hr />
<div>==Ключи доступа==</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63294Survey settings/ru2014-09-29T17:06:05Z<p>Ddrmoscow: Created page with "=Обзор="</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Обзор=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Settings=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Tokens==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Import==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Copy==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/3/ru&diff=63293Translations:Survey settings/3/ru2014-09-29T17:06:04Z<p>Ddrmoscow: Created page with "=Обзор="</p>
<hr />
<div>=Обзор=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Survey_settings/ru&diff=63292Survey settings/ru2014-09-29T17:06:02Z<p>Ddrmoscow: Created page with "__ОГЛАВЛЕНИЕ__"</p>
<hr />
<div><languages /><br />
<br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Overview=<br />
<br />
To create a new survey, click on the Add button [[File:add.png]] on the right side of the administration button bar and a "Create New Survey" screen will appear. You can edit most of these settings later again by click the 'Edit survey settings' icon [[File:token_manage_30.png]] in the 'Survey properties' dropdown menu of the survey toolbar.<br />
<br />
=Settings=<br />
<br />
All survey settings and functions are organized in tabs. The following is a description of each tab and field.<br />
<br />
==General==<br />
#'''Base language''': This sets the base language for the survey. Once saved, you cannot change it later. The language-set is the base language for possible translations of the survey. That way you can have multilingual surveys. During survey creation you cannot add additional languages. You will be able do that if you edit the survey properties again, later.<br />
#'''Title''': This is the brief descriptive name of the survey (ie: "Enterprise Bargaining Survey 2003", or "Views on Ice Cream"). This title will be displayed on every page of the public survey.<br />
#'''Description''': This allows you to enter a description of the survey. (ie: "A survey to collect your ideas on the next round of enterprise bargaining" or "A survey to find out the popularity of chocolate ice cream"). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor. By default, description is used on invitation email.<br />
#'''Welcome message''': This allows you to enter a message that will display when a participant first logs into your survey. (ie: "Thank you for taking the time to participate in this survey..") You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End message''': This allows you to enter a message that will display when a participant completes your survey. (ie: "Thank you for completing our survey. We will publish results soon."). You can incorporate HTML elements such as images or videos in this section using the WYSIWYG editor.<br />
#'''End URL''': This URL will be presented as a link at the end of the survey, and allows you to direct your participants back to your home page (or, in fact, anywhere). The End URL has to be entered with "http://" at the beginning, eg. http://www.limesurvey.org. <br />You can use they placeholder {SAVEDID}, {TOKEN}, {SID} and {LANG} in this URL.<br />SAVEDID is the id assigned to this particular submission, TOKEN is the token used to participate in the survey, SID is the survey ID and LANG is the language code<br />eg. http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}&var3;={SID}&lang;={LANG} <br />From version 1.82+ you can use [[URL fields]] with this field to pass parameters from the start URL to then end URL. <br />You can also use {INSERTANS:SGQA} in this URL (since 1.82+). This allows adding the response to a specific question in the survey to the final url. This can be useful for sending a response to an external script (ie an email address collected during the survey). eg: "http://www.limesurvey.org/test.php?email={INSERTANS:1234X56X7}"<br />
#'''URL description''': The description for the link using the End URL.<br />
#'''Administrator''': This is the name of the contact person who administers the survey. It will be included in emails sent out inviting participants to respond.<br />
#'''Admin email''': This is the email address of the administrator (as above) and is used as the 'reply to:' address on any emails sent. You can also enter several email addresses separated with a semicolon - that way survey administrator notifications are sent to more than one person. (Example: "firstaddress@test.com;secondaddress@test.com")<br />
#'''Bounce email''': This is the email address where a delivery error notification email should be sent. By default, this is the same as the administrator's email address. If you want to use a custom script to parse delivery error emails, then use a special Bounce Email address here and automatically process emails reaching this address with your script. This script could then update the Email Status field of the token line corresponding to this email address (see tokens).<br />
#'''Fax to''': This field is used to give a fax number on the "printable survey" - ie: when you want to send someone a hard copy because they cannot use the online survey.<br />
<br />
<div class="simplebox">'''Caution''': the HTML WYSIWYG editor doesn't allow you to upload files during the survey creation process. Trying to do so will end up with an error message like: "''This file uploader is disabled''". If you need to upload pictures or any other ressources, please do so after survey creation, by editing the newly created survey.</div><br />
<br />
==Presentation & navigation==<br />
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".<br />
#:[[File:Setting_Pres_Format_EN.png]]<br />
#*'''Question by Question''': Public survey will display one question per page.<br />
#*'''Group by Group''': Public survey will display all questions in a group per page. Group at a time surveys still have a separate "welcome" page and "submit" page, like "Question by Question" surveys.<br />
#*'''All in one''': Public survey will display all questions in one single page. Activated All in one surveys do not have a "welcome" page or "submit" page - the welcome message and submit button all appear on the same page.<br />
#'''Template''': Choose from the installed templates in your system. The default template is rather dull, but functional. More information on creating your own templates is available [[The template editor|here]].<br />
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.<br />
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds<br />
#'''Show <nowiki>[</nowiki><< Prev] button''': This option defaults to yes, however if you set it to "No" then users will not have the option of moving to a previous page while completing the survey.<br />
#'''Show question index / allow jumping''': Yes/No. Default No. When Yes, an index will be displayed on the right side. Users can jump to any section in the survey. In 2.05 the options have changed to Disabled / Incremental / Full. Disabled and Incremental represent the current No and Yes options. Full always shows all groups / questions, this allows the user to freely navigate through the survey. This might not work for all kinds of conditions.<br />
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.<br />
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar<br />
#'''Participants may print answers?''': This option defaults to no. When it is set to yes, a participant can print a summary of responses at submit time.<br />
#'''Public statistics''': Yes/No. Default No. If set to "Yes" users who have submitted the survey will be presented a link to statistics of the current survey. The admin can set which questions should be included at these statistics by [[Advanced question settings#public_statistics|applying the according question attribute]].<br />
#'''Show graphs in public statistics''': (''since 1.80'') Determines if public statistics for this survey include graphs or only show a tabular overview. Creating graphs for huge surveys with lots of answers takes some time and server resources so this is the switch to turn them on/off (default setting: ''off'').<br />
#'''Automatically load URL when survey complete''': Yes/No. Default No. If yes, when the survey is submitted, it will automatically redirect to the End URL. The end URL can be defined in the Text Elements Section. Please note that this only works on an active survey.<br />
#'''Show "There are X questions in this survey"''': Yes/No. Default Yes. If Yes, the message will be displayed on the Welcome Screen. This option will not affect the print version.<br />
#'''Show group name and/or group description''': Will control the display of Group Names and Descriptions. This option will not affect the print version. Four Options:<br />
#*'''Show Both''' - Default<br />
#*'''Show Group Names Only'''<br />
#*'''Show group description Only'''<br />
#*'''Hide Both'''<br />
#'''Show question number and/or code''':<br />
#*'''Show Both''' - Default<br />
#*'''Show Question Number Only'''<br />
#*'''Show Question Code Only'''<br />
#*'''Hide Both'''<br />
#'''Show "No answer"''': Yes/No. Default Yes. When Yes, the No Answer will be displayed as the default option for non-mandatory single-select questions. Be aware that if you switch this off, the participant won't be able to unselect a chosen answer option in a non-mandatory question.<br />
<br />
==Publication & access control==<br />
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal<br />
# '''Start date/time''': Set this to some date if you want your survey to start on a certain date. The survey will start on midnight of that day and only then will people be able to answer to it. To disable this just clear the date from the input field.<br />
#'''Expiry date/time''': Set this to some date if you want your survey to expire on a special date. This is the last date on which the public survey script will let people participate. (Example: If you set it for the 31st of December, then people will no longer be able to use the survey script on the 1st of January). To disable this just clear the date from the input field.<br />
#'''Set cookie to prevent repeated participation?''': If you set this to 'Yes', and your survey does not use a tokens table to control participant access, then a cookie will be saved to the client computer of each survey participant once they have submitted a survey. This cookie will stop the same user on that computer from accessing the survey more than once. There are inherent limitations in the 'security' strength of such a system, but, in general, it allows you to retain some control over multiple entries on public surveys.<br />
#'''Use CAPTCHA for''': With this option you can decide when you want a CAPTCHA to be used. Default is to enable CAPTCHA only for the public Registration page, but you can also enable it before accessing the survey, and before Load/Saving partial answers.<br />
<br />
==Notification & data management==<br />
#'''Send basic admin notification email to:''' and '''Send detailed admin notification email to:''' These fields allow you to send notifications or survey responses to additional email addresses once the survey is submitted. You can edit the templates for these emails under 'Email templates'. Multiple recipients can be set by seperating the entries with a semicolon (;) - eg "yourname@test.com; myname@test.com;hisname@test.com" OR when using placeholders "yourname@test.com;{INSERTANS:82733X12X73};{TOKEN:EMAIL}". Make sure that at least your administrator email is set properly in the survey settings - otherwise no email will be sent or there will be an 'Invalid address:' message when a participant finishes a survey. Please note that there are three different ways for entering an address:<br />
##Enter a specific ''email address'' (ie: yourname@test.com)<br />
##Enter a ''SGQA code'' and the response will be sent to an email address entered as an answer to that particular question (use the format {INSERTANS:9999X88X12}, in the same way you would [[Adding a question#Information from previous answers|Re-use information from previous answers]])<br />
##Enter a ''Token code'' (only possible if your survey is ''not'' anonymous) and the response will be sent to an email address retrieved from a token field (use the format {TOKEN:EMAIL} or {TOKEN:ATTRIBUTE_1} in the same way you would [[Adding a question#Information from tokens table|Re-use Information from the Tokens Table]])<br />
##''As of Version 1.92:'' Enter a valid expression conforming to [[Expression Manager|Expression Manager]] syntax. This lets you use question code instead of SGQA syntax (for easier readability), plus conditional logic (e.g. route the notifications to different people depending upon the data entered into the survey).<br />
#'''Date stamp?''': This field allows you to determine whether the survey will datestamp all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the time and date that the response was made. (See configuration settings for $timeadjust setting.)<br />
#'''Save IP address?''': This field allows you to determine whether the survey will save an IP-address for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response indicating the ip-address of the participant.<br />
#'''Save referrer URL?''': This field allows you to determine whether the survey will save the referrer URL for all responses. If you choose "Yes", then when a response is submitted, a field will be included in that response where this URL is saved. A referrer URL is the URL from which the user was led to your survey URL.<br />
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.<br />
#'''Save timings''': If activate then on survey activation a separate table will be created where timings for your questions will be saved, e.g. how long a user stays on one page during taking the survey.<br />
#'''Participant may save and resume later?''': This setting allows a participant to save his responses and resume to answer the survey at a later time. Please note that this makes most sense with open surveys or surveys with anonymized answer. If you are using tokens and the survey is not anonymous in most cases it is better to activate 'Token-based response persistence' in the token tab.<br />
#'''Google Analytics API Key for this survey''': Allows for integration with Google Analytics. The API key can be inserted into templates using {GOOGLE_ANALYTICS_API_KEY}. The full JavaScript that Google Analytics expects (including the key) can be included in templates via {GOOGLE_ANALYTICS_JAVASCRIPT}<br />
#'''Google Analytics Style for this Survey''': Choices are:<br />
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string<br />
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key<br />
##'''SurveyName-<nowiki>[</nowiki>SID]/GroupName''' - {GOOGLE_ANALYTICS_JAVASCRIPT} contains customized Google Analytics code to log the URL as {SURVEYNAME}-<nowiki>[</nowiki>{SID}]/{GROUPNAME}. This can be helpful if you want to analyze navigation paths through your survey, time spent per page, and drop-off rates per page.<br />
<br />
'''Google API howto''':<br />
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]<br />
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.<br />
# Go to your survey's global settings in LimeSurvey.<br />
# Put the key in appropriate field (Google Analytics API Key). It's probably the best to set GA Style to track all pages as you can have more info.<br />
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.<br />
# Activate the survey.<br />
# Do the survey.<br />
# Go to GA panel mainsite. (select appropriate account in left-hand upper corner if you have more than one). You should see some graphs with the statistics. Beware of the dates in upper right corner.<br />
<br />
==Tokens==<br />
<br />
#'''Anonymized responses?''': This allows you to determine whether responses to your survey are matched up with information from your surveys tokens table, or kept 'anonymous'. The default is 'No'. If you choose 'Yes' then your survey is set to radically anonymize responses - there is really no way to connect answers and participants. Even the admin can't link response data and participant/token data. However you will always be able to specifically view each response entered by your participants in the survey. Thus individual, but anonymous, statistics is still possible to do. '''''Attention:''''': If this feature is activated the response submission date and the token completed date are always set to 1980-01-01 00:00, no matter of other settings. Why? Invalidating the submission date ensures no match with webserver logs where the token key might show up when a survey is started. Invalidating the token completed date makes sure that you can't align the order of submitted responses to the order of the token date/time.<br />
<br />
#'''Allow multiple responses or update responses with one token?''': Default: No . If you activate this setting the participants may return to his survey by clicking the invitation link, even if he already submitted the survey. If survey is anonymous or Enable token-based response persistence is set to NO, this add a new responses. If survey is not anonymous and Enable token-based response persistence is Yes, user update existing responses.<br />
<br />
#'''Enable token-based response persistence''': If your survey uses tokens and your responses are not anonymized, then you may want to enable this feature. If you turn this on, then your participants can leave your survey and resume later at any time without using the 'Resume later' function - for example if he/she gets distracted or his browser crashes. Upon clicking the invitation link again he will find his survey answers so far still in place when returns to the survey and will even continue on the last page seen.<br />
<br />
#'''Allow public registration''': If you use tokens to control access to your survey, the only people who can use the survey are those who have an entry and a unique token from the token table. If you would like to use tokens, but also allow public registration, set this to "Yes". The "Yes" setting will allow a visitor to register his name and email address. The script will create a new entry in your tokens table for this person, then send them an invitation email. The script will ensure that only one person per email address can complete your survey.<br />
<br />
#'''Use HTML format for token emails?''': When set to yes, all emails sent by the token management interface (invite, reminder, confirmation) will be formatted as HTML. You'll then be able to use rich formatting for this emails. Default is Yes at survey creation. Caution, when you switch on/off this feature, you'll have to double check that your email templates are still displayed as you want.<br />
<br />
#'''Set token length to''': Usually you don't need to change this, the default setting of 15 digits (max. supported value: 99) is fine. If changing this setting please enter a number (X) which should be greater than 5 (if the number entered is <5 it will be converted to the default value of 15). When generating tokens all tokens will use a length of X digits.<br />
<br />
==Import==<br />
<br />
Alternatively you can [[Importing a survey structure|import a survey structure]] from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended).<br />
<br />
==Copy==<br />
<br />
Alternatively you can copy an existing survey from this tab on survey creation. You have the option to let LimeSurvey automatically convert relative URLs to local images/media files and INSERTANS tags (recommended). The other options are pretty self-explaining. Please note that when copying a survey the start date and the end date of a survey cleared.<br />
<br />
==Panel integration (URL parameters)==<br />
<br />
<div class="simplebox"> Please note that this tab is currently not visible on survey creation but only when you edit the survey settings after saving them for the first time.</div><br />
<br />
On this tab you can set which additional URL parameters will be accepted by your survey. If you like you can also save the value as a response of a "Short text question" or "Multiple short text question" type (you will be able to select any short text question to save it to). Even if you do NOT save the value of the URL parameter you will be able to use this parameter in the end URL. Please have a look at the documentation of the [[URL_fields#Passthrough_fields_.28LimeSurvey_2.x_or_later.29|End-URL]] for further information.<br />
<br />
==Resources==<br />
<br />
This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor and it is only visible if you edit a survey - not during survey creation.<br />
<br />
You can:<br />
* Browse available files<br />
* Export files as a ZIP archive<br />
* Import a ZIP archive of files<br />
<br />
Important hints:<br />
* Authorized files extensions are defined in config-defaults.php.<br />
* Files for the survey are in the upload/surveys/<sid> subdirectory.<br />
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).<br />
* Do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who know the URL to the file.<br />
* You can't import a ZIP file containing subdirectories.<br />
<br />
=Additional languages=<br />
<br />
To add more language to a survey you have to create and save it - then edit it again. Now you can add and remove additional languages to the survey. If you remove a language from a survey the complete contents of that language in that survey is deleted permanently so be careful what you are doing.<br />
<br />
By clicking on the button 'Save and continue' on the first page in the survey settings you will be taken to the language-specific page which lets you change all texts for each language like ''Survey name'', ''Welcome Text'', etc. You can also edit the date format which should be used for a certain language.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Survey_settings/2/ru&diff=63291Translations:Survey settings/2/ru2014-09-29T17:06:02Z<p>Ddrmoscow: Created page with "__ОГЛАВЛЕНИЕ__"</p>
<hr />
<div>__ОГЛАВЛЕНИЕ__</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Version_change_log/ru&diff=63290Version change log/ru2014-09-29T17:04:50Z<p>Ddrmoscow: Created page with "вы можете '''найти журнал последних изменений на [https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/release_notes.txt Github]'''."</p>
<hr />
<div><languages /> <br />
=Общее=<br />
<br />
вы можете '''найти журнал последних изменений на [https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/release_notes.txt Github]'''.<br />
<br />
Also tagged releases are available at [https://github.com/LimeSurvey/LimeSurvey/tags Github].</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Version_change_log/2/ru&diff=63289Translations:Version change log/2/ru2014-09-29T17:04:50Z<p>Ddrmoscow: Created page with "вы можете '''найти журнал последних изменений на [https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/release_notes.txt Github]'''."</p>
<hr />
<div>вы можете '''найти журнал последних изменений на [https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/release_notes.txt Github]'''.</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Version_change_log/Page_display_title/ru&diff=63288Translations:Version change log/Page display title/ru2014-09-29T17:03:49Z<p>Ddrmoscow: Created page with "Журнал изменений версий"</p>
<hr />
<div>Журнал изменений версий</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Version_change_log/ru&diff=63287Version change log/ru2014-09-29T17:03:12Z<p>Ddrmoscow: Created page with "=Общее="</p>
<hr />
<div><languages /> <br />
=Общее=<br />
<br />
You can '''find the latest change log at [https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/release_notes.txt Github]'''.<br />
<br />
Also tagged releases are available at [https://github.com/LimeSurvey/LimeSurvey/tags Github].</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Version_change_log/1/ru&diff=63286Translations:Version change log/1/ru2014-09-29T17:03:12Z<p>Ddrmoscow: Created page with "=Общее="</p>
<hr />
<div>=Общее=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/23/ru&diff=63285Translations:Question type - Array/23/ru2014-09-29T17:00:10Z<p>Ddrmoscow: Created page with "{{QS:Page_break}}"</p>
<hr />
<div>{{QS:Page_break}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/24/ru&diff=63284Translations:Question type - Array/24/ru2014-09-29T17:00:04Z<p>Ddrmoscow: Created page with "{{QS:Public_statistics}}"</p>
<hr />
<div>{{QS:Public_statistics}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/25/ru&diff=63283Translations:Question type - Array/25/ru2014-09-29T16:59:59Z<p>Ddrmoscow: Created page with "{{QS:Random_group}}"</p>
<hr />
<div>{{QS:Random_group}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/26/ru&diff=63282Translations:Question type - Array/26/ru2014-09-29T16:59:54Z<p>Ddrmoscow: Created page with "{{QS:Random_order}}"</p>
<hr />
<div>{{QS:Random_order}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/27/ru&diff=63281Translations:Question type - Array/27/ru2014-09-29T16:59:51Z<p>Ddrmoscow: Created page with "{{QS:scale_export}}"</p>
<hr />
<div>{{QS:scale_export}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/28/ru&diff=63280Translations:Question type - Array/28/ru2014-09-29T16:59:47Z<p>Ddrmoscow: Created page with "{{QS:use_dropdown}}"</p>
<hr />
<div>{{QS:use_dropdown}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/31/ru&diff=63279Translations:Question type - Array/31/ru2014-09-29T16:59:43Z<p>Ddrmoscow: Created page with "{{QS:min_answers}}"</p>
<hr />
<div>{{QS:min_answers}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/32/ru&diff=63278Translations:Question type - Array/32/ru2014-09-29T16:59:39Z<p>Ddrmoscow: Created page with "{{QS:max_answers}}"</p>
<hr />
<div>{{QS:max_answers}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/47/ru&diff=63277Translations:Question type - Array/47/ru2014-09-29T16:59:36Z<p>Ddrmoscow: Created page with "{{QS:em_validation_q}}"</p>
<hr />
<div>{{QS:em_validation_q}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/48/ru&diff=63276Translations:Question type - Array/48/ru2014-09-29T16:59:26Z<p>Ddrmoscow: Created page with "{{QS:em_validation_q_tip}}"</p>
<hr />
<div>{{QS:em_validation_q_tip}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/33/ru&diff=63275Translations:Question type - Array/33/ru2014-09-29T16:59:21Z<p>Ddrmoscow: Created page with "Category:Question types"</p>
<hr />
<div>[[Category:Question types]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Question_type_-_Array/ru&diff=63274Question type - Array/ru2014-09-29T16:59:11Z<p>Ddrmoscow: Created page with "=Общее описание="</p>
<hr />
<div><languages /> <br />
__ОГЛАВЛЕНИЕ__<br />
<br />
=Short description=<br />
<br />
<onlyinclude>{{#ifeq:{{{transcludesection|short_description}}}|short_description|<br />
An array allows you to create subquestions as your left hand headings along the y-axis of a table, and let your participants respond with a series of possible answer options using those subquestions along the y-axis of the table. Examples of uses for this type include multiple point choice scales and questions that require feedback on several aspects of a particular topic.<br />
}}</onlyinclude><br />
=Общее описание=<br />
<br />
[[File:F_AFL.jpg]]<br />
<br />
Download english sample question: [[Media:F_-_Array_Flexible_Labels.csv|F_-_Array_Flexible_Labels.csv]]<br />
<br />
A further option available with Arrays is the '''Semantic Differential''' . You have to choose Array or Array (5 point choice) as your question type and afterwards you can part the answer which should be on the left side from the answer on the right side of the array by using a Pipe Char '|' (If you do not know where is the Pipe Char on your keyboard you can enter it by pressing and holding Alt key, entering 124 and releasing the Alt key). For example: If you want to have 'Good' and 'Evil' on the left and right of the row just write 'Good|Evil' into the answer field:<br />
<br />
[[File:H_SD.jpg]]<br />
<br />
Download english sample question: [[Media:H_-_Array_Flexible_Labels_-_Semantic_Differential.csv|H_-_Array_Flexible_Labels_-_Semantic_Differential.csv]]<br />
<br />
=Основные Настройки=<br />
<br />
{{QS:mandatory}}<br />
<br />
{{QS:other}}<br />
<br />
{{QS:relevance}}<br />
<br />
=Advanced settings=<br />
<br />
{{QS:answer_width}}<br />
<br />
{{QS:array_filter}}<br />
<br />
{{QS:array_filter_exclude}}<br />
<br />
{{QS:Hidden}}<br />
<br />
{{QS:Page_break}}<br />
<br />
{{QS:Public_statistics}}<br />
<br />
{{QS:Random_group}}<br />
<br />
{{QS:Random_order}}<br />
<br />
{{QS:scale_export}}<br />
<br />
{{QS:use_dropdown}}<br />
<br />
{{QS:min_answers}}<br />
<br />
{{QS:max_answers}}<br />
<br />
{{QS:em_validation_q}}<br />
<br />
{{QS:em_validation_q_tip}}<br />
<br />
[[Category:Question types]]</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/5/ru&diff=63273Translations:Question type - Array/5/ru2014-09-29T16:59:10Z<p>Ddrmoscow: Created page with "=Общее описание="</p>
<hr />
<div>=Общее описание=</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/19/ru&diff=63272Translations:Question type - Array/19/ru2014-09-29T16:58:31Z<p>Ddrmoscow: Created page with "{{QS:answer_width}}"</p>
<hr />
<div>{{QS:answer_width}}</div>Ddrmoscowhttps://manual.limesurvey.org/index.php?title=Translations:Question_type_-_Array/17/ru&diff=63271Translations:Question type - Array/17/ru2014-09-29T16:58:25Z<p>Ddrmoscow: Created page with "{{QS:relevance}}"</p>
<hr />
<div>{{QS:relevance}}</div>Ddrmoscow