Hello All
I am working in a cross-country research team and some of my colleagues are using NVivo 8, while others are using Atlas ti 6. We are wondering if there is a way to move the coded data between the two programmes, without losing the coding and in an ongoing way, so that we can keep coding as we go alomg, with everyone on board at the same time. I came across a thread in 2004 (pasted in below), wherein there was some promise of future versions of atlas accommodating this sort of process. I am wondering if this has come to fruition with version 6 and if anyone can direct me to an accessible, not too techy explanation of how to do it.
Thanks and warm regards

Glad, that my Essex presentation of what XML could do for QDA and archiving=

fell on such fertile soil!-)
Wish we could have done even more in A5, especially in regard to XMLized
primary data, but we are working on it.

- Thomas
PS: http://qualitative-research.net/fqs-...3-00muhr-e.htm

At 14:57 01.10.2004, you wrote:
>Your query could not have been more timely. I'm involved, with others
>here at Qualidata and elsewhere, in attempting to build both the data
>standards and tools to support precisely this capability to share data
>seamlessly, to publish it to the web, and to archive it.
>We are in the process of creating an XML DTD (document type definition)
>that integrates two standards: the DDI (data documentation initiative)
>for social science metadata mark-up, and the TEI (text encoding
>initiative) for content-level mark-up of diverse forms of text. We're
>trying to come up with a DTD that is rich enough to handle the diversity
>of qualitative data types, without being excessively burdensome or
>intimidating for researchers. (For a presentation on this, see
>When your email arrived, I was immersed in writing tenders that would
>develop and test natural language processing tools to semi-automate this
>mark-up. Doing the mark-up is technically possible now, but so
>time-consuming as to be prohibitive in most situations.
>We have been in discussions with Thomas and Susanne at Atlas and are
>very excited that Atlas has already moved to enable XML tagging and
>That's a long winded way of saying I can't help you now, but I hope
>things improve soon! Meanwhile, as users, we should all pressure our
>software suppliers to develop XML-based outputs. They have to realise
>that this proprietary model is not in their interest in the longer term.
>Also, I'm eager to hear from anyone facing similar challenges and
>especially from any projects that have successfully dealt with these
>matters. Good luck with your data transfer.
>Libby Bishop, Ph.D.
>Manager, ESDS Qualidata
>UK Data Archive - Economic and Social Data Service
>University of Essex
>Wivenhoe Park, Colchester, CO4 3SQ UK
>+ 44 (0) 1206 872664
>Legal Disclaimer: Any views expressed by the sender of this message are
>not necessarily those
>of the UK Data Archive or the ESDS. This Email and any files transmitted
>with it are confidential
>and intended solely for the use of the individual(s) or entity to whom
>they are addressed.
>-----Original Message-----
>From: ATLAS.ti The Knowledge Workbench - User Forum
>[mailto:ATLAS-TI@LISTSERV.DFN.DE] On Behalf Of Katy Lawley
>Sent: 29 September 2004 16:31
>Subject: importing projects into atlas
>Hi. I am moving into Atlas-ti from QSR NVivo, and wonder if there is
>a way to move all of our coded data without having to manually import
>and recode everything in Atlas. I have read a previous post from this
>list (1 June 2004), in which Susanne says that qsr's proprietary
>standard prevents its import into Atlas.
>IF (and I emphasize "if") we are able to convert the qsr data into
>XML, is there a way to import these XML files into Atlas so that they
>will appear as coded documents? Does anyone have knowledge of other
>ways to use a middle-man format to convert out of NVivo and into
>Thanks so much for any help,
>Katy Lawley
>College of Information Studies
>University of Maryland

__________________________________________________ _________________
=84Computers, like every technology, are a vehicle for the transformation
of tradition=93 (Winograd & Flores, 1987)
Scientific Software Development - Berlin - www.atlasti.com
Dipl.-Psych. Dipl.-Inform. Thomas Muhr - muhr@atlasti.de
Purchase online at: www.atlasti.com/products.shtml

Thomas Muhr