Grooper 21.00.0082 is available as of 12-12-2023! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.00.0044 is available as of 06-20-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0026 is available as of 09-16-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 24.0.0012 is available as of 10-10-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Spawn Batch Question
[Deleted User]
Posts: 0 ✭✭
Grooper Version 2.60.0106
We are attempting to use Spawn Batch to allow for Data Extraction on a specific group of doc types. However, when moving the doc types over to a new batch, the naming convention of the batch changes with a new date and time. I know that it is possible to add a prefix, but our optimal solution for what we are trying to achieve would be if we could retain the same file name that the parent file has. For example, our files that we export out of our system are similar to "1234567". If we could have the spawned batch also be named "1234567", even if it had (1) at the the end of it, we could export it properly into our system.
We are attempting to use Spawn Batch to allow for Data Extraction on a specific group of doc types. However, when moving the doc types over to a new batch, the naming convention of the batch changes with a new date and time. I know that it is possible to add a prefix, but our optimal solution for what we are trying to achieve would be if we could retain the same file name that the parent file has. For example, our files that we export out of our system are similar to "1234567". If we could have the spawned batch also be named "1234567", even if it had (1) at the the end of it, we could export it properly into our system.
Tagged:
0
Best Answer
-
GrooperGuru Posts: 481 adminJimmy, I think I know what you are trying to accomplish. Your original file comes in as one large PDF file named "1234567". That document would be a level 1 folder in the batch. Now you run Classification/Separation on that document to produce a bunch of classified level 2 documents that are children of the original document. At this point, your goal is to only run extraction on a small handful of Doc Types. Then export everything in such a way that each classified lvl2 document still has awareness of which PDF it came from.
To do this, I would recommend that you not use Batch Spawning at all. As soon as you break the lvl2 documents out of the batch, you lose the understanding of where the document originally came from. Instead, (assuming this won't cause other issues) I would first recommend a quick reorganization of your Content Model. I would create a Content Category in the model named something like "Extraction" and move all of the Doc Types eligible for extraction inside of that category. Then, on your extraction step in the process, use a Should Submit Expression telling Extraction to only run on documents whose Parent Content Category is the "Extraction" category. The Expression would look something like this:DirectCast(Item,BatchFolder).ContentType.ParentNode.Name.ToString = "Extraction"
Matt Harrison
Product Manager
mharrison@bisok.com7
Answers