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

Question

Question

Why documents are sent to the OCR queue instead of being OCRed immediately

asked on August 28, 2019

In WEbclient 10.4 I'm getting the message "The documents were sent to the OCR queue" after I select a document to be OCRed, why?

 

The document actually never goes through the OCR process.

 

0 0

Answer

APPROVED ANSWER
replied on August 28, 2019 Show version history

OCR in the Web Client is not done locally, it is done by DCC. In order to be processed by DCC it needs to be sent to a queue so that an available worker can perform the work and return the results.

As to why the work is not being done... Have you verified that DCC is installed and configured correctly, and is working?

4 0
replied on August 28, 2019

To expand on Devin's comment, the reason OCR is handled this way in the Web Client is that OCR is a very resource-intensive process.

Offloading Web Client OCR to a DCC ensures that OCR tasks will not consume server resources needed to support the web application, which could very easily impact overall system performance.

With the desktop client, the OCR can occur locally on the PC, so there is no burden on the servers and therefore minimal impact.

2 0
replied on August 28, 2019

Hi Devin, I'm the IT person who worked with the migration to the new server for LF for Laura. I'm still in the learning phase so what you mentioned regarding DCC helped. It was installed but it was not setup during the process. After setting it up, it looks like it's processing the jobs. Thank you very much!

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.