LimeSurvey Manual - User contributions [en]

Changing an active survey/ja

2014-06-27T07:55:07Z

Yamatt: Created page with "VV-ImportとVV-Exportは、別のサーバー上で行われた同じアンケートの結果を統合するときにも使います。"

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。

=インポート・エクスポートを使った、実行中のアンケートの修正=

実行中のアンケートで質問の追加や削除をする必要が生じてしまったら、"VV-Import"と"VV-Export"という機能を使います。これはあるアンケートのすべての回答を別のアンケートに移すツールです。

VV-ImportとVV-Exportは、別のサーバー上で行われた同じアンケートの結果を統合するときにも使います。

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/7/ja

2014-06-27T07:55:06Z

Yamatt: Created page with "VV-ImportとVV-Exportは、別のサーバー上で行われた同じアンケートの結果を統合するときにも使います。"

VV-ImportとVV-Exportは、別のサーバー上で行われた同じアンケートの結果を統合するときにも使います。

Changing an active survey/ja

2014-06-27T07:54:24Z

Yamatt: Created page with "実行中のアンケートで質問の追加や削除をする必要が生じてしまったら、"VV-Import"と"VV-Export"という機能を使います。これはあるア..."

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。

=インポート・エクスポートを使った、実行中のアンケートの修正=

実行中のアンケートで質問の追加や削除をする必要が生じてしまったら、"VV-Import"と"VV-Export"という機能を使います。これはあるアンケートのすべての回答を別のアンケートに移すツールです。

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/6/ja

2014-06-27T07:54:23Z

実行中のアンケートで質問の追加や削除をする必要が生じてしまったら、"VV-Import"と"VV-Export"という機能を使います。これはあるアンケートのすべての回答を別のアンケートに移すツールです。

Changing an active survey/ja

2014-06-27T07:48:45Z

Yamatt: Created page with "=インポート・エクスポートを使った、実行中のアンケートの修正="

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。

=インポート・エクスポートを使った、実行中のアンケートの修正=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/5/ja

2014-06-27T07:48:45Z

Yamatt: Created page with "=インポート・エクスポートを使った、実行中のアンケートの修正="

=インポート・エクスポートを使った、実行中のアンケートの修正=

Changing an active survey/ja

2014-06-27T07:48:26Z

Yamatt: Created page with "それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。"

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。

= Changing an active survey by import and export=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/4/ja

2014-06-27T07:48:25Z

Yamatt: Created page with "それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。"

それ以上に込み入った変更をするには、インポート・エクスポートをうまく使わなくてはいけません。次節で説明。

Changing an active survey/ja

2014-06-27T07:47:16Z

Yamatt: Created page with "* 質問の文言の修正（タイポの修正など） * 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）"

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

To make more complicated changes, you need to use the import/export facilities described in the next section.

= Changing an active survey by import and export=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/3/ja

2014-06-27T07:47:15Z

Yamatt: Created page with "* 質問の文言の修正（タイポの修正など） * 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）"

* 質問の文言の修正（タイポの修正など）
* 質問の属性の修正（統計の公開、複数選択のうちｘ個入力必須、等々）

Changing an active survey/ja

2014-06-27T07:45:07Z

Yamatt: Created page with "アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:"

<languages />

=実行中のアンケートを変更する=

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

* Modify the text of a question (for example to correct typos or whatever)
* Modify the attributes of a question (for example to include it in the public statistics, insist on a particular number of answers for a multiple options question or whatever).

To make more complicated changes, you need to use the import/export facilities described in the next section.

= Changing an active survey by import and export=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/2/ja

2014-06-27T07:45:07Z

Yamatt: Created page with "アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:"

アンケートが実行中のときには、質問の追加や削除、質問タイプの変更はできません。できることは:

Changing an active survey/ja

2014-06-27T07:44:18Z

Yamatt: Created page with "=実行中のアンケートを変更する="

<languages />

=実行中のアンケートを変更する=

While a survey is active, it is not possible to add or remove questions or answers, or to change the type of the question. However, it is still possible to:

* Modify the text of a question (for example to correct typos or whatever)
* Modify the attributes of a question (for example to include it in the public statistics, insist on a particular number of answers for a multiple options question or whatever).

To make more complicated changes, you need to use the import/export facilities described in the next section.

= Changing an active survey by import and export=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/1/ja

2014-06-27T07:44:18Z

Yamatt: Created page with "=実行中のアンケートを変更する="

=実行中のアンケートを変更する=

Changing an active survey/ja

2014-06-27T07:44:07Z

Yamatt: Created page with "実行中のアンケートを変更する"

<languages />

= Changing an active survey=

While a survey is active, it is not possible to add or remove questions or answers, or to change the type of the question. However, it is still possible to:

* Modify the text of a question (for example to correct typos or whatever)
* Modify the attributes of a question (for example to include it in the public statistics, insist on a particular number of answers for a multiple options question or whatever).

To make more complicated changes, you need to use the import/export facilities described in the next section.

= Changing an active survey by import and export=

If you find you need to add or remove questions or answers or a combination of these, LimeSurvey has functions called "VV-Import" and "VV-Export" that can be used to move all the results from one survey across to another survey.

VV-Import and VV-Export can also be used to combine survey results when the same survey has been run on more than one server.

The method for using VV-Import and VV-Export is as follows:
* Create a new survey and copy the structure of the original one. If necessary modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _old_ survey
* Perform the VV-Import into the _new_ survey

