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

Question

Question

Using Substitution to Correct Pattern Matching

asked on June 8, 2015

I'm running  a Quick Fields session on older documents and I'm having a certain piece of metadata that is commonly misread

Shafter City Council become, Shatter City Council or Shaffer City Council. I created a substitution so that anytime the OCR reads those inputs it changes it to the correct Shafter City Council.

My question is how do I use this new token along with the original one to capture when it is ready correctly? Do I put both in the metadata field? Is there an option to click use substition if first pattern matching returns invalid results? 

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on June 17, 2015

Hi Brittney,

 

This is possible, and one way to do this would be using the “Replace the input token’s value with the result” option within the substitution activity.  After you make your substitution, it will update your original token with that new value.  This way, you can always use that one token in the metadata.  In the event a substitution isn’t needed, the original token remains unaffected. 

 

For example, I used an OmniPage Zone OCR activity to grab a city council name (“Shafter City Council”) from a set of documents .  I then used a substitution to replace “Shatter” with “Shafter”, and it would then update the original Zone OCR token.  

 

 

With the Zone OCR token in my metadata field, it successfully replaced an incorrect spelling (“Shatter”) and assigned the correct one to that piece of metadata.  I also scanned in a document with the correct spelling without changing the activities above, and it successfully assigned the correct name to the metadata field. 

 

This way, you only have to use one token in your metadata and update it accordingly.  For more information on how the substitution activity works, check out this Help Article here.   

2 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.