Manual Bloquera Ceta-ram

NIPO DSC for IBM SPSS
Version 2.00.005
User's Guide
Rev: 2 8-8 -20 15

© 2015 NIPO Software
All rights reserved
The software contains proprietary information of NIPO Software. It is provided under a license agreement
containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of
the software is prohibited.
Due to continued product development this information may change without notice. The information and
intellectual property contained herein is confidential between NIPO Software and the client and remains
the exclusive property of NIPO Software. If you find any problems in the documentation, please report
them to us in Email. NIPO Software does not warrant that this document is error-free. In cases where the
documentation significantly differs from the software implementation, the end user is encouraged to
contact NIPO Software. However, the information in this document can not be used to grant the end user of
the product any rights with regard to updates or fixes, demanding a match with the existing documentation.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by
any means, electronic, mechanical, photocopying, recording or otherwise without the prior written
permission of NIPO Software.
Contents
Introduction 1
Supported IBM SPSS Products 1
Included in This Release 1
Not Included in This Release 1
NIPO DSC for IBM SPSS Version History 2
Changes in NIPO DSC for IBM SPSS 2.00.005 2
Changes in NIPO DSC for IBM SPSS 2.00 2
Contacting Us 2
Contacting NIPO Software Sales 2
Contacting the NIPO Software Helpdesk 3
Your Feedback on this Guide 3
Typographical Conventions 3
Known Issues and Incompatibilities 4
Installing the NIPO DSC for IBM SPSS 5

Prerequisites 5
System Requirements 5
Running the Installer 6
Opening NIPO Software Data in IBM SPSS Applications 7

IBM SPSS Statistics and PASW SPSS Statistics 7
IBM SPSS Data Collection Survey Reporter 9
IBM SPSS Data Collection Base Professional 9
Working with Open-Ended Answers 11

Using Open-Ended Answers on Data from NIPO ODIN Script 11
Using Open-Ended Answers on Data from NIPO Diana / Nvision Script 11
Working with Missing Case Values 13

Adding Missing Case Value Categories as a Rule 13
Adding Missing Case Value Categories by Exception 15
Working with Hierarchical Data 19

Adding Hierarchical Data in NIPO ODIN 20
Adding Tables 20
Adding Grids 21
Adding Hierarchical Data in Nvision Script / NIPO Diana 22
Adding Tables 23
Adding Grids 24
Working with Job Files 27

Job Requirements 27
NIPO DSC for IBM SPSS Configuration 29

NIPO DSC for IBM SPSS Settings Panel 29
Changing the Configuration in mrScriptBasic 30
Page I
NIPO DSC for IBM SPSS 2.00.005 User's Guide
Variable Translation 33
Index 35
Page II
Introduction
The NIPO DSC for IBM SPSS is NIPO Software's data source component for the IBM SPSS Data Collection
Data Model, previously known as SPSS Dimensions or the PASW Data Model.
Key features
 Open and use NIPO Software data directly in PASW Statistics, IBM SPSS Data Collection Survey Reporter
and IBM SPSS Data Collection Base Professional.
 Includes both closed and open answer sets.
 Use hierarchical data views in the IBM SPSS Data Collection suite on NIPO Software data.
 Run NIPO Diana / Nvision Script processing jobs automatically upon opening NIPO Software data in IBM
SPSS products, combining the power of both.
Supported IBM SPSS Products

The NIPO DSC for IBM SPSS allows you to open NIPO Software data in the following products:
 IBM SPSS Data Collection 6.0 Survey Reporter, Survey Reporter Professional, Survey Reporter Developer
Kit, Survey Reporter Data Merge and all previous versions
 IBM SPSS Statistics 20 Standard, Professional, Premium, IBM SPSS Statistics 19, PASW Statistics 18 and
PASW Statistics 17
 IBM SPSS Data Collection 6.0 Base Professional and previous versions
Important note:
An installation of the IBM SPSS Data Collection Survey Reporter Developer Kit is required to open
NIPO Software data in IBM SPSS Statistics and PASW Statistics. The Survey Reporter Developer Kit is
automatically installed with the IBM SPSS Data Collection suite. For information on obtaining a
version of the Survey Reporter Developer Kit that is compatible with your installation, go to
http://www.ibm.com/support.
Included in This Release

The following files are included in this release:
 The installer for NIPO DSC for IBM SPSS 2.00.005
 NIPO DSC for IBM SPSS 2.00.005 User's Guide
Not Included in This Release

The NIPO DSC for IBM SPSS 2.00.005 requires variable definition exports created by the NIPO ODIN
Developer 5.16.005 and later. This software is available as a separate download from the customer's section
of http://www.niposoftware.com.
Page 1
NIPO DSC for IBM SPSS Version History

Changes in NIPO DSC for IBM SPSS 2.00.005
This version includes the following issues:
 PBI #6239: 64-bit version of DSC
 PBI #6519: Adapt DSC to support *MATRX command
Fixed an issue that caused a variable with calculated categories in a table not to work properly.

This version includes a single fix that resolves three issues:
 PBI #5096: Fixed an issue that caused the NIPO DSC for IBM SPSS 2.00.002 to malfunction.
 PBI #5096: Fixed an issue where an export to a SAV file in a JOB file caused the NIPO DSC for IBM SPSS
to stop on error.
 PBI #5096: NIPO DSC for IBM SPSS can now properly execute typologies.

 UST #4829: Fixed an issue where open-ended answer data were neither readable nor transferred to the
NIPO DSC.

 Special characters in NIPO ODIN script no longer lead to errors when opening NIPO Software data in IBM
SPSS products.
 Using HDATA no longer leads to occasionally improperly arranged VDATA.
Changes in NIPO DSC for IBM SPSS 2.00

 Added support for open-ended answers.
 If a period is used in a *VAR defined variable name, it is now changed in an underscore in an Nvision
Script / NIPO Diana variable definition.
 If a variable name defined with *VAR starts with a number, its Nvision Script / NIPO Diana variable is
preceded by an underscore.
 Fixed an order issue with stored *RANDOM orders in the result random order variables.
Contacting Us
For support, licensing information, product news or any other queries or feedback regarding NIPO Software
products, feel free to contact us by phone or by mail. NIPO Software has three offices around the globe -
check the office nearest to your time zone for feedback during your working hours.
Contacting NIPO Software Sales

For any queries on your license, on license pricing or to receive information on any other NIPO Software
products, please contact the NIPO Software Sales department during working hours.
Page 2
Introduction
NIPO Software Sales Amsterdam

PO Box 247
1000 AE Amsterdam
The Netherlands
Tel: +31 20 5225 989 (GMT +1)
Email: sales@niposoftware.com
Contacting the NIPO Software Helpdesk

In case of any queries or issues not covered in this guide, or when experiencing technical difficulties, you
can contact the NIPO Software Helpdesk at three offices worldwide.
 If contacting by mail, please enclose version information, if applicable, and the file(s) associated with
your question, if any. Please ZIP your files before sending.
 If contacting by phone, contact the office nearest to your time zone for immediate assistance.