In older Versions of LimeSurvey (<2.05+) you need to apply a method involving some manual handling of data files:
* Export the structure of the original survey. Then import that file as a new survey, and - if necessary - modify this new survey so it has the changes you want.
* Activate the new survey
* Perform a VV-Export from the _new_ survey (we'll call this the 'first export')
* Perform a VV-Export from the _old_ survey (we'll call this the 'second export')
* Cut the two top rows from the first export and insert them as the top two rows in the second export.
* While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.
* Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)
* Save it all as a Tab-Delimited file
* Perform the VV-Import into the _new_ survey

Exporting the survey structure is done in the survey toolbar. The VV-Import and VV-Export buttons are found in the "Browse responses" page of an active survey.

= Tricks=
* When '''rearranging columns''' switch column ids ( row 2) instead of all content columns (3-end)
* '''Rename vv files''' as .txt and excel will open them correctly (save as unicode and rename)
* To '''change the survey title''' go to your admin section and click the 'edit survey' button you will be presented with a screen where you can edit your survey details. On the first Edit Survey - Step 1 of 2 page, click the 'Save and continue' button at the bottom of the page and you will get the screen you need to change the title.

Translations:Changing an active survey/Page display title/ja

2014-06-27T07:44:06Z

Yamatt: Created page with "実行中のアンケートを変更する"

実行中のアンケートを変更する

Plugins/ja

2014-06-26T01:28:10Z

Yamatt: Created page with "LimeSurvey2.05から、公式にプラグインがサポートされるようになりました。プラグインのうちいくつかは、LimeSurveyチームがサポート..."

LimeSurvey2.05から、公式にプラグインがサポートされるようになりました。プラグインのうちいくつかは、LimeSurveyチームがサポートするコア機能となりますが、外部の開発者がサポートするものもあります。 [[Available third party plugins]] に行って見つけましょう。また、ご自分で書いたプラグインも登録してください。

プラグインは、利用者にLimeSurveyのカスタマイズを可能にさせ、将来のアップデートにも耐えるものです。

このドキュメントは、開発者がLimeSurveyの機能を拡張するためのものです。一般の利用者にはあまり役に立ちません。

プラグインは、[https://github.com/LimeSurvey/LimeSurvey/blob/2.05/application/libraries/PluginManager/iPlugin.php iPlugin] インターフェースを実装していなくてはなりません。[https://github.com/LimeSurvey/LimeSurvey/blob/2.05/application/libraries/PluginManager/PluginBase.php PluginBase] クラスを継承してプラグインクラスを作成するのがよいでしょう。

By extending you benefit from common functionality required by plugins that we already have implemented for you. One of these function is the implementation of the getPluginSettings function. This function must return an array describing the configuration options for the user.

Survey settings/ja

2014-06-20T02:23:52Z

Yamatt: Created page with "<div class="simplebox">このタブはアンケートの新規作成時には見えないようになっています。設定を直してから見えるようになります..."

<languages />

__TOC__

=Overview=

新しいアンケートを作成するには、管理ボタンバーの右側にある「追加」ボタン[[File:add.png]]を押します。

この操作で「アンケートの新規作成」画面が表示されます。以下、各項目について解説します：
#'''題名''': アンケートのタイトルを記します。（例：「企業取引に関する調査2003」「アイスクリームについて」）。ここで記入した題名は、公開されるアンケートのすべてのページに表示されます。
#'''摘要''': アンケートの詳細について記します（例：「企業取引の新時代についてどう考えるかを問う調査」「チョコレートアイスの人気っぷりを知るための調査」）。htmlタグを用いることができます。
#'''ようこそ文''': アンケートの回答者がログインしたときに最初に表示される文章を記します。（例：「この度はアンケートに御協力いただきありがとうございます。」）htmlタグを用いることができます。
#'''管理者''': アンケートの管理者名を記します。ここで記入した管理者名は、回答者に送付されるすべてのメールに記載されます。
#'''管理者 E-mail''': アンケートの管理者のメールアドレスを記入します。ここで記入したアドレスは、回答者に送付されるすべてのメールの返信先として用いられます。
#'''Fax番号''': ここで記入したFAX番号は、「印刷用のアンケート」に記載されます。オンラインのアンケートを利用できない回答者に、紙で印刷したものを送付するときに便利です。
#'''フォーマット''': アンケートの回答画面の表示方法です。「質問ごと」「グループごと」「一括」の中から選択します。
##'''質問ごと''': １質問１ページで表示します。
##'''グループごと''': １質問グループ１ページで表示します。「ようこそ画面」「投稿画面」はこれらとは別に１ページで表示されます。
##'''一括''': すべての質問を１ページで表示します。「ようこそ画面」「投稿画面」ではなく、「ようこそ文」「投稿依頼文」が質問と同じページに表示されます。
#'''テンプレート''': 回答画面のテンプレートです。インストールされている中から選択します。デフォルトのテンプレートは、面白みはないかもしれませんが機能的につくってあります。テンプレートを自作したい場合は、 [[テンプレート]] の説明を参照してください。
#'''クッキーを使用しますか？''': クッキーを使用する場合、回答者のアクセス管理はクッキーを用いて行われ、トークンテーブルは利用しません。クッキーは回答者各人のコンピュータに保存されます。クッキーを利用すると、同じ人が複数回アンケートに回答するのを防ぐことができます。この方法にはセキュリティ強度の点で内在的な限界がありますが、たいていの状況では複数回の回答を阻むことができます。
#'''保存を許可しますか？''': 「はい」を選択すると、回答者が回答途中で未投稿のアンケートを保存して、後で再開することができるようになります。
#''' <nowiki>[</nowiki><<前へ] ボタンを表示''': デフォルトでは「はい」が選択されます。「いいえ」を選択すると、アンケートを完了するまで回答者は前のページに戻ることができなくなります。
#'''管理者通知''': 回答者がアンケートを完了して投稿した際に、管理者にメールで通知するかどうかを、以下から選択します：
##通知なし - 通知しません。
##通知あり（簡易） - 回答があったということだけ管理者にメールで通知します。
##通知あり（詳細：結果つき） - 回答結果を管理者にメールで通知します。
#'''匿名にしますか？''': デフォルトでは「はい」が選択されます。「いいえ」を選択すると、アンケートの回答をトークンテーブルのデータと突き合わせることができるようになります（追跡可能）。この場合はトークンテーブルを作成する必要があります。（訳注：アンケートを追跡可能にする方法については[[トークン]]も御参照ください。）
#'''案内メール題名''': トークンを利用して参加者に案内メールを送る際に用いられる題名です。
#'''案内メール本文''': トークンを利用して参加者に案内メールを送る際に用いられる本文です。状況に応じて自由に変更することができます。デフォルトで表示される文面は言語ファイルで設定されています。トークンを利用しない場合には、メールは送信されないのでここに何が記入してあろうと影響はありません。メール本文では、各人によって異なる情報を入力するために以下のタグを用いることができます：
##'''{FIRSTNAME}''' - 名。トークンテーブルの "firstname" の値と置き換えられます。
##'''{LASTNAME}''' - 姓。トークンテーブルの "lastname" の値と置き換えられます。
##'''{SURVEYNAME}''' - アンケート題名。アンケートの題名と置き換えられます。
##'''{SURVEYDESCRIPTION}''' - アンケート摘要。アンケートの摘要と置き換えられます。
##'''{ATTRIBUTE_1}''' - 属性1。トークンテーブルの "attribute 1" の値と置き換えられます。
##'''{ATTRIBUTE_2}''' - 属性2。トークンテーブルの "attribute 2" の値と置き換えられます。
##'''{SURVEYURL}''' - アンケートURL。アンケートのURLと置き換えられます。<br />これらのタグは以下のメール本文にも有効です。
#'''催促メール題名''': トークンを利用して参加者に催促メールを送る際に用いられる題名です。
#'''催促メール本文''': トークンを利用して参加者に催促メールを送る際に用いられる本文です。タグ等の詳細は「案内メール本文」と同じです。
#'''確認メール題名''': トークンを利用する場合に、回答を完了した回答者に自動的に送付される確認メールで用いられる題名です。
#'''確認メール本文''': 確認メールの本文です。
#'''参加登録を許可しますか？''': トークンを利用する場合、アンケートに回答できるのは、トークンテーブルにエントリがあり、一意なトークンを持つ人だけです。アンケートでトークンを利用し、かつ、一般参加者の登録も受け付けたい場合にこの設定を用います。「はい」にすると、アンケートのURLをはじめて訪れた人がそこで名前とメールアドレスを登録できるようになります。するとスクリプトによりトークンテーブルにエントリが新しく作成され、その人にアンケートの案内メールが送られます。このスクリプトは１メールアドレスあたり１回しか回答できないようになっています。
#'''参加登録メール題名''': サイトで参加登録した一般参加者に送られる登録確認メールの題名です。
#'''参加登録メール本文''': サイトで参加登録した一般参加者に送られる登録確認メールの本文です。タグ等の詳細は「案内メール本文」と同じです。
#'''トークン属性名''': トークンテーブルには2つの予備の属性フィールドがあり、そこにユーザについての追加的な情報を入れることができます。一般参加者の登録を許可する場合、各属性欄には一般の人がよくわかるようにタイトルを付ける必要があります。たとえば「属性1」に回答者の部署名を入れているのであれば、それがわかるようなタイトルをうまくつけてください。
#'''回答に日付をスタンプしますか？''': アンケートのすべての回答に日付を記録するかどうかを設定します。「はい」にすると、回答が投稿されたときの日時を記録するフィールドが自動的に設けられます。（configuration設定の $timeadjust を参照してください。）
#'''IPアドレスを保存しますか？''': アンケートのすべての回答者のIPアドレスを記録するかどうかを設定します。「はい」にすると、各回答者のIPアドレスを記録するフィールドが自動的に設けられます。
#'''リンク元URLを保存しますか？''': アンケートのすべての回答者のリンク元URLを記録するかどうかを設定します。「はい」にすると、各回答者がどのURLからアンケートのURLにきたかを記録するフィールドが自動的に設けられます。
#'''基本言語''': アンケートで基本となる言語を設定します。この設定は後から変更することができません。この基本言語をもとにして他言語への翻訳版をつくれば、多言語でのアンケートが可能になります。アンケートを新規作成するときには、追加言語を設定することはできません。追加言語の設定は、アンケート作成後それを編集する際に可能となります。
#'''追加言語''': アンケートの他の言語版を追加・削除します。アンケートの新規作成時以外ならいつでも追加・削除できます。追加言語を削除すると、そのアンケートで当該言語用に作成された質問や回答などがすべて失われますので気をつけてください。
#'''有効期限を設定しますか？''': 、 '''有効期限''': 「はい」にするとアンケートの終了期限を設定することができます。アンケートの一般公開を終了する日を有効期限として設定します。（例：12月31日に設定すると、1月1日以降はアンケートに回答できなくなります。）
#'''終了URL''': ここで記入したURLは、アンケートの最後に表示されます。たとえばアンケートの回答者に、実施元のページ（その他、どこでも）に来てもらうようにすることができます。URLは" http:// "から書いてください。（例： http://www.limesurvey.org）

URLの中に、{SAVEDID} と {TOKEN} を含めることができます。SAVEDID はこの投稿の保存時に割り振られたID、TOKENは回答者のトークンです。例：

http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}
#'''URL詳細''': 上記の終了URLをクリックしたときの行き先についての説明です。
#'''アンケート終了時に、URLを自動的にロードしますか？''': 「はい」にすると、アンケート終了時に「これで完了です」画面を表示するかわりに、上記URLを自動的にロードします。[[アンケートの評価]]を利用する場合は、この機能を用いてはいけません。

以上のかわりに、このページから[[アンケートのインポート]]を行うこともできます。

=Settings=

All survey settings and functions are organized in tabs. The following is a description of each tab and field.

==General==
#'''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.
#'''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.
#'''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.
#'''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.
#'''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.
#'''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}"
#'''URL description''': The description for the link using the End URL.
#'''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.
#'''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")
#'''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).
#'''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.

<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>

==Presentation & navigation==
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".
#:[[File:Setting_Pres_Format_EN.png]]
#*'''Question by Question''': Public survey will display one question per page.
#*'''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.
#*'''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.
#'''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]].
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds
#'''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.
#'''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.
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar
#'''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.
#'''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]].
#'''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'').
#'''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.
#'''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.
#'''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:
#*'''Show Both''' - Default
#*'''Show Group Names Only'''
#*'''Show group description Only'''
#*'''Hide Both'''
#'''Show question number and/or code''':
#*'''Show Both''' - Default
#*'''Show Question Number Only'''
#*'''Show Question Code Only'''
#*'''Hide Both'''
#'''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.

==Publication & access control==
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal
# '''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.
#'''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.
#'''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.
#'''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.

==Notification & data management==
#'''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:
##Enter a specific ''email address'' (ie: yourname@test.com)
##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]])
##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]])
##''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).
#'''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.)
#'''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.
#'''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.
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.
#'''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.
#'''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.
#'''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}
#'''Google Analytics Style for this Survey''': Choices are:
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key
##'''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.

'''Google API howto''':
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.
# Go to your survey's global settings in LimeSurvey.
# 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.
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.
# Activate the survey.
# Do the survey.
# 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.

==Tokens==

#'''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.

#'''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.

#'''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.

#'''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.

#'''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.

#'''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.

==Import==

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).

