Troubleshooting

If a search does not work . . .

If you start a search, either on the Quick search or the Advanced search level, then you may find that Corpus Presenter states almost immediately that there was no find for the string(s) you entered. This may indeed be the case, or you may have misspelled a search string, but it may also be due to incorrect search parameters. The following tables contain a few tips about what might go wrong when entering parameters and suggest some solutions.

On the Quick search level

What you did Why this is a problem A solution

You have specified a search range, such as Branch only or Just current text, without paying due attention to whether this is appropriate to the retrieval task at hand. There is no find within the search range specified. Change the search range. In particular if you choose Branch only, make sure that you are located at the top of the branch you wish to examine (check tree on left of screen on the main level). If you do not have a tree, i.e. if you have just loaded a set of files from disk, then Branch only should never be used as a search range.

What you did Why this is a problem A solution

You entered a wildcard as the first character in a string. This is not permissible in Corpus Presenter. Change the string and use the wildcard in the middle or at the end of the search string.

What you did Why this is a problem A solution

You ticked the box String is whole word. Your search string only applies to sections of words. Remove the tick from the box String is whole word.

What you did Why this is a problem A solution

You searched for a string but a lot of punctuation was returned within the delimiters for finds. Corpus Presenter allows you to define punctuation and word delimiters so it does not decide in advance what these are. Check what has been entered for (i) Sentence delimiters, (ii) Word delimiters and (iii) Punctuation. Alter these where necessary and repeat the search. You can check on these settings in the Parameters window on the Advanced search level.

What you did Why this is a problem A solution

You ticked the box Case-sensitive search. Your search string does not match potential finds with respect to case. Remove the tick from the box Case-sensitive search.

What you did Why this is a problem A solution

You entered a search string, but got very different returns back (perhaps none). The option Use input list was ticked and so any entry in the line String to be found will be ignored. Uncheck Use input list or check if the input list matches the type of search you wish to carry out.

What you did Why this is a problem A solution

You entered a search string and got finds within various kinds of bracketing (not desired). You did not turn on checking of markup codes Click on button Markup codes and turn on checking for these codes. Take a look at the codes in the table as well.

On the Advanced search level

Many of the causes of unsuccessful searches, which have been identified above, also apply to the Advanced search level. In particular the question of search range (see first issue discussed above) is relevant here as well. Remember that to enter parameters on this level you must obviously click on the button Parameters to open the relevant window.

What you did Why this is a problem Some solutions

You entered strings for a search but unexpectedly nothing was returned. Maybe you searched for a syntactic frame but did not specify a double string search. Perhaps you did not specify the position of strings 1 and 2 in words correctly or perhaps you did not allow for spaces between strings 1 and 2. Maybe the option Consult Cocoa settings during searches and/or the option Check file name section was ticked when it should not have been. Check the box Allow spaces between strings 1 and 2 and the box Double string search. Make sure that the word positions of strings 1 and 2 are appropriate for your search. Check whether you have requested input lists to be used. All of these options are to be found in the box String specifications in the right-hand corner of the Parameters window.

What you did	Why this is a problem	A solution
You have specified a search range, such as Branch only or Just current text, without paying due attention to whether this is appropriate to the retrieval task at hand.	There is no find within the search range specified.	Change the search range. In particular if you choose Branch only, make sure that you are located at the top of the branch you wish to examine (check tree on left of screen on the main level). If you do not have a tree, i.e. if you have just loaded a set of files from disk, then Branch only should never be used as a search range.

What you did	Why this is a problem	Some solutions
You entered strings for a search but unexpectedly nothing was returned.	Maybe you searched for a syntactic frame but did not specify a double string search. Perhaps you did not specify the position of strings 1 and 2 in words correctly or perhaps you did not allow for spaces between strings 1 and 2. Maybe the option Consult Cocoa settings during searches and/or the option Check file name section was ticked when it should not have been.	Check the box Allow spaces between strings 1 and 2 and the box Double string search. Make sure that the word positions of strings 1 and 2 are appropriate for your search. Check whether you have requested input lists to be used. All of these options are to be found in the box String specifications in the right-hand corner of the Parameters window.