NIPO Software Helpdesk
Email: helpdesk@niposoftware.com
The EMEA office (Amsterdam) : +31 20 5225 980 (GMT +1)
The APAC office (Hong Kong) : +852 2328 1728 (GMT +8)
The AMER office (Buenos Aires) : +54 11 4891 6470 (GMT -3)
Your Feedback on this Guide

Development and documentation are continuously ongoing processes. New features are added, issues are
solved and functionality is improved. Although we strive to keep the information in our documentation up
to date and accurate, we cannot guarantee that this guide is without error and omission. You are
encouraged to contact us to inform us of shortcomings in all our help files, on-line documentation or
printed material. Suggestions and opinions are also welcomed.
When providing feedback, please make sure to mention the guide and article you are referring to. If you are
reading the documentation from within a browser, click the COPY URL link and provide the URL in your
message.
NIPO Software Documentation
Email: documentation@niposoftware.com
Typographical Conventions
Before you start using this guide, it is important to understand the terms and typographical conventions
used in the documentation.
The following kinds of formatting in the text identify special information:
Example Type of Information
Step-by-step instructions to perform and complete a specific task.

» To Open a File
Help > About... Application controls such as menu options, buttons, tabs,
check-boxes, fields, drop-down boxes and their content and edit
fields.
NIPO Fieldwork System Technical Titles of software documentation.

Reference
Script Script snippets and syntax, file paths and filenames.
Alt-F4 Names of keyboard keys and key combinations.
Page 3
Known Issues and Incompatibilities

The following issues and incompatibilities have been reported by NIPO DSC for IBM SPSS users:
 NIPO DSC for IBM SPSS configuration options (see "NIPO DSC for IBM SPSS Settings Panel" on page 29)
can only be set on a survey-specific or project-specific level if you use IBM SPSS Data Collection Base
Professional (see "Changing the Configuration in mrScriptBasic" on page 30). If using advanced settings
it is strongly recommended to review the configuration options before opening the data in an IBM SPSS
product.
 The NIPO ODIN script variable type *ALPHA (equivalent to Nvision Script *TEXT and NIPO Diana *TEK)
are defined as TEXT type variables in IBM SPSS products. They do not generate labels from values or
predefined categories such as supported by Nvision Script / NIPO Diana.
 Characters for single quotes, doubles quotes, <, > and & are valid label characters in NIPO ODIN script,
Nvision Script and NIPO Diana, but are not supported by the interface with the IBM SPSS product.
Currently these characters are replaced with spaces.
 The JOB and VAR files cannot be correctly opened or accessed when they are opened in an IBM SPSS
applications if they are locked for editing by other applications. Before proceeding to load the data,
close these files in the NIPO ODIN Developer, Nvision Script, NIPO Diana or any text editor in which you
have opened these files.
 Questions in NIPO ODIN subroutines are not embedded in hierarchical data structures. They appear in
the 'root' table always.
 Unbounded loops in hierarchical data structures are not supported because NIPO ODIN has limited
iterations in a *REPEAT block.
Page 4
Installing the NIPO DSC for IBM SPSS
This section is intended for the system administrator who deploys the software on a workstation.
Prerequisites
Before installing this software, make sure the workstation where this software is installed meets the
following prerequisites:
 An installation of the IBM SPSS Data Collection suite. IBM SPSS Statistics and PASW Statistics require the
Data Collection Data Model in this software to be able to open NIPO Software data. This software is
included in the IBM SPSS Data Collection suite. For information on obtaining a version of the Survey
Reporter or the Survey Reporter Developer Kit that is compatible with your installation, go to
http://www.ibm.com/support.
 Any IBM SPSS application that supports the Data Collection Data Model. This includes several