==Copy==

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.

==パネル統合(URLパラメータ)==

<div class="simplebox">このタブはアンケートの新規作成時には見えないようになっています。設定を直してから見えるようになります。</div>

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.

==Resources==

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.

You can:
* Browse available files
* Export files as a ZIP archive
* Import a ZIP archive of files

Important hints:
* Authorized files extensions are defined in config-defaults.php.
* Files for the survey are in the upload/surveys/<sid> subdirectory.
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).
* 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.
* You can't import a ZIP file containing subdirectories.

=Additional languages=

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.

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.

Translations:Survey settings/19/ja

2014-06-20T02:23:52Z

<div class="simplebox">このタブはアンケートの新規作成時には見えないようになっています。設定を直してから見えるようになります。</div>

Survey settings/ja

2014-06-20T02:22:30Z

Yamatt: Created page with "==パネル統合(URLパラメータ)=="

<languages />

__TOC__

=Overview=

新しいアンケートを作成するには、管理ボタンバーの右側にある「追加」ボタン[[File:add.png]]を押します。

この操作で「アンケートの新規作成」画面が表示されます。以下、各項目について解説します：
#'''題名''': アンケートのタイトルを記します。（例：「企業取引に関する調査2003」「アイスクリームについて」）。ここで記入した題名は、公開されるアンケートのすべてのページに表示されます。
#'''摘要''': アンケートの詳細について記します（例：「企業取引の新時代についてどう考えるかを問う調査」「チョコレートアイスの人気っぷりを知るための調査」）。htmlタグを用いることができます。
#'''ようこそ文''': アンケートの回答者がログインしたときに最初に表示される文章を記します。（例：「この度はアンケートに御協力いただきありがとうございます。」）htmlタグを用いることができます。
#'''管理者''': アンケートの管理者名を記します。ここで記入した管理者名は、回答者に送付されるすべてのメールに記載されます。
#'''管理者 E-mail''': アンケートの管理者のメールアドレスを記入します。ここで記入したアドレスは、回答者に送付されるすべてのメールの返信先として用いられます。
#'''Fax番号''': ここで記入したFAX番号は、「印刷用のアンケート」に記載されます。オンラインのアンケートを利用できない回答者に、紙で印刷したものを送付するときに便利です。
#'''フォーマット''': アンケートの回答画面の表示方法です。「質問ごと」「グループごと」「一括」の中から選択します。
##'''質問ごと''': １質問１ページで表示します。
##'''グループごと''': １質問グループ１ページで表示します。「ようこそ画面」「投稿画面」はこれらとは別に１ページで表示されます。
##'''一括''': すべての質問を１ページで表示します。「ようこそ画面」「投稿画面」ではなく、「ようこそ文」「投稿依頼文」が質問と同じページに表示されます。
#'''テンプレート''': 回答画面のテンプレートです。インストールされている中から選択します。デフォルトのテンプレートは、面白みはないかもしれませんが機能的につくってあります。テンプレートを自作したい場合は、 [[テンプレート]] の説明を参照してください。
#'''クッキーを使用しますか？''': クッキーを使用する場合、回答者のアクセス管理はクッキーを用いて行われ、トークンテーブルは利用しません。クッキーは回答者各人のコンピュータに保存されます。クッキーを利用すると、同じ人が複数回アンケートに回答するのを防ぐことができます。この方法にはセキュリティ強度の点で内在的な限界がありますが、たいていの状況では複数回の回答を阻むことができます。
#'''保存を許可しますか？''': 「はい」を選択すると、回答者が回答途中で未投稿のアンケートを保存して、後で再開することができるようになります。
#''' <nowiki>[</nowiki><<前へ] ボタンを表示''': デフォルトでは「はい」が選択されます。「いいえ」を選択すると、アンケートを完了するまで回答者は前のページに戻ることができなくなります。
#'''管理者通知''': 回答者がアンケートを完了して投稿した際に、管理者にメールで通知するかどうかを、以下から選択します：
##通知なし - 通知しません。
##通知あり（簡易） - 回答があったということだけ管理者にメールで通知します。
##通知あり（詳細：結果つき） - 回答結果を管理者にメールで通知します。
#'''匿名にしますか？''': デフォルトでは「はい」が選択されます。「いいえ」を選択すると、アンケートの回答をトークンテーブルのデータと突き合わせることができるようになります（追跡可能）。この場合はトークンテーブルを作成する必要があります。（訳注：アンケートを追跡可能にする方法については[[トークン]]も御参照ください。）
#'''案内メール題名''': トークンを利用して参加者に案内メールを送る際に用いられる題名です。
#'''案内メール本文''': トークンを利用して参加者に案内メールを送る際に用いられる本文です。状況に応じて自由に変更することができます。デフォルトで表示される文面は言語ファイルで設定されています。トークンを利用しない場合には、メールは送信されないのでここに何が記入してあろうと影響はありません。メール本文では、各人によって異なる情報を入力するために以下のタグを用いることができます：
##'''{FIRSTNAME}''' - 名。トークンテーブルの "firstname" の値と置き換えられます。
##'''{LASTNAME}''' - 姓。トークンテーブルの "lastname" の値と置き換えられます。
##'''{SURVEYNAME}''' - アンケート題名。アンケートの題名と置き換えられます。
##'''{SURVEYDESCRIPTION}''' - アンケート摘要。アンケートの摘要と置き換えられます。
##'''{ATTRIBUTE_1}''' - 属性1。トークンテーブルの "attribute 1" の値と置き換えられます。
##'''{ATTRIBUTE_2}''' - 属性2。トークンテーブルの "attribute 2" の値と置き換えられます。
##'''{SURVEYURL}''' - アンケートURL。アンケートのURLと置き換えられます。<br />これらのタグは以下のメール本文にも有効です。
#'''催促メール題名''': トークンを利用して参加者に催促メールを送る際に用いられる題名です。
#'''催促メール本文''': トークンを利用して参加者に催促メールを送る際に用いられる本文です。タグ等の詳細は「案内メール本文」と同じです。
#'''確認メール題名''': トークンを利用する場合に、回答を完了した回答者に自動的に送付される確認メールで用いられる題名です。
#'''確認メール本文''': 確認メールの本文です。
#'''参加登録を許可しますか？''': トークンを利用する場合、アンケートに回答できるのは、トークンテーブルにエントリがあり、一意なトークンを持つ人だけです。アンケートでトークンを利用し、かつ、一般参加者の登録も受け付けたい場合にこの設定を用います。「はい」にすると、アンケートのURLをはじめて訪れた人がそこで名前とメールアドレスを登録できるようになります。するとスクリプトによりトークンテーブルにエントリが新しく作成され、その人にアンケートの案内メールが送られます。このスクリプトは１メールアドレスあたり１回しか回答できないようになっています。
#'''参加登録メール題名''': サイトで参加登録した一般参加者に送られる登録確認メールの題名です。
#'''参加登録メール本文''': サイトで参加登録した一般参加者に送られる登録確認メールの本文です。タグ等の詳細は「案内メール本文」と同じです。
#'''トークン属性名''': トークンテーブルには2つの予備の属性フィールドがあり、そこにユーザについての追加的な情報を入れることができます。一般参加者の登録を許可する場合、各属性欄には一般の人がよくわかるようにタイトルを付ける必要があります。たとえば「属性1」に回答者の部署名を入れているのであれば、それがわかるようなタイトルをうまくつけてください。
#'''回答に日付をスタンプしますか？''': アンケートのすべての回答に日付を記録するかどうかを設定します。「はい」にすると、回答が投稿されたときの日時を記録するフィールドが自動的に設けられます。（configuration設定の $timeadjust を参照してください。）
#'''IPアドレスを保存しますか？''': アンケートのすべての回答者のIPアドレスを記録するかどうかを設定します。「はい」にすると、各回答者のIPアドレスを記録するフィールドが自動的に設けられます。
#'''リンク元URLを保存しますか？''': アンケートのすべての回答者のリンク元URLを記録するかどうかを設定します。「はい」にすると、各回答者がどのURLからアンケートのURLにきたかを記録するフィールドが自動的に設けられます。
#'''基本言語''': アンケートで基本となる言語を設定します。この設定は後から変更することができません。この基本言語をもとにして他言語への翻訳版をつくれば、多言語でのアンケートが可能になります。アンケートを新規作成するときには、追加言語を設定することはできません。追加言語の設定は、アンケート作成後それを編集する際に可能となります。
#'''追加言語''': アンケートの他の言語版を追加・削除します。アンケートの新規作成時以外ならいつでも追加・削除できます。追加言語を削除すると、そのアンケートで当該言語用に作成された質問や回答などがすべて失われますので気をつけてください。
#'''有効期限を設定しますか？''': 、 '''有効期限''': 「はい」にするとアンケートの終了期限を設定することができます。アンケートの一般公開を終了する日を有効期限として設定します。（例：12月31日に設定すると、1月1日以降はアンケートに回答できなくなります。）
#'''終了URL''': ここで記入したURLは、アンケートの最後に表示されます。たとえばアンケートの回答者に、実施元のページ（その他、どこでも）に来てもらうようにすることができます。URLは" http:// "から書いてください。（例： http://www.limesurvey.org）

