text: For those of you still on NVivo 10 – it's definitely time to move on! As always with new releases, any NVivo 10 or 11 projects can be opened in the latest version of the software. There's no backwards compatibility though, so you'll need to stick with NVivo 12 once you've upgraded. NVivo quick reference (Mac) Boston University Educational Technology, Training and Outreach Help There are two places to go to for help with NVivo.
  NVivo projects created on the Mac platform have a different file format from those created in NVivo on the Windows platform. NVivo 11 for Mac (.nvpx). NVivo 11 for Windows (.nvp) You cannot open an NVivo 11 for Windows project (.nvp) in your NVivo for Mac software—you will need to convert it to the NVivo 11 for Mac format first. You can do this using the 'copy project' feature in NVivo 11 for Windows. You can also export selected items from an NVivo 11 for Windows project to a new NVivo for Mac (Version 11) project.
  You can open an NVivo for Mac (Version 11) project (.nvpx) in NVivo 11 for Windows and it will be converted into the NVivo 11 for Windows format for you. Alternatively, you can also import the content from an NVivo for Mac project into an NVivo for Windows project. If you want to convert an NVivo for Mac (Version 10) project to the NVivo 11 for Windows format, you must first using NVivo for Mac (Version 11), then convert the project using NVivo 11 for Windows. For detailed information on converting projects into the Mac format (by copying or exporting) refer to the. NVivo for Mac has a subset of the features available on NVivo 11 for Windows. If you convert your NVivo 11 for Windows project and access it on the Mac, you may not be able to work with all your project items. WARNING If a source in the original NVivo for Windows project contained 'see also' links, then do not edit the source in NVivo for Mac—otherwise, all 'see also' links in the source will be permanently deleted.
  Always ensure you are on the latest version of the software—future versions may address this limitation. Can I work with a project on Windows and Mac? It is possible to work with a project on both Windows and Mac (cross-platform), however, we recommend that you work with your project on a single platform due to some known limitations and issues.
  Refer to for more information. Can we work as a team with some users on Windows and others on Mac?
  We recommend that all team members use the same version of the software (and do not work cross-platform). Refer to for more information on known limitations and issues. Cross-platform limitations and issues There are some known limitations that you should consider before working on a project cross-platform:. The initial releases of NVivo for Mac have a subset of the features available on the NVivo 11 for Windows platform. If you convert your NVivo 11 for Windows project and access it on the Mac, you may not be able to work with all your project items. If a source in the original NVivo for Windows project contained 'see also' links, then editing the source in NVivo for Mac will cause the 'see also' links to be permanently deleted.
  File links must be updated each time you convert a project—refer to for more information. Some queries created in NVivo for Windows will not run in a converted project in NVivo for Mac. For more information, refer to. Project conversion can take a long time depending on the number of documents and PDFs and the amount of coding. We are working on compatible project file formats in the future that will not require conversion. In addition, you may experience the following issues when working with projects cross-platform:. A corrupt PDF file (that is, a PDF file that could not be opened with Adobe Reader) was successfully imported and coded in an NVivo for Windows project.
  However, the PDF could not be opened in a project converted to NVivo for Mac format. Certain documents in an NVivo for Mac project failed to convert when the project was converted to NVivo for Windows format. These documents also could not be exported from NVivo for Mac to.doc or.docx format. If you code documents that contain embedded images or complex tables in NVivo for Mac, and then open the project in NVivo for Windows, you may experience problems when you open the node. You can avoid these problems by converting documents with embedded images or complex tables into PDF files before importing them into your project.
  Executing multiple project conversions during the same session can slow the conversion process or cause the conversion to fail. Rebooting the computer between project conversion can improve performance. If you decide to work with a project cross-platform, knowing these limitations, we recommend that you import all sources into the Windows project.
  Furthermore, if you are working in a team, the Windows project should be the 'master project' because the Windows version of the software has the full feature set. Always ensure you are on the latest version of the software—future versions may address many of these limitations. Why does my converted Windows project look different on Mac? When you open a converted project in NVivo for Mac, items that are not supported on the Mac version of the software are hidden. If your project contains Search Folders or queries that are not yet available in the Mac version of the software (for example, compound queries), you will notice that:.
  You cannot see the Search Folders in Navigation View. You cannot see these queries in List View. Queries will only search items that are visible in your project.
  If the scope of a query is defined by a Search Folder it will not return any results. Annotations are only supported for documents, PDFs, externals and memos.
  If your project contains annotations in audios, videos, pictures or datasets, then you will notice that:. You cannot see these annotations in these sources. You cannot see these annotations in the Annotations folder of the Collections group. Other project items (for example, maps and reports) that are not available in the Mac version are also hidden. If you convert the project back into the Windows format, and open it in NVivo for Windows you will be able to see everything again.
  IMPORTANT Do not delete folders that appear to be empty when you are working with a converted project, because the folder may contain hidden project items. For example, framework matrices are not supported in NVivo for Mac, so a folder that only contains framework matrices will appear to be empty when viewed in NVivo for Mac. Understand why file links must be updated in converted projects The Windows and Mac operating systems use different formats for file links. This means that if you convert your Windows project and open it in NVivo for Mac (or vice versa), you will not be able to access linked files unless you update the file links. Within NVivo you can create links to files outside your project in the following ways:. External sources that link to a file. Audio and video sources with media files stored outside the project (not embedded).
  Hyperlinks within documents and memos to files When you convert a project from NVivo 11 for Windows to NVivo for Mac format, you will need to update the file links if you want to access the files. Understand why some queries will not run in converted projects If a converted project makes use of features not supported by NVivo for Mac, you may be prevented from running certain queries that were created in the Windows version. For example, you cannot run queries where the:.
  Scope of the query includes source types (for example, framework matrices) that are not currently supported in the Mac version. Scope of the query includes folders (for example, Search Folders, Node Matrices or Results) that are not supported as valid query options in the Mac version. Criteria of the query includes options that are not currently supported in the Mac version (for example, coded by a selected user). Text Search or Word Frequency query searches for synonyms, specializations or generalizations.
  Coding or Matrix Coding query searches using an unsupported operator (for example, NOT or NEAR). We recommend that you create new queries for your converted project within NVivo for Mac—refer to for more information. Why do Coding Comparison queries produce different results in a converted project? If a converted project has a Coding Comparison query, you may find that when you run the query in NVivo for Mac, you get different results than if you ran the query in NVivo 11 for Windows. Coding Comparison queries in NVivo for Mac currently support documents, memos, and externals as source types.
  Coding Comparison queries in NVivo 11 for Windows support additional source types—for example, pictures, audio and video. If the Coding Comparison query criteria is defined using All Sources, then the query results may be different in NVivo for Mac. NVivo 11 for Windows supports additional node types (relationships and sentiment nodes) that are not available in NVivo for Mac. If the original Coding Comparison query criteria is defined using All Nodes, then the query results may be different in NVivo for Mac.
  We recommend that you create new queries for your converted project within NVivo for Mac—refer to for more information. Can I work with Mac projects on NVivo Server? You cannot connect to NVivo Server from NVivo for Mac. If you have an NVivo Server project that you want to work with in NVivo for Mac, you need to convert it to NVivo for Mac format using NVivo 11 for Windows. If you have an NVivo for Mac project that you want to store on the server, you need to first convert the project to NVivo for Windows format using NVivo 11 for Windows. Related topics.
  . Create a new set and add members. On the Create tab, in the Collections group, click Set. Enter a name for the set. (Optional) Enter a description - for example, you could explain how you intend to use the set.
  Click Done. The new set is added to the Sets folder. On the Create tab in the Collections group, click Set and hold down the mouse button, and then click Add Set Members. Select the sources or nodes you want to add to the set, and then click Select. Select project items and create as a set You can create a set based on selected project items that are displayed in List View or Detail View—for example, find or query results.
  In List View or Detail View, select the items that you want to create as a set. On the Create tab in the Collections group, click Set and hold down the mouse button, and then click Create As Set. Enter a name for the set. (Optional) Enter a description - for example, you could explain how you intend to use the set. Click Done. Select project items and add to a set.
  In List View or Detail View, select the items that you want to add to a set. On the Create tab in the Collections group, click Set and hold down the mouse button, and then click Add To Set. Click the set you want to add the items to, and then click Select. Move set members from one set to another To move set members, select them in List View and do one of the following:. Drag and drop them into the required set. Copy the set members and move them to another set—on the menu bar, choose Edit Copy, select the new set (press the Option key) and click Move Here. Copy set members to another set.
  In List View, select the members you want to copy. On the Home tab, in the Clipboard group, click Copy. Keyboard shortcut To copy, press ⌘+C. In Navigation View click the new set. On the Home tab, in the Clipboard group, click Paste. Keyboard shortcut To paste, press ⌘+V. Sort the members of a set By default, members of a set are organized alphanumerically by Name in List View but you can.
  Sort members based on a property such as creation or modification date—click on the required column heading. Remove members from a set. In List View, select the members that you want to remove. On the Home tab, in the Editing group, click Delete. Keyboard shortcut: To delete the selected item, press DELETE.