We generate HTML5 output and are evaluating our settings for the search.
Currently, we have not enabled partial search. We are aware that compile time and output size will go up with this feature enabled. We have tested using a minimum character entry of 8, as this seemed to be a compile time and search database size we could tolerate.
However, we are thinking that having the limit of 8 characters could be misleading; if a user puts in 6 characters, they would get a message saying that there are no results, but this could be because their entry did not meet the minimum entry size.
I am wondering If users expect to be able to do partial searches, and are confused if you don't enable it? Or, is enabling it with something higher than 3 more confusing that helpful? Is there a sweet spot in terms of number of characters?
Also, using the Stop List that Flare provides seems like it would produce better-targeted results. Is there much of a down side to not using it? I guess the results could miss some exact phrases that include the stop word, but I'm not sure how frequently this occurs.
I know to some extent the answer might depend on your content, but am wondering if there is also a best practices answer.
I would greatly appreciate any thoughts or experience you have on this subject.
Best practices for search - partial search or no?
Re: Best practices for search - partial search or no?
Hi!
Others may have thoughts on best practices - but I've always been for making search as easy and robust as possible. This means living with the build times and increase in search database size in the output.
I've found a great way to point users to the fact that you have enable partial term searching, is to display text in the Search button -> tooltip field (edited in the HTML5 skin "UI Text" tab). Here's a screenshot example I made that displays the text "Enter at least 3 characters to Search".
http://i.imgur.com/ecpE3tD.jpg
Doing this will enable users to have some way of knowing (even indirectly) that they have the option of searching with at least 3 characters.
More info on editing the Skin settings in Flare can be found here: http://webhelp.madcapsoftware.com/flare ... Styles.htm
Others may have thoughts on best practices - but I've always been for making search as easy and robust as possible. This means living with the build times and increase in search database size in the output.
I've found a great way to point users to the fact that you have enable partial term searching, is to display text in the Search button -> tooltip field (edited in the HTML5 skin "UI Text" tab). Here's a screenshot example I made that displays the text "Enter at least 3 characters to Search".
http://i.imgur.com/ecpE3tD.jpg
Doing this will enable users to have some way of knowing (even indirectly) that they have the option of searching with at least 3 characters.
More info on editing the Skin settings in Flare can be found here: http://webhelp.madcapsoftware.com/flare ... Styles.htm
-
Lydia
- Sr. Propeller Head
- Posts: 373
- Joined: Tue Apr 23, 2013 3:19 am
- Location: The Netherlands, Amsterdam Area
Re: Best practices for search - partial search or no?
I would even use the Search field itself and instead of "Search" put in text like "Enter at least 3 characters". This setting is in the Skin, UI Text tab, property Seach Input (Placeholder). Just in case someone misses the tooltip ...
Using Flare 10.2 and Flare 11 on Win 7
Re: Best practices for search - partial search or no?
Thanks, Jose and Lydia for your useful suggestions on how to make the required number of characters evident to users.
We have gone back and forth on whether to implement the partial search feature. The build time for the war file seems to be the show stopper. It is taking too long (over an hour) and that process can be very time sensitive as certain stages of the release cycle. We are considering implementing partial search for our technical Help, but only for the Help that is posted to our Web site (not what is delivered on the DVD).
Additionally, many internal users of the Help have said that they do not use partial search (and wouldn't if we implemented it - this was said without knowing about the build time). I was guessing that users probably expected partial search, but the feedback from internal users is leading me to question my thinking.
Does anyone have anything to add about best practices for searching, and your experiences in assessing users expectations regarding search?
Thanks for your help....
We have gone back and forth on whether to implement the partial search feature. The build time for the war file seems to be the show stopper. It is taking too long (over an hour) and that process can be very time sensitive as certain stages of the release cycle. We are considering implementing partial search for our technical Help, but only for the Help that is posted to our Web site (not what is delivered on the DVD).
Additionally, many internal users of the Help have said that they do not use partial search (and wouldn't if we implemented it - this was said without knowing about the build time). I was guessing that users probably expected partial search, but the feedback from internal users is leading me to question my thinking.
Does anyone have anything to add about best practices for searching, and your experiences in assessing users expectations regarding search?
Thanks for your help....