I would try to generate the syntax using formulas in That you easily fix an error by fixing the syntaxĪlso, if you have the information in a spreadsheet, An added advantage of doing it this way is Think that will be MUCH quicker than individuallyĬlicking and editing these values using theĪ lot of people are scared of syntax, but it's not That you generate syntax and execute that syntax. Maybe someone elseīut to make it as quick as possible, I'd recommend I find applying labels to be very time-consuming, Those numeric variables to have sensible value labels. Variables like Likert responses) into numeric values toīe used in analysis. Import your data into PSPP, you then have to write aīunch of syntax to change those strings (of numeric OfĬourse, that solves the labeling in a way, but when you That would be clear to anyone looking at the data. INDEX/MATCH to replace the codes with response strings And I guess if you had your labels inĪ spreadsheet you could probably arrange to use The Sex variable might have values: 'male', 'female', I guess the other way to deal with this is to not useĬodes, in favor of response strings, in the dataset. The SAV file format (over, say, SQL or CSV). Labeling data is so important and such an improvement in I don't think there is, and that's a shame. Minutes googling whether there was a way to import aĬode book. Good luck, however, remembering what the fiveĮlio ninja'd me last night because I spent a few Rename/label, but it's fairly easy to remember that V3 dat file and not single quote ''.Yes, but variable labels aren't always that big a deal in Limesurvey can I tweak the spss export in some way to use the double quote "" qualifier in the. is there a way of exporting to spss with only the numeric questions is the fact I have a UK keyboard set to UK ansi causing the problems (since the and " are swapped between keys) at export to spss what have I done wrong as there are not that many options. rather than just MS1 I will have MS1 Management style. However spss format would be best as it keeps not only the question codes as variables but also the associated question text as a variable label which will be great for making graphs and cross tab tables meaningful. When I export to csv I can choose which items I want to export and can leave out the free text answers. We're all happy here.','3',Īnd seems to be using apostrophes as the qualifier which is causing the problem. V20 is text 15 characters max, V22 is a scale etc. The apostrophe in the we're is being read as a delimiter.Īnd all the variables are properly shown as being numbers or text e.g.:Į.g. (Respondees who have not used truncation have all their data against the right variable headings which makes me think that everything has mostly gone right with the export.) Have the issue to with the variable surname if we have O'Leary. We're all happy working here.Īnd the next bit is shunted along into the next variable column which is a likert scale and the rest of the data is all shunted along into the wrong variables for that respondee. Where a respondee has used a truncation the answer has been split into two for example. However where some of the variables are text then I have this issue: sps file is all pink where it should be showing that variables have been defined properly. I cannot specify that a question answer is text.Īll the difficult stuff seems to have gone OK and when I run the. In Limesurvey I have in the advanced settings for each question specified the variable type e.g. I am exporting data in spss format to take into PSPP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |