Stage 1 · Getting startedTutorial 3 of 21 · 8 minutes · Written

Import a project from NVivo, MAXQDA or ATLAS.ti

Export your NVivo, MAXQDA or ATLAS.ti project in the REFI-QDA format and import it, so your coding opens as a map without retyping.

Open the live demoDownload the template
  • What you needA project with your coding in it in NVivo, MAXQDA or ATLAS.ti, and a few minutes in that program before you start.
  • How longA few minutes to export, then one in the viewer.
  • At the endYour coding open as a map, and the template files downloaded to keep.

Step by step

The same steps as the video, written out so you can follow at your own pace.

Steps
  1. Use pseudonyms first
  2. Export the project
  3. Import the file
  4. Read the import report
  5. Open or download

Use pseudonyms first

In your coding software, rename participants to the pseudonyms you will report, before you export. In NVivo, rename participants and cases, since participants come across from NVivo cases.

Export the project

Export the project as a REFI-QDA file ending in .qdpx. In NVivo, choose File, then Export Project on a Mac, or Share, then Export Project, then REFI-QDA Project on Windows. In MAXQDA, choose Save Project As on the Home tab, with the file type REFI-QDA Project. In ATLAS.ti, choose Project, then Export, then REFI-QDA Project on Windows, or File, then Export, then QDPX Project Bundle on a Mac. Save the file where you keep your study's data.

Import the file

On the viewer's Start a project screen, choose Import from your coding software, then the tab for your program, and select the exported file. The viewer reads it in your browser and writes the template files from it, with a short import report.

Tip: Your project in your coding software is not changed by the import.

Read the import report

Top level codes become themes and the codes beneath them become codes and sub-codes. Coding on PDFs, images, audio and video is counted in the report and left out, and connections between codes do not come across.

Open or download

Open the viewer straight away, or download the CSV files and carry on in the template. Save your progress before you close the tab.

Your path

