Thanks for sharing the knowledge. It very helps. Could you please create a video for Hypotheses and optimizing the search and Tips for group and structure to maintain large search elements in Abbyy FC studio.
Thank you for watching our videos and for the suggestion! We're always looking for new video topics and we will add this one to our list. If you have any other questions, please feel free to ask!
Hello, thank you for watching our video. In ABBYY FlexiCapture, documents are processed in batches. When batches are created, they have to be assigned a batch type. This batch type determines the processing settings to be used for the batch Typically batches are assigned to the "Default" batch type. The settings for this default can be found in the "Project Properties" window of the "Project" tab in the "Project Setup Station". As mentioned in our video, if we want to handle processing differently, then you can create and use a new (or multiple) batch type(s). Some of the options you can control in a batch type are the default priority of the batch type, image quality to be used when displaying images on the Processing Stations, registration parameters, specifying how documents should be separated, what preprocessing procedures should be applied to images, how to handle blank pages, which documents definitions to use and which order to use them, recognition settings, specifying a classifier, verification settings, or workflow settings, just to name a few. As mentioned in our video. One of the more common reasons we use batch types is to control registration parameters. Another common need to have a unique batch type is to control the workflow. In the workflow, we can add additional verification stations, along with "automatic" workflow stages such as additional recognition stages or even scripted stages. We do have a video that shows how to create new stages/queues. You can find that video here: ruclips.net/video/vF4bMHzDnFQ/видео.html (Note: In the video we add these queues in the "default" batch settings, this can also be done in each of your batch types as well). As also mentioned in our video, we typically create a "Main" batch type when we first create the project. This allows us to make custom changes to the registration parameters if needed, but it also helps keep the default settings in case it's needed. Hopefully this helps clarify batch types and it's uses a bit more. If you have any other questions, please don't hesitate to ask.
Hi, thanks for another informative video. Recently I've come across another needed functionality, which I'm sure exists but I'm not aware of, and was wondering if you could shed some light on it. Is there a way, along with the data exported to an excel as per a document definition, to also export original filename/link to original document in that excel? If I throw in 50 pdfs for recognition and verification I'd like to know where each came from.
Hi Akis, good question. The IPage has an ImageSource property, so you can access it for example from rule script like this Context.Document.Pages[0].ImageSource; and thus save it to a dedicated Field. Don't forget to check help where is an important sentence: "Contains an empty value if the image was imported by a user manually."
Hello, sorry for the late reply, I'm not sure how your question was missed. Thank you for watching our video and for the question. Something like image source can easily be added an export by creating Service Field. To do this, in the Document Definition editor, right click on the Document Structure name (on right side where field names are located) and select "Create Field" and then "Service Field". In the "Data Source" tab select "Image Source" from the "Source:" dropdown list. Name the field in the "General Tab" and ensure that "Export field value" is selected (should be on by default). When you export to excel you should have a new column with the Image Source name populated in it. Once again I apologize for the delayed response. If you have any other questions please feel free to ask.
Hello, thank you for watching our video. The main use of a test batch is to test your document definition without it counting against your page count. Testing in a test batch also doesn't require your document definition to be published, so you can actually save time by not having to do that. You can save even more time by creating a test batch in the document definition editor. To do this, click the "Batch" tab and then select "Switch to Test Batch...". A new window will pop up where you can either select a test batch that's already been created, or you can create a new test batch. Note: you can't open a test batch that you currently have open. So before opening the document definition editor, you'll have to make sure you're not in any test batches you may want to test in while in the document definition editor. Now to the differences (at least a few of the major ones): 1. In a test batch, you're not in a workflow. This means if you created a custom test batch with extra stages, you won't be able to test those stages. A test batch is basically only the Recognition Stage of your workflow. A Working batch however does follow the workflow. So depending on how you set up image import, the images will automatically flow into ABBYY, create a batch and move through any workflows you have created (along with the standard workflows such as Recognition, Verification, and Export). 2. In a test batch, only the person who created the test batch can see these batches. In a Working batch, whoever has access to the project can see these batches. This viewing is performed in the Verification Station. Since the Verification Station is a completely different station than the Project Setup Station, you can give users access to verifying the batches without giving them access to your project, so you know your settings cannot be adjusted. 3. The last major difference is automation. This one is somewhat related to the first point. Because the test batch is not part of the workflow, there is no possibility for automation. In a working batch however, once the batch is ingested in to ABBYY, it is possible for completely touch-free automation. Depending on how you have the stages set up in the workflow, a batch could potentially move from the scanning stage of the workflow (image import) all the way to the Export stage and then Processed stages of the workflow without a human ever needing to touch the batch. There are other differences between the two types batches, but these are some of the main reasons why you may want to use a working batch vs a test batch. Hopefully this helped. If not, or you have any more questions, please don't hesitate to ask.
im getting an error of invalid version when I tried to open a fsp file created using fc12 distro version in fc12 standalone in another monitor, could you please help in this ?
Hello, I apologize for the delayed response. I'm not sure how your comment was missed. Most likely you're seeing this message because your version of FlexiCapture 12 Distributed is on a newer build version than your FlexiCapture 12 Standalone. If this is the case, you'll need to update your Standalone version in order to use the .fsp file from the Distributed version. Hope this helps. Once again I apologize for the delayed response.
Thanks for sharing the knowledge. It very helps. Could you please create a
video for Hypotheses and optimizing the search
and Tips for group and structure to maintain large search elements in Abbyy FC studio.
Thank you for watching our videos and for the suggestion! We're always looking for new video topics and we will add this one to our list. If you have any other questions, please feel free to ask!
@@Ufcinc : Please also include Fuzzy interval and it's usage. Ex Fuzzy quality
Hi Can you tell me what is a batch type and what is the use of a batch type
Hello, thank you for watching our video. In ABBYY FlexiCapture, documents are processed in batches. When batches are created, they have to be assigned a batch type. This batch type determines the processing settings to be used for the batch Typically batches are assigned to the "Default" batch type. The settings for this default can be found in the "Project Properties" window of the "Project" tab in the "Project Setup Station". As mentioned in our video, if we want to handle processing differently, then you can create and use a new (or multiple) batch type(s). Some of the options you can control in a batch type are the default priority of the batch type, image quality to be used when displaying images on the Processing Stations, registration parameters, specifying how documents should be separated, what preprocessing procedures should be applied to images, how to handle blank pages, which documents definitions to use and which order to use them, recognition settings, specifying a classifier, verification settings, or workflow settings, just to name a few.
As mentioned in our video. One of the more common reasons we use batch types is to control registration parameters. Another common need to have a unique batch type is to control the workflow. In the workflow, we can add additional verification stations, along with "automatic" workflow stages such as additional recognition stages or even scripted stages. We do have a video that shows how to create new stages/queues. You can find that video here: ruclips.net/video/vF4bMHzDnFQ/видео.html (Note: In the video we add these queues in the "default" batch settings, this can also be done in each of your batch types as well).
As also mentioned in our video, we typically create a "Main" batch type when we first create the project. This allows us to make custom changes to the registration parameters if needed, but it also helps keep the default settings in case it's needed.
Hopefully this helps clarify batch types and it's uses a bit more. If you have any other questions, please don't hesitate to ask.
Hi, thanks for another informative video. Recently I've come across another needed functionality, which I'm sure exists but I'm not aware of, and was wondering if you could shed some light on it. Is there a way, along with the data exported to an excel as per a document definition, to also export original filename/link to original document in that excel? If I throw in 50 pdfs for recognition and verification I'd like to know where each came from.
Hi Akis, good question.
The IPage has an ImageSource property, so you can access it for example from rule script like this Context.Document.Pages[0].ImageSource; and thus save it to a dedicated Field.
Don't forget to check help where is an important sentence: "Contains an empty value if the image was imported by a user manually."
Hello, sorry for the late reply, I'm not sure how your question was missed. Thank you for watching our video and for the question. Something like image source can easily be added an export by creating Service Field. To do this, in the Document Definition editor, right click on the Document Structure name (on right side where field names are located) and select "Create Field" and then "Service Field". In the "Data Source" tab select "Image Source" from the "Source:" dropdown list. Name the field in the "General Tab" and ensure that "Export field value" is selected (should be on by default). When you export to excel you should have a new column with the Image Source name populated in it.
Once again I apologize for the delayed response. If you have any other questions please feel free to ask.
Hi, Can anyone tell me what is the use of test batch and also what is the difference between working batch and test batch.
Hello, thank you for watching our video. The main use of a test batch is to test your document definition without it counting against your page count. Testing in a test batch also doesn't require your document definition to be published, so you can actually save time by not having to do that. You can save even more time by creating a test batch in the document definition editor. To do this, click the "Batch" tab and then select "Switch to Test Batch...". A new window will pop up where you can either select a test batch that's already been created, or you can create a new test batch. Note: you can't open a test batch that you currently have open. So before opening the document definition editor, you'll have to make sure you're not in any test batches you may want to test in while in the document definition editor.
Now to the differences (at least a few of the major ones):
1. In a test batch, you're not in a workflow. This means if you created a custom test batch with extra stages, you won't be able to test those stages. A test batch is basically only the Recognition Stage of your workflow. A Working batch however does follow the workflow. So depending on how you set up image import, the images will automatically flow into ABBYY, create a batch and move through any workflows you have created (along with the standard workflows such as Recognition, Verification, and Export).
2. In a test batch, only the person who created the test batch can see these batches. In a Working batch, whoever has access to the project can see these batches. This viewing is performed in the Verification Station. Since the Verification Station is a completely different station than the Project Setup Station, you can give users access to verifying the batches without giving them access to your project, so you know your settings cannot be adjusted.
3. The last major difference is automation. This one is somewhat related to the first point. Because the test batch is not part of the workflow, there is no possibility for automation. In a working batch however, once the batch is ingested in to ABBYY, it is possible for completely touch-free automation. Depending on how you have the stages set up in the workflow, a batch could potentially move from the scanning stage of the workflow (image import) all the way to the Export stage and then Processed stages of the workflow without a human ever needing to touch the batch.
There are other differences between the two types batches, but these are some of the main reasons why you may want to use a working batch vs a test batch. Hopefully this helped. If not, or you have any more questions, please don't hesitate to ask.
im getting an error of invalid version when I tried to open a fsp file created using fc12 distro version in fc12 standalone in another monitor, could you please help in this ?
Hello, I apologize for the delayed response. I'm not sure how your comment was missed. Most likely you're seeing this message because your version of FlexiCapture 12 Distributed is on a newer build version than your FlexiCapture 12 Standalone. If this is the case, you'll need to update your Standalone version in order to use the .fsp file from the Distributed version.
Hope this helps. Once again I apologize for the delayed response.