Hi Guys, Sorry for the Late reply
From my understanding, Many of you guys misunderstood the Classification Scope part of DU which I will explain.
PLS BARE WITH ME FOR 5 MINUTES!
We got a manual solution but effective in a short timeline!
We had 10 documents which are Promissory Note for Loan Approval
These documents are fixed templated documents which we assumed the position of the fields also will be the same. IT WAS NOT!
With the given samples you can notice that the fields that need to be extracted are differently positioned (Eg: Loan Number, MIN Number, etc.,)
Using DU, we defined Taxonomy, Digitization as it should be (Note: We didn’t Classify the document because all the keywords in the document are BASICALLY SAME!)
We reached a point where we need to decide the extraction method. In the Data Extraction Scope, There four major things were available.
This extraction method requires a Predefined ML Model which is not present or We had to create a custom ML Model which requires time and there were only 10 documents so NO!
Intelligent Form Extractor:
Since we didn’t need any handwritten fields to be extracted. NO!
Let’s get to the obvious methods. Regex Extractor and Form Extractor
Most of the fields don’t have a pattern like (Eg. Name, Address, and EVEN Loan Number!)
So the Most obvious would be FORM EXTRACTION
Since FORM EXTRACTION is basically Position based approach we couldn’t determine the Template that needs to be created.
After a lot of research and the Trail & error method, we found that we can CREATE MULTIPLE TEMPLATES for the SAME DOCUMENT TYPE ID!
So we had to create 6-7 templates to compensate for the bad results
It takes some time to process the documents (took 2-4 mins in Data extraction scope) But works like a charm.
FOR LONG RUN this will not be a valid solution because with templates it may or may not extract the correct details.
This is where ML comes in!. We need to create a custom ML Model approach with AI Fabric, Data Manager, and DU Tools.
NOTE: We did create templates on different desktop and while exporting and sharing through OneDrive the same.
WE EXPERIENCED A ERROR WHILE IMPORTING and FOUND THAT ONEDRIVE COMPRESSION CAUSED THIS ERROR. GOOGLE DRIVE JUST WORKS FINE!!!
THANKS, GUYS FOR ALL THE SUPPORT!
@Lahiru.Fernando @prasath17 @poorna_nayak07 @tudor.serban