Question

Quick Fields not populating metadata field using Omnizone OCR process

Quick Fields

Updated December 29, 2016

asked on December 28, 2016

Hello,

I am having an issue where one zone within the OmniPage OCR process is not populating the associated metadata field value. This was working previously for years, but suddenly stopped when I added a new data field to the document. The OCR zone in question was not changed when the additional field was added, only a slight tweak to the actual zone size to accommodate the new zone. I am using the same test page as I used for my sample page to confirm the zone fields line up correctly.

Looking at the output when I run a sample page, I can see the value is being read/OCR'd correctly. I took that value and used it to test the token regular expression, no issues. It read the correct value removing the data I did not want to capture.

I went as far as deleting the zone and creating a new one for this particular field. No luck.

Any thoughts as to why this field no longer works?

Thanks!

Tom

0 0

Answer

SELECTED ANSWER

replied on December 29, 2016

Hi Blair,

Thanks for the response. I figured it out. I wasn't taking into account the non-alphanumeric character in my expression.

1 0

Replies

replied on December 29, 2016

Hey Thomas,

What expression are you using in your pattern matching token to retrieve the data?

You said you changed the size, did you change the height or width of the box? Was it a single line or multiline OCR previously?

You could specify which line within the OCR that you want it to extract within pattern matching.

Cheers,

0 0

You are not allowed to follow up in this post.

Question

Question

Quick Fields not populating metadata field using Omnizone OCR process

Answer

Replies

Sign in to reply to this post.