Jump to content

Karma

Members
  • Content count

    104
  • Joined

  • Last visited

  • Days Won

    2

Karma last won the day on May 4 2015

Karma had the most liked content!

Community Reputation

5 Neutral

About Karma

  • Rank
    Advanced Member
  • Birthday 10/31/1971

Contact Methods

  • Website URL
    http://www.academic-freedom.ca

Profile Information

  • Gender
    Male
  • Location
    Vancouver, Canada
  1. Annotations - ideas

    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 variety of functions.
  2. 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
  3. Annotations in N10

    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
  4. Annotations in N10

    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 particular themes in content (mostly literature) that I want to address/explore in my analyses. What I need is an easy way to retrieve all my annotations (with linking to associated content) so that I can facilitate these processes. At present this is not something that is easy to accomplish via N10. be well, Chris
  5. Annotations in N10

    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.
  6. 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 irritating limitation on content length that has been placed on annotations (which I would like to see removed), thanks. be well, Chris
  7. 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 machine (16GB RAM, multi-core processors) and can cause the program to crash.
  8. Spell Check

    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.
  9. 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.
  10. Better font drop-down menu

    I would second this request. I would also like to see an option in the preferences to specify the 5 preferred user fonts.
  11. Annotations and comments

    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.
  12. Annotation View/Print

    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.
  13. Is there a way to access the administrative account of the SQL database backend directly?
  14. Voice recognition software incompatibility

    Cecilia Using Dragon 9 and Nvivo 7 together is not the best bet unless you have a dual-core processor and over 1GB RAM as N7 is not entirely stable running on it's own (due to the introduction of the SQL database back-end I suspect). This said, I have found that with a higher-end system N7 is quite adaptable to Dragon 9 and once you get over the initial learning/growth curve involved in setting up the voice commands it can be easier to code using Dragon than it often is to use a standard mouse.
  15. List view of Free nodes AND Tree Nodes

    Indeed, that would make things much easier. I have found that while some of the new coding features in N7 are much needed improvements, overall, coding has become a bit more cumbersome. It would even be nice to have nodes accessible via a contextual menu (i.e., right mouse click) so that one doesn't have to break their stream of concentration to access the coding area.
×