Converting ATLAS.ti Projects to NVivo

ATLAS.ti projects (versions 5.2 and 5.5) can be converted to NVivo. To do this, you will need to first export the Hermeneutic Unit (HU) as an XML file (*.xml), including its Primary Documents (PDs) and Quotations (meta info only). When you open the ATLAS.ti XML file in NVivo, a new project is created with a .nvp extension—the original project is not overwritten.

Before exporting to XML from ATLAS.ti

In the ATLAS.ti HU, change any relative file-paths (HUPATH or TBPATH) of each PD to 'Absolute', e.g. C:\Documents and Settings\username\My Documents\PrimaryDocument1.doc. If not changed to 'Absolute' paths,NVivo will not be able to locate the files and the PDs will be converted to 'externals' —any coding will be discarded and the file path will simply be recorded in the external properties.

Also, make sure that the PDs are in the following formats:

These will be converted into sources (i.e. Documents, Audio, Video and Picture Sources) in NVivo.

If you have PDs that are in a format other than the ones listed above, these PDs will be converted to 'externals' in NVivo.

When you export an ATLAS.ti 5.2 HU to XML and import it to NVivo, any quotations for videos will automatically be converted. If you have opened your ATLAS.ti 5.2 HU in ATLAS.ti version 5.5 and it contains quotations for videos, you will need to open any .avi and .mpeg videos and play a segment before exporting the HU to XML. This will ensure that the quotations for videos will be converted correctly in NVivo.

Opening the ATLAS.ti XML file in NVivo

To open and convert the ATLAS.ti XML file:

  1. On the File menu, click Open Project.

The Open Project dialog box is displayed.

  1. From the Files of type drop-down list (at the bottom of the dialog box), select theAtlas XML Export (*.xml).

  1. Locate the folder that contains the project you want to convert.

  2. Click the required file.

  3. Click the Open button.

The Convert Project dialog box is displayed.

  1. Click the Browse button to choose the destination and enter a name for the converted project.

  2. Using the Save in drop-down list, click the destination folder for the newly created project.

  3. In the File name field, enter a name for the converted project.

  4. Click Save.

  5. Set any required Import Options  

    Option

    Description

     

    Code sources at cases

    Click this option to create a case for each primary document (PD) that is converted to a source. The case name is based on the PD name. Each PD, which is converted as a 'source' in NVivo, is coded at the case created for it.

    Import paragraph styles

    This option is not available when converting an ATLAS.ti XML file.

    Project requires a username, or username and password

    This option is not available when converting an ATLAS.ti XML file.

     

  6. Click the Convert button.

How ATLAS.ti elements are converted to NVivo project items

ATLAS.TI

NVivo

 Notes

 

HU exported as a single XML file

HU name is retained as the NVivo project name.

Text will be truncated during conversion if it contains more than 512 characters.

You can apply various settings to the converted project. For information, refer to Setting Project Properties.

 

ATLAS.TI

NVivo

 Notes

 

Text file

Document source

The source will contain the original content of the text file.

Audio file

Audio source

You will be able to play the media content within the created source but conversion will not embed the file within the NVivo project. The audio file will remain stored outside the NVivo project.

Video file

Video source

You will be able to play the media content within the created source but conversion will not embed the file within the NVivo project. The video file will remain stored outside the NVivo project.

Picture file

Picture source

The source will contain the image from the original picture file.

Memo promoted to PD

Memo

The promoted memo is not converted to a source 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.

If the file being converted is not found, is using an unknown file format or the file path is relative and begins with <HUPATH> or <TBPATH>, the files will be converted to an 'external'. For more information about externals, refer to About Internals, Externals and Memos.

If you selected the option 'Code sources to cases', the PDs will be converted to sources and a case will be created for each source. Both the source and case created will have the same name. The entire source will be coded to the case. For more information, refer to Creating Cases from Sources.

Comments will be converted as source descriptions and truncated if they contain more than 512 characters.

ATLAS.TI Elements

NVivo Project Items:

 Notes

 

Quotation

Node reference

All quotations created in PDs are converted as node references for the created sources in NVivo. The codes where they were linked to in ATLAS.ti are converted as free nodes in NVivo. See 'Codes and Families' for more information.

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 to a free node named 'Unused Quotations'.

Comment in a quotation

Annotation

Any comment created for the quotation is converted as an annotation for the source. For more information, refer to About Annotations.

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 source to the memo. For more information, refer to About See Also Links.

 

Free codes are converted to 'Free Nodes' in NVivo .A free node called "Unused Quotations" is created for quotations not mapped to any code in ATLAS.ti. For more information, refer to About Nodes.

Coding relations are converted to 'Relationship Types' in NVivo. For more information, refer to About Relationships.

Families are converted to 'Sets' in NVivo. For more information, refer to About Sets.

Memos are converted to 'Memos' in NVivo. For more information, refer to About Internals, Externals and Memos.

If a memo is linked to a free code in ATLAS.ti, a 'See Also' link will be used to relate the converted memo and node. For more information, refer to About See Also Links.

Items Not Converted

The following ATLAS.ti family types will not be converted:

 

Related Topics