URLの中に、{SAVEDID} と {TOKEN} を含めることができます。SAVEDID はこの投稿の保存時に割り振られたID、TOKENは回答者のトークンです。例：

http://www.limesurvey.org/test.php?var1={SAVEDID}&var2;={TOKEN}
#'''URL詳細''': 上記の終了URLをクリックしたときの行き先についての説明です。
#'''アンケート終了時に、URLを自動的にロードしますか？''': 「はい」にすると、アンケート終了時に「これで完了です」画面を表示するかわりに、上記URLを自動的にロードします。[[アンケートの評価]]を利用する場合は、この機能を用いてはいけません。

以上のかわりに、このページから[[アンケートのインポート]]を行うこともできます。

=Settings=

All survey settings and functions are organized in tabs. The following is a description of each tab and field.

==General==
#'''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.
#'''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.
#'''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.
#'''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.
#'''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.
#'''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}"
#'''URL description''': The description for the link using the End URL.
#'''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.
#'''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")
#'''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).
#'''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.

<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>

==Presentation & navigation==
#'''Format''': Choose from "Question by question", "Group by group" or "All in one".
#:[[File:Setting_Pres_Format_EN.png]]
#*'''Question by Question''': Public survey will display one question per page.
#*'''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.
#*'''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.
#'''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]].
#'''Show welcome screen''': Yes/No. If Yes, then the welcome message defined in Text Elements section will be displayed. Default is Yes.
#'''Navigation delay''': Number of seconds before Previous and Next buttons are enabled. Default 0 seconds
#'''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.
#'''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.
#'''Keyboard-less operation''': By activating this setting there will be a virtual keyboard available for certain question types.
#'''Show progress bar''': Yes/No. Default Yes. Allow the administrator to turn off the Progress bar
#'''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.
#'''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]].
#'''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'').
#'''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.
#'''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.
#'''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:
#*'''Show Both''' - Default
#*'''Show Group Names Only'''
#*'''Show group description Only'''
#*'''Hide Both'''
#'''Show question number and/or code''':
#*'''Show Both''' - Default
#*'''Show Question Number Only'''
#*'''Show Question Code Only'''
#*'''Hide Both'''
#'''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.

==Publication & access control==
#'''List survey publicly''': Yes/No. Default No. When it is set to yes, your survey will be listed in the 'available surveys' portal
# '''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.
#'''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.
#'''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.
#'''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.

==Notification & data management==
#'''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:
##Enter a specific ''email address'' (ie: yourname@test.com)
##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]])
##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]])
##''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).
#'''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.)
#'''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.
#'''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.
#'''Enable assessment mode?''': With this setting you can enable/disable [[Assessments|assessments]] for this survey.
#'''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.
#'''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.
#'''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}
#'''Google Analytics Style for this Survey''': Choices are:
##'''Do not use Google Analytics''' - so {GOOGLE_ANALYTICS_JAVASCRIPT} is an empty string
##'''Default Google Analytics''' - {GOOGLE_ANALYTICS_JAVASCRIPT} uses the standard Google Analytics code, inserting the proper Google Analytics Key
##'''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.

