Setting up ConnectedText

In an earlier post I have discussed how to set up your desktop layout in ConnectedText, as part of getting started with CT. In this post I will offer a few more tips on setting up CT for general use but also for our intended purpose here as a CAQDAS tool.

One of the things that puts people off from using wikis in general and CT in particular is the need to use (and having to learn) markups. Especially if you have never learnt or used a markup before, it may seem too technical and daunting and even unnecessary in this day and age of icons and touch screens.

The good news is that CT makes it relatively easy to use markups. First, it uses a simplified markup language, so there is no need to learn a huge amount of markups. I only use maybe 4 or 5 markups on a regular basis. CT also reduces the need to type markups in a number of ways.

First, it offers a number of buttons in the header and commands in the right-click context menu that obviate the need to type the markup yourself.

Second, you can just drag and drop certain items, such as URLs from your browser and file links from your Windows Explorer, rather than having to type the associated markup. Some markup also gets inserted automatically for you if you are starting a list, such as a bulleted or numbered list or a list of comments. Finally, there is also something called “completion proposal,” which means that if you start typing a certain markup, it brings up a pull-down menu of options, and you just click on the markup you need to insert it automatically.

One complaint about having to use markups is that they disrupt the flow of writing or reading in edit mode. As far as the speed of writing is concerned, I think this might be more of an issue of perception stemming from the habit of clicking buttons and selecting menu items in the headers of standard office applications. While it may seem that it is easier or quicker to highlight a piece of text, go to the menu, select a command, and click on it, in reality that also disrupts your flow of writing because you need to take your hand off the keyboard, grab the mouse, move it, click on things, and then move your hand back to the keyboard. If you know the markup, it’s much quicker to just type the markup and achieve the same result, without your hand having to leave the keyboard.

But it is true that the presence of markup in the text itself may disrupt the comprehension of the text you are writing, after all you might be inserting some notation that looks like gibberish  (at least until you get used to it, which is another way of dealing with this problem: use it long enough for it to become second nature).

Fortunately CT has a feature that can somewhat alleviate this effect of disruption. If you select custom colours for specific mark-ups, they become more easily recognisable in the text, and your eyes will learn to skip over them and ignore them when you want to concentrate on the content of your writing in edit mode (and of course you can always just switch to view mode, if you don’t want to see any markup at all).

Here is how to select the custom colours for your markup: go to Tools > Options (or hit CTRL+O) > Editor, and you will see a box called “Colors,” as well as a corresponding preview box at the bottom that will show you the colours you have chosen. You can change both the foreground colour (the font colour) and the background colour (which works as highlighting) for your given markup or feature. You will also need to tick the box “Use syntax highlighter” for this to show in the edit mode.

You can see that I have selected orange for my comments, dark blue for internal links, light blue highlighting for headings, green for commands (which also includes external links), and red for “includes.” (By the way, the “include” command is a powerful feature. It allows you to include sections of other topics in the body of your current topic. More about that later.)
And this is what these markups look like in CT’s edit mode (note that internal links to other topics are dark blue, while external links – which are recognised as a type of command – are green).
And this is what this topic looks like in view mode (the orange comments are not visible because they are only meant for the edit environment, a kind of a “note to self” feature):

Dragon NaturallySpeaking 12 and ConnectedText

I have been a Dragon user (I’m talking about the speech recognition software) since version 9, although I have only started using it on a regular basis since version 11, as previously it was just far too temperamental. Version 11, and especially 11.5, on the other hand reached near perfection compared to what it had been before, with its 99% plus accuracy (as long as you used Dragon’s own DragonPad to dictate). Unfortunately it didn’t play nicely with ConnectedText, producing errors that made Dragon effectively unusable with CT.

A month or so ago Dragon 12 arrived on the block, pre-marketed to existing users initially. Up until today I held off, thinking, “I’m not going to risk having to upgrade my hardware, should it turn out to be a monster of an upgrade” (like version 11 was), not to mention the amount of money it costs to upgrade from what numerically seems like a tiny step from 11.5 to 12. But this morning a discounted offer landed in my mailbox and it made me think: “What if…? What if this upgrade might just make Dragon compatible with CT? I could always downgrade and ask for my money back…”

