You are viewing limited content. For full access, please sign in.

Discussion

Discussion

How does the improved search interface on Weblink 9 handle dashes?

posted on March 17, 2015 Show version history

I have a client who has product numbers dating back years and years that have a format of 

"123-4567"

 

When searching with the previous versions of Weblink the dashes always meant that they searched anything starting with 123 that didn't contain 4567. 

As a result when we deployed them we needed to recompile the ASP scripts to include javascript that would change the search text to "123&4567" automatically. 

In the new version is this still needed? If there is a dash with no space in front of it is it handled the same?
I would expect a "-" with a space in front of it to be handled as a negative, and a dash embedded without spaces to not handle as a negative.   This is how Google and most other search providers handle these. 

 

 

0 0
replied on March 17, 2015

Hello Chris,

WebLink 9 should solve your problem and let you search much more easily. In this version, we incorporated LFBasic search so that WebLink General searches match the Client and Web Access. Testing your case in particular, a search for "123-4567" will bring up documents titled 123-4567, and the server will not see the hyphen as an operator for NOT. 

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.