Open and convert an ATLAS.ti project
ATLAS.ti projects (versions 5.2, 5.5, 6.0, 6.1, 6.2 and 7.0) can be exported to XML and then opened (and converted) in NVivo.
You will get best results, if you prepare the ATLAS.ti project for conversion before you export it to XML.
You can also import a project in .qdpx file format. REFI-QDA Standard for project exchange
Prepare an ATLAS.ti project
Before you export your ATLAS.ti project, you need to do the following:
- Check that Primary Documents (PDs) use 'absolute' file paths— for example, 'C:\Documents and Settings\username\My Documents\PrimaryDocument1.doc'. Change any relative file-paths (HUPATH or TBPATH) PDs with relative paths, will be converted to NVivo 'externals', coding will be discarded and the file path will be recorded in the external properties.
NOTE For ATLAS.ti 7, if the Primary Documents are stored in 'My Library' or 'Team Library', you do not need to do the above step.
- Check that PDs use supported file formats. Any PDs in unsupported formats will be converted to 'externals' in NVivo. Supported file formats are:
- Text files ( .doc, .docx, .rtf, .txt, .pdf)
- Audio files ( .mp3, .wma, .wav);
- Video files (.mpg, .mpeg, .mpe, .wmv, .avi, .mov, .qt., mp4);
- Image files( .bmp, .gif, .jpg, .jpeg, .tif, .tiff).
- If the Hermeneutic Unit (HU) contains .avi or .mpeg videos, check whether the HU was created in ATLAS.ti 5.2 and then opened in a later version—if so, you should open and play a segment of each video. This will ensure that the quotations for videos are converted correctly in NVivo.
- Export the Hermeneutic Unit (HU) as an XML file (*.xml), including its Primary Documents (PDs) and Quotations (meta info only). The exported XML file can be opened in NVivo.
Open (and convert) an ATLAS.ti XML file in NVivo
Once the ATLAS.ti project has been exported, it can be opened (and converted) in NVivo.
IMPORTANT Use the same computer (and user account) to export the XML file, and then to open and convert it in NVivo—so that NVivo can locate PDs that are stored in the file system.
- Click the File tab, and then click Open.
- Select ATLAS.ti XML Export (*xml) from the File or Project type list.
- Locate and select the project you want to open.
- Click Open. The Convert Project dialog box opens.
- Click Browse, and then choose where you want to save the converted project.
- Do one of the following:
- To save as a standalone project, select NVivo Projects (*.nvp ) from the Save as type list, and then enter a name for the converted project in the File name box.
- To save as an NVivo for Teams project, select NVivo Server Projects from the Save as type list, then select the server from the Connection name box, and then enter a name for the converted project in the Project name box.
- Click Save.
- Do one of the following:
- (Optional) Select the Code files at nodes check box, to create a node for each primary document (PD) that is converted to an NVivo file. The node name is based on the file name, and the file is coded at the node created for it.
- Click Convert.
A new NVivo project is created—ATLAS.ti PDs are converted to NVivo files, free codes are converted to nodes, and quotations are converted to node references.
- The Connection name box is empty if you have not set up any NVivo for Teams connections—click the Add button to create a new connection using the Connection Properties dialog box.
- If you cannot select NVivo Projects (*.nvp), check your connections. You need a standalone connection to create a standalone project saved to your computer or a network drive.
- If you receive a message indicating that you do not have permission to create a project on NVivo for Teams, verify with your NVivo for Teams administrator that you are in a user group that has permission to create new projects.
- Files that cannot be accessed will be imported into your NVivo project as 'externals'. However, paths to the files will still refer to their original location (for example, '\\All Users\\my_project_files\\'). Before you delete the ATLAS.ti project, you should copy these files to a different folder and update the file path or location within the NVivo externals. Externals
Hermeneutic Unit properties
|Comment||Project Description||The text will be truncated during conversion, if the comment is more than 512 characters.|
|Authors||Users||Any Authors (all those in the co-authors list as well as those assigned to objects but not present in the co-authors list) in the HU will be created as users in NVivo.|
Primary documents (PDs)
PDs are converted to files. However, in the following circumstances, PDs are converted to externals:
- PD cannot be found
- PD has unsupported file format (for example, live Google Earth™ documents *.kml, or *.kmz)
- PD has relative file path ( <HUPATH> or <TBPATH>)
Comments are converted to file descriptions and truncated if they contain more than 512 characters.
|Text files||Document file||Line numbering is not available in NVivo. If a text cannot be imported into NVivo for any reason, it is represented in NVivo by an external.|
|PDF files||PDF file||If a PDF cannot be imported into NVivo for any reason, it is represented in NVivo by an external.|
|Audio files||Audio file||You will be able to play the media content within the created file but conversion does not embed the file within the NVivo project. The audio file will remain stored outside the NVivo project. Only audio files in supported formats are converted. Files in other formats will be represented by an external in the NVivo project.|
You will be able to play the media content within the created file but conversion does not embed the file within the NVivo project. The video file will remain stored outside the NVivo project.
Only video files in supported formats are converted. Files in other formats will be represented by an external in the NVivo project.
Image files, including Google Earth™ snapshots
Only image files in supported formats are converted. Files in other formats will be represented by an external in the NVivo project.
Memo promoted to PD
The promoted memo is not converted to a document in NVivo, even if it is considered a PD in the ATLAS.ti HU. It is converted as a memo in NVivo and retains any coding references.
|Quotation||Node reference||Quotations created in PDs are converted to node references for the created files in NVivo. The codes which they were linked to in ATLAS.ti are converted as nodes in NVivo. Quotations in PDF files are not converted to node references. The quotations are provided in a linked memo, which lists the quotation and the approximate location of the quotation in the PDF. Quotations in Google Earth™ documents are not converted to node references. The quotations (with longitude and latitude) are provided in the external which represents the Google Earth™ document in NVivo.|
|Quotation not linked to any code||Node reference||If a quotation is not linked to any code in ATLAS.ti, then it will be converted as a node reference in a node named 'Unused Quotations'.|
|Comment in a quotation||Annotation||Any comment created for the quotation is converted as an annotation for the file.|
|Memo linked to a quotation||'See also' link||If a memo is linked to a quotation, a 'see also' link is created from the quoted text in the file to the memo.|
Codes and families
|Free code||Node||A node called 'Unused Quotations' is created for quotations not mapped to any code in ATLAS.ti. Code color attributes are converted to node colors—the ATLAS.ti color is converted to the closest NVivo color (blue, green, purple, orange, red, pink, or yellow).|
|Coding relations||Relationship Types|
ATLAS.ti elements that are not converted
The following ATLAS.ti family types are not converted:
- Super Code Family
- Super Memo Family
- Super Primary Document Family
- Network Views