Rafael Pólit
Rafael Pólit
How is this not critical? If I have an entity named "Original Name" with a document and an extractor configured for Title, I go into the extractor and see: |...
Check that changing properties OTHER than title is also leaving obsolete data in the current values, or if they are updating correctly and it is only Title that has this...
> I guess this is actually potentially destroying user values? Yes. Values set by user. > This is not correct. In the table we should have one row per document...
There are more complications regarding languages: When sending data to train the model, I believe we are sending "entities that have value in ANY of the languages", but we are...
Please, ensure that all the thesaurus operations are using IDs or temporary IDs and NEVER labels. This problem is not the only issue with duplicated name values, which suggests an...
@mfacar is this still relevant or has this been done through other issues?
Konz mentions this could be related to the error handling in pages. We should definitely know what is the culprit to determine priority and possible fix.
The Medium priority reflects the fact that clicking works, so you can bypass the problem fairly easily. But these type of errors should not escape our testing processes.
After some discussions, we are going to try to: a. Strip the data sent by the "geolocation" endpoint to only geolocation properties b. try to use the same "pagination" approach...
@fnocetti what is the status of the 10.000 limit pagination so we can look into channeling that into the geolocation endpoints?