LimeSurvey Manual
Menu
Navigation
Main page
Recent changes
Help
Special pages
Printable version
Recent changes
Help
English
Log in to Manual
Login
Log in to your account
English
Log in to Manual
Get started for free
Sign up
Actions
Translate
Language statistics
Message group statistics
Export
Special
Export translations
Settings
Group
Activating a survey
Adding answers or subquestions
Administering LimeSurvey
Alternatives to the LimeSurvey import function
Assessments
Backup entire database
Batch deletion
Category:Advanced Question Settings
Category:General Question Options
Category:Question Settings
Central Participant Database
Changing an active survey
Check data integrity
Check question logic
Check survey logic - Advanced
Closing a survey
ComfortUpdate
Copy question
Custom translation
Data encryption
Data entry
Data policy settings
DateFunctions
Default answers
Delete question
Delete survey
Display/Export survey
Edit question
Email bounce tracking system
Email templates
Export question
Export responses
Exporting results
Expression Manager
Expression Manager sample surveys
ExpressionScript - Presentation
ExpressionScript Engine - Quick start guide
ExpressionScript examples
ExpressionScript How-tos
ExpressionScript sample surveys
Extension compatibility
Failed email notifications
First login - your user preferences
General FAQ
General settings
Getting started
Global settings
Google API howto
Home page settings
How to design a good survey (guide)
Import responses
Importing a survey
Installation - LimeSurvey CE
Installation FAQ
Installation of the LimeSurvey XAMPP package
Installation security hints
Installation using a command line interface (CLI)
Installation Version 1.92 or older
Iterate survey
Label sets
LDAP settings
License
LimeSurvey Manual
LimeSurvey PRO vs LimeSurvey CE
LimeSurvey Users
LimeSurvey Video-Tutorial
LimeSurvey-compatible hosting companies
List question groups
List questions
Localization
Major version upgrade
Make your plugin compatible with LS4
Manage user groups
Manage users
Menu configuration
Menu entries configuration
Multilingual survey
New Template System in LS3.x
Not categorized and advanced features
Notifications & data
Optional settings
Overview
Panel integration
Participant settings
Plugin manager
Plugin menu
Plugins - advanced
Presentation
Preview function
Problems & solutions
Publication & access
QS:Allowed filetypes
QS:Alphasort
QS:Answer width
QS:Array filter
QS:Array filter exclude
QS:Array filter style
QS:Assessment value
QS:Autocheck exclusive option
QS:Category separator
QS:Chart type
QS:Choice column width
QS:Choice header
QS:Code filter
QS:Commented checkbox
QS:CSS Class
QS:Date max
QS:Date min
QS:Date time format
QS:Display chart
QS:Display columns
QS:Display map
QS:Display rows
QS:Display type
QS:Dropdown dates
QS:Dropdown dates year max
QS:Dropdown dates year min
QS:Dropdown prefix
QS:Dropdown prepostfix
QS:Dropdown separators
QS:Dropdown size
QS:Dualscale headerA
QS:Dualscale headerB
QS:Em validation q
QS:Em validation q tip
QS:Em validation sq
QS:Em validation sq tip
QS:Encryption
QS:Equals num value
QS:Equation
QS:Exclusive option
QS:Get order previous q
QS:Hidden
QS:Hide tip
QS:Input box size
QS:Input boxes
QS:Input max characters
QS:Label column width
QS:Location city
QS:Location country
QS:Location defaultcoordinates
QS:Location mapheight
QS:Location mapservice
QS:Location mapwidth
QS:Location mapzoom
QS:Location nodefaultfromip
QS:Location postal
QS:Location state
QS:Mandatory
QS:Max answers
QS:Max filesize
QS:Max num value
QS:Max num value n
QS:Max num value sgqa
QS:Max subquestions
QS:Maximum chars
QS:Maximum number of files
QS:Min answers
QS:Min num value
QS:Min num value n
QS:Minimum number of files
QS:Minute step interval
QS:Month display style
QS:Multiflexible checkbox
QS:Multiflexible max
QS:Multiflexible min
QS:Multiflexible step
QS:Num value int only
QS:Numbers only
QS:Other
QS:Other comment mandatory
QS:Other numbers only
QS:Other Position
QS:Other replace text
QS:Page break
QS:Prefix
QS:Preg validation
QS:Printable survey relevance help
QS:Public statistics
QS:Question theme
QS:Random group
QS:Random order
QS:Rank header
QS:Relevance
QS:Remove text or uncheck checkbox
QS:Repeat headers
QS:Reverse
QS:Samechoiceheight
QS:Samelistheight
QS:Scale export
QS:Show comment
QS:Show grand total
QS:Show title
QS:Show totals
QS:Showpopups
QS:Slider accuracy
QS:Slider default
QS:Slider handle shape
QS:Slider handle Unicode shape
QS:Slider initial value
QS:Slider layout
QS:Slider max
QS:Slider middlestart
QS:Slider min
QS:Slider orientation
QS:Slider rating
QS:Slider reset
QS:Slider reverse
QS:Slider separator
QS:Slider showminmax
QS:Subquestion width
QS:Suffix
QS:Text input width
QS:Theme editor - advanced options
QS:Time limit
QS:Time limit action
QS:Time limit countdown message
QS:Time limit disable next
QS:Time limit disable prev
QS:Time limit message
QS:Time limit message delay
QS:Time limit message style
QS:Time limit timer style
QS:Time limit warning
QS:Time limit warning display time
QS:Time limit warning message
QS:Time limit warning style
QS:Use dropdown
QS:Value range allows missing
Question groups - introduction
Question toolbar options
Question type - 5 point choice
Question type - Array
Question type - Array (10 point choice)
Question type - Array (5 point choice)
Question type - Array (Increase-Same-Decrease)
Question type - Array (Numbers)
Question type - Array (Texts)
Question type - Array (Yes-No-Uncertain)
Question type - Array by column
Question type - Array dual scale
Question type - Date
Question type - Equation
Question type - File upload
Question type - Gender
Question type - Huge free text
Question type - Language switch
Question type - List (Dropdown)
Question type - List (Radio)
Question type - List with comment
Question type - Long free text
Question type - Multiple choice
Question type - Multiple choice with comments
Question type - Multiple numerical input
Question type - Multiple short text
Question type - Numerical input
Question type - Ranking
Question type - Short free text
Question type - Text display
Question type - Yes-No
Question types
Questions - introduction
QueXML PDF Export
Quick start guide - LimeSurvey 2.50+
Quick start guide - LimeSurvey 3.0+
Quick-translation
Regenerate question codes
Reorder questions and question groups
Reset conditions
Resources
Responses & statistics
Responses (survey results)
Running a survey safely
Setting conditions
SGQA identifier
Statistics
Survey group permissions
Survey menu
Survey participants
Survey permissions
Survey quotas
Survey settings
Survey settings version 2
Survey structure
Survey toolbar options
Surveys - introduction
Surveys - management
Tab Separated Value survey structure
Template:Deprecated
Template:DeprecatedIn
Template:Example
Template:FeatureChange
Template:FeatureStarting
Template:Hint
Template:NewIn
Template:UpdatedIn
Testing a survey
Text elements
Theme editor
Theme options
Themes
Timing statistics
Tools
Transferring an installation
Translating LimeSurvey
Troubleshooting
TwoFactorAdminLogin
Upgrading from a previous version
URL fields
Using regular expressions
Version change log
Version guide
View saved but not submitted responses
Workarounds
Language
aa - Afar
aae - Arbëresh
ab - Abkhazian
abs - Ambonese Malay
ace - Achinese
acm - Iraqi Arabic
ady - Adyghe
ady-cyrl - Adyghe (Cyrillic script)
aeb - Tunisian Arabic
aeb-arab - Tunisian Arabic (Arabic script)
aeb-latn - Tunisian Arabic (Latin script)
af - Afrikaans
aln - Gheg Albanian
alt - Southern Altai
am - Amharic
ami - Amis
an - Aragonese
ang - Old English
ann - Obolo
anp - Angika
ar - Arabic
arc - Aramaic
arn - Mapuche
arq - Algerian Arabic
ary - Moroccan Arabic
arz - Egyptian Arabic
as - Assamese
ase - American Sign Language
ast - Asturian
atj - Atikamekw
av - Avaric
avk - Kotava
awa - Awadhi
ay - Aymara
az - Azerbaijani
azb - South Azerbaijani
ba - Bashkir
ban - Balinese
ban-bali - Balinese (Balinese script)
bar - Bavarian
bbc - Batak Toba
bbc-latn - Batak Toba (Latin script)
bcc - Southern Balochi
bci - Baoulé
bcl - Central Bikol
bdr - West Coast Bajau
be - Belarusian
be-tarask - Belarusian (Taraškievica orthography)
bew - Betawi
bg - Bulgarian
bgn - Western Balochi
bh - Bhojpuri
bho - Bhojpuri
bi - Bislama
bjn - Banjar
blk - Pa'O
bm - Bambara
bn - Bangla
bo - Tibetan
bpy - Bishnupriya
bqi - Bakhtiari
br - Breton
brh - Brahui
bs - Bosnian
btm - Batak Mandailing
bto - Iriga Bicolano
bug - Buginese
bxr - Russia Buriat
ca - Catalan
cbk-zam - Chavacano
cdo - Mindong
ce - Chechen
ceb - Cebuano
ch - Chamorro
chn - Chinook Jargon
cho - Choctaw
chr - Cherokee
chy - Cheyenne
ckb - Central Kurdish
co - Corsican
cps - Capiznon
cpx - Pu–Xian Min
cpx-hans - Pu–Xian Min (Simplified Han script)
cpx-hant - Pu–Xian Min (Traditional Han script)
cpx-latn - Pu–Xian Min (Latin script)
cr - Cree
crh - Crimean Tatar
crh-cyrl - Crimean Tatar (Cyrillic script)
crh-latn - Crimean Tatar (Latin script)
crh-ro - Dobrujan Tatar
cs - Czech
csb - Kashubian
cu - Church Slavic
cv - Chuvash
cy - Welsh
da - Danish
dag - Dagbani
de - German
de-at - Austrian German
de-ch - Swiss High German
de-formal - German (formal address)
dga - Dagaare
din - Dinka
diq - Zazaki
dsb - Lower Sorbian
dtp - Central Dusun
dty - Doteli
dv - Divehi
dz - Dzongkha
ee - Ewe
efi - Efik
egl - Emilian
el - Greek
eml - Emiliano-Romagnolo
en - English
en-ca - Canadian English
en-gb - British English
eo - Esperanto
es - Spanish
es-419 - Latin American Spanish
es-formal - Spanish (formal address)
et - Estonian
eu - Basque
ext - Extremaduran
fa - Persian
fat - Fanti
ff - Fula
fi - Finnish
fit - Tornedalen Finnish
fj - Fijian
fo - Faroese
fon - Fon
fr - French
frc - Cajun French
frp - Arpitan
frr - Northern Frisian
fur - Friulian
fy - Western Frisian
ga - Irish
gaa - Ga
gag - Gagauz
gan - Gan
gan-hans - Gan (Simplified Han script)
gan-hant - Gan (Traditional Han script)
gcf - Guadeloupean Creole
gcr - Guianan Creole
gd - Scottish Gaelic
gl - Galician
gld - Nanai
glk - Gilaki
gn - Guarani
gom - Goan Konkani
gom-deva - Goan Konkani (Devanagari script)
gom-latn - Goan Konkani (Latin script)
gor - Gorontalo
got - Gothic
gpe - Ghanaian Pidgin
grc - Ancient Greek
gsw - Alemannic
gu - Gujarati
guc - Wayuu
gur - Frafra
guw - Gun
gv - Manx
ha - Hausa
hak - Hakka Chinese
haw - Hawaiian
he - Hebrew
hi - Hindi
hif - Fiji Hindi
hif-latn - Fiji Hindi (Latin script)
hil - Hiligaynon
hno - Northern Hindko
ho - Hiri Motu
hr - Croatian
hrx - Hunsrik
hsb - Upper Sorbian
hsn - Xiang
ht - Haitian Creole
hu - Hungarian
hu-formal - Hungarian (formal address)
hy - Armenian
hyw - Western Armenian
hz - Herero
ia - Interlingua
ibb - Ibibio
id - Indonesian
ie - Interlingue
ig - Igbo
igl - Igala
ii - Sichuan Yi
ik - Inupiaq
ike-cans - Eastern Canadian (Aboriginal syllabics)
ike-latn - Eastern Canadian (Latin script)
ilo - Iloko
inh - Ingush
io - Ido
is - Icelandic
it - Italian
iu - Inuktitut
ja - Japanese
jam - Jamaican Creole English
jbo - Lojban
jut - Jutish
jv - Javanese
ka - Georgian
kaa - Kara-Kalpak
kab - Kabyle
kai - Karekare
kbd - Kabardian
kbd-cyrl - Kabardian (Cyrillic script)
kbp - Kabiye
kcg - Tyap
kea - Kabuverdianu
kg - Kongo
kge - Komering
khw - Khowar
ki - Kikuyu
kiu - Kirmanjki
kj - Kuanyama
kjh - Khakas
kjp - Eastern Pwo
kk - Kazakh
kk-arab - Kazakh (Arabic script)
kk-cn - Kazakh (China)
kk-cyrl - Kazakh (Cyrillic script)
kk-kz - Kazakh (Kazakhstan)
kk-latn - Kazakh (Latin script)
kk-tr - Kazakh (Turkey)
kl - Kalaallisut
km - Khmer
kn - Kannada
ko - Korean
ko-kp - Korean (North Korea)
koi - Komi-Permyak
kr - Kanuri
krc - Karachay-Balkar
kri - Krio
krj - Kinaray-a
krl - Karelian
ks - Kashmiri
ks-arab - Kashmiri (Arabic script)
ks-deva - Kashmiri (Devanagari script)
ksh - Colognian
ksw - S'gaw Karen
ku - Kurdish
ku-arab - Kurdish (Arabic script)
ku-latn - Kurdish (Latin script)
kum - Kumyk
kus - Kʋsaal
kv - Komi
kw - Cornish
ky - Kyrgyz
la - Latin
lad - Ladino
lb - Luxembourgish
lbe - Lak
lez - Lezghian
lfn - Lingua Franca Nova
lg - Ganda
li - Limburgish
lij - Ligurian
liv - Livonian
lki - Laki
lld - Ladin
lmo - Lombard
ln - Lingala
lo - Lao
loz - Lozi
lrc - Northern Luri
lt - Lithuanian
ltg - Latgalian
lus - Mizo
luz - Southern Luri
lv - Latvian
lzh - Literary Chinese
lzz - Laz
mad - Madurese
mag - Magahi
mai - Maithili
map-bms - Basa Banyumasan
mdf - Moksha
mg - Malagasy
mh - Marshallese
mhr - Eastern Mari
mi - Māori
min - Minangkabau
mk - Macedonian
ml - Malayalam
mn - Mongolian
mnc - Manchu
mnc-latn - Manchu (Latin script)
mnc-mong - Manchu (Mongolian script)
mni - Manipuri
mnw - Mon
mo - Moldovan
mos - Mossi
mr - Marathi
mrh - Mara
mrj - Western Mari
ms - Malay
ms-arab - Malay (Jawi script)
mt - Maltese
mus - Muscogee
mwl - Mirandese
my - Burmese
myv - Erzya
mzn - Mazanderani
na - Nauru
nah - Nāhuatl
nan - Minnan
nap - Neapolitan
nb - Norwegian Bokmål
nds - Low German
nds-nl - Low Saxon
ne - Nepali
new - Newari
ng - Ndonga
nia - Nias
nit - కొలామి
niu - Niuean
nl - Dutch
nl-informal - Dutch (informal address)
nmz - Nawdm
nn - Norwegian Nynorsk
no - Norwegian
nod - Northern Thai
nog - Nogai
nov - Novial
nqo - N’Ko
nrm - Norman
nso - Northern Sotho
nv - Navajo
ny - Nyanja
nyn - Nyankole
nyo - Nyoro
nys - Nyungar
oc - Occitan
ojb - Northwestern Ojibwa
olo - Livvi-Karelian
om - Oromo
or - Odia
os - Ossetic
pa - Punjabi
pag - Pangasinan
pam - Pampanga
pap - Papiamento
pcd - Picard
pcm - Nigerian Pidgin
pdc - Pennsylvania German
pdt - Plautdietsch
pfl - Palatine German
pi - Pali
pih - Norfuk / Pitkern
pl - Polish
pms - Piedmontese
pnb - Western Punjabi
pnt - Pontic
prg - Prussian
ps - Pashto
pt - Portuguese
pt-br - Brazilian Portuguese
pwn - Paiwan
qu - Quechua
qug - Chimborazo Highland Quichua
rgn - Romagnol
rif - Riffian
rki - Arakanese
rm - Romansh
rmc - Carpathian Romani
rmy - Vlax Romani
rn - Rundi
ro - Romanian
roa-tara - Tarantino
rsk - Pannonian Rusyn
ru - Russian
rue - Rusyn
rup - Aromanian
ruq - Megleno-Romanian
ruq-cyrl - Megleno-Romanian (Cyrillic script)
ruq-latn - Megleno-Romanian (Latin script)
rut - Rutul
rw - Kinyarwanda
ryu - Okinawan
sa - Sanskrit
sah - Yakut
sat - Santali
sc - Sardinian
scn - Sicilian
sco - Scots
sd - Sindhi
sdc - Sassarese Sardinian
sdh - Southern Kurdish
se - Northern Sami
se-fi - Northern Sami (Finland)
se-no - Northern Sami (Norway)
se-se - Northern Sami (Sweden)
sei - Seri
ses - Koyraboro Senni
sg - Sango
sgs - Samogitian
sh - Serbo-Croatian
sh-cyrl - Serbo-Croatian (Cyrillic script)
sh-latn - Serbo-Croatian (Latin script)
shi - Tachelhit
shi-latn - Tachelhit (Latin script)
shi-tfng - Tachelhit (Tifinagh script)
shn - Shan
shy - Shawiya
shy-latn - Shawiya (Latin script)
si - Sinhala
simple - Simple English
sjd - Kildin Sami
sje - Pite Sami
sk - Slovak
skr - Saraiki
skr-arab - Saraiki (Arabic script)
sl - Slovenian
sli - Lower Silesian
sm - Samoan
sma - Southern Sami
smn - Inari Sami
sms - Skolt Sami
sn - Shona
so - Somali
sq - Albanian
sr - Serbian
sr-ec - Serbian (Cyrillic script)
sr-el - Serbian (Latin script)
srn - Sranan Tongo
sro - Campidanese Sardinian
ss - Swati
st - Southern Sotho
stq - Saterland Frisian
sty - Siberian Tatar
su - Sundanese
sv - Swedish
sw - Swahili
syl - Sylheti
szl - Silesian
szy - Sakizaya
ta - Tamil
tay - Tayal
tcy - Tulu
tdd - Tai Nuea
te - Telugu
tet - Tetum
tg - Tajik
tg-cyrl - Tajik (Cyrillic script)
tg-latn - Tajik (Latin script)
th - Thai
ti - Tigrinya
tk - Turkmen
tl - Tagalog
tly - Talysh
tly-cyrl - Talysh (Cyrillic script)
tn - Tswana
to - Tongan
tok - Toki Pona
tpi - Tok Pisin
tr - Turkish
tru - Turoyo
trv - Taroko
ts - Tsonga
tt - Tatar
tt-cyrl - Tatar (Cyrillic script)
tt-latn - Tatar (Latin script)
ttj - Tooro
tum - Tumbuka
tw - Twi
ty - Tahitian
tyv - Tuvinian
tzm - Central Atlas Tamazight
udm - Udmurt
ug - Uyghur
ug-arab - Uyghur (Arabic script)
ug-latn - Uyghur (Latin script)
uk - Ukrainian
ur - Urdu
uz - Uzbek
uz-cyrl - Uzbek (Cyrillic script)
uz-latn - Uzbek (Latin script)
ve - Venda
vec - Venetian
vep - Veps
vi - Vietnamese
vls - West Flemish
vmf - Main-Franconian
vmw - Makhuwa
vo - Volapük
vot - Votic
vro - Võro
wa - Walloon
wal - Wolaytta
war - Waray
wls - Wallisian
wo - Wolof
wuu - Wu
wuu-hans - Wu (Simplified Han script)
wuu-hant - Wu (Traditional Han script)
xal - Kalmyk
xh - Xhosa
xmf - Mingrelian
xsy - Saisiyat
yi - Yiddish
yo - Yoruba
yrl - Nheengatu
yue - Cantonese
yue-hans - Cantonese (Simplified Han script)
yue-hant - Cantonese (Traditional Han script)
za - Zhuang
zea - Zeelandic
zgh - Standard Moroccan Tamazight
zh - Chinese
zh-cn - Chinese (China)
zh-hans - Simplified Chinese
zh-hant - Traditional Chinese
zh-hk - Chinese (Hong Kong)
zh-mo - Chinese (Macau)
zh-my - Chinese (Malaysia)
zh-sg - Chinese (Singapore)
zh-tw - Chinese (Taiwan)
zu - Zulu
Format
Export for off-line translation
Export in native format
Export in CSV format
Fetch
{{DISPLAYTITLE:Exportando resultados}}<languages /> <div class="mw-translate-fuzzy"> __TOC__ </div> __TOC__ <div class="mw-translate-fuzzy"> Depois que o seu questionário estiver ativo, você poderá começar a navegar pelos registros e exportá-los. Para chegar à visão geral dos registros do questionário, clique em... </div> [[File:browse_results.png]] <span id="Export_to_application_(Excel/.csv)"></span> =Exportar para um aplicativo (Excel/.csv)= No topo da página, várias opções de exportação são listadas. [[File:export2.png]] <div class="mw-translate-fuzzy"> Ao exportar resultados para um aplicativo, existem várias opções de filtro que são separadas em: *'''Geral''' **Configure um intervalo como os registros de exportação X a Y; **Configure para exportar todos os registros OU apenas registros completos OU apenas registros incompletos; *'''Perguntas''' **Configure como o cabeçalho deve ser: Cabeçalho abreviado OU cabeçalhos completos OU códigos de pergunta **Converta espaços em questão do tipo texto para sublinhados *'''Respostas''' **Você pode exportar respostas completas ou converter os códigos de resposta Y e N para uma variável definida; *'''Formato''' **Microsoft Word (conjunto de caracteres latinos); **Microsoft Excel (todos os conjuntos de caracteres); **Arquivo CSV (todos os conjuntos de caracteres) **HTML; **PDF; *'''Coluna Controle''' **Configure quais respostas devem ser exportadas. Todas as respostas nesta lista são representadas por seu [[SGQA identifier/pt-br|Identificador SGQA]]; **Defina quais dados '''token''' devem ser exportados. Esta opção só está disponível se a sua pesquisa for '''não anônima'''. </div> [[File:export_tokens.png]] =SPSS Export= ==General== SPSS Statistics is software used for logical batched and non-batched statistical analysis. You can use official SPSS package or use [https://www.gnu.org/software/pspp/ GNU PSPP] replacement for the proprietary program SPSS. To export your response data to SPSS go to ''Responses & Statistics'' section and click the icon to export to SPSS. ==Export and filter data== When exporting data to SPSS there are two filter options. You can select '''which data''' should be selected (''all records/completed records only/incompleted records only'') and for '''which SPSS version''' the export files will be used (''prior version 16/16 or up''). SPSS export includes two files: # a syntax file (''survey_xxxx_SPSS_syntax_file.sps'') # and a data file (''survey_xxxx_SPSS_data_file.dat''). After downloading these files, you can open them using a raw text editor like notepad to take a look at how the exported data looks. The syntax file holds the commands that should be run to import the data. It is like a programming language inside SPSS. The data file contains a comma separated file with all data. If you just import this data as csv via a wizard you loose information about questions, labelsets etc. so we do not do that. ==Import data in SPSS== Place the two files in the same folder on your drive (example: ''c:\data\survey_xxxx_SPSS_syntax_file.sps'' and ''c:\data\survey_xxxx_SPSS_data_file.dat'') We have two options now: 1. When using Windows use the explorer to browse to the folder used above. If SPSS is connected to the .sps file extension you can just open the file by double clicking it: [[File:spss_explorer-screenshot.jpg]] Now you can choose Run->All from the opened window and after some time have your output dataset that you can save as a normal .sav file. 2. Sometimes the easy solution above does not work. Then you can proceed as follows: * Open SPSS * Choose File->Open->Syntax * Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps * Now the syntax opens. * Change the line that reads ''/FILE='survey_xxxx_SPSS_data_file.dat' '' to include the path where the files are: ''/FILE='c:\data\survey_xxxx_SPSS_data_file.dat' '', for mac user : ''/FILE='HD/Users/username/survey_xxxx_SPSS_data_file.dat' '' * Now mark the whole command text and choose Run->All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc. =R Export= Feel free to add more information if you have some! The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is an export to an application export in Limesurvey. Instructions on how to import your dataset in R: #Download both the syntax file and the data file. #Store both files in R working directory (use ''getwd()'' and ''setwd()'' in a R command window to get and set). # In your code enter ''source("Surveydata_syntax.R", encoding = "UTF-8")'' in R command window which will import the data in the correct format to a data frame called "data". Responses with limited options will be factored with the levels matching the code of the question and the labels matching the options. Questions with other as an option will have the question field with _Other appended as a new column for the other data. NB: R-export is a plugin in Limesurvey. If you cannot find the R-export options (''R (syntax file)'', ''R (data file)'') under ''Export results to application'', make sure the R-export plugin is enabled in the plugin menu. =STATA-xml Export= <div class="simplebox">This option is available from version 2.05</div> STATA is a commercial data analysis and statistical software package. This export routine was created to facilitate rapid analysis of data collected with LimeSurvey. It creates an XML-file in STATAs proprietary format, which can be imported independent of the platform STATA is run on. Using this format offeres several advantages over importing plain CSV files: *Data sets are fully labelled including variable labels (question, subquestion) and value labels (answers, if applicable). *Dates are already transformed to STATAs internal date format and thus can directly be used to calculate difference between days etc. *Variable names are, if necessary, converted to a STATA compatible format. *Data formats of variables (string, integer, float, etc.) are already set according to the underlying data. (No more numbers encoded as strings!). '''How to load the file in STATA: In STATA's menu, click on File, Import, xml-data. Choose browse to navigate to your exported file and click 'OK'. That should be it. If you prefer STATA's binary .dta files, you can just save your data again in this format. ''' '''Be aware:''' *Due to a limitation in STATA's data format, the length of string (text) variables have a maximum of 244 characters (Stata versions 8-12) and 2045 characters (Stata version 13 and above). Please indicate your Stata version in the settings of the export plugin. *STATA only supports attaching value labels to numerical values. So to achieve short answers (usually one or two digits) and have these properly labelled, one should use numerical answer-codes in LimeSurvey (1=Totally agree).cIf non-numerical answer codes are used (A=Totally agree), then the complete answer text will be used as answer (eg.: 'Totally agree'). =VVExport and VVImport= {{FeatureChange|v=2.05}} Once you have started collecting responses, there may be occasions where you need to be able to directly edit and modify large quantities of data from your responses table, where a spreadsheet tool may be more useful. VVExport (the "VV" stands for vertical verification) allows you to export your responses table into a .csv file. So long as the general structure of the file remains intact, you can then edit values within it, and then import the file again into your responses table using the "VVImport" feature. Things you should be aware of: * If you want to import responses using "VVImport" make sure to check whether the responses should be added to the existing responses or all responses should be overwritten. * If you are trying to import responses from a different yet identical (e.g. identical questions/answers from another survey) make sure you are using the correct vv file and that the first two lines of the .csv-file are correct. * If you import a survey to your LimeSurvey installation the SID will (if possible) not change. The group id and question id however might change. So you might have to adjust the first two heading lines to match the new group id/question id. See '''Adjusting vv file headings''' == VVExport file version 2 {{NewIn|2.05}} == This new feature allows different column names than the database. If your question codes are unique, then the new version is selected. In the new version each column name uses the [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]]. For example this allows to update an existing survey in different installation more easily. ==Exporting a VV survey file== [[File:limesurveyExportVVen.jpg]] When you choose to export responses using VVExport you will be given the option to choose which survey to be exported, whether you want to export all responses or complete responses only or incomplete responses only. The file extension allows you to choose which extension the exported file will have. For easy use .csv should be chosen. A 'vv survey file' allows you to import the responses to a survey when the question/answer combinations have changed. Effectively this allows you to add or remove questions in an active survey. Clicking on "Export a VV survey file" will then produce a tab delimited file that can be opened by Excel or similar style spreadsheet program. The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response. You should not modify the first two rows of this spreadsheet if you want to be able to "import" the data back into LimeSurvey at a later point. ===Exporting a VV survey file {{NewIn|v=2.05}}=== {{FeatureStarting|v=2.05}} [[File:VV2-export-en.png|center]] * '''Export survey''' : The survey ID to be exported (read-only) * '''Export''' : The completion state of the responses to be exported * '''File extension''' : The file extension. The file is a TSV ([[wikipedia:Tab-separated_values|Tab-separated values]]) file. For easy opening in MS-Excel set the extension to .txt, with LibreOffice, OpenOffice or other spreadsheet program you can leave it to .csv. * '''VV export version''' : The 1.0 version uses database column headers, version 2.0 uses [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]]. Version 2.0 is selected by default if all of your question code are unique. The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question. The second row is the real column name (Internal DB- or Qcode-name) for that response. ==Editing a VV survey file== When a .vv file has been successfully exported you can use a spreadsheet tool to open and edit the file. If you have to choose a column separator when opening the file please use the "Tab" character. If you are using non-ASCII characters make sure you set "UTF-8" as character set. {{Alert|If you are using Microsoft Excel to edit the exported vv file, you should know that excel destroys the original data structure of the file. This causes an error when you try to re-import the edited .vv file.}} By default the first two rows of the .vv file are headers. If needed you can remove the first line to have a real TSV file. There are different use cases for importing a .vv file so we will differentiate between adding new responses to a survey and overwriting all responses of the survey. Example structure of a .vv file: ===VV version 1 TSV file=== <syntaxhighlight lang="text"> Response ID Date submitted Last page Start language Token please vote from 1 to 6 (1 - super, 6 - worst) id submitdate lastpage startlanguage token 46492X40X1991 183 09.11.11 11:44 3 de jsfhusdgqfygqsy 4 184 09.11.11 11:53 3 de sdfhsifgsyergze 2 190 09.11.11 11:44 3 de qsdqshkfhkdsjhj 1 </syntaxhighlight> ===VV version 2 TSV file=== <syntaxhighlight lang="text"> Response ID Date submitted Last page Start language Token please vote from 1 to 6 (1 - super, 6 - worst) id submitdate lastpage startlanguage token QCODE 183 09.11.11 11:44 3 de jsfhusdgqfygqsy 4 184 09.11.11 11:53 3 de sdfhsifgsyergze 2 190 09.11.11 11:44 3 de qsdqshkfhkdsjhj 1 </syntaxhighlight> Here SQGA identifier are not used - instead Qcode variable naming <code>QCODE</code> is used in the second line. ===Reserved names=== .VV file uses left and right brackets for reserved names, when importing this string is replaced by : * <code>{question_not_shown}</code> : NULL value in database. LimeSurvey use [empty string] for not answered question, and NULL value for question not shown (by Expression manager or max step in survey). * <code>{quote}</code> : " (a double quote) * <code>{cr}</code> : Carriage return * <code>{newline}</code> : A new line * <code>{lbrace}</code> : Left bracket (for example, if you want to have {cr} in response : use <code>{lbrace}cr}</code> ) ===VV Version 1 editing=== ====Adding new responses to the existing responses of a survey==== This is not supported for version 1 of the format as it easily can lead to various problems including data being imported into the wrong columns. The version 1 of the .vv file was always meant for vertical verification of data in an external tool like Excel, not as a mean to pull together data from different source (like the same survey running on another server). ====Modify all responses of a survey==== If you want to modify responses of survey you can just add the edit the file. '''Example:''' Step 1: Open the file <syntaxhighlight lang="text"> Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst) id submitdate lastpage startlanguage 46492X40X1991 183 09.11.11 11:44 3 de 4 184 09.11.11 11:53 3 de 2 190 09.11.11 11:44 3 de 1 </syntaxhighlight> Step 2: Modify responses <syntaxhighlight lang="text"> Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst) id submitdate lastpage startlanguage 46492X40X1991 1000 09.11.11 11:44 3 de 3 1001 09.11.11 11:53 3 de 3 1002 09.11.11 11:44 3 de 3 </syntaxhighlight> You can then import the survey, make sure to override the existing responses (see "Importing a VV survey file"). ==Importing a VV survey file== [[File:LimeSurveyImportVVen.jpg]] As long as the first two lines are intact, you can then import the data in your vv survey file back into an active LimeSurvey survey. If you used Microsoft Excel to edit the exported vv file, the data structure of this file may be corrupted, so LimeSurvey is not able to import the edited file. You can try the following workaround to get the import working without an error: *Open your exported vv file in Excel and do your changes (I guess you already did that) *Save it as tab-separated text file (It creates a new file with the extension .txt) *Do another "clean" vv export from LimeSurvey *Open this new exported vv file with a texteditor like notepad or something else (I used textwrangler on mac) *Press CTRL + A to mark all of the content and delete it *Open the Excel edited vv file (the tab separated .txt file) with a texteditor and press CTRL + A to mark all of the content *Press CTRL + C to copy the content and paste it into the new (now empty) vv file *Press CTRL + S to save the file as it is (as .csv) *Now try to import this file Then, from the browse screen, choose the "Import a VV Survey file" icon. The "Import a VV Survey File" screen needs you to choose the "vvexport" file you are importing. If you choose to "Exclude Record IDs" the records will be imported and brand new Record ID's will be generated for them (use this option for the use case "Adding new responses to the existing responses of a survey"). If you un-check this box, then the original record id's will be imported (use this option for the use case "Overwriting all responses of the survey"). There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries. *Report an error (and skip the new record). *Renumber the new record *Replace the existing record (uses this for the use case "Overwriting all responses of the survey") ===Importing a VV survey file {{NewIn|2.05}}=== * '''File''' : Select the file to be uploaded. The file must be a [[wikipedia:Tab-separated_values|TSV file]]: A text file with each column separated by TAB. * '''Exclude record IDs?''' : If 'id' column exist in the file you can exclude this line or not. If this setting is checked then a new record is added for each line of the .vv file. If unchecked you can choose: * '''When an imported record matches an existing record ID''': ** ''skip'' : Report and skip the new record. After upload you will see if the record already existed - if it existed it's not imported. ** ''renumber'' : Renumber the new record. A new record is added to the response table with answer of the VV file. ** ''replace'' : Replace the existing record. The old record is deleted and completely replaced by the record from the VV file ** ''replaceanswer'' : Replace response details from the file in the existing record. The old record is updated with the new response from the VV file. This allow to replace only one question in the response table. * '''Import as not finalized response?''' : If checked the submitdate is set to NULL, so the response is set to not completed. * '''Character set of the file''' : You can choose the character set of the file - the default and recommended value is UTF-8 but some spreadsheet program don't allow to choose a character set. * '''First line contains question codes''' : By default VV file first line contain human readable question, the real column names are in the second line. This allow to use the first line as the real column names. * '''Force import''' : If the question codes are not found in the database name or in [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]] then columns are assigned depending of order. This can be used to import VV file from different LimeSurvey instance but each survey must be exactly the same. We strongly recommend to use this only if you know what you are doing. It can be very dangerous and lead to results ending up in the wrong column. =Other export options= ==Export a single response== If you want to export an individual response, you can do it in 3 ways: 1. Login to limesurvey admin backend, choose your survey, goto "Edit survey settings" -> "Notification and data management" and make sure you receive basic email notifications. Every time someone has completed a survey, you will receive an email with a link: "Click the following link to see the individual response" This will take you to a page with a button above the data saying "Export this response" 2. Login to limesurvey admin backend, choose your survey and "Browse responses for this survey". Click on "Display responses" and the id number you want to export in the left column. Then you can click on "Export this survey" above the data. 3. Login to limesurvey admin backend, choose your survey and "Export results to application". In the last field above "Export data" you can choose which entry you want to export. ==Match responses from different surveys== If you want to track survey responses for particular individuals over time, LimeSurvey can help you do that. A possible use case is to track group responses before and after the group takes a particular seminar. The steps to implementing this are as follows: 1. Create the survey 2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey: a - Click on the icon General settings. b - Then under the Tokens tab select "No" for Anonymized responses. 3. Activate the survey. When you activate the survey, click on the "switch to closed-access mode" button to create the token table: [[File:switch_to_closed.png]] 4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ). 5. Export the survey results and make sure you include the token information. To export click ''browse results''... [[File:browse_results.png]] ...and then ''export'': [[File:export2.png]] Remember to choose one or more elements from the token table to associate with the survey responses: [[File:export_tokens.png]] 6. When you run the survey again, which can easily be done by copying the survey and tokens table using export/import, just repeat the steps, and make sure the same query is used to build the csv token import file. =Problems & Solutions= ==Excel== ===Modifying responses in Excel prior to Import=== In order to make multiple changes to responses, you may choose to Export and open a file in Excel. Make changes to the data (other than the top lines) and then save as a .txt file. If you save as .csv, Excel uses comma-delimits which will not import into LimeSurvey. By saving as a .txt file, Excel saves as a tab-delimited file which imports back into LimeSurvey. ===Edit .csv with Excel=== In general '''''we do not recommend to use Excel to edit the exported .csv files''''' because Excel does some changes to the internal data structure which results in a failing import. If you nevertheless want to use Excel you have to set the seperator for Excel to a comma in System Control (Windows Systems): System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with , ===Workaround to edit .csv files with Excel=== Using Excel for editing questions can prevent you from being able to re-import them. But editing is the way to go if you have more than 5 or so options or ranking options, want to use Excel capabilities like sorting, etc. This is a partial workaround that seems to work in 1.82-essentially, only use Excel on the part of the file that is the data: * Export a question similar to what you would like to reuse as .csv file * Open the CSV file in a rawtext editor * Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent. * Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish * Save the file as Excel CSV, which will likely have no quotes. * Open this file in the editor, and Select All, Copy * Go back to the file you opened with the rawtext editor * Paste over the answers there * Save AS, with a different name, maybe one that you can remember for reuse * Import this file. ===Excel - export limited to 255 columns=== Due to limitations in Excel (versions lower and equal to 2003), LimeSurvey can export only 255 columns at the same time. Microsoft has proposed a [http://support.microsoft.com/kb/272729/en-us workaround as a VB macro]. Although newer spreadsheets (Excel >= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can't export more than 255 columns. Two workarounds are however possible, use one of the following solutions: * Either export to CSV and import in your spreadsheet * Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results ===Excel/.csv - export fails=== If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies. ==CSV== ===CSV defaults to 255 columns=== When exporting large surveys the GUI by default limits the export to the first 255 columns. To work around this, simply mark all data sets for export. ==SPSS export== ===General steps=== To import the LimeSurvey response data please use the following steps: #Click the 'Export to SPSS' icon. #From the select boxes select which responses you want to export and your SPSS version. #Download both files, the .sps (SPSS syntax command file) and .dat file (data file) #Open the .sps file with SPSS by opening SPSS, then select 'Choose another type of file' and select the downloaded .sps file. #Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with '/FILE=...' #Edit that line and adjust the path so it points to your .dat file. Example: Your *.dat file is in c:\temp so set this line to /FILE='c:\temp\survey_(xxxx)_SPSS_data_file.dat' #Now select all commands inside the editor by pressing CTRL-A. #From the SPSS menu select Run/All. #Be patient, it will take some time to import all data and labels. Check the status bar for the progress. #Done! ===Possible error messages in SPSS=== ====ERROR. command name:Get Data==== If you receive the error message ''ERROR. command name:Get Data. 2267 Unexpected Token missing.'' please edit the forth line of your syntax file so it points to the absolute path of the data file like <div class="simplebox">C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat</div> ====Error: "Text value unmappable in the current server locale"==== This error can happen if you try to open an exported syntax file in SPSS 16. The solution is to force SPSS to interpret the syntax file as unicode. <div class="simplebox">Open SPSS. Go to Edit > Options > Character encoding for data and syntax. Change the option to "unicode".</div> LimeSurvey data can now be exported to SPSS 16 without any problem. ===Define the scale to use for your variable=== It is possible to override the default scale used for a variable by setting the question attribute [[Advanced question settings#scale_export|scale_export]] to the appropriate value. ==VV Export/Import== ===VV - Problems with vv import=== If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine. ==Other problems and solutions== ===Copying responses into a different survey (using tokens)=== # Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file. # Export the responses from the old survey, including tokens, open in Excel. # Use this data to create an Excel worksheet for the standard token file import (eg. Firstname, Lastname, Token, Email address, Email status (OK), Language (En)). Save as .csv and import tokens to the new survey in LimeSurvey. # In Excel, copy the response fields from the old survey responses that you want in the new survey (including token) into the appropriate Excel column of the new survey format. # Save as .txt file. # Use VVImport to import the new data into the new survey. # Possible import errors include date format - some system date fields do not allow a NULL value, some do. If the date looks okay but gives an error, use the Excel cell format "2009-12-01".