SUGGESTION: A quick upgrade to the Search function ... as per another thread

A few things that I think would help make the Search function easier for users to navigate. See Enhancement of Bible browser needed in support of easy search for a related request and Logos Staff: A Story to Give you something to think about for what led to this post.

• Users tend to hit the Search icon when they wish to do a search. We need to be reminded that is not always the best choice - perhaps the top line of the Search panel could offer options while defaulting to its current functions. It may be better to start with:
• the inline search it you want to search the current text or include punctuation
• the media browser may be better than a media search for your needs
• the Bible browser may allow you to pare down the text searched before building a search or may be all you need
• a direct link to the Morph Query Builder
• a direct link to the Syntax Query Builder
• Display all the parameters that affect the search including those "hidden" in the panel menu or built into the application e.g. scope and range of search type or range of NEAR
• The Bible Browser should be enhanced to provide these functions:
• build results at the facet level that includes all passages within that facet
• extend the build a Passage List function to include build a Passage list and send to Search which would open a Bible Search limited to the Passage List
• Over time, the Bible Browser --> Search via the Passage List capability could be usefully added to several of the interactives.

This solution would minimize a number of issues:

• Users not choosing the right tool
• Users puzzled by the results because they've set the wrong parameters in the panel menu
• Users puzzled by the results because they don't understand the scope differences between Basic and Bible
• Users not understanding / finding search strings too complex to build for many of the dataset based searches.

Yes, there is a long list of items this does not improve but I do believe this represents low-hanging fruit. Yes, I know exporting the Passage list is less accurate than exporting a search string but it keeps the results transparent to the average user.