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

Question

Question

Metadata information are inaccurate when scanning from 2 different versions of scanners

Version 10 Laserfiche Quick Fields
Updated August 17, 2017
asked on August 17, 2017 • Show version history

Hi all,

I have set a QF session with a HP LJ400 M425 scanner. OCR zones are being done correctly on images scanned with this scanner and the metadata information is being captured correctly.

However, when scanning from another advanced version of HP scanner (HP LJ Pro MFP M521dn), the metadata fields are capturing garbage. But, while performing a 'test processes' on the OmniPage Zone OCR process, it is bringing correct information in the Processing Information section.

Thanks to advise.

0 0

Replies

replied on August 17, 2017

Are your OCR zones set up to read by pixel or percent?  If the scanners scan at different DPI and quick fields is set up to read by pixel - you will not be reading the same location of the page.

2 0
replied on August 17, 2017 • Show version history

Hello Jennifer,

Zones have been set up to read by pixels. 100 ppi is used on the HP LJ400 M425 scanner and 100 dpi on the HP LJ Pro MFP M521dn. Then do you recommend that percent is used to read the OCR zones? Even though percent is used, garbage information is displayed in the metadata fields but 'test processes' shows information quite accurate. Is there any confidence level that can be used?

Please advise.

0 0
replied on August 17, 2017

I always use percent as a general best practice for us.  We have so many different departments and scanners that we can not count on the scanners being set the same.

Have you run the quick fields process while it is open and not stored the documents immediately so you can review what it is finding?  Although they both scan at 100 DPI, maybe one of the scanners is dirty and is creating a distorted image when it scans?

I have had that before where one of the scanners was dirty and it was adding lines to the scanned image that were distorting the text it was trying to read.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...