'''Google API howto''':
# Register/login on Google Analytics (GA): [http://www.google.com/analytics/ www.google.com/analytics/]
# Create a key (the site should not point to the survey, but to the part before 'index.php?') The key should be UA-xxxxx.
# Go to your survey's global settings in LimeSurvey.
# 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.
# You don't need to do anything in shipped templates, as the {GOOGLE_ANALYTICS_JAVASCRIPT} part is already there.
# Activate the survey.
# Do the survey.
# 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.

==Tokens==

#'''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.

#'''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.

#'''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.

#'''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.

#'''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.

#'''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.

==Import==

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).

==Copy==

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.

==パネル統合(URLパラメータ)==

<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>

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.

==Resources==

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.

You can:
* Browse available files
* Export files as a ZIP archive
* Import a ZIP archive of files

Important hints:
* Authorized files extensions are defined in config-defaults.php.
* Files for the survey are in the upload/surveys/<sid> subdirectory.
* Uploaded files will only been seen while browsing resources on this survey (groups, questions, answers) not in other surveys or objects (labels).
* 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.
* You can't import a ZIP file containing subdirectories.

=Additional languages=

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.

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.

Translations:Survey settings/18/ja

2014-06-20T02:22:29Z

Yamatt: Created page with "==パネル統合(URLパラメータ)=="

==パネル統合(URLパラメータ)==

Survey participants/ja

2014-05-29T04:36:39Z

Yamatt:

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。アンケートごとに設定するか、システム全体の設定を使うかを選べます。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=バウンス設定{{NewIn|1.91}}=

正しくこの機能を設定して使うために、[[Email bounce tracking system]] のページも読んでおいてください。

[[File:surveyBounseSettings.png]]
*'''既定のサイトバウンス(エラー)メールアドレス''': メールの返信先
*'''適用するバウンス設定''': 三つから（なし・下の設定・システム全体の設定）を選びます。「下の設定」のときのみ以下の設定が有効です。
*'''サーバータイプ'''：なし、IMAP、POP から選びます。
*'''サーバー名、ポート''': ホスト名とポート番号を設定します。例：mail.example.net:25 、 imap.gmail.com:995
*'''ユーザ名'''：メールアカウントにアクセスするときのユーザーID
*'''パスワード'''：パスワード
*'''暗号化タイプ'''：なし、SSL、TLS から選びます。

=ユーザー定義属性=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/13/ja

2014-05-29T04:36:38Z

Yamatt:

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。アンケートごとに設定するか、システム全体の設定を使うかを選べます。

Survey participants/ja

2014-05-29T04:35:08Z

Yamatt: Created page with "=ユーザー定義属性="

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=バウンス設定{{NewIn|1.91}}=

正しくこの機能を設定して使うために、[[Email bounce tracking system]] のページも読んでおいてください。

[[File:surveyBounseSettings.png]]
*'''既定のサイトバウンス(エラー)メールアドレス''': メールの返信先
*'''適用するバウンス設定''': 三つから（なし・下の設定・システム全体の設定）を選びます。「下の設定」のときのみ以下の設定が有効です。
*'''サーバータイプ'''：なし、IMAP、POP から選びます。
*'''サーバー名、ポート''': ホスト名とポート番号を設定します。例：mail.example.net:25 、 imap.gmail.com:995
*'''ユーザ名'''：メールアカウントにアクセスするときのユーザーID
*'''パスワード'''：パスワード
*'''暗号化タイプ'''：なし、SSL、TLS から選びます。

=ユーザー定義属性=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/24/ja

2014-05-29T04:35:07Z

Yamatt: Created page with "=ユーザー定義属性="

=ユーザー定義属性=

Survey participants/ja

2014-05-29T04:34:58Z

Yamatt: Created page with "File:surveyBounseSettings.png *'''既定のサイトバウンス(エラー)メールアドレス''': メールの返信先 *'''適用するバウンス設定''': 三つか..."

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=バウンス設定{{NewIn|1.91}}=

正しくこの機能を設定して使うために、[[Email bounce tracking system]] のページも読んでおいてください。

[[File:surveyBounseSettings.png]]
*'''既定のサイトバウンス(エラー)メールアドレス''': メールの返信先
*'''適用するバウンス設定''': 三つから（なし・下の設定・システム全体の設定）を選びます。「下の設定」のときのみ以下の設定が有効です。
*'''サーバータイプ'''：なし、IMAP、POP から選びます。
*'''サーバー名、ポート''': ホスト名とポート番号を設定します。例：mail.example.net:25 、 imap.gmail.com:995
*'''ユーザ名'''：メールアカウントにアクセスするときのユーザーID
*'''パスワード'''：パスワード
*'''暗号化タイプ'''：なし、SSL、TLS から選びます。

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/23/ja

2014-05-29T04:34:58Z

[[File:surveyBounseSettings.png]]
*'''既定のサイトバウンス(エラー)メールアドレス''': メールの返信先
*'''適用するバウンス設定''': 三つから（なし・下の設定・システム全体の設定）を選びます。「下の設定」のときのみ以下の設定が有効です。
*'''サーバータイプ'''：なし、IMAP、POP から選びます。
*'''サーバー名、ポート''': ホスト名とポート番号を設定します。例：mail.example.net:25 、 imap.gmail.com:995
*'''ユーザ名'''：メールアカウントにアクセスするときのユーザーID
*'''パスワード'''：パスワード
*'''暗号化タイプ'''：なし、SSL、TLS から選びます。

Survey participants/ja

2014-05-29T04:24:23Z

Yamatt: Created page with "正しくこの機能を設定して使うために、Email bounce tracking system のページも読んでおいてください。"

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=バウンス設定{{NewIn|1.91}}=

正しくこの機能を設定して使うために、[[Email bounce tracking system]] のページも読んでおいてください。

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/22/ja

2014-05-29T04:24:22Z

Yamatt: Created page with "正しくこの機能を設定して使うために、Email bounce tracking system のページも読んでおいてください。"

正しくこの機能を設定して使うために、[[Email bounce tracking system]] のページも読んでおいてください。

Survey participants/ja

2014-05-29T04:23:27Z