Information on CT’s compatibility with DNS12 was nowhere to be found, so I took the plunge and bought the upgrade this morning. As I started installing it, there were a few hitches which almost made me regret my decision. First, InstallShield wasn’t able to close down one of the applications that it needed closed down: “Acresso software manager.” I tried to go into “msconfig” and shut it down, it still wouldn’t do so. In the end I tried to click “Help” on the “InstallShield” window to find a solution, which it somehow interpreted as “next” and carried on and installed the software anyway. After the installation I discovered that the problem apparently was caused by InstallShield itself, as the name of its company – and therefore of the software – changed from Acresso” to FLEXnet because of trademark infringement. So it was a weird loop caused by InstallShield not recognising itself, it seems.

The second hitch was a cryptic message at one point in the installation process, which said something along the lines of “Dragon has installed C++, do you want to remove C++?” What?? Why are you asking me that for?? It would have been one thing to say one was an older version than the other and no longer needed, but there was no additional information whatsoever. I wonder how they expect average Joe Bloggs to know what that was all about. In the end I decided to keep C++. If Dragon had bothered to install it, I assume it knew what it was doing? Anyway, so far there haven’t been any adverse consequences of that decision.

The third hitch presented itself during the upgrade tutorial. After a few screens Dragon just stopped recognising my input, suggesting that what I said was not recognisable or that my mic was not up to the task. I have a Plantronics headset that I bought specifically for Dragon a few years ago, and while this model is obsolete, it worked just fine with v. 11.5. “Here we go,” I thought, “I can start shopping for a new headset. So that’s why they gave me a Logitech 30% discount voucher at the checkout…” But, once I finished the tutorial and launched Dragon proper, my Plantronics mic worked perfectly again.

All’s well that ends well… After the somewhat rocky installation Dragon ended up working like a dream. The touted 20% improvement in accuracy (which is already around 99%) was noticeable to me because there were only 1 or 2 corrections to be made where I would have had 5 or 6 mis-recognitions before. This is near perfection.

However, the litmus test and indeed the whole rationale of the purchase was to see whether Dragon 12 would work with CT. I was pleasantly surprised. It’s not the perfect solution yet, but progress has been made. The perfect solution would be if I could just dictate straight into CT and it would work like it does in DragonPad. We’re not there yet. However, dictating into CT now triggers Dragon’s Dictation Box, which then pastes the contents directly into CT. See the two screenshots below for the Dictation Box and the results pasted in. This is an improvement, as it saves having to dictate into DragonPad and then do CTRL+A, CTRL+C, and CTRL+V, plus having to click in and out of windows to activate them, in order to copy and paste content (which I didn’t bother to do anyway). With the Dictation Box, it’s now down to one or two clicks. Just wake up Dragon (I assigned it to F1), and start talking, then click “transfer” and that’s it. I might start using Dragon with CT more frequently after all.

Verdict: I’m happy with this purchase (minus the initial aggravation).

Dragon’s Dictation Box:

And the results transferred into CT:

Getting started with ConnectedText

