Status Update
No update yet.
Comments
sh...@google.com
sh...@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.
sh...@google.com
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.
ge...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
If you are looking for a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
nr...@google.com
nr...@google.com
Hello,
Thanks for reaching out to us!
This issue request is acknowledged and we will validate it further. Though we can't provide an ETA on this issue nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products.
Thanks
Description
Problem you have encountered:
When labeling documents in the UI for custom document extractor training, 0 values that are underlined are not detected as text. This implies that they cannot be selected as value for a label. When trying to put a bounding box around the 0 and assigning it to a label, an error message is displayed:
Cannot create labels with empty values
Enter a value or adjust your bounding box to ensure text has been selected.
What you expected to happen:
The character 0 should be detected, even when underlined.
Steps to reproduce:
Additional information
This issue is not encountered with other underlined numbers or text.