Question

Scanning Page Removal Default Value

Ideas Scanning

Updated October 27, 2014

asked on October 21, 2014

Just wanted to find out why in the Laserfiche scan client the default option for the Page Removal Image Processing feature is set to Remove Page 1 instead of Images whose file size is less than 3000 bytes. Besides the second option being the by far the most common usage with my customers (to delete blank pages/back sides when duplex scanning) it is also the less dangerous of the two options, as I've had several customers inadvertently add this and find out later what was lost. Maybe other people use the actual page 1 removal piece more and I am the exception but I just wanted to see what the reasoning was for that default choice?

1 0

Answer

SELECTED ANSWER

replied on October 24, 2014

Beau, what Brett is saying is that Page Removal defaults to page 1 in LF Scanning because it defaulted to page 1 in Quick Fields. And in Quick Fields, the main use case was for removing slipsheets. And you get a chance to test before you save the session. But you're right that in ad-hoc scanning, removing blank pages is the more common use case and since you're not saving the configuration for further use, testing it first rather than assuming it will work the way you want is not expected behavior.

I'll add it to the to-do list for next version.

1 0

replied on October 27, 2014

I agree it should still be the default in QuickFields as those slipsheets are very common. Thanks for adding that in the to-do list to switch the default in the LF scan client as some of the users don't always properly test after clicking on that option. I appreciate y'all's help on this.

0 0

Replies

replied on October 24, 2014

Hi Beau,

I don't know if we have any hard stats about which setting is used more often, but removing page 1 is definitely a very widely used option. Slipsheets are a popular method of identifying document classes, but results in a mostly useless barcode sheet as page 1 in your document. Using the "remove page 1" setting fixes that issue.

Hopefully people are testing before deploying their Quick Fields sessions in a production environment, but I can certainly see your point about that being a "dangerous" setting to have as the default. We'll be sure to pass your thoughts on to the development team for consideration. Thanks for the feedback!

1 0

You are not allowed to follow up in this post.

Question

Question

Scanning Page Removal Default Value

Answer

Replies

Sign in to reply to this post.