This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Wednesday, 12 July 2017 22:21 EEST
When we input a multi-word search term, the results return a list of content for each individual word in the search term. For example, if we search for "standard record" we get results for "standard record," but also for the individual words "standard" and "record." We tried to limit the search results by selected "Exact Phrase" instead of "All Words" (in Edit Instance) but for some reason that returned results that were OUTSIDE of our selected "Category" (category "GPO Cataloging Guidelines") that we selected, including returning results from archived articles in other categories.

Is there a back end setting or a search term protocol that will limit the results to the exact phrase AND within the category that we select.

*Please remember to LOG IN because the module is currently published "special."
chadd Depasuale
Minitek Live Search - Professional Subscription
Thursday, 13 July 2017 16:03 EEST
Hi there,

Please update to the latest version of the component and let me know if you still have this problem.
Yannis
Support Team
Friday, 14 July 2017 19:51 EEST
The problem is NOT resolving. We updated to the latest version of the component—(3.42) and module (3.41) for Minitek live search—and are STILL having the problem with results being returned for article categories that we did NOT select.

We want to be able to search for an "exact phrase" (e.g., a multi-word term) but only in the category "GPO Cataloging Guidelines" that we select. What is happening is if we specify "Exact Phrase" in the module setting (see attached image "Minitek Module setting") the results change and start to search through all the categories (for example "Cataloging Guidelines," "News and Alerts," Projects, etc. (See "Minitek Results Returned 2").


Attachment
chadd Depasuale
Minitek Live Search - Professional Subscription
Saturday, 15 July 2017 04:15 EEST
I will issue an update next week with a fix for this problem.
Yannis
Support Team
Monday, 17 July 2017 16:30 EEST
Hi there,

This problem should now be fixed in version 3.4.3.
Yannis
Support Team

This website uses cookies so that we can provide you with the best user experience. By clicking "continue" you agree to cookies being used in accordance with our Cookies Policy.

Search