Question

First page identification is not always on first page

Quick Fields

Updated May 13, 2014

asked on May 9, 2014

The customer has a unique situation in that they need to identify the first page of the document that isn't always the first page. It could range from page 2 to page 5. If you are using Capture Engine as the scan source, you do not have the ability to specify what pages to look on for the identification. It will always treat the first page of the document as the first page and not process the additional pages for identification. The customer wants to know is there a work around to this and if not, are there any plans to add this feature in future versions of Quick Fields.

0 0

Replies

replied on May 9, 2014

Quick Fields needs some sort of consistency in order to identify and separate documents. In your case, since the first page isn’t always the first page, First Page Identification will not be able to distinguish where a document starts and ends. Anytime that first page condition is met, even if it was in the middle of the actual document, that would become the new first page of the next document. This is how First Page Identification is designed to work, as the first page is usually, in fact, the first page.

If the customer's first page is not consistent, you may need to come up with another method for identifying documents. Are the documents all the same number of pages? If so you could limit each document to only contain that number of pages. Are there any consistent identifying factors on the last page of the document? If so why not use Last Page Identification! Another consideration would be to put a slip-sheet in between documents to separate them. You can mix and match identification conditions to further define what should be one document.

If you give us a little more information on the process and the documents themselves, perhaps we can come up with a work around. For more information on different identification methods and how they can interact, check out our online help files.

1 0

replied on May 12, 2014 • Show version history

The question was entered on my behalf. When we identify a document, I populate a metadata field with a specific value based on the identification criteria.

Here's the situation:

We use Capture Engine instead of scanning in documents.

Our documents are anywhere from 1 page to many pages (generally 1 to 5 pages) and originate from a multi-page tiff file via import agent. The multiple pages always represent a single Document.

Once the document is identified, I populate a metadata field and route the document to a new folder.

The problem is that the identification criteria may be on a page other than page one. Since you added the option of Last Page identification in version 9 of Quick Fields, I wondered if it is feasible to add an option such as "Any Page".

0 0

replied on May 13, 2014

Well the way I identify a specific page as being page 1 is I use the key identification criteria and use pattern matching to then conditionally split the page.

An example of this would be if the page I want has a social security number as the identifying criteria. I would then pattern match the SSN and set the identification condition.

In doing so this will however split this page out from the rest of the pages. Are you wanting it to just identify a criteria in order to add it to metadata without splitting the page out from the rest of the document? If that is the case, instead of using the identification condition to split the page out you could use pattern matching to then fill in whatever metadata you would like.

Is what you are entering into the metadata dynamic based on the identification criteria?

0 0

You are not allowed to follow up in this post.

Question

Question

First page identification is not always on first page

Replies

Sign in to reply to this post.