Question

Quick Fields - First/Last Page Identification

Quick Fields

Updated June 18, 2015

asked on June 10, 2015

I am using Quick Fields batch processing to separate, rename and populate metadata on printed forms that were scanned in large batches. It is renaming and collecting data really well, however, it is not respecting the last page identification the way I expected. I have First Page ID with zone OCR to look for the Account # (but no conditions set) and Last Page ID with zone OCR for the Account # and told it to recognize the last page as being when the last page ID Zone OCR does not equal First Page Zone OCR collected.

Yet, my results are that it still makes 3 separate documents for the three pages with the same account number on them. The Processing Information messages show that those zone OCR's are collecting the right information. Is there something more that I need to set?

Thx, Connie Prendergast, Flagstaff County

0 0

Answer

APPROVED ANSWER

replied on June 10, 2015

If you have no conditions in First Page Identification, then each page is a first page.

Token values are not preserved from page to page, so the last page identification will never be satisfied. But if it were to be satisfied, you'd end up with the first page with a different account ID appended to the previous document.

0 0

View 1 previous reply

replied on June 10, 2015

I had looked at the conditions for First Page ID and couldn't see what I needed. I was thinking I need it to read: where the <empty> would be something that reflects the zone results from the last page, but I don't see where I can get that choice in there. Maybe by creating a new token that holds the result from the last page? If so, can you tell me how I would create that token?

Connie.

0 0

replied on June 10, 2015

Also, my Last Page Identification was

and I had hoped that this would be enough. I now realize that it is probably reading the last page and first page on the same page each time. I guess this Zone OCR of the Account Number idea just isn't going to work. :(

Connie

0 0

replied on June 10, 2015

"X Does not equal empty" is an invalid condition. You want to use "is not empty" if you want to check for non-blank values.

The way Quick Fields identification works is by looking at each page. The simplified process is:

1. Run First Page ID processes

2. Is this a first page?

Yes, start a new doc
No, append to the previous doc

Once it has a document going, if there are Last Page ID processes, Quick Fields checks to see if each subsequent page is the last page of a document. Token values are not kept from page to page. So your Last Page ID condition wouldn't have any knowledge of tokens from previous pages.

1 0

replied on June 10, 2015

I have just thought of something else I could use for first page zone OCR. The total amount spot will have CONTINUED in it if it is not the last page. It will have a dollar value in that spot if it is the last page. I could use that instead of trying to get it to recognize an Account Number change! Thanks!

Connie Prendergast

0 0

Replies

replied on June 18, 2015

My VAR helped me with this. Here's what we used and it worked!

We removed everything out of First Page Identification. Then we used Zone OCR in Last Page Identification. The "Total Amount" is only on the Last Page. On all others, the Total Amount shows only the word CONTINUED.

OmniPage Zone OCR Settings:
- Set it for “All Pages”
- Advanced Options, changed only Character Preference to “Numbers”
- Identification Condition set for the Zone “Is Not Empty”
- Token Format set within the Identification Condition window by hitting Edit Token. Format used was \d.\d\d. The condition is only expected to determine that there are actually numbers in that zone, and that is when it will decide this is the last page.
- Optimization is set for “Accuracy”.

Thanks!

Connie Prendergast, Flagstaff County

1 0

You are not allowed to follow up in this post.

Question

Question

Quick Fields - First/Last Page Identification

Answer

Replies

Sign in to reply to this post.