Jump to content

The mixed methods coach

Trainers
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About The mixed methods coach

  • Rank
    Member
  • Birthday 07/18/1974

Contact Methods

  • Website URL
    http://www.spi.ox.ac.uk/test-area/staff-detail.html?tx_oxford_pi1%5Bstaff%5D=103&cHash=9295dc565da97e83d464fa55ad06d3b5

Profile Information

  • Gender
    Female
  • Location
    Barcelona
  • Interests
    Research interests:
    - Use of multidimensional scaling, cluster analysis and correspondence analysis as ways to support theoretical inference from qualitative data;
    - Strategies to triangulate qualitative and quantitative findings in mixed methods research;
    - CAQDAS support for data transformation
    Research practice:
    - Mixed methods research in international social work;
    - Participatory practice in psychosocial intervention and research;
    - Effectiveness and appropriateness of intervention;
    - Community participation in ending harmful cultural practices.
  1. Hello everybody, I am using Framework for thematic analysis and use coding stripes to locate the occurrence of keywords in the data. Unfortunately though, when clicking on a coding stripe, its associated keyword does not get highlighted in the Associated View. It is also impossible to anchor a Hyperlink although Annotations and See Also Link work. I am wondering whether these problems are normal behaviour, QSR? If they aren’t, could they please be fixed in the next hotfix? As far as analysis is concerned, the Associated View of Framework should be as functional as the Detail View since it is where data are shown and where the analysis starts. It is therefore important that all functions we use in the Detail View be operational in the Associated View of Framework. Many thanks, Marie-Hélène Paré Open University of Catalonia Barcelona
  2. The mixed methods coach

    Add Features to Quick Access Toolbar

    Hi everyone, Could we please have the option of adding more functions onto the NVivo toolbar? All Microsoft Office applications offer such feature (only by right-clicking on the desired function) which greatly reduces the searching time across tabs and subsequent clicking. For instance, I must change the Detail View from Right to Bottom display about 30 times per day depending on how I need the information to be displayed in a NVivo project. Always having to go click first on the View Tab, then click on Detail View, and click on the display I want is really repetitive and should be made much efficient. Instead, I would like to be able to click on the Right or Bottom display icons directly on the toolbar. At present only 7 functions are available on the toolbar, and I did not find a place in Project Options or Project Properties to add more functions onto it. Many thanks, Marie-Hélène
  3. The mixed methods coach

    Coding Stripes Show More Than They Should When Working With PDFs

    Dear Ben, Many thanks for your reply. I did go the PDF Editor route two years ago when I converted 250+ academic papers into text files to analyse them in NVivo. Although this seems the logical thing to do when one wants to use NVivo for text analysis, the work that it involved was incredibly cumbersome since you never really know how bad the PDF will look like when you turn it into a text file, and how much time you’ll need to invest so that the source can be coded and analysed. Also, after importing the text files in NVivo, the fact that the visual context of the PDFs was gone negatively impacted on the coding. I felt it was like coding the sound of a video recording without being able to look at the video shooting. So, when comparing these disadvantages with the PDF glitches in V9, I still prefer to code the original PDF. Hopefully the glitches I mentioned will be solved soon. Hope all is well with you and yes, Cork was lovely! Take care, Marie-Hélène
  4. Great, thanks for this Marcus. Best wishes, Marie-Hélène
  5. Hi everyone, Further to my post yesterday on the problem of coding a databite to more than one node while having to move the scrollbar of the List View, another glitch appears today which really wears off my enthusiasm to use NVivo to code and analyse PDF. In a PDF source, if two separate databites coded at a node are located at the top and the bottom of a page, the associated coding stripe does not correspond to the actual databite sections in the text. Rather the coding stripe expands throughout the page. See picx 1 for the databites coded at the node attitude. This problem also occurs when viewing the coding at attitudes within another node, selecting the PDF view Tab in the Detail View– see picx 2. Could we expect this problem to be resolved soon, please? Thanks, Marie-Hélène
  6. Hi everyone, I am currently coding an extensive PDFs dataset and unfortunately found that the coding is very unstable if you manually move the scrollbar of the List View in order to code a databite to more than one node. The problem goes like this: In a PDF, I select a databite and coded it at a node. Until here, everything goes well - see picx Step 1 The problem occurs when the same databite has to be coded at a second node which, in order to be located, I manually move the scrollbar of the List View. After locating the second node and moving back in the Detail View over the highlighted databite in order to drag and drop it to the second node, here is what happens to the databite I originally selected - see picx Step 2. The databite disappears and the whole PDF goes haywire. There is a way to avoid this problem which makes the coding very cumbersome: 1- Go back straightaway to the selected databite after coding it at the first node; 2- Then move the cursor back to the List View while pressing left click (as if I was to drag and drop) 3- Point the cursor to the direction you want the coding scheme to move; 4- Drag and drop at the second node. Needless to say that this behaviour is really un-ergonomic (if you never tried it, just give it a go to see) since moving the coding scheme this way is not smooth at all, feels mechanical, and is too fast. This bug seems to be generalized across V9 projects since it occurs in a variety of projects of mine including the Sample Project and in three computers where I tried it. Thanks for adding it to the list of bugs to fix.
  7. Hi everyone, I am currently coding an extensive PDFs dataset and unfortunately found that the coding is very unstable if you manually move the scrollbar of the List View in order to code a databite to more than one node. The problem goes like this: In a PDF, I select a databite and coded it at a node. Until here, everything goes well - see picx Step 1 The problem occurs when the same databite has to be coded at a second node which, in order to be located, I manually move the scrollbar of the List View. After locating the second node and moving back in the Detail View over the highlighted databite in order to drag and drop it to the second node, here is what happens to the databite I originally selected - see picx Step 2. The databite disappears and the whole PDF goes haywire. Not good news… There is a way to avoid this problem which makes the coding very cumbersome: 1- Go back straightaway to the selected databite after coding it at the first node; 2- Then move the cursor back to the List View while pressing left click (as if I was to drag and drop) 3- Point the cursor to the direction I want the coding scheme to move; 4- Drag and drop at the second node. Needless to say that this behaviour is really un-ergonomic (if you never tried it, just give it a go to see) since moving the coding scheme this way is not smooth at all, feels mechanical, and is too fast. This bug seems to be generalized across V9 projects since it occurs in a variety of projects of mine including the Sample Project and in three computers where I tried it. Thanks for adding it to the list of bugs to fix.
  8. The mixed methods coach

    Nvivo 9: quickness and flexibility

    Dear Alex I can't agree more about your criticism regarding the lack of efficiency for inductive coding in V9. I posted something along the same lines last week in the Forum after playing a bit with V9. See in Question and Answer 'NVivo9 Floating Quick Coding Tool: What is Quick About it?' dated Oct 22. Hopefully these will be taken on board soon and improved. However, until a more efficient coding toolbar is provided in V9, I have to stick with V8 in order to finish the inductive coding of a huge textual dataset. That's a pity because V9 runs quicker overall. Regards, Marie-Hélène Paré
  9. The floating option of the Quick Coding Bar is far from been quick and is frankly or little use. First it needs to be stretched 19 cm long on your screen – I’ve measured it - in order for user to see the downside arrow on the right that allows to select the next node to code at. That’s a big put off as that literally blocks the view of what lies behind. If you reduce its size, you then can use the down arrow on your keyboard to see the whole listing of active nodes to code at, but that’s really not what I call a ‘quick coding’ tool. Second, and more importantly, the option to code at node by pressing Enter has disappeared. This is a such a mistake QSR. If you spend hours and weeks inductively coding a dataset, you want the software to facilitate the coding by reducing to the MINIMUM the clicking and manipulation you have to do. In NVivo 8 we can select the node to code at in the list of active nodes in the Coding Toolbar and then press Enter. That’s quick and efficient and this is what a software should offer. This simple feature free us of the hassles to drag and drop the same chuck of text to nodes that are buried somewhere in the coding scheme, or endlessly right-clicking to Code Selection at Existing Node or to ‘Recent nodes’ at it appears in V9. Third, I can’t figure out why is it that after all these years QSR still does not offer the option to code a chunk of text at multiple nodes by first selecting them in the coding scheme and then pressing Enter. Do you know QSR how much time we would save and how much that would make the coding task easier? I actually doubt it. While I am delighted of some of the text mining features to code data in V9, I strongly plea for equal interest to be invested so that inductive coding at multiple nodes become the CORE improvement of the next V9 update / hotfix. This is currently the weakest link of the software.
×