Question

Can text searches be eliminated completely from Web and Windows Client?

Web Client Laserfiche Search and Retrieval

Updated April 4, 2017

asked on March 30, 2017 • Show version history

I have a client with a very large repository. Currently they run into an issue where an end user(s) run a quick search for a word like "Bail". If template or entry is selected this search works as expected without issue. If the user has text selected Armagideon begins and the server must be given mouth to mouth to get it operational again. If everyone waits long enough the search will complete and return back millions of results.

This client has asked many many times if they can shut off text searching. They want to do this very badly!

I know the following exists...

https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/LFAdmin/Content/search-attributes.htm#Selected

This discusses what is checked and not checked in the quick search drop down.

Also there is;

https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/LFAdmin/Content/settings-lockdown.htm#Search

Which discusses setting the limit of text search results. (Will this only return the first 100 and end the search or will it run the whole search and display the top 100?)

They are looking for a way to remove the possibility of a text search from this DB/Server entirely in the Web and Windows client.

Is there a way to do this? If not, why not? This server only runs Laserfiche and SQL. It has dual 12 core processors and 128GB of memory and serves about 100 users. The text search still drags the server to it's knees.

Thanks

John

0 0

Answer

SELECTED ANSWER

replied on March 31, 2017

You could also add some of those words as Stop Words for LFFTS so they are not indexed to begin with.

1 0

Replies

replied on March 30, 2017 • Show version history

I know that this does not do what you are asking about, but have you tried running LFFTS in parallel IO mode to improve search performance?

See DevNotes: LFFTS9.2/List Of Changes921

1 0

replied on March 31, 2017

I have not but I am willing to give anything a try. Thanks Bert I will give it a try.

0 0

replied on March 31, 2017

Would you please be more specific about 'text search'? If it refers to full text search, and you want to disable it for all the users using the repository, then you can delete the catalog in Admin Console. (If you are not sure about whether it will break other features the customer need, then you can detach it first, and attach it back on necessary). And if it refers to all the search types in LFS, and you want to disable it for the selected users, then you can use the search feature right setting. And if you want to disable the selected (common) words in full text search, then, as Blake suggested, you can use stop word. And as Bert mentioned, parallel IO mode can improve full text search performance, however it doesn't work for database search.

As for the search performance issue, it requires more information to troubleshoot the issue: like the query, the search settings, the query type, the content in the documents, the document number, the folder structure, and security settings. I would suggest to open a support case for the search performance issue.

1 0

replied on April 2, 2017

Hi John,

Completely remove the Text search feature by removing the Catalog from Index node in the Admin Console, as Chi also mentioned.

So that index will not be available for the search, and it will not impact the field level search. If you have a large repository and having millions of documents, means that there will be a larger search catalog too. Or

Restricting users by Attributes of Everyone Groups:

[Settings]LimitSearchResults is set to Yes

[Settings]FullTextSearchLimit is set to 100(or any numbers of results required)

Hope this will help you a lot.

1 0

replied on April 4, 2017

Thanks for all the feedback. If we detach the search index if a scanning station or someone's import settings have OCR and Index selected they will get an error correct? Also if they do pick text search they would also get an error when search correct?

I kinda already know the answer but worth tossing it out there.

To keep tickets lower I think we are going to try to add as many stop words as we can think of first and limit the search results to 100. Is there a way to know what word was searched for when the SQL server goes into a spin?

Thanks

John

0 0

You are not allowed to follow up in this post.

Question

Question

Can text searches be eliminated completely from Web and Windows Client?

Answer

Replies

Sign in to reply to this post.