This seems like such a simple solution but when an operator does this a dozen times a day, every day, this will become a very mundane process, especially when hundreds of documents are scanned at once AND especially since they are used to the current process.  

The alternative solution is not a good answer IMHO.  The only reason I would upgrade to version 10 would be so my users can use the Scanning application.   I see this as a major improvements because I won't have to worry about my operators mucking up the session template.

I would like to request an enhancement so the capability that exists now is brought back....Ability to enter metadata before the documents are scanned that is then applied to every document.

Hi Gene,

Can you elaborate on what type of information the operators are entering at the beginning of each batch scan? This will help us properly address your use case in future versions. 

1. We have a batch number that gets entered for every session.  The same batch number is applied to all documents in the session.  This field is part of every type of document we scan.
2. We have a meeting every Wednesday where notes are written onto documents.  These documents are then scanned using Quick Fields.  The meeting date is one of the fields in the template.  This meeting date is the same date for every document scanned.  Currently the operator enters the batch number and meeting date before the documents are scanned.
3. Another document type contains a field that specifies the Date Received (the date the document was received in the mail).  We cannot use the Creation Date because we often do not scan the documents the same day they are received and it is important for auditing purposes for us to know exactly what date the documents are received in the mail.  This is another field that is entered once for every document in the session.

Thank you for the use cases! We'll look into streamlining this process in future versions. In the meantime, I think your best bet is to train scanner operators to use "CTRL + A" to select all the documents for the batch, and then type the desired values into the fields (which will apply those values to all selected documents).

One additional question: out of curiosity, does the batch number correspond to something specific (like something outside of Laserfiche), or is it just there to provide a unique number? I ask because I'm wondering if this is something we could automate in a future version. 

We have a similar case and the batch number correspond to the box number where the document will be physically store and send to an external vault.

We look to get fields that we can set before the scanning process and can be use as metadata in the quickfield process. so we can use these system fields to populate laserfiche fields.

is this kind of feature can be customize with the actual version of QF 10 ?

If you want to set some fields manually before running the document through Quick Fields,  probably the best way to do this would be to scan into Laserfiche first, apply fields containing the batch number information, then use Quick Fields' Laserfiche Capture Engine to do the rest of the processing. This way, Quick Fields can read the existing field data and use that information in its processing. 

it is really not user friendly. we should be at the scaning phase to add a lot number manually or automaticaly

We will look into a more user-friendly way to do this in future versions.

For now, here is a summary of some alternatives:

• After scanning the batch in Quick Fields Scanning, use "CTRL + A" to select all the documents for the batch, and then type the desired value into the appropriate field (which will apply those values to all selected documents).
   
• Use Quick Fields instead of Quick Fields Scanning to do the scanning and edit the document class before each scan (as described by the original post).
   
• Scan into Laserfiche first, apply fields containing the batch number information, then use Quick Fields' Laserfiche Capture Engine to do the rest of the processing. 
   
• Before scanning a batch, create a cover sheet with the batch number on it (perhaps as a barcode). Scan the cover sheet as the first page of the batch and configure the Token Collector process to automatically pass the information from the scanned cover sheet to all the documents in the batch.