Boolean versus Construct searches

[Peter Brylov Christensen]

Hi there!

 

Sometimes I can't decide between using the boolean or the construct searches. But generally I prefer to use the boolean searches for the simple stuff, and for searches with several arguments, I tend to use the construct search instead in order to avoid writing long lines.

 

Anyway, I was wondering what works best for all of you - do you stick to just one search method or do you mix them?

 

With kind regards

 

Peter Christensen

[Λύχνις Δαν]

By boolean I'm assuming you mean typing search commands in the search box.

I generally use construct when I cannot get a command search to do it.

For automation I have to use the command search because you cannot use constructs from scripts.

 

I also use construct for syntax searches.

 

I will sometimes do a construct where I could use the command line if its complex but that doesn't happen that often.

 

Regarding long search box lines you can resize the search argument box and type in very long stuff that is all still visible

 

Thx

D

[Peter Brylov Christensen]

By boolean I'm assuming you mean typing search commands in the search box.

I generally use construct when I cannot get a command search to do it.

For automation I have to use the command search because you cannot use constructs from scripts.

 

I also use construct for syntax searches.

 

I will sometimes do a construct where I could use the command line if its complex but that doesn't happen that often.

 

Regarding long search box lines you can resize the search argument box and type in very long stuff that is all still visible

 

Thx

D

 

Yes, that's what I meant. I went with the name from the Accordance help files. Nevertheless, maybe I should've written "command search vs construct search" instead.

[Λύχνις Δαν]

Wow ! I never knew that term existed in the doc. It does but it's funny in the doc where it's described.

 

file:///Applications/Accordance.app/Contents/Resources/Accordance Help/Default.htm#topics/06_braa/undrstnd_constrct_vs_srch.htm

 

The HTML title for this page is "Understanding Construct Searches vs Standard Searches" whereas the heading on the page itself is "Understanding Construct vs Boolean Searches" which is also what the table of contents calls it.

 

Oh well - learn something new every day.

 

thx

D

[Ken Simpson]

I think Boolean is the older term (for us). I remember Helen saying that they developed the contruct window very early on (it was in v1) to make searches simpler. A drag and drop visual interface.

 

So I wonder if there was some thought that perhaps the Construct search would become the “standard search” rather than the Boolean (or command line) search.

[Peter Brylov Christensen]

I think Boolean is the older term (for us). I remember Helen saying that they developed the contruct window very early on (it was in v1) to make searches simpler. A drag and drop visual interface.

 

So I wonder if there was some thought that perhaps the Construct search would become the “standard search” rather than the Boolean (or command line) search.

 

I guess that it would make sense, seeing that the Boolean search method in Accordance is sort of a hybrid between regular expressions and intuitive commands, whereas the more visual construct search avoids the former completely. Darin Franklin's app extension RegexForAccordance is an interesting addition in that regard as it is the antithesis to the construct search: The intuitive commands have been removed in favor of the more complex regular expressions, which in turn offers more possible search options...if one knows how to write scripts, that is.

Edited December 14, 2014 by Pchris

[Fr. Rich]

The term "Boolean search" refers to the way the underlying math works to accomplish the search. It has do do with ones and zeroes.

[Peter Brylov Christensen]

Heh, look at what the discussion has turned into - serves me right for using the word "Boolean!"