Search the Community
Showing results for tags 'search'.
Found 3 results
Dear QSR team, I made the below request about a year ago, but it appears you have not had a chance to implement it, so I thought I'd restate my interest in this new (straightforward) feature: Could you please add a 'node search function' to the toolbar. You already provide this feature, but I have to use a work-around to get there. At the moment, in order to search my nodes I have to use the 'query' tab and then click on 'selected items' and then select 'nodes' to get the option to search all nodes. This is rather time consuming and could probably be fixed quite easily with a 'nodes search button' at the top level. I appreciate that for some users this feature will be less essential, but my research projects are rather large (longitudinal), requiring me to develop several hundred distinct nodes/sub-nodes, which makes it hard to remember them all (and which can lead to unnecessary duplication of nodes). Please find attached screenshots of the work-around I currently using to get there. Thanks and all the best, Tobi
I would find it helpful to have a quick way to search for text within the open document that I am viewing—something akin to the Find command in TextEdit or Word. I know it is possible to run a Query and to select only one document, but I find that to be overkill if, for example, I know a name was mentioned within a long transcript and I open the transcript and want to find that reference quickly within the document.
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.