applications within the IBM SPSS Data Collection Suite and IBM SPSS Statistics or PASW Statistics.
The installation must be be performed with a user account with administrator privileges.
System Requirements
The following operating systems are supported for the NIPO DSC for IBM SPSS:
Supported Operating Systems
 Microsoft Windows XP SP3 (all editions except Starter)
 Microsoft Windows Vista SP2 32-bit and 64-bit (all editions except Starter)
 Microsoft Windows 7 32-bit and 64-bit (Starter, Home Basic, Home Premium, Professional, Ultimate
 Windows 8/8.1 (all versions)
 Windows 10, as released per July 2015
Page 5
Running the Installer

» To install the NIPO DSC for IBM SPSS
1. Run the installation file provided with this release and follow the on-screen instructions.
2. A configuration dialog appears during installation:
Changes the settings according to the requirements and click OK to finish the installation (listed
below). Clicking Cancel cancels the installation of the NIPO DSC for IBM SPSS.
The following settings can only be set by an administrator. If these settings need to be edited after
installation, right-click Start > Program Files > NIPO Software > NIPO DSC for IBM SPSS > Configure NIPO
DSC for IBM SPSS from the start-up menu and select Run as... to run as administrator.
Log Directory
The location is the folder where the NIPO DSC for IBM SPSS stores log files for all attempts to load NIPO
Software data in IBM SPSS products. These files may be requested by the NIPO Software Helpdesk for
investigation in case of technical issues. Specify an existing path where all users of the current workstation
have read / write access. If no folder is specified, no log files are created. Files are stored with the name
NipNvDscActionsLog.nnn where nnn is the log number (NipNvDscActionsLog.001 is always
the latest log file).
Log Level
This sets the level of log detail, a value ranging from 1 to 9 inclusive where 1 is low detail and 9 is high
detail. If left blank, the default value 3 is used.
The remaining settings (see "NIPO DSC for IBM SPSS Settings Panel" on page 29) do not need to be
configured at this point, but you may change these options to set a default configuration for all users of this
workstation. Users have access to this configuration panel to customize settings to their requirements.
Page 6
Opening NIPO Software Data in IBM SPSS
Applications
This section deals with opening NIPO Software data in IBM SPSS Statistics, IBM SPSS Data Collection Survey
Reporter and IBM SPSS Data Collection Base Professional.
To start, you need any of the following:
 A NIPO variable definition file without data (*.var). This is a variable map only and does not contain
any data.
 A NIPO data file and NIPO variable definition file (*.dat or *u and *.var). This is a variable map with
data.
 An Nvision Script / NIPO Diana job file (*.job). This is a file that executes variable file definitions, data
file definitions and data transformation on the fly before opening the data. This file may, but does not
have to be, delivered with variable files and data files.
Note:
If a job file was provided with data files and variable files, you must open the job file in your IBM
SPSS application rather than the variable file. The job file should contain preprocessing instructions
such as data merging and data transformation that are to be executed before reviewing the data in
the IBM SPSS application.
IBM SPSS Statistics and PASW SPSS Statistics

IBM SPSS Statistics and PASW SPSS Statistics open NIPO Software data by setting up a data link. This data
link allows for read-only access to NIPO Software data.
Page 7
» To open NIPO Software data in IBM SPSS Statistics or PASW SPSS Statistics
1. Start IBM SPSS Statistics (version 19 or 20) or PASW SPSS Statistics (version 17 or 18).
2. From the menu, select File > Open Data Collection Data (version 19 and 20), or File > Open PASW
Data Collection Data (version 17 and 18). A dialog appears:
Note that the dialog appearance may differ depending on the version of the application you are
using.
3. From the Metadata Type drop-down menu, select NIPO Metadata (read-only).
4. At Metadata Location, click Browse... An open file dialog appears.
5. Select the variable file (*.var) to open. If you have a job file (*.job) in addition or instead of a
variable file, select that file instead. Click Open.
6. If you opened a job file, or if you only wish to open a variable definition without loading data,
proceed at step 9. Otherwise, from the Case Data Type drop-down menu, select NIPO Case Data
(read-only).
7. At Case Data Location, click Browse... An open file dialog appears.
8. Select the data file (*.dat or *u) to open and click Open.
9. Back at the Data Link Properties dialog, click OK to proceed. The Data Collection Data Import dialog
appears.
10. Optionally de-select the variables to exclude and / or make a Case Selection and click OK to finish.
Page 8
Opening NIPO Software Data in IBM SPSS Applications
IBM SPSS Data Collection Survey Reporter

IBM SPSS Data Collection Survey Reporter opens NIPO Software data by opening either a variable file
(*.var) or a job file (*.job). If you open a variable file, it assumes that the data file bears the same
name, and has the extension *.dat. If you open the job file, the job file is assumed to open the relevant
data files and variable definition files and optionally perform data transformations.
» To open NIPO Software data in IBM SPSS Data Collection Survey Reporter
1. Start IBM SPSS Data Collection Survey Reporter.
2. From the menu, select File > Open. The Open file dialog appears.
3. At Files of Type, select NIPO variable/job files from the drop-down box.
4. Select the variable file or job file to open and click Open. Alternatively, click Advanced... to set up a
data link. This works in the same manner as setting up a data link in IBM SPSS Statistics and PASW
SPSS Statistics (on page 7).
IBM SPSS Data Collection Base Professional

IBM SPSS Data Collection Base Professional loads NIPO Software data by setting up a valid
ConnectionString in the InputDataSource method in an mrScriptBasic script.
Pass the Nvision Script / NIPO Diana var file as the input meta data file. The input data file and the
(optional) open-ended answer file (O-file) are derived from the var file: for a variable file named
project.var, the NIPO DSC for IBM SPSS expects a data file project.dat and an optional
open-ended answer file projecto (no extension, file name suffixed with o) to be available in the same
folder. The mrScriptBasic example below loads project.var and its related project.dat and optional
projecto file file from the folder C:\MyProjects. Any input case data file is ignored.
Note:
Due to an mrScriptBasic issue, case data and meta data output files in some products require to have
different project names. For example, for a project.var input file you cannot use a
project.ddf and project.mdd as output file names. Use alternative names for output.
Example mrScriptBasic file opening NIPO Software data for input (variable file)
#define root "C:\MyProjects\"
#define INPUT_METADATA root + "project.var"
#define OUTPUT_CASEDATA root + "project_out.ddf"
#define OUTPUT_METADATA root + "project_out.mdd"
InputDataSource(myInputDataSource)
ConnectionString = "Provider=mrOleDB.Provider.2; _
Data Source=nipNvDsc; _
Initial Catalog=" + INPUT_METADATA + "; _
MR Init MDSC=nipNvDsc"
End InputDataSource
OutputDataSource(myOutputDataSource)
Data Source=mrdatafileDsc; _
Location=" + OUTPUT_CASEDATA
MetaDataOutputName = OUTPUT_METADATA
End OutputDataSource
You may also load an Nvision Script / NIPO Diana job file.
Page 9
Example mrScriptBasic file opening NIPO Software data for input (job file)
#define INPUT_METADATA root + "project.job"
MR Init MDSC=nipNvDsc"
End InputDataSource
Any data transformations in the job file are executed before the data is accessed by IBM SPSS Data
Collection Base Professional.
Note:
If the output file already exist, IBM SPSS Data Collection Base Professional attempts to merge new
meta-data with existing meta-data in the specified output files, causing unwanted effects. To
prevent this, delete your *.DDF and *.MDD files before running your jobs. You can also add the
following code snippet to your scripts to delete existing output files. The script assumes that the files
OUTPUT_CASEDATA and OUTPUT_METADATA have already been defined.
Example mrScriptBasic removing existing output files

Event(OnBeforeJobStart, "Delete existing output files")
Dim fso
Set fso = CreateObject("Scripting.FileSystemObject")
If fso.FileExists(OUTPUT_METADATA) Then
fso.DeleteFile(OUTPUT_METADATA)
debug.Log("Deleted: " + OUTPUT_METADATA)
end if
If fso.FileExists(OUTPUT_CASEDATA) Then
fso.DeleteFile(OUTPUT_CASEDATA)
debug.Log("Deleted: " + OUTPUT_CASEDATA)
end if
End Event
Page 10
Working with Open-Ended Answers
The NIPO DSC for IBM SPSS can automatically include answers to open-ended and semi-open ended
questions, both from NIPO ODIN scripts and Nvision Script / NIPO Diana job and variable files enriched with
open-ended answer files from the NIPO Fieldwork System. Open-ended answers result in IBM SPSS
application as Text type variables.
Using Open-Ended Answers on Data from NIPO ODIN Script

» To include open-ended answers in data opened in IBM SPSS applications
1. Place the open-ended answer file (*o file) in the same folder as the *.DAT and *.VAR files that
were exported directly from the NIPO ODIN Developer. Ensure the file name consists of the survey
name, without extension but appended with an O. For example, for a survey with data file
PROJECT.DAT and variable definition file PROJECT.VAR, the open-ended answer file must be
named PROJECTO.
2. Proceed to open the file in your application of choice (see "Opening NIPO Software Data in IBM SPSS
Applications" on page 7).
Using Open-Ended Answers on Data from NIPO Diana /

Nvision Script
Note:
This section is recommended for experienced users of Nvision Script or NIPO Diana.
Nvision Script / NIPO Diana lists does not make a semantic difference between coded questions and
open-ended answer questions. Assuming the variable definition file was not exported using the NIPO ODIN
Developer, you must add special directives to the variable definition file to ensure the data can be opened
in IBM SPSS applications.
Page 11
» To include open-ended answers on data from NIPO Diana / Nvision Script

1. To include open-ended answers in data opened in IBM SPSS applications, place the open-ended
answer file (*o file) in the same folder as the *.JOB, *.DAT and *.VAR files that were created
with Nvision Script / NIPO Diana. The filename used to access the file is the last file name used by the
*.JOB file, without extension but appended with an O. For example, for a job file that last opened a
file called PROJECT.DAT, the open-ended answer file must be named PROJECTO. If no job file
exists, the name of the data file is used.
2. Open to edit all variable definition files (*.VAR) and look up variable definitions that contain a
position reference that is matched by the open-ended answer file. A variable is defined by using an
asterisk (*) at the beginning of a line, immediately followed by the variable name.
*V100 *MV 61L29

%V100: Can you make any suggestions on how the company may improve their
customer service?
3. Insert COM QTYPE:OPEN below the variable definition:
*V100 *MV 61L29

COM QTYPE:OPEN
%V100: Can you make any suggestions on how the company may improve their
customer service?
4. Repeat steps 2-3 for all variables that require a label for missing values. Save the *.VAR file(s) and
close the editor.
Page 12
Working with Missing Case Values
In NIPO Software data, missing case values are represented by blanks in the data. No category for missing
case values is available unless it is explicitly created in the NIPO Software data files. If required, the NIPO
DSC for IBM SPSS can automatically add categories for missing values when the data is opened in an IBM
SPSS application. These categories appear with a "No answer" label.
This may be done in two ways:
 You can select to automatically add categories for missing case values in variables, and optionally mark
the variables that do not require categories for missing case values. This is appropriate if categories for
missing values are a requirement to work with the data.
 You can select to automatically add categories for missing case values in variables only if those variables
have been marked to include categories for missing case values. This is appropriate if categories for
missing values are required only by exception.
Both methods are described in this section.
Adding Missing Case Value Categories as a Rule

To add missing case value categories to variables you need to change the configuration of the NIPO DSC for
IBM SPSS. Optionally you can mark variables that should not receive a missing case value category.
Page 13
» To add missing case value categories to variables as a rule

1. Click Start > Program Files > NIPO Software > NIPO DSC for IBM SPSS > Configure NIPO DSC for IBM
SPSS. A settings panel appears:
1. At Add 'No Answer' Category, ensure Only when #COUNTBLHOR (#HBT) is not used is selected.
2. Click OK. Proceed to open the file in your application of choice (see "Opening NIPO Software Data in
IBM SPSS Applications" on page 7).
To mark exceptions, you need to make modifications to the NIPO Software variable definition file (*.VAR)
before opening the file in an IBM SPSS application.
Page 14
» To mark variables that should not receive a missing case value category
1. Open the Nvision Script / NIPO Diana VAR file in a text editor of your choice.
2. Search for the variables that should not have a category for missing case values. A variable is defined
using an asterisk (*) at the beginning of a line, immediately followed by the variable name. Below is
an example of a variable defining the respondent's age, in which V10 is the variable name.
*V10 *SNG 61L1: What is your age?

1: 16-34
2: 35-44
3: 45-54
4: 55-64
5: 65+
3. Insert the text OPT #HBT directly below the lines containing the variable label, but before the
answer categories if these are available.

OPT #HBT
1: 16-34
2: 35-44
3: 45-54
4: 55-64
5: 65+
4. Repeat steps 2-3 for all variables that should not have a label for missing values. Save the VAR file
and close the editor.
Adding Missing Case Value Categories by Exception

To add missing case value categories by exception, you need to change the configuration of the NIPO DSC
for IBM SPSS and mark the variables for which you require missing case value categories.
Page 15
» To add missing case value categories by exception

Page 16
2. At Add 'No Answer' Category, ensure Only when COUNTBLHOR (HBT) is used is selected.
3. Click OK.
4. Open the Nvision Script / NIPO Diana VAR file in a text editor of your choice.
5. Search for the variables that need a category for missing case values. A variable is defined by using
an asterisk (*) at the beginning of a line, immediately followed by the variable name. Below is an
example of a variable defining the respondent's age, in which V10 is the variable name.

1: 16-34
2: 35-44
3: 45-54
4: 55-64
5: 65+
6. Insert the text OPT HBT directly below the lines containing the variable label, but before the answer
categories if these are available.

OPT HBT
1: 16-34
2: 35-44
3: 45-54
4: 55-64
5: 65+
7. Repeat steps 5-6 for all variables that require a label for missing values. Save the *.VAR file and
close the editor.
Page 17
Working with Hierarchical Data
IBM SPSS Data Collection Survey Reporter and IBM SPSS Data Collection Survey Tables support hierarchical
data (HDATA) views, which enables variables to be presented in relationship to each other. Using the NIPO
DSC for IBM SPSS, NIPO Software data offers two types of hierarchical data views:
 Tables, which are typically used for variables that come from questions in loops (NIPO ODIN *REPEAT
command).
 Grids, which are typically used series of variables using the same set or type of answers (NIPO ODIN
*FORM question).
The NIPO DSC for IBM SPSS supports nested tables and grids.
Hierarchical data structures can be applied by either editing the NIPO ODIN script before the variable export
or by editing the Nvision Script / NIPO Diana variable definitions. Both methods are discussed in this
section. Editing the NIPO ODIN questionnaire is the recommended format, since the export produces the
required Nvision Script / NIPO Diana syntax.
Before you continue, make sure Hierarchical Data Structures are enabled in the NIPO DSC for IBM SPSS:
» To enable using hierarchical data structures
2. Ensure Apply Hierarchical Data Structure(s) when available is checked.

3. Click OK. Any Hierarchical Data structures defined within the variable definitions will now be used
when the variable file is loaded into an IBM SPSS application.
Page 19
Adding Hierarchical Data in NIPO ODIN

This section is primarily intended for the NIPO ODIN script programmer.
NIPO ODIN generates Hierarchical Data information automatically where the *TABLE command has been
specified. It creates a grid or a table dependent on the context in which the command was applied. The
*TABLE command is an export option only and does not affect execution of the questionnaire.
Note:
NIPO ODIN Developer 5.16.006 or later (with integrated NIPO ODIN parser 1.13.001 or later) must be
used in combination with the NIPO DSC for IBM SPSS 2.0.
Do not use Hierarchical Data commands on scripts that are to be deployed in the NIPO Fieldwork
System or the NIPO CAPI System. These systems generate a syntax error on the *TABLE command.
Instead, it is highly recommended to insert *TABLE commands on a copy of the questionnaire file.
Adding Tables
In NIPO ODIN script, tables are created from repetition blocks. Tables are created using the *TABLE
command. The *TABLE command is placed inside the repeat block. It takes a text as the parameter that
must contain the name of the table and the current horizontal iteration against which the set of questions
are asked. Tables themselves may embed grids.
Example NIPO ODIN script REPEAT BLOCK
The following example creates a table called "Rating" with 4 brands horizontally and 2 questions vertically.
The *TABLE command sets the horizontal iteration texts, while the *LABEL directives are used to
generate the vertical variable texts.
*TEXTVARS Brand
*REPEAT 4
*REPNUM 1: *PUT Brand "Grolsch"
*REPNUM 2: *PUT Brand "Hertog Jan"
*REPNUM 3: *PUT Brand "Amstel"
*REPNUM 4: *PUT Brand "Leeuw"
*TABLE "Rating *? Brand"
*QUESTION 5 *CODES L1 *LABEL "Taste experience"

For *? Brand, please mark your overall taste experience:
1: Good
2: Above average
3: Average
4: Below average
5: Bad
*Q 10 *CODES L1 *LABEL "Drinks weekly"

Do you drink *? Brand on a weekly basis?
1: Yes
2: No
*ENDREP
Page 20
Requirements
 The *TABLE command must be used before the first question in the *REPEAT block
 The parameter for the *TABLE must be fixed text. It cannot start with a text substitution (*?).
In NIPO ODIN script, tables are also created from Matrix questions. Tables are created using the *TABLE
command. The *TABLE command is placed below the Matrix question. It takes a text as the parameter
that must contain the name of the table.
Example NIPO ODIN script MATRIX
The following example creates a table called "Rating" with 4 brands horizontally and 2 questions vertically.
The *TABLE command sets the horizontal iteration texts, while the *LABEL directives are used to
generate the vertical variable texts.
*QUESTION 1 *CODES L4 *MULTI
Which of the following beers do you drink?
1: "Grolsch"
2: "Hertog Jan"
3: "Amstel"
4: "Leeuw"
*MATRIX 4 Q1 W *FIELD L8
*TABLE "Rating"
*QUESTION 5 *CODES L1 *LABEL "Taste experience"
Please rate your overall taste experience:
1: Good
2: Above average
3: Average
4: Below average
5: Bad
*QUESTION 10 *CODES L1 *LABEL "Drinks weekly"
Do you drink this on a weekly basis?
1: Yes
2: No
*ENDMATRIX
Requirements
 The *TABLE command must be used right after the *MATRIX command
 The parameter for the *TABLE must be fixed text. It cannot start with a text substitution (*?).
Adding Grids
In NIPO ODIN script, grids are created from *FORM questions. The NIPO DSC for IBM SPSS mimics the
structure of the *FORM question in order to display the grid: horizontal fields are placed as columns, while
the vertical categories are placed as rows. The *SCALE command generates a scale using the header texts
as horizontal iterations.
For grids, the *TABLE command is placed on the *FORM question definition. No parameter is used. The
standard export name or the defined export variable name for the question is used. You may also use a
*LABEL to set the grid's label text.
Example NIPO ODIN script using scales
The following example creates a grid with the name "ConsumptionRate" with a text label "Weekly
Consumption rate". The grid contains the 5 scales horizontally against the the 5 brands vertically.
*TAB 40,50,60,70,80
*QUESTION 4 *FORM *TABLE *LABEL "Weekly Consumption Rate" *VAR "ConsumptionRate"

Please state how often you drink any of the brands on a weekly basis.
Drink often» Drink sometimes» Drink not very often» Do not drink at all» Don't
know»»
1: Heineken» *SCALE L1 5 5»
Page 21
2: Grolsch» *SCALE L1 5 5»
3: Hertog Jan» *SCALE L1 5 5»
4: Amstel» *SCALE L1 5 5»
5: Leeuw» *SCALE L1 5 5»
*ENDREP
Example NIPO ODIN script using multiple horizontal fields

The following example results in a grid with the name "V10" and the text label "Average beer consumption
rate" The grid contains quantity and price per unit horizontally against the 5 brands vertically.
*Q 10 *FORM *TABLE
Average beer consumption rate
» Quantity» Price per unit (€)»
1: Heineken» *NUMBER L2» *NUMBER L1.2»
2: Grolsch» *NUMBER L2» *NUMBER L1.2»
3: Hertog Jan» *NUMBER L2» *NUMBER L1.2»
4: Amstel» *NUMBER L2» *NUMBER L1.2»
5: Leeuw» *NUMBER L2» *NUMBER L1.2»
Requirements
 The vertical categories must be preceded by category numbers.
 Fields in the same column must all be of the same type and size.
Adding Hierarchical Data in Nvision Script / NIPO Diana

Note:
This section is recommended for experienced users of Nvision Script or NIPO Diana.
To apply Hierarchical Data structures to Nvision Script / NIPO Diana, the variable definition file(s) (*.VAR)
must be edited before the data is loaded in an IBM SPSS application. Hierarchical Data structures are
applied by specifying comments below the variable definition using the comment (COM) keyword. The NIPO
DSC for IBM SPSS uses these comments to apply hierarchical data structures when data is being loaded in
an IBM SPSS application. The comments are ignored in Nvision Script / NIPO Diana job execution.
Comments are placed directly below the variable definition:
Example Nvision Script / NIPO Diana variable definitions
*V4_1 *SNG 73L1: Please state your rate of satisfaction on the following items
COM SPSSGRID:Satisfaction,GN:4,GI:1,QC:"Consumptions on offer"
1:Very satisfied
2:Satisfied
3:Neither Satisfied nor unsatisfied
4:Unsatisfied
5:Very unsatisfied
*V5_1 *SNG 65L1: Mercedes ownership

COM SPSSTABLE:Rating,AN:4,AI:2,QN:2,QI:1,QT:"Mercedes ownership"
Comments must use either a GRID or a TABLE specification which will result in a grid or table respectively.
Both specifications are discussed in this section.
Page 22
Adding Tables
A table represents the answers to a number of questions vertically against a fixed number of iterations
horizontally. With NIPO Software data a table is typically useful for representing a list of questions that
came from a repetition block.
An IBM SPSS table has a name, a label, a fixed number of questions vertically, and a fixed set of iterations
horizontally.
Syntax
COM SPSSTABLE:<tablename>,<AN:iterations>,<AI:current>,<QN:questions>
<QI:question>[,QT:"Label"][,QC:"Iteration Text"]
tablename
The table's name. Must be valid IBM SPSS syntax for a table name.
AN:iterations
Total number of iterations (columns) in the table. Must be the same value for all variables in this table.
AI:current
Specifies which iteration number the current variable applies to, in other words, the horizontal position of
the iteration. Must be unique within the table.
QN:questions
Total number of questions (rows) in the table. Must be the same value for all variable definitions in this
table.
QI:question
The current question in the table, in other words, the vertical position of the question in the table. Must be
unique within the table.
QT:"Label"
Defines the label for the question (row) variable. Only the first defined label for the row is used, it may be
omitted for the remaining variables that belong to the row. If omitted entirely, the Nvision Script / NIPO
Diana variable label is used.
QC:"Iteration text"
The text of the current iteration in the table. If omitted, the iteration number is used. The iteration text only
needs to be defined once for a certain iteration number, as it is used for all row variables.
The variable categories need to be defined only once, as they are assumed to be the same for all variables
in the grid.
Requirements
 Each SPSSTABLE definition must include the table's name, total number of iterations, the current
iteration, the total number of questions and the current question.
 All questions (rows) must use at least one variable. If a table is listed to contain 5 questions, the NIPO
DSC for IBM SPSS expects to find at least 5 variables that have been defined to be part of the table.
However, not all iterations need to be defined. Missing iterations result as "undefined" in the output.
 All questions on a single row must be of the same type. If the question has a category list, then the first
category list encountered for the question on the row is used.
 The iteration number for each variable must be unique in the grid. No two variables in a grid can have
the same iteration number.
 The variable name for the IBM SPSS variable for a question index is the name of the first (alphabetically
ordered) NIPO Diana / Nvision Script variable for this question index.
Tables, like repetition blocks, may be nested in other tables. Multiple SPSSTABLE commands are allowed
within the variable comment - the first specifies the root level table, the second the table within the root
level table, et cetera.
Page 23
Table example
The following example results in a table called "Rating" containing two questions vertically against 4 brands
iterated horizontally.
*V10_1 *SNG 62L1: BMW ownership
COM SPSSTABLE:Rating,AN:4,AI:1,QN:2,QI:1,QT:"BMW ownership"
1:Yes
2:No
*V20_1 63L2
COM SPSSTABLE:Rating,AN:4,AI:1,QN:2,QI:2
%V20_1: How would you rate BMW as a brand on a scale of 1 to 10?
*V10_2 *SNG 65L1: Mercedes ownership

COM SPSSTABLE:Rating,AN:4,AI:2,QN:2,QI:1,QT:"Mercedes ownership"
*V20_2 66L2
%V20_2: How would you rate Mercedes as a brand on a scale of 1 to 10?
*V10_3 *SNG 68L1: Audi ownership

COM SPSSTABLE:Rating,AN:4,AI:3,QN:2,QI:1,QT:"Audi ownership"
*V20_3 69L2
%V20_3: How would you rate Audi as a brand on a scale of 1 to 10?
*V10_4 *SNG 71L1: Volkswagen ownership

COM SPSSTABLE:Rating,AN:4,AI:4,QN:2,QI:1,QT:"Volkswagen ownership"
*V20_4 72L2
%V20_4: How would you rate Volkswagen as a brand on a scale of 1 to 10?
Adding Grids
Grids present a number of questions vertically against a set list of categories horizontally. With NIPO
Software data a grid is typically useful for representing a grid of scales.
An IBM SPSS grid has a name, a label, and a fixed number of iterations vertically, and a fixed set of
categories horizontally.
Syntax
COM
SPSSGRID:<gridname>,<GN:iterations>,<GI:current>[,QT:"Label"][,QC:"Iterat
ion text"]
gridname
The grid's name. Must be valid IBM SPSS syntax for a grid name.
GN:iterations
Specifies the number of iterations in the grid. Must be the same value for all variable definitions in this grid.
GI:current
Specifies which iteration number the current variable applies to. This number must be unique within the
grid.
QT:"Label"
Defines the label for the grid. Only the first defined label for the grid is used, it may be omitted for the
remaining variables that belong to the grid. If omitted entirely, the Nvision Script / NIPO Diana variable label
is used.
QC:"Iteration text"
The text of the current iteration in the grid.
Page 24
The variable categories need to be defined only once, as they are assumed to be the same for all variables
in the grid.
Requirements
 All variables in a single grid must be of the same type.
 Each SPSSGRID definition must include the grid's name, total number of iterations, and the iteration
this variable is in.
 All iterations must be specified. If a grid is listed to contain 5 iterations, the NIPO DSC for IBM SPSS
expects to find 5 variables that have been defined to be part of the grid.
 The iteration number for each variable must be unique in the grid. No two variables in a grid can have
the same iteration number.
Grid example
The following example results in a grid called "Satisfaction" with the label "Drink" with 4 iterations.
*V4_1 *SNG 73L1: Please state your rate of satisfaction with the following drinks:
COM SPSSGRID:Satisfaction,GN:4,GI:1,QT:"Drink",QC:"Heineken"
1:Very satisfied
2:Satisfied
3:Neither Satisfied nor unsatisfied
4:Unsatisfied
5:Very unsatisfied
COM SPSSGRID:Satisfaction,GN:4,GI:2,QC:"Amstel"
COM SPSSGRID:Satisfaction,GN:4,GI:3,QC:"Grolsch"
COM SPSSGRID:Satisfaction,GN:4,GI:4,QC:"Hertog Jan"
To place grids in a table, the SPSSTABLE and SPSSGRID parameters must be specified in the same
comment:
Syntax for an SPSSGRID in an SPSSTABLE
COM SPSSTABLE:<tablename>,<AN:iterations>,<AI:current>,<QN:questions> \
<QI:iteration>[,QT:"Label"][,QC:"Iteration Text"] \
SPSSGRID:<gridname>,<GN:iterations>,<GI:current>[,QT:"Label"][,QC:"Iteration text"]
Page 25
Working with Job Files
This section is primarily intended for the Nvision Script / NIPO Diana user who provides data files to the
data analyst.
With the NIPO DSC for IBM SPSS, the data analyst can open job files instead of data and variable files
directly in IBM SPSS applications. The data and variable sets loaded or produced by the job file are made
available as a single data set in the IBM SPSS application. This offers several possibilities for "just-in-time"
data manipulation and enrichment:
 You can easily combine several data files using the DEFINE (Nvision Script) or DE (NIPO Diana)
directives, thereby accessing several data sources as if they were contained within a single file.
 You can load several variable sets at once using the DEFVAR (Nvision Script) or DV (NIPO Diana)
directives, making all of the contained variables accessible in your IBM SPSS application as if they were
contained within a single file.
 You can access and retrieve information coming from sources contained within database tables.
 You can sort and merge data files before accessing the data in your IBM SPSS application.
 You can apply any kind of data transformations using Typologies to clean or modify data in any sense
required.
With careful preparation, using JOB files you can pull and adjust data from various sources of continuous
fieldwork and unify these every time the file is accessed.
Note:
The IBM SPSS applications open the data in read-only mode. The original job, variable and data files
are never modified.
Job Requirements
To successfully open data and variable files in IBM SPSS applications, the job file has the following
requirements:
 It must load at least one data file or open one database table for reading.
 It must define variables or load a variable file.
The last data file opened in the Nvision Script / NIPO Diana file is the data file to be accessed by the IBM
SPSS application. All variables defined or loaded within the scope of the job are used as the variable map.
The following is a valid job file that can be used with the NIPO DSC for IBM SPSS:
DEFINE C:\MyProject\project.dat
DEFVAR C:\MyProject\project.var
You can combine several files into one in a single job file:
DEFINE C:\MyProject\wave1.dat+C:\MyProject\wave2.dat+C:\MyProject\wave3.dat
DEFVAR C:\MyProject\project.var+C:\Defaults\Background.var
In addition, you can perform data transformations and enrichment using sorting, merging and Typologies.
When Typologies are executed by the job, the output file last opened, sorted or written is the data file
accessed by the IBM SPSS application.
Page 27
Recommendations when creating job files

 Execution of a job file has no visible output. Therefore, any output normally directed towards the
screen, such as charts or graphs, is ignored.
 Job files are executed using the working directory of the IBM SPSS application. Therefore, depending on
the location of the job file and the files it attempts to read or write, the relative file paths may not
resolve correctly. It is highly recommended to use full file paths in Nvision Script / NIPO Diana job files.
Page 28
NIPO DSC for IBM SPSS Configuration
The NIPO DSC for IBM SPSS applies the following default configuration. The defaults apply to data opened in
all IBM SPSS products.
NIPO DSC for IBM SPSS defaults
 No categories are added to count blank ('no answer') values
 No axis lines are created
 No NIPO Software system variables are included
 No hierarchical data structures are applied, even if available in the variable definitions.
Note:
The defaults may have been changed by the administrator who installed the software.
The default settings may be changed according to your requirements. This section deals with advanced
configuration of the NIPO DSC for IBM SPSS using the settings panel.
NIPO DSC for IBM SPSS Settings Panel

Before opening the NIPO Software data in an IBM SPSS application, verify and change the settings below
according to your requirements. The settings apply to all projects and all IBM SPSS products supporting the
IBM SPSS Data Collection Data Model.
» To access and change the NIPO DSC for IBM SPSS settings panel
2. Change the configuration options as required and click OK to save the configuration options. The
settings apply when a NIPO Software data set is next opened in an IBM SPSS application.
Log Directory
The log folder where the NIPO DSC for IBM SPSS stores log files for using NIPO Software data files. This
setting can only be changed by an administrator during installation. These files may be requested by the
NIPO Software Helpdesk for investigation in case of technical issues. Files are stored with the name
NipNvDscActionsLog.nnn where nnn is the log number (NipNvDscActionsLog.001 is always
the latest log file).
Log Level
The level of detail of the log levels. Can only be set by the administrator during installation.
Add 'No Answer' Category
Specifies whether or not the variable definitions should contain a category for missing case values:
Page 29
 Never. No category is created and missing case values are ignored.

 Only when COUNTBLHOR (HBT) is used. The 'No Answer' category is created only if the variable
definition in the VAR file contains the HBT option (see "Adding Missing Case Value Categories by
Exception" on page 15).
 Only when #COUNTBLHOR (#HBT) is not used. The 'No Answer' category is created always unless the
variable definition uses the #HBT option (see "Adding Missing Case Value Categories by Exception" on
page 15).
Axis properties
IBM SPSS Data Collection Survey Tabulation and IBM SPSS Data Collection Survey Reporter Professional may
use axis expressions to define categories for certain kinds of variables. The settings in this section enable
and affect the axis expressions.
Use axis lines
Sets whether or not to include axis expressions. Enabling axis lines includes the label defined for the total
number of respondents for the variable in Nvision Script / NIPO Diana. By default this is "Sample size". A job
file may set a different label.
 Add Stat lines
Adds the Nvision Script / NIPO Diana defined labels for various statistical reporting options (REPOPT)
applied to the variable, for example mean, chi square, gamma and median values.
 Add Total Answers for Multiple Variables. Adds Nvision Script / NIPO Diana defined label for the total
number of answers to the axis expression.
Add System Variables
If set, the NIPO Software system variables (such as INTNR, SCRCNT and CHANNEL) are included in the
result data.
Apply Hierarchical Data Structure(s) when available
Apply hierarchical data structures if these are available in the variable definitions (see "Working with
Hierarchical Data" on page 19).
Changing the Configuration in mrScriptBasic

The settings configured in the NIPO DSC for IBM SPSS settings panel (see "NIPO DSC for IBM SPSS Settings
Panel" on page 29) apply to all data sets opened with an IBM SPSS application. Users of IBM SPSS Data
Collection Base Professional can override these settings in a mrScriptBasic file, ensuring that data is always
opened using the required settings. Settings are changed in the ConnectionString of the
InputDataSource method.
Example mrScriptBasic file using NIPO Software data as the input source
#define INPUT_METADATA root + "project.var"
MR Init MDSC=nipNvDsc; _
MR Init Custom=' _
AddAxis=0; _
AddStatLines=0; _
AddSystemVariables=0; _
AddTotalAnswers=0; _
NoanswerIndication=0; _
UseHDATA=0'"
End InputDataSource
Page 30
NIPO DSC for IBM SPSS Configuration
TThe script above loads the file project.var (and implicitly project.dat and optionally projecto)
from C:\MyProjects and applies the settings as provided in the ConnectionString. The data is
transformed into meta data files project_out.ddf and project_out.mdd. The settings applied in
the example are the default settings.
Alternatively, an Nvision Script / NIPO Diana job file can be loaded as the Initial Catalog file. The job
file is assumed to define the data files and variable files.
Note:
It is recommended to always specify all settings in the custom settings of the
ConnectionString.
Custom NIPO DSC for IBM SPSS data source settings

Setting Function
AddAxis Enables axis lines on the variables (0=no, 1=yes)
AddStatLines Add statistic lines to variables (0=no, 1=yes)
AddSystemVariables Add NIPO Software system variables (such as INTNR,
SCRCNT and CHANNEL) are included in the result data
(0=no, 1=yes)
AddTotalAnswers Add axis lines for total number of answers and total number
of respondents to the axis (0=no, 1=yes)
NoanswerIndication Specifies whether or not the variable definition should have
a value label for missing values (0=never, 1=Only when
COUNTBLHOR (HBT) is used, 2=Only when
#COUNTBLHOR (#HBT) is not used)
UseHDATA Apply Hierarchical Data structures if these are available in
the variable definitions (0=no, 1=yes)
Page 31
Variable Translation
This section provides a brief overview of how NIPO ODIN question types and Nvision Script / NIPO Diana
variables are translated into IBM SPSS types.
Question type and variable translation in the NIPO DSC for IBM SPSS
NIPO ODIN question type Nvision Script / NIPO Diana variable IBM SPSS type
*CODES question with categories, Single-coded variable (variable definition Categorical variable.
not *MULTI containing *SINGLE / *SNG) with categories
*CODES question without categories Single-coded variable (variable definition Integer variable.
(typically a *DUMMY question), not containing *SINGLE / *SNG) without categories,
*MULTI no decimal places, up to nine digits
*CODES question using *MULTI Multiple-coded variable (any variable definition Categorical variable.
without *SINGLE / *SNG but with one or more
categories).
Question using *NUMBER Numerical variable (variable without type Long variable.
specification and without categories)
Question using *ALPHA Text variable (*TEXT / *TEK) without categories Text variable. The length of the field is set
to the length defined in the Nvision Script /
NIPO Diana variable.
Question using *OPEN Numerical variable (variable without type Text variable.
specification and without categories) using the
QTYPE:OPEN comment
*CODES question using *BUT Categorical variable. The codes defined
with *BUT are added as categories to the
variable.
*OPEN and *NUMBER question using Text or Long variable respectively with a
*BUT categorical helper field containing all defined
buttons as categories.
Compound variable consisting of categories using Several Categorical variables with an
code references, the!C operator or the %operator iteration number. The number of variables
using category references created depends on the number of
categories in the Nvision Script / NIPO Diana
variable.
Compound variable consisting of one or more Long variable. The value is set to the value
categories using the !V or !W operator or the % of the first category in the Nvision Script /
operator without category references NIPO Diana variable.
Compound variable consisting of categories using Several Categorical variables with an
a combination of %, !C and !V or !W operators iteration number. The number of variables
created depends on the number of
categories in the Nvision Script / NIPO Diana
variable.
Categorical. Nvision Script / NIPO Diana
categories using the !V or !W operators or
the % operator without category references
are not included as IBM SPSS variable.
Note:
Incorrect variable definitions in Nvision Script / NIPO Diana variable files are ignored and do not
appear in the variable map.
Page 33
Index
A U
Adding Grids ................................................................... 21, 24 Using Open-Ended Answers on Data from NIPO Diana /
Adding Hierarchical Data in NIPO ODIN ................................ 20 Nvision Script ................................................................... 11
Adding Hierarchical Data in Nvision Script / NIPO Diana....... 22 Using Open-Ended Answers on Data from NIPO ODIN Script11
Adding Missing Case Value Categories as a Rule ................... 13
Adding Missing Case Value Categories by Exception ............ 15 V
Adding Tables.................................................................. 20, 23
Variable Translation ............................................................. 33
C
W
Changes in NIPO DSC for IBM SPSS 2.00 ................................. 2
Changes in NIPO DSC for IBM SPSS 2.00.001 .......................... 2 Working with Hierarchical Data ............................................ 19
Changes in NIPO DSC for IBM SPSS 2.00.002 .......................... 2 Working with Job Files .......................................................... 27
Changes in NIPO DSC for IBM SPSS 2.00.003 .......................... 2 Working with Missing Case Values ....................................... 13
Changes in NIPO DSC for IBM SPSS 2.00.005 .......................... 2 Working with Open-Ended Answers..................................... 11
Changing the Configuration in mrScriptBasic ........................ 30
Contacting NIPO Software Sales ............................................. 2 Y
Contacting the NIPO Software Helpdesk................................. 3
Your Feedback on this Guide .................................................. 3
Contacting Us .......................................................................... 2
I
IBM SPSS Data Collection Base Professional ........................... 9
IBM SPSS Data Collection Survey Reporter ............................. 9
IBM SPSS Statistics and PASW SPSS Statistics ......................... 7
Included in This Release .......................................................... 1
Installing the NIPO DSC for IBM SPSS ...................................... 5
Introduction ............................................................................ 1
J
Job Requirements ................................................................. 27
K
Known Issues and Incompatibilities ........................................ 4
N
NIPO DSC for IBM SPSS Configuration ................................... 29
NIPO DSC for IBM SPSS Settings Panel .................................. 29
NIPO DSC for IBM SPSS Version History .................................. 2
Not Included in This Release ................................................... 1
O
Opening NIPO Software Data in IBM SPSS Applications .......... 7
P
Prerequisites ........................................................................... 5
R
Running the Installer ............................................................... 6
S
Supported IBM SPSS Products ................................................ 1
System Requirements ............................................................. 5
T
Typographical Conventions ..................................................... 3
Page 35
NIPO Software is a specialist software supplier to the market research industry. We
focus on adding value to our customers’ businesses. Today we serve over 200
companies all over the world. We have developed multiple industry standards
and we keep innovating to this day.
your challenge | our solution
NIPO Software
Grote Bickersstraat 74
1013 KS Amsterdam
The Netherlands
http://www.niposoftware.com
info@niposoftware.com
Page 36

Limbă

Bine ați venit la Scribd!

Manual Bloquera Ceta-ram

Încărcat de

Informații document

Descriere:

Data încărcării

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Descriere:

Drepturi de autor:

Formate disponibile

Manual Bloquera Ceta-ram

Încărcat de

Descriere:

Drepturi de autor:

Formate disponibile

Titluri conexe

NIPO DSC for IBM SPSS

Rev: 2 8-8 -20 15

Installing the NIPO DSC for IBM SPSS 5

Opening NIPO Software Data in IBM SPSS Applications 7

Working with Open-Ended Answers 11

Working with Missing Case Values 13

Working with Hierarchical Data 19

Working with Job Files 27

NIPO DSC for IBM SPSS Configuration 29

Supported IBM SPSS Products

Included in This Release

Not Included in This Release

NIPO DSC for IBM SPSS Version History

Changes in NIPO DSC for IBM SPSS 2.00.003

Changes in NIPO DSC for IBM SPSS 2.00.002

Changes in NIPO DSC for IBM SPSS 2.00.001

Changes in NIPO DSC for IBM SPSS 2.00

Contacting NIPO Software Sales

NIPO Software Sales Amsterdam

Contacting the NIPO Software Helpdesk

Your Feedback on this Guide

Step-by-step instructions to perform and complete a specific task.

NIPO Fieldwork System Technical Titles of software documentation.

Alt-F4 Names of keyboard keys and key combinations.

Known Issues and Incompatibilities

Running the Installer

IBM SPSS Statistics and PASW SPSS Statistics

IBM SPSS Data Collection Survey Reporter

IBM SPSS Data Collection Base Professional

Example mrScriptBasic removing existing output files

Using Open-Ended Answers on Data from NIPO ODIN Script

Using Open-Ended Answers on Data from NIPO Diana /

» To include open-ended answers on data from NIPO Diana / Nvision Script

*V100 *MV 61L29

*V100 *MV 61L29

Adding Missing Case Value Categories as a Rule

» To add missing case value categories to variables as a rule

*V10 *SNG 61L1: What is your age?

*V10 *SNG 61L1: What is your age?

Adding Missing Case Value Categories by Exception

» To add missing case value categories by exception

*V10 *SNG 61L1: What is your age?

*V10 *SNG 61L1: What is your age?

2. Ensure Apply Hierarchical Data Structure(s) when available is checked.

Adding Hierarchical Data in NIPO ODIN

*TABLE "Rating *? Brand"

*QUESTION 5 *CODES L1 *LABEL "Taste experience"

*Q 10 *CODES L1 *LABEL "Drinks weekly"

*QUESTION 4 *FORM *TABLE *LABEL "Weekly Consumption Rate" *VAR "ConsumptionRate"

3: Hertog Jan» *SCALE L1 5 5»

Example NIPO ODIN script using multiple horizontal fields

» Quantity» Price per unit (€)»

1: Heineken» *NUMBER L2» *NUMBER L1.2»

2: Grolsch» *NUMBER L2» *NUMBER L1.2»

3: Hertog Jan» *NUMBER L2» *NUMBER L1.2»

4: Amstel» *NUMBER L2» *NUMBER L1.2»

5: Leeuw» *NUMBER L2» *NUMBER L1.2»

V100 MV 61L29

V100 MV 61L29

V10 SNG 61L1: What is your age?

V10 SNG 61L1: What is your age?

V10 SNG 61L1: What is your age?

V10 SNG 61L1: What is your age?

TABLE "Rating ? Brand"

QUESTION 5 CODES L1 *LABEL "Taste experience"

Q 10 CODES L1 *LABEL "Drinks weekly"

QUESTION 4 FORM TABLE LABEL "Weekly Consumption Rate" *VAR "ConsumptionRate"

1: Heineken» NUMBER L2» NUMBER L1.2»

2: Grolsch» NUMBER L2» NUMBER L1.2»

3: Hertog Jan» NUMBER L2» NUMBER L1.2»

4: Amstel» NUMBER L2» NUMBER L1.2»

5: Leeuw» NUMBER L2» NUMBER L1.2»

V5_1 SNG 65L1: Mercedes ownership

V10_2 SNG 65L1: Mercedes ownership

V10_3 SNG 68L1: Audi ownership

V10_4 SNG 71L1: Volkswagen ownership