Lexical search and wild cards

17.08.2015, 20:53

I am trying to find certain symbols in a Maxqda document while excluding others that contain them from my search. For example, I have instances of / and of // and /~ and only want to find (and autocode) the first. Unfortunately, I haven't found a way to exclude the other two from my search. It doesn't work with the extended search (/ but not //) or with wild card characters in the lexical search <(/)> (as a matter of fact, the wild card search with < > doesn't seem to work at all). It also doesn't help to tick "whole words only" as it is not really a word. Is there a way of doing this?
Thanks a lot and best regards
Silja Ang
Posts: 5
Joined: 17.08.2015, 16:34

Re: Lexical search and wild cards

23.08.2015, 13:20

Hi Silja,

I think we found a solution for getting the results you are looking for. You need to create multiple search items in one search and integrate all characters that may follow "/".
Please search for

/[space] => please type in a space instead of [space]

The list of search strings will be long but you can search for them at once. Please note that you can save such a search request and re-load it later if you need it again.

By the way:
<() => search for word begin and
()> => search for word end
cannot be combined. This may have led to the impression that the search with wildcards didn't work at all.

Best regards on behalf of the MAXQDA team,
Dr Stefan Rädiker
Training, Coaching, Analysis for Research & Evaluation
Stefan Rädiker
Posts: 254
Joined: 12.02.2007, 10:18

Re: Lexical search and wild cards

27.08.2015, 16:34

Dear Stefan

Thank you very much for your answer. I tried it out, but unfortunately, it does not work for me, because if the / is at the end of someone's turn, it will also include the next turn in the autocoding, and I need to count the individual symbols in each speaker's turn.

I started autocoding with the AND NOT option (// AND NOT //~), which works for single-line turns at least. In longer turns it does not code // if there is a //~ nearby, of course. If there was the option to choose "within one line" rather than "within one sentence" in the extended search, it would work for me, as I have one symbol at the end of each line. I assume there is no way of doing this?

Another option I tried was to autocode //~ and autocode //, then do a coding query and look for intersections, so that I could delete all the //~ that overlap with // from the list. However, this did not work as I wasn't able to delete all the instances in the table at once (and doing it one at a time takes too long for several thousand instances).

I also assume there is no wildcard that represents the end of a line?

I am adding an extract from my transcription below, maybe this will explain my issue a bit better. Each of the four turns makes up one paragraph.

Best wishes


C: <H::>
<F<HI ^yeah but HI>F> \~
<W I I <HI still HI> think people are quite ^ignorant W> \\
<P<CRK<LO when it ^comes to LO>CRK>P> \
… ((37:24))
<P<HSK<LO your^selves LO>HSK>P> /~
… ((37:26))
<P<HSK the whole .. <LO ^p:roblem LO>HSK>P> /
<PP<LO<HSK about ^politics [and all] that HSK>LO>PP> \
L: [<P<HSK ^yeah HSK>P>] \~
C: <P<HSK<W and .. I <HI ^think HI> that’s W>HSK>P> \
… ((37:31))
L: and it [a^nnoys you] _

Posts: 5
Joined: 17.08.2015, 16:34

Re: Lexical search and wild cards

01.09.2015, 14:14

I found a (slightly complicated) way of doing this, in case anyone has a similar problem:

1. I first looked for all signs of one kind with the extended search (AND NOT), e.g. // AND NOT //~ AND NOT //\\~. Now I only had signs left that co-occurred in the same sentence as the AND NOT signs. The more complex signs like //\\~ (that contain others but are not contained in other signs) I could auto-code completely like this.
2. I automatically coded all signs of one kind in a separate code (e.g. // , coded as //+), starting with the longest/most complex ones.
3. I then activated all codes that contain // (e.g. \\//~, //\ etc.)
4. I did a code query, picking ONLY THIS CODE and chose //+ as the single code.
5. Like this, I found all instances that are coded with // and nothing else; I coded these auto-matically as //.
6. Finally I deleted the new category //~ again and checked if there were any overlaps left (ac-tivating everything containing //  code query  intersection (set) 2 overlaps).
7. I then did this for \\, then for / and \ etc.
Posts: 5
Joined: 17.08.2015, 16:34

Re: Lexical search and wild cards

07.09.2015, 16:03

Hi sang,

we are glad you have found a way to get the information you need. We were still working on a solution, but your post was faster :wink:

Good look for finishing the analysis!
The MAXQDA team
Dr Stefan Rädiker
Training, Coaching, Analysis for Research & Evaluation
Stefan Rädiker
Posts: 254
Joined: 12.02.2007, 10:18

Return to Technical Questions

Who is online

Users browsing this forum: No registered users and 2 guests

We use cookies to ensure that we provide you with the best possible user-experience on our website. In addition to cookies necessary for the basic functionality of our website, e.g. for the use of our online shopping cart, we also use cookies to integrate our social media services, for interest-based advertising purposes and for the anonymous evaluation of website visits to improve our marketing strategies and online content. By clicking on OK, you agree to the use of these non-functional cookies.
You can find more detailed information on our use of cookies in our Privacy Policy.