Following on from my previous post on “getting ConnectedText,” here are my suggestions on how to get started with CT if you are brand new to it.

  1. Download and install the software. (If you have special needs for installing things in a particular folder or if you need to sync files with other computers, read the relevant sections (“Changing user data location” and “Project synchronization tips”) of the Help file first, which is available here [2.9MB], as you may need to do some things differently then. But these are fairly advanced issues. If you are not sure what these are about, just go with the standard installation process.)
  2. Read (or rather, work through – see point 5) the “First steps” section in the Welcome project (which is CT’s Help file). A ‘project’ is CT’s term for a database, within which ‘topics’ (documents) reside. Keep the Welcome project always open in a tab for easy access. You may even want to load it onto your smartphone or tablet (using a CHM reader app, so you can read it when you are out and about). The Welcome project has over 300 topics, so probably few users read it from “cover to cover,” but it’s there for you to search when you need specific help.
  3. Sign up to the CT Forum. Search it for issues for which CT’s Welcome project may not have an answer to. If you can’t find an answer, post your question, and you are likely to get a quick reply.
  4. Note that CT’s main window has two modes: an edit mode for creating content in a topic, and a view mode for viewing the content. Learn how to toggle between them (e.g. type ALT+E or click the Edit button).
  5. Create a new project (database) file, call it “Test”, and try out the various features as you are learning about them. Make sure to select “Auto Backup” for any new project you create in the Project wizard, otherwise you won’t be able to recover deleted topics. You can download a cheat sheet with the basic mark-up commands here [PDF]. Use the Welcome project to practice on how to navigate an existing fair-sized project.
  6. Go through all the menu items in the pull-down menus, to learn the main commands. Similarly, check out all the buttons in the toolbar, to become familiar with them. Also check the commands in the right-click context menu, e.g. when you select some text in the topic editor window.
  7. Read some of the existing tutorials online: Steve Zeoli on some of the basic features of CT and Prof. Manfred Kuehn on the basic mark-ups he uses in CT.
  8. Develop your preferred desktop configuration for the various panes. Go to “View” pull-down menu and try out the various options. The most important panes for me are the “Table of Contents,” “Topics,” “Categories,” “Outline,” “Notes,” and “Navigator.” As the Navigator allows you to view a map of your topic relationships, it’s best to use it undocked as a standalone window in a separate monitor (using Windows’ Extended Desktop feature). Make sure to save your favourite desktop configuration by going to View > Desktop > Save Desktop. You can save a variety of desktop configurations for different scenarios (such as reading, writing, annotating, outlining etc.).
  9. Practice docking the panes because it can get tricky and it can happen that you end up in a mess (with panes stuck where they shouldn’t be and there not being an obvious way to return to the previous state). That’s the time to go to your saved desktop and load it.
  10. If you have already messed up your desktop and need a fresh start (just like I did early on), download this desktop template [ZIP file] from the Forum, courtesy of one of the users. Here are his or her instructions: “Put it into your user settings folder, where you keep CT’s icon folder, dictionary folder etc. The First_Aid.lay should go on the same level where CT stores your bookmarks.xml, fulltext.xml, filters.xml etc. After you put the file there, call it up via View > Desktop > First_Aid.” Below is what the First_Aid desktop layout looks like, once called up. It’s the swiss army knife of CT desktop layouts. You can just close the panes that are not needed.
  11. My preferred desktop configuration (for the qualitative data analysis that I will discuss in future posts) is the following: view/edit window in the middle, Table of Contents and Outline docked on the left (as tabs in the same pane), and Topic List, Categories, and Notes docked on the right (as tabs in the same pane), with Navigator undocked in a separate monitor. If you don’t have a separate monitor, you can still have it undocked, but you will need to call it up by F7 or clicking on the Navigate button and then close it, otherwise it will cover your main CT window. Alternatively you can dock the Navigator on either the left pane (like in this YouTube video) or the right pane.
  12. Once you become comfortable with CT’s main features, make sure to install Python on your computer, so you can use some Python plugins that will help your work. Instructions for how to install Python are in the Welcome project. I use three Python scripts (all downloaded from the Forum) on a regular basis: one for doing word count in a topic, and the other two for creating bullet-point and numbered lists. There are also a lot of AutoHotKey scripts on the forum but I don’t use any at the moment. [Update (11/3/13): I do now…]

In my next post I will discuss my work flow regarding qualitative data analysis in CT.

Getting ConnectedText

In an earlier post I have outlined my reasons for switching to ConnectedText (CT) from NVivo 8 as my main CAQDAS tool. However, before I get into discussing how I use CT for qualitative data analysis, I need to tackle the delicate issue of “getting” or “not getting” ConnectedText. It is a common complaint by new or prospective users that there is a learning curve associated with CT or that they simply “do not get CT.”

I empathise with these comments because I was also one of these people. I had first encountered CT back in 2007 perhaps, and I ‘trialled’ it  several times over the years. I say ‘trialled’ because most of the time I couldn’t get passed the first screen and I gave up on it very quickly. In retrospect I realise that there were a number of reasons why I didn’t get CT back then and why I get it now (at least for my purposes).

Some of the reasons have to do with the profile and the expectations of the prospective user. If you have never used a wiki or mark-up before, if you are not a programmer or blessed with an engineer’s mind, if you have been raised on the common fare of Microsoft Office type applications, if your background is in the humanities or social sciences, then encountering an idiosyncratic tool like CT may prove initially a challenge.

