Terminology changes
includes a number of terminology changes from previous NVivo versions.
Node → Code
Early versions of NVivo used 'node' as a term for any item that could be coded to. This included 'theme nodes' and 'case nodes'. In version 12, 'case nodes' were referred to just as 'cases', but 'theme nodes', or just 'nodes' continued in use. With the transition is completed, with simply 'cases' and 'codes'.
Sets—static and dynamic
Previous Windows versions of NVivo had two types of 'set':
- 'sets' were manually selected groups of project items
- 'search folders' were groups of project items defined by search criteria (so new items could be automatically added as a project grew).
In the two types of set are known collectively as 'sets', and individually as 'static sets' (previously 'sets') and 'dynamic sets' (previously 'search folders').
NVivo Mac does not have dynamic sets, but uses 'static set' for consistency with Windows.
Reports—formatted and text
NVivo Windows produces formatted and non-formatted (text) reports.
In previous versions the collective name for the reports was 'output', with formatted reports called 'reports' and non-formatted reports called 'extracts'.
In the collective name is 'reports' and the two types: 'formatted reports' and 'text reports'.
Add to project
Some queries in NVivo allow you to save the query criteria, allowing you to run exactly the same query at a later time and see changes as a project develops. This is in contrast to saving query results, which are the output of a query run at a specific time.
In previous versions the button to save query criteria was labeled 'Add to Project'. This is changed to 'Save Criteria'.
NVivo Collaboration Server
NVivo for Teams has been renamed NVivo Collaboration Server. This Windows-only product for institutions is installed on a server in the institution's local network. Users connect to the server with standard client NVivo Windows applications.