Assigned
Status Update
No update yet.
Comments
va...@google.com
ar...@google.com
Hello,
To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue:
- Has this scenario ever worked as expected in the past?
- Do you see this issue constantly or intermittently ?
- If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
- To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
- It would be greatly helpful if you could attach screenshots of the output related to this issue.
Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.
Thank you for your understanding and cooperation.
ar...@google.com
Hello,
Thank you for reaching out. Here is the information requested regarding the reported issue:
In response to the first point, I previously conducted an uptraining with approximately twenty bank statements, and this issue did not occur.
For the second point, I have attempted the uptraining three times, and the same error appeared each time.
To reproduce the issue: I labeled 76 bank statements, dividing them as follows—59 in the training dataset and 17 in the test dataset. I also modified the label schema by deactivating the following labels: account_types, bank_address, bank_name, client_address, and client_name. Additionally, I created a new label for rib (bank account identifier). I then proceeded to uptrain a new version, and the issue arises during this process.
I hope this information helps clarify the situation. Please let me know if you need any further details.
Thank you for your assistance in resolving this matter.
Thank you for reaching out. Here is the information requested regarding the reported issue:
In response to the first point, I previously conducted an uptraining with approximately twenty bank statements, and this issue did not occur.
For the second point, I have attempted the uptraining three times, and the same error appeared each time.
To reproduce the issue: I labeled 76 bank statements, dividing them as follows—59 in the training dataset and 17 in the test dataset. I also modified the label schema by deactivating the following labels: account_types, bank_address, bank_name, client_address, and client_name. Additionally, I created a new label for rib (bank account identifier). I then proceeded to uptrain a new version, and the issue arises during this process.
I hope this information helps clarify the situation. Please let me know if you need any further details.
Thank you for your assistance in resolving this matter.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
We are facing the same issue as described here:
We utilise the service to cater to both US & European regions (different processors). The normalised date returned by DOCAI seems to be inconsistent/ and potentially incorrect for the European region. It usually defaults to MM-DD-YYYY when reading dates in AA-BB-CCCC formats, except for cases when AA>12 in which case it parses the data as DD-MM-YYYY. This works fine in the US market as the expected date formats are almost always MM-DD-YYYY. However, in the European markets this would lead to inconsistent date formats. This inconsistency makes it difficult for us to choose a specific date format (MM-DD-YYYY or DD-MM-YYYY) on our end when reading the normalised date returned by DOCAI.
What you expected to happen:
Ability to choose the expected date format on DOCAI to be used for normalizing date fields. This would allow us to set the specific formats based on the region we are catering to.
Steps to reproduce:
Upload any invoice with the above date formats and submit to DOC AI
Other information (workarounds you have tried, documentation consulted, etc):