Every tutorial in order. This one is marked, and the ones you finish fill in.

  1. Getting started

    From the template or an NVivo project to your first map, and saving it as files you keep.

    0 of 3 done
    1. Load your first fileMake a copy of the template, code a few rows, and open them in the viewer to see your first map.Getting started10 minutesOpen the tutorial
    2. Save your progress and carry on laterThemescape keeps no copy of your project. Save your work as files on your computer and load them next time.Getting started5 minutesOpen the tutorial
    3. Import a project from NVivo, MAXQDA or ATLAS.tiExport your NVivo, MAXQDA or ATLAS.ti project in the REFI-QDA format and import it, so your coding opens as a map without retyping.Getting started8 minutesOpen the tutorial

  2. Exploring

    Reading the map in its three views, opening themes in the reader and searching your project.

    0 of 3 done
    1. Move between the three viewsThe node network, the hierarchy and the file tree show the same coding. Learn what each one shows and when to reach for it.Exploring6 minutesOpen the tutorial
    2. Read a theme's definition and quotesSelect any theme or code to read its working definition, the participants behind it and its quotes, without leaving the map.Exploring5 minutesOpen the tutorial
    3. Search across codes, themes and quotesFind the theme, code or line of quote text you remember, and go straight to it on the map.Exploring4 minutesOpen the tutorial

  3. Refining

    Definitions, favourite quotes and connections in Work mode, and restructuring themes in the spreadsheet.

    0 of 7 done
    1. Edit definitions and favourite quotes in Work modeRewrite working definitions beside the quotes they account for, star your strongest evidence, and save the changes as files.Refining8 minutesOpen the tutorial
    2. Record connections between themesDraw the links you see between themes, codes and sub-codes, each marked Empirical or Theoretical, with a note on why.Refining7 minutesOpen the tutorial
    3. Merge, split and rename themesRestructure your analysis in the spreadsheet, where the coding lives, then load the files again to see the new shape.Refining8 minutesOpen the tutorial
    4. Arrange the map with Custom placementPut themes and codes where they make sense to you, in each view, and keep the arrangement in your layout file.Refining5 minutesOpen the tutorial
    5. Load a published model and check the mappingMap your coded data into a published model or framework, and check how it maps before you open the model.Refining8 minutesOpen the tutorial
    6. Change relationships and keep a reflexive logIn Model mode's Work mode, add relationships found in your data, adjust the published ones, and record why in the reflexive log.Refining8 minutesOpen the tutorial
    7. Try arrangements of a modelMove a model's top level parts to new rows and columns, save the arrangement under a name, and compare it with others.Refining5 minutesOpen the tutorial

  4. Presenting

    Present mode, figures from Build mode and taking your changes back to the spreadsheet.

    0 of 5 done
    1. Present to a supervisor or a panelHide the tools and walk through your themes, bringing your favourite quotes forward as you talk.Presenting5 minutesOpen the tutorial
    2. Make a figure in Build modeTurn a figure style into a finished figure, set its colours and export it for a thesis, article or poster. Build mode is in beta.Presenting10 minutesOpen the tutorial
    3. Bring your changes back into your spreadsheetTake the definitions, favourites and connections you refined in Themescape back into your coding workbook, in the same format.Presenting6 minutesOpen the tutorial
    4. Choose a starting layout and arrange a figureStart a Build mode figure from one of the figure styles, then move, shape, align and group its parts. Build mode is in beta.Presenting8 minutesOpen the tutorial
    5. Undo, Reset, Fit and Show hidden in Build modeHide what a figure does not need, undo a step, start again from the starting layout, and fit the figure to the screen.Presenting5 minutesOpen the tutorial

  5. Guided analysis

    For Student plans: working through Braun and Clarke's Phases 3 to 5 in Themescape for students.

    0 of 3 done
    1. Start guided analysis, and come backOn a Student plan, take your project into guided analysis in Themescape for students, save your progress, and return to the main viewer.Guided analysis5 minutesOpen the tutorial
    2. Generate and review themes in guided analysisPhase 3 sorts your codes into piles of candidate themes. Phase 4 reviews each candidate against its quotes and the whole dataset.Guided analysis10 minutesOpen the tutorial
    3. Refine, define and name themes in guided analysisPhase 5 gives each theme a name, a central organising concept and a definition, sets the order of your write up and confirms each theme.Guided analysis8 minutesOpen the tutorial

Your data stays with you

Themescape reads your data in the browser. The host never receives it.

  • Read locally

    Transcripts and quotes are read locally and never leave the machine.

  • Nothing to submit

    No file submission or permanent storage is required.

  • Quotes untouched

    Verbatim quotes are never altered, with a separate refined column for presentation wording.

  • Sheets is opt in

    The Google Sheets mode is opt in, for non-sensitive data only.

Read about privacy and data
Your file. Your browser. Your screen. Nothing travels to Themescape.

Common questions

Short answers to what researchers ask most. The FAQ page has the rest.

See all questions

What comes across from NVivo?

Top level codes become themes, and the codes beneath them become codes and sub-codes; deeper levels are folded into the sub-code. Coded text from text documents comes across as quotes, participants come from NVivo cases, and code descriptions become working definitions. Coding on PDFs, images, audio and video is counted in the import report and left out, and connections between codes do not come across, so add them in Work mode.

Does Themescape change my NVivo file?

No. Import from your coding software reads the project file NVivo exports in the REFI-QDA format and writes the Themescape template files from it, with a short import report. Your NVivo project is not changed, and the import happens in your browser.

Do I still need my coding software?

Yes, if you use one. Themescape works alongside coding software such as NVivo, MAXQDA and ATLAS.ti and replaces none of it. Keep coding where you code, then bring the result in through the spreadsheet template or Import from your coding software, which changes nothing in your project.

See your own themes come to life

Try the live demo or start a 7 day free trial. Your data is read in your browser and never leaves your computer.

Try the live demoStart 7 day free trial