But some of the difficulties arise out of the characteristics of CT and the way it is initially presented to this non-programmer, non-techie type of user. CT’s main strengths are also its main weaknesses when it comes to selling these strengths to the uninitiated. At its heart it is a desktop wiki that is enhanced by a wide array of sophisticated tools that can turn that wiki into any number of specialist solutions (such as CAQDAS in my case).

The problem with ‘just’ being a wiki at its heart is that it makes CT into a highly generalist application, in the sense that a wiki can be whatever you make of it. A desktop wiki after all is your own mini internet or intranet, and as such it can be organised in a myriad different ways, as far as the content and the structure of the output are concerned. Therefore  it might be more difficult to “get CT” if you come to it without a specific need to solve a particular information management problem. Just like with the case study method or practice-based learning, it helps to have a real-life problem at hand to which you can apply CT as the solution.

At the same time CT is also packed with some very sophisticated features, such as special ways of connecting the “web pages” (called ‘topics’ in CT), analysing them, visualising them, organising them, enhancing them with various add-ons and scripts etc., etc., which probably can also scare the novice away. At the moment the way information is presented on the website, in the software when it is first launched, and in the Welcome project (which is the Help file, 2.9MB), CT probably appeals to the sophisticated programmer-type audience more, than let’s say the humanities-type person with no experience in using mark-up. When I recommended CT to another PhD colleague of mine with a social science background, he said, “Wow, and I thought learning Scrivener was a challenge!”

For this reason I would like to recommend some strategies for this latter type of prospective users on how to increase the chances of “getting CT” because I think it is well worth the effort (in my experience). I will provide a particular way into CT in my next post. However, in the meantime let me emphasise that if you want to give CT a chance as your main database for your PhD (or any other type of) project and as a qualitative analysis tool, then you will need to become a member of CT’s forum because it is a live extension of CT’s Help file. There are not only some very helpful human beings on there but it is also a depository of existing knowledge, user case studies and Python and AutoHotkey scripts (more about those later).

Why do I love ConnectedText?

I have decided to change tack with how I discuss ConnectedText (CT) on this blog. First I thought I’d proceed in a linear manner by introducing interested new users to CT through a series of step-by-step tutorials. Unfortunately the writing of full-blown illustrated tutorials is very time-consuming and obviously I’m pretty busy with writing the PhD itself at the moment. So while I’ll carry on working on the longer but less frequent tutorial posts in the background, I will also start posting occasional short musings on CT as and when they occur to me.

So you may wonder, what compels someone to spend time writing blog posts about a piece of software? The short answer to that is that I simply love CT. If it were a woman, I would want to marry it. Is this a short term infatuation or a long-term relationship? Well, I’ve been attracted to the idea of CT for many years: I’ve been circling around it like a moth around a street lamp. However, we’ve been now in a serious relationship for 7 months and things are going really well…

Why do I love CT so much? I think it comes down to flexibility. It allows me to do things that other mainstream software just won’t. For example, let’s take the interface [check out the screenshots on CT’s homepage]. It’s totally modular and flexible. Let’s say I don’t like the Table of Contents pane (Outliner pane, Navigator pane, etc., etc.) docked on the left? Well, I can dock it on the right, or have it as a third docked pane on the right, or drag it out altogether and have it as an independent window on a separate monitor.

Okay, there might be other software that can also do that to some extent (Ultra Recall comes to mind). However, CT’s flexibility also extends to its conceptual use, the way you use it to organise and analyse existing ideas or develop new ones. The reason I talk about it as a CAQDAS software on this blog is because even though it hasn’t been designed as such, it allows me to model thought processes and work flows that usually only dedicated CAQDAS can do. That’s what I call flexibility (which leads to versatility). And it’s just amazing to hear the wildly different uses that people adapt CT for. Just the other day I heard of someone who uses CT 90% of the time for numerical work. So it’s not just ConnectedText but ConnectedNumbers as well!

Finally, there is the flexibility and responsiveness of the developer, Eduardo Mauro. He uses the CT Forum actively to elicit ideas from his users on how to improve the software, tests ideas on them and implements suggestions and requests with amazing speed. CT is an evolving creature that not only is developing in front of your eyes but you can actively take part in shaping it. Now try doing that with [substitute your favourite big name global software company]!