Question

Fixing OCR issues with date fields - Substitution, or is there something better?

Quick Fields Scanning

Updated March 17, 2014

asked on March 14, 2014

Hi folks,

I'm new to this, so I'm sure someone has already solved this:

In Quickfields, I'm OCRing a date, but I keep getting "O" instead of zero. My initial thought is to just grab that token value and substitute any "Os" for zeros. This works for finding the first O but not for a subsequent O. Is it possible to replace all the Os in a token using one Substitution activity?

Having asked that question, is there a better way to do this than substitution?

Thanks,

Adam

0 0

Answer

APPROVED ANSWER

replied on March 14, 2014

Adam,

One thing you can try is setting the character preference. When configuring your zones, click the Advanced options link under Region Selection. In the Advanced Options dialog box, under Setup, you'll see a Character preference option. Select Numbers from the Character preference drop-down. When the OCR engine encounters a character that could be identified as either a letter (O) or number (0), it will default to the type you select here. See if this fixes your issue.

2 0

replied on March 15, 2014

Thanks Misty. Is there a way to do that when collecting values within a multi-value token?

0 0

replied on March 17, 2014

Adam,

That same setting should also work for values collected within multi-value tokens.

0 0

Replies

replied on March 14, 2014

It doesn't matter how much time I spend on this beforehand, the answer usually comes seconds after hitting the submit button.

I'd still be curious to know if there is a better way to do this rather than substitution.

0 0

You are not allowed to follow up in this post.

Question

Question

Fixing OCR issues with date fields - Substitution, or is there something better?

Answer

Replies

Sign in to reply to this post.