How to use

It is best to view the github wiki for Qualcoder.

The wiki shows how to install for Linux, Windows and MacOS. How to start the software and how to use the various functions of QualCoder.

The wiki is divided into sections for each main part of QualCoder:





File management

Case management

Coding text

Coding images

Coding audio and video


Imports and exports


18 responses to “How to use

  1. Pingback: QualCoderのインストール - 質的データ分析研究会

  2. Fantastic to see your work on QualCoder. For 8 years I’ve been looking for an open-source, cross-platform QDL and contacted the developers of many early attempts. None of them developed as far as QualCoder. I can’t code, but perhaps I can help with testing or instructional materials. Let’s all hope that other code specialists will join in and help build QualCoder into an even more powerful open-source QDA.

    • Thanks for your interest Ray. This have been a gradual work in progress, as it is primarily a hobby and with zero cash resources. I have a Debian installer for Linux distributions, but it take a bit more nous to install on Mac and Windows – this is something that I would like to explore and hopefully resolve some day.
      I think a lot of the basic analysis functionality is in the software now, but it would be good to get your views on what can be done to improve it. I have others who leave ‘issues’ – whether bugs or suggestions for improved functionality – on the github site.
      I am not always able to implement suggestions as my programming skills and the ability to test across platforms limits this.
      with regards Colin

  3. Michael

    This is great, Colin. I found out about QualCoder now that RQDA won’t run for many of us and its future looks uncertain. QualCoder already does most of the ‘code and retrieve’ work I need. There are a few stability issues and room for improvement of course. I appreciate developing QualCoder may not be a priority, but in case this feedback is useful, below are a few issues (Windows 10 x64, QualCoder 1.9, Python 3.8 32 bit). I would think that some of these are easy to address and would improve usability.
    * importing RQDA files sort of works but the codes list in ‘Code Text’ displays as dark fonts on dark background — practically unreadable. I changed the colours but the text on the right looks as uncoded. It is coded though because when I ask QualCoder to produce a codes report it works.
    * The ‘select file’ dialogue when importing files shows the wrong modified date compared to Windows Explorer (off by an hour, GMT rather than BST)
    * ‘show coded text and media’ shows the About info — with the wrong QualCoder version, v1.8 instead of the actual 1.9.
    * on a couple of occasions I got an ‘uncaught exception’ but not sure yet how
    * QualCoder seems to forget settings I change (eg default folder, windows sizes/positions)
    * ‘?’ doesn’t do anything here.

    And some suggestions:
    * currently, overlapping highlights make it impossible to tell when a snippet is coded for more than one code.
    * snippets in code reports should be linked to the source text for context. More generally, double-clicking on things like the snippets, the codes tree, graph visualisations and frequencies should produce relevant info (eg contextualised text or a codes report).
    * autosave would be nice (essential actually)
    * QualCoder could offer defaults for file-types when saving etc.
    * Open recent files would be good for efficiency

    Many thanks

    • ccbogel

      Thanks Michael, as you know I have now worked through most of these issues now. The BST time is trickier to sort out, and window sizes were not stored, but will consider code for this.

      • Michael

        Thank you, Colin. Qualcoder changed a lot in these two weeks. I would highly recommend it to anyone doing code and retrieve.

  4. ccbogel

    Thanks Michael,
    I’m glad Qualcoder works reasonably well for you.
    I have made some comments below about possible changes that I may (or not) be able to do.
    regards Colin

    RE your feedback:
    * The import with dark fonts on dark backgrounds – I will test on Windows – this has not occurred to me on Linux. Also the text coding should be visible. So again will test the RQDA import on Windows my end. One possibility is that the code colors in RQDA are very dark, and might need changing. I have limited the range of code colors available in Qualcoder to highlight black text on the coloured background, but the original RQDA colour codes I have not changed on import.
    * Select file dialog and the date BST vs GMT – currently I am at a loss on this, as python should draw from the computer’s current set date and time.
    * The about info with 1.8 vs 1.9 – yes I forgot to update the text.
    * Uncaught exceptions – there is a log file that might give some details – if you fed it back to me to review. Or at least copy the text or screenshot for me to give me some ideas.
    * Forgetting settings – some are not stored to be forgotten – e.g. screen sizes and positions.
    The default folder – maybe in some dialog windows I have missed this – if you come across these let me know which dialog is opened that misses the default folder – as I might have to review the code to recognise the default folder.
    * ‘?’ does not do anything here – I am not sure what you mean.

    Your suggestions:
    * Overlapping highlights – yes – not sure how to resolve at the moment – so will put it in the too hard basket for now.
    * The code snippets and contextualisation – yes this is a good point, with a double click and showing another dialog window with the surrounding text. Do-able but will take me some time.
    * Autosave. In the settings, it automatically backs up a copy of the qualcoder folder on opening, unless switched off. All changes that are made after opening are automatically updated (or autosaved if you prefer). There is no undo, unless you open a previous backup.
    * defaults for file types when saving. Do you mean for the report format? As other exports are done as text files. Also note I will not be able to export to Microsoft Word or Excel – that would require a lot of coding know-how.
    * open recent files – I am not sure exactly what you mean here. The last Qualcoder project should open again when opening Qualcoder.

  5. Omar Bautista González

    Helping this project in Spanish, a video installing QualCoder using Microsoft Windows 10:

  6. Omar Bautista González

    And opening QualCoder with a link in the desktop of Microsoft Windows 10:

  7. Michele

    Dear Colin,

    This is impressive work! I am a Professor of Urban Studies in the UK, using Ubuntu as my main platform and for years I has to use half-baked solutions to code my interviews. What you did here is very welcome! It works well with my markdown notes and files. Are you going to continue working on this software (ie further developing it for Ubuntu?) Let me know if there is a way to ‘buy you a coffee’.

    All best

    • ccbogel

      Thanks Michele. Yes I am working on QualCoder including for Ubuntu (I use Ubuntu 20.04 as my main machine). When I release another version, 2.3 it will be more polished with a tabbed interface, rather than many pop-up windows. Once it gets to that stage, instead of a coffee – well – how about some YouTube How To Use videos 🙂
      with regards Colin

      • Michele

        Hi Colin
        Greetings, and thanks! It is exciting to hear you’ll continue development. RE YouTube – message received! I can’t do it strait away, but I will.
        Best wishes,

  8. esemas

    Hello, I just got QualCoder and am just getting used to the interface… I do not know how to do it but I would like to help with the spanish translation (my native language), if I get an instruction I can work on some parts that require some tuning… 🙂

    • ccbogel

      Hello, first you need to get a GitHub account.
      When you download the folder QualCoder-master:
      1 There is a translation file inside the inner qualcoder folder: es.po
      This file is opened with a program called poedit – you can edit the Spanish and fix it, then upload it to the GitHub page or email it to me.

      2 There is a second file inside the /GUI folder called app_es.ts
      This can be edited with a program called QtLinguist – which is harder to install.
      However, if you are careful and exit the text file directly the translation is stored between tags like this:

      All coders
      Todos los codificadores

      The translation text is in the tags:

      Best to email it to me.

      with regards Colin

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s