Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Karma last won the day on May 4 2015

Karma had the most liked content!

Community Reputation

5 Neutral

About Karma

  • Rank
    Advanced Member

Profile Information

  • Location
    Vancouver, Canada

Contact Methods

  1. I agree, this would be a very useful option.
  2. This feature has been requested for YEARS during beta testing and product evaluation surveys, yet we are still waiting. I third this request in this thread.
  3. I agree that the annotations function could/should be developed since many users rely solely on annotations as opposed to memos. During beta testing for v.9 and v.10 I requested that annotations be retrievable in the same way it is currently possible to retrieve material coded at a node. To further this, I would like to then be able to click on the retrieved annotation text to return the section of original material where the annotation was recorded. I agree with JonEP that being able to code annotations would be fantastic,such a facility would come in useful in team environments for a
  4. Thanks Brett. Option 1 works rather well and appears to be a much more graceful solution than text searches with special characters. Unfortunately, option 2 is far too labour intensive especially given the fact that we are dealing with over 1500 sources. Thanks for the insights. be well, Chris
  5. Hi Marcus. Yes, at the moment I am using a very cumbersome text search query that either retrieves annotations that use a standard defining string such as [ANNOTATION] at the beginning of an annotation or specifying a series of wild cards that cover any word that could be used (e.g., a* OR b* OR c* OR d* OR etc) - to acquire a user-friendly contextual display of all the annotations in a single project. Even on avery powerful system this takes a lot of time and there is a high risk of crashing the program. Chris
  6. Hi Marcus. I am interested in both the annotation and the content but I am not interested in having to locate each annotation/content pair within each individual document. As I read through documents I node code, map relations and I annotate ( I rarely use memos as they are far too disconnected from the content and require opening other docs as opposed to viewing in context). My second and third passes of content usually involve me going back to my annotations and developing nodes or models based on the ideas that appear within my annotations. I also use the annotations to identify particu
  7. I would like to see the annoying content length limitation on annotations removed. I would also like to be able to access (view) the content of ALL annotations in a project in a single output. At present this is only possible (to a limited degree) by generating a very generic text querry which takes a lot of time to run and can crash less powerful systems.
  8. Hi Brett. Yes, the annotations folder tells us that we have annotations but requires that each one (or the connecting link to the document they annotation is in) be opened individually which does nothing for people who want to view the content of all their annotations in one place without having to open each individual document. Annotations function as themes and for those of us who use Nvivo for GT coding or for writing papers the themes are vital qualitative data points that need to be more easily accessible. As for the shortened [A], a great suggestion for getting around the rather
  9. Has anyone been able to determine an easy way - other than using a standard defining string such as [ANNOTATION] at the beginning of an annotation or specifying a series of wild cards that covers any word that could be used (e.g., a* OR b* OR c* OR d* OR etc) - to acquire a user-friendly contextual display of all the annotations in a single project? As it sits I can see no easy way to access all the annotations I have made across a project otehr than by going into each individual document. A side note, the wildcard query approach takes a very long time (20 mins) to run on a very high power
  10. Please do more than consider this for future releases as this rather simple feature is vital, particularly for collaborative projects or projects where Nvivo and Nvivo server are used for analysis and writing.
  11. I agree, this is an absolute necessity for future updates. I spend far too much time resetting source and nodal tree views when I first open a project file and when Nvivo crashes after failed queries.
  12. I would second this request. I would also like to see an option in the preferences to specify the 5 preferred user fonts.
  13. I think that importing comments as annotations would be an excellent addition to Nvivo as much collaborative writing these days involves the extensive use of comments in MS Word and even in Adobe Acrobat.
  14. It would be helpful to be able to click on an annotation in the collections folder and have the option of viewing either the content of the individual annotation or the source file. Currently, it is only possible to view the annotation by opening the source file. Further, it would be nice to be able to run a search or coding query to generate a detailed summary of all of the annotations in a project and to sort the annotations according to source.
  15. Is there a way to access the administrative account of the SQL database backend directly?
  • Create New...

Important Information

Privacy Policy