Yamatt: Created page with "=バウンス設定{{NewIn|1.91}}="

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=バウンス設定{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/21/ja

2014-05-29T04:23:26Z

Yamatt: Created page with "=バウンス設定{{NewIn|1.91}}="

=バウンス設定{{NewIn|1.91}}=

Survey participants/ja

2014-05-29T04:22:57Z

Yamatt: Created page with "姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。"

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/20/ja

2014-05-29T04:22:57Z

Yamatt: Created page with "姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。"

姓名、メールアドレス、デフォルト言語は、全部のダミートークンで同じ値になることに注意してください。

Survey participants/ja

2014-05-29T04:22:22Z

Yamatt:

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/16/ja

2014-05-29T04:22:21Z

Yamatt:

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

Survey participants/ja

2014-05-29T04:22:07Z

Yamatt: Created page with "<center>File:dummyToken.png</center> *'''トークン数''': 追加するトークンの数です。初期値は100。 *'''トークンの長さ''': トークンの文字..."

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。次段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/19/ja

2014-05-29T04:22:07Z

<center>[[File:dummyToken.png]]</center>
*'''トークン数''': 追加するトークンの数です。初期値は100。
*'''トークンの長さ''': トークンの文字長です。初期値は15。
*'''姓・名''': （ダミー）回答者の名前です。
*'''E-mail''': （ダミー）回答者の電子メールアドレスです。
*'''言語''': デフォルト言語です。
*'''残りの回数''': トークンが使える残り回数です。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。後段参照。

Survey participants/ja

2014-05-29T04:14:42Z

Yamatt: Created page with "ダミートークンはバージョン1.91から使えるようになりました。画面例:"

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。次段参照。

=ダミートークン=

ダミートークンはバージョン1.91から使えるようになりました。画面例:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/18/ja

2014-05-29T04:14:41Z

Yamatt: Created page with "ダミートークンはバージョン1.91から使えるようになりました。画面例:"

ダミートークンはバージョン1.91から使えるようになりました。画面例:

Survey participants/ja

2014-05-29T04:13:54Z

Yamatt: Created page with "=ダミートークン="

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。次段参照。

=ダミートークン=

Dummy Tokens were added in 1.91. Here is a typical screen:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/17/ja

2014-05-29T04:13:53Z

Yamatt: Created page with "=ダミートークン="

=ダミートークン=

Survey participants/ja

2014-05-29T04:00:55Z

Yamatt: Created page with "<center>File:token_editing2.png</center> *'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます *'''メールアドレス''': ..."

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''姓・名''': .. 回答者のものです。電子メールやアンケート内で使えます
*'''メールアドレス''': .. 回答者の電子メールアドレスです。
*'''メール状態''': .. 失敗したメールの記録用です。たとえば、この回答者に出したメールのエラーを管理者が受け取った場合、OK以外（不明、メール容量オーバーなど）の状態に手動でセットします。OK以外にしておくと、アンケート案内や催促のメールが出されなくなります。この属性は手動設定なことに注意してください。何か自動設定のための外部的なスクリプトでも書くことはできるでしょうが。
*'''トークン''': これが招待のためのコードです。通常は「トークン生成」ボタンで自動生成されます。
*'''言語''': この回答者が使うデフォルト言語です。必要なときに使います。
*'''招待済''': 初期値は 'N' です。招待メールを出した後は、その日付が入ります。
*'''催促済''': 初期値は 'N' です。催促メールを出した後は、その日付が入ります。
*'''完了''': 初期値は 'N' です。非匿名アンケートのときは回答完了時の日付が入ります。匿名アンケートのときは、完了時には 'Y' とのみ入ります。
*'''残り回数''': トークンがあと何回使えるかが入ります。 ''注:'' これを回数切れになったあとで増やすときは、完了フィールドを改めて 'N' に直しておく必要があります。
*'''有効期限''': このトークンが使える有効期限を、開始日時と終了日時という形でセットします。期限設定をしないばあいは、空のままよいです。注: 実際の回答中に回答期限が来てしまった場合は、その時点でアンケートの続行はできなくなり、もう回答完了できません。
*'''Attribute1 to Attribute x''': ユーザー定義属性です。次段参照。

=Dummy Tokens=

Dummy Tokens were added in 1.91. Here is a typical screen:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/16/ja

2014-05-29T04:00:55Z

Survey participants/ja

2014-05-29T03:48:19Z

Yamatt: Created page with "典型的なトークンは次の属性を持ちます。"

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

典型的なトークンは次の属性を持ちます。

<center>[[File:token_editing2.png]]</center>
*'''First and last name''': .. of the participant (can be used in the emails & survey)
*'''Email''': the participant's email address
*'''Email status''': a field to keep track of bad emails. For instance, if the survey administrator received email error notifications from this email, the he can set this field to anything other than 'OK' (for instance 'user unknown', or 'mailbox quota exceeded'). Marking this token with an email status other than 'OK', will help skip this entry when sending invitation or reminder emails. Note that this is completely manual, unless you decide to implement a script which does update this field automatically.
*'''Token''': this is the invitation code. It is usually automatically generated by the 'Generate tokens' button
*'''Language''': if you want to set the default language for this participant
*'''Invite sent''': defaults to 'N', otherwise would contain the date when the invitation email was sent
*'''Reminder sent''': defaults to 'N', otherwise would contain the date when the reminder email was sent
*'''Completed''': defaults to 'N', otherwise would contain the date when the survey was submitted for not anonymous survey, or 'Y' for anonymous survey
*'''Uses left''': A counter of number of times the token can be used. ''Note:'' When increasing this value (default = 1) for a user who has already filled out the survey (which sets uses left to 0), you have to add "N" at the "completed" field.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

=Dummy Tokens=

Dummy Tokens were added in 1.91. Here is a typical screen:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/15/ja

2014-05-29T03:48:18Z

Yamatt: Created page with "典型的なトークンは次の属性を持ちます。"

典型的なトークンは次の属性を持ちます。

Survey participants/ja

2014-05-29T03:47:55Z

Yamatt: Created page with "=トークンの編集/追加="

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=トークンの編集/追加=

A typical token entry contains the following fields:

<center>[[File:token_editing2.png]]</center>
*'''First and last name''': .. of the participant (can be used in the emails & survey)
*'''Email''': the participant's email address
*'''Email status''': a field to keep track of bad emails. For instance, if the survey administrator received email error notifications from this email, the he can set this field to anything other than 'OK' (for instance 'user unknown', or 'mailbox quota exceeded'). Marking this token with an email status other than 'OK', will help skip this entry when sending invitation or reminder emails. Note that this is completely manual, unless you decide to implement a script which does update this field automatically.
*'''Token''': this is the invitation code. It is usually automatically generated by the 'Generate tokens' button
*'''Language''': if you want to set the default language for this participant
*'''Invite sent''': defaults to 'N', otherwise would contain the date when the invitation email was sent
*'''Reminder sent''': defaults to 'N', otherwise would contain the date when the reminder email was sent
*'''Completed''': defaults to 'N', otherwise would contain the date when the survey was submitted for not anonymous survey, or 'Y' for anonymous survey
*'''Uses left''': A counter of number of times the token can be used. ''Note:'' When increasing this value (default = 1) for a user who has already filled out the survey (which sets uses left to 0), you have to add "N" at the "completed" field.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

=Dummy Tokens=

Dummy Tokens were added in 1.91. Here is a typical screen:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/14/ja

2014-05-29T03:47:54Z

Yamatt: Created page with "=トークンの編集/追加="

=トークンの編集/追加=

Translations:Survey participants/12/ja

2014-05-29T03:47:26Z

Yamatt: Created page with "File:token-menu2.png"

[[File:token-menu2.png]]

Survey participants/ja

2014-05-29T03:46:15Z

Yamatt:

<languages /> __TOC__

<div class="simplebox">'''注意''': トークンの仕様は、バージョン1.85から大きくかわりました。以前のバージョンを使っているときは、このマニュアルの内容とは違っていますので、アップグレードをおすすめします。</div>

=はじめに=

アンケートの案内を一定のグループの人に送付したり、誰がアンケートに回答したかを確認したり、回答をひとり一回だけに制限したり、といったことがしたくなるときがあるでしょう。トークンを用いると、次のようなことができます：

*参加者の名前・メールアドレスのリストをインポート（CSV形式、または、LDAPクエリ）
*参加者ひとりひとりを識別できる一意なトークン（招待コード）を付与する
*アンケートの案内状を、参加者に一括で／個別に送信する
*アンケートの催促状を、まだ回答していない参加者に一括で／個別に送信する
*特定の参加者の回答を追跡する
*トークンを持たない人や、すでに回答を終えた人がアンケートにアクセスすることを制限する
*参加者のリストを編集する
*案内のメールや回答の催促について、メール文面のテンプレートを編集する

アンケートをクローズド・アクセスモードにすると（つまりトークンを有効にすると）、'''有効な（未使用の）トークンコードを持つ人だけがアンケートにアクセスできます'''。

アンケートの設定で''自動登録''を有効にしておくと、参加者は個人用のトークンコードを登録画面から取得できるようになります。

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}

==トークンを使うと、アンケート回答が匿名化できる?==

この問いへの答えは'''YES'''です。トークンは匿名用と非匿名用に使えます。これはアンケートの設定で決まります。アンケートが非匿名（追跡可）な場合は、個々人の回答を知るためにトークンリストと見比べることができます。アンケートが匿名な場合は、トークンリストと回答は互いにリンクされません（技術的には、データベース間にリレーションを張りません）。

=トークンを有効化する方法=

トークンを有効化する方法は二通りです:
#アンケートを開始するときに、トークンを有効化するかを聞かれます。[[File:Switch-to-closed-access-mode.png]]
#'''あるいは、'''トークンのアイコン[[File:tokens.png]]をクリックしてもよいです。アンケートを実行開始する前でもこれはできます。

=トークン管理ツール=

[[File:token-menu2.png]]

トークンテーブルを作ったのちに、トークンアイコンをクリックして管理画面に入ります。下がそれぞれの機能概要です。
*'''Admin''': 管理者ホーム画面に戻ります。
*'''Summary''': トークンの数、招待メールを送った数、回答のあった数、などの概要を表示します。後述のようなデータベースの操作機能もあります。
*'''Browse''': トークンの完全なリストを見ます。ウェブブラウザから個々のトークンを変更したり削除したりできます。
*'''Add new token entry''': トークンテーブルに追加します。
*'''Add dummy token''': 複数のトークンをいちどにテーブルに追加します。
*'''Manage additional field attributes''': トークンテーブルに属性を追加して、参加者のデータをカスタム化できます。
*'''Import from CSV''': CSVからインポートします。
*'''Import from LDAP''': LDAPからインポートします。openLDAPでテストしましたが、ActiveDirectoryのように、LDAPの仕様に従った他のディレクトリシステムも大丈夫でしょう。
*'''Export tokens to CSV file''': 標準的なCSV（コンマ区切りファイル）で、すべての参加者トークンデータをエクスポートします。
*'''Edit [[Email templates|email templates]]''': アンケートの案内、アンケート回答の催促、登録メールの文面テンプレートを編集できます。
*'''Send email invitation''': まだ案内メールを送っていない参加者に、案内メールを一斉送信します。
*'''Send email reminder''': 案内メールを送ったのに回答がまだである参加者に、催促のメールを一斉送信します。
*'''Generate tokens''': トークンをまだ割り当てていない参加者データについて、トークンを生成します。
*'''Drop token table''': トークンテーブルを削除し、アンケートをオープンモードにします。
*'''Bounce settings''': バウンス（送信失敗通知）についての設定です。バージョン1.91より。これはシステムレベルの設定です。

=Editing/adding a token=

A typical token entry contains the following fields:

<center>[[File:token_editing2.png]]</center>
*'''First and last name''': .. of the participant (can be used in the emails & survey)
*'''Email''': the participant's email address
*'''Email status''': a field to keep track of bad emails. For instance, if the survey administrator received email error notifications from this email, the he can set this field to anything other than 'OK' (for instance 'user unknown', or 'mailbox quota exceeded'). Marking this token with an email status other than 'OK', will help skip this entry when sending invitation or reminder emails. Note that this is completely manual, unless you decide to implement a script which does update this field automatically.
*'''Token''': this is the invitation code. It is usually automatically generated by the 'Generate tokens' button
*'''Language''': if you want to set the default language for this participant
*'''Invite sent''': defaults to 'N', otherwise would contain the date when the invitation email was sent
*'''Reminder sent''': defaults to 'N', otherwise would contain the date when the reminder email was sent
*'''Completed''': defaults to 'N', otherwise would contain the date when the survey was submitted for not anonymous survey, or 'Y' for anonymous survey
*'''Uses left''': A counter of number of times the token can be used. ''Note:'' When increasing this value (default = 1) for a user who has already filled out the survey (which sets uses left to 0), you have to add "N" at the "completed" field.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

=Dummy Tokens=

Dummy Tokens were added in 1.91. Here is a typical screen:

<center>[[File:dummyToken.png]]</center>
*'''Number of tokens''': Number of tokens to be added. Default is 100.
*'''Token length''': Number of characters or length of token. Default 15
*'''First and last name''': .. of the participant.
*'''Email''': the participant's email address
*'''Language''': If you want to set the default language for this participant
*'''Uses left''': A counter of number of times the token can be used.
*'''Valid from''' & '''Valid until''' : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don't want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won't be able to finish the survey.
*'''Attribute1 to Attribute x''': These are user-definable attribute fields - see the next paragraph.

Note that Name, email, language will be set to the same value for all dummy Tokens

=Bounce Settings{{NewIn|1.91}}=

Please also check out the [[Email bounce tracking system]] page for more information how to correctly configure this feature.

[[File:surveyBounseSettings.png]]
*'''Survey bounce email''': A valid email address for return mail. For faster bounce back processing, this email box should be limited to bounce back only.
*'''Bounce settings to be used''': There are three options: 1- None (default) - no bounce back processing, 2- Use settings below - Will set bounce back processing at the survey level, or 3- Use global settings -- Settings based on the system level.
*'''Server type''': Three options: 1- Off, 2- IMAP or 3- POP
*'''Server name & port''': Host name and port number. Port number isn't typically needed unless the email host uses a non-standard port. Example: mail.example.net:25 or imap.gmail.com:995
*'''User name''': User Name or User ID of the email account
*'''Password''': password of the email account
*'''Encryption type''': Three options: 1- None (default), 2- SSL, or 3- TLS

=User-defined attribute fields=

It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.

Detailed instructions on how to add additional attribute fields and use conditions based on these values can be found at this blog post: "[http://www.limesurvey-consulting.com/limesurvey-conditions-based-on-token-attributes/ Conditions based on token attributes]"

=Using the browse screen and editing tokens=

The browse screen will show you a list of all entries in the tokens table, as well as giving you some 'action' buttons that can perform specific tasks for that individual entry.

The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.

The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.

The "Actions" column gives a list of specific tasks that can be performed on that individual entry:

[[File:token-actions.png]]
*Do the survey using the unique token of this entry
*Edit this entry
*Delete this entry
*Send a invitation/reminder to this individual entry
*If the survey is a 'tracked' (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.

=Database Admin=

[[File:token-summary.png]][[File:token-db-mgt.png]]

While the summary screen shows a brief summary of tokens in the table, it also provides access to the "Database Admin" features which include:
*Clear invites: Sets all records that an invitation has been sent out to 'N'. Obviously shouldn't normally be used.
*Clear tokens: Clears all tokens. Similarly shouldn't normally be used.
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.

= Importing/exporting tokens=

== CSV import==

When you click the icon to import tokens you will be presented with the following screen:

[[File:uploadtoken.jpg]]

Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:

firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...

To obtain a full list of token field names, export an existing token table.

The fields can be in any order but ''firstname, lastname and email are mandatory'', and they must contain at least one character. Empty data (such as "") is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.

A bare minimum CSV file could look like this:

firstname,lastname,email
John,Doe,john@doe.net

'''Date format for token import'''

The date format for the "validfrom" and "validuntil" fields in the CSV token inport file is "YYYY-MM-DD HH:MM", e.g.:

2012-01-01 00:00

--would correspond to 1st January, 2012, at 12:00 AM.

'''Filtering duplicates'''

If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name & Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.

'''Troubleshooting the token import'''

A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, depending on the locale of the OS Microsoft may use semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If not sure just open the file with a standard text editor and check what separator was used. Starting in version 2.00 can you select the used separator during import.

Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.

You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.

'''Add additional attributes at import'''
It is also possible to add new custom attributes when import a CSV file. It is still needed to define what attributes will be added. The way to do this is:
firstname,lastname,email
attribute_1 <Casenr>; token; attribute_2 <Title>; attribute_3 <destination>; lastname; firstname; attribute_4 <Sender>;

== Creating CSV file with Excel on the Mac==

When you create a CSV file with Excel 2011 on the MAC and use the standard "save as" option, you loose special characters such as ü, ë, é etc. when importing into LimeSurvey Token Table.

To make this work properly choose to save the file as a Windows text CSV file (tested on the Dutch version of Excel, saved as "Door lijstscheidingstekens gescheiden Windows tekst (.CSV)").

Then when importing the file in the LimeSurvey token table, under "character set of file" choose "Mac West European". The special characters will be imported correctly.

Tested on LimeSurvey 2.0 only.

== CSV export==

When you export your tokens the following fieldorder is exported:

tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,...

== LDAP import==

[[File:token-Ldap-import.png]]
* Queries are manually defined by the system administrator in the config-ldap.php file
* Duplicates are identified by First Name, Last Name & Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.

== A tip for generating a large number of fake e-mail addresses==

Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let's assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and "@test.com", which is =CONCATENATE(A1;"@test.com"). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.

With the 1.91, you can use "Generate dummy token" functionnality

== A tip for generating a large number of individual links which include the token already==

The structure of the survey link is the following:

Limesurvey 1.x: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token={TOKEN}

Limesurvey 2.x: http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/{TOKEN}

So you proceed similar to the example above for generating email adresses.
*First column: http://url-to-your-limesurvey-installation/index.php?sid=XXXX&lang=en&token= (for version 1.x) OR http://url-to-your-limesurvey-installation/index.php/survey/index/sid/xxxx/newtest/Y/lang/EN/token/ (for version 2.x) (same URL for all, as long as the language is the same!)
*Second column: {TOKEN} (put your tokens here, of course they must be individual)
*Third column: use the CONCATENATE function to join the first column with the second column.

= Emailing=

== Email placeholders==

アンケートの設定画面で、案内メールや催促メールのテンプレートを作成できます。テンプレート作成時には次のフィールド名が使用できます。メールのプレビューでは、これらのフィールド名は実際のデータと置き換えられます。

{ADMINEMAIL} アンケート管理者のメールアドレス

{ADMINNAME} アンケート管理者の名前

{SURVEYNAME} アンケートの題名

{SURVEYDESCRIPTION} アンケートの摘要

次のフィールド名は、実際にメールを送信するときに置き換えられます。

{EMAIL} 受信者のメールアドレス

{FIRSTNAME} 名（First Name）

{LASTNAME} 姓（Last Name）

{SURVEYURL} アンケート開始時のURL

{TOKEN} このアンケートへのアクセスに必要なトークン

{ATTRIBUTE_1} 属性 1

{ATTRIBUTE_2} 属性 2

If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript. You can use these fields in confirmation and notification email template, too.

===Additional hints===
*If your survey is using anonymized responses then token-related placeholders will not work in notification email templates.
*You can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email{{NewIn|1.92}}. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.
Also have a look at the examples on using [[Adding a question#Information from tokens table|information from tokens table]].

==Emails settings==
#'''Invitation Email Subject''': The subject line for the invitation email that gets sent out when tokens are used with your survey.
#'''Invitation Email''': This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don't plan to use tokens on your survey, whatever is in this field is irrelevant. You can use the following "form" fields to insert individualized information in each email:
**'''{FIRSTNAME}''' - gets replaced with the token table's "firstname" value
**'''{LASTNAME}''' - gets replaced with the token table's "lastname" value
**'''{SURVEYNAME}''' - gets replaced with your surveys name
**'''{SURVEYDESCRIPTION}''' - gets replaced with your surveys description
**'''{ATTRIBUTE_1}''' - gets replaced with the token table's "attribute_1" value
**'''{ATTRIBUTE_2}''' - gets replaced with the token table's "attribute_2" value and so on
**'''{SURVEYURL}''' - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link
**'''@@SURVEYURL@@''' - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)
**'''{OPTOUTURL}''' - gets replaced with the URL for a respondent to opt-out of this particular survey

Note that these "form fields" apply to the following email fields.
#'''Email Reminder Subject''': The subject line for the reminder email that gets sent out from the tokens tool
#'''Email Reminder''': This is the text for the reminder email that gets sent out when tokens are used with your survey. See "invitation email" for specific details on how this field is used.
#'''Confirmation Email Subject''': When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey
#'''Confirmation Email''': This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.
#'''Public Registration Email Subject''': This is the subject line for the invitation email sent to members of the public who register for a survey.
#'''Public Registration Email''': This is the text for the invitation email sent to members of the public who register for a survey. The same "form fields" apply in this email as in the earlier ones.

==Sending emails==

=== Send invitations===

[[File:token-invite.png]]

You can skip tokens for which the email status field is different from 'OK', by choosing the 'Bypass token with failing email addresses' option.

==== Resending invitations====

Sometimes you might want to send invitations again to certain token entries / persons. When you use the '''send invitations'''-function only e-mail addresses that ''has not previously received an invitation'' will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.

This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date '''Invite sent?''' for a capital '''N''' (no) and click '''send invitations''' again.

==== Participant opt-out====

When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don't harrass them with reminder emails. A participant that opted out of your survey will have the email status 'OptOut' set in the token.

=== Send reminders===

[[File:token-remind.png]]

When sending reminders you can:
* bypass tokens with failing email addresses
* skip tokens for which an email has been 'recently' sent
* skip tokens for which a given number of emails have already been sent

Note: A reminder will only be send to tokens where the "completed" field is not "N" (this means the respondent has either not taken or has not completed the survey).

=== Sending emails by batch===

When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).

You'll then need to click "Next" to send the next batch, and so on untill all emails have been sent.

=== Confirmation email===

If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.

If you don't want this message to be sent, just deactivate this in the General survey settings.

=== Spam problems===

Often users complain not having received an invitation/reminder email because the user’s spam filter treated the email as spam.

If an email is treated as spam mostly depends on the spam filter being used and its settings. A spam filter usually checks the sender address and the email subject and content, so there are ways and means to influence how they treat your LimeSurvey invitation and reminder emails.

At [http://www.limesurvey-consulting.com/how-to-prevent-limesurvey-email-invitations-or-reminders-being-treated-as-spam/ this blog post] on limesurvey-consulting.com a lot of possible issues and solutions are listed.

===Wrong domain in invitation/reminder email link===

LimeSurvey automatically tries to determine the URL for the invitation link by looking at the URL by which you logged in to the LimeSurvey administration. However with some server (mis-)configurations this might not work properly and you will have to set this manually.

You can edit application/config/config.php to change the default base URL value. Add hostInfo property like this to the existing 'components' array.

<syntaxhighlight lang="php" enclose="div"> 'components' => array(
...
'request' => array(
'hostInfo' => 'http://www.example.com',
),
)
</syntaxhighlight>

Regarding the source of the problem: LimeSurvey tried to determine the domain from the server PHP variable $_SERVER<nowiki>[</nowiki>'HTTP_HOST'] or $_SERVER<nowiki>[</nowiki>'SERVER_NAME'].

Some web server software do not properly seem to provide this information or are mis-configured.

=登録画面の公開=

=公開登録の許可=

一般にアンケートへの回答を求めたいが、トークンを使った制御もしたいということがあるでしょう。できます。トークンテーブルを初期化して、公開登録を設定しておけばよいです。アンケートのURLにトークンを持たずにアクセスしてくると、まず登録画面が表示されます。そこで入力した内容をもとにトークンが作られ、案内メールが送られつという仕組みです。この機能を使った参加者は、「R」ではじまるトークンコードを持ちます。

==キャプチャ(CAPTCHA)==

登録画面を守るために、バージョン1.48からキャプチャ機能を使うことができます。お使いのPHPにGDライブラリが入っている必要があります。(see [[Installation|Installation Requirements]])

Translations:Survey participants/130/ja

2014-05-29T03:46:15Z

Yamatt:

{{Hint|Text=トークンの設定のいくつかは、アンケート設定画面から行えます。see [[Creating a new survey#Tokens]]}}