Repository navigation
Replies: 2 comments 3 replies
Hi Michael, yes, the different spelling is exactly the cause, and it's a bug in paperless-gpt, not in your setup. What happens: paperless-ngx treats correspondent names as unique regardless of case, so The fix is in #1147:
Once it's merged it will be in Until then, for document 40: remove |
Update: #1147 is merged. In about 15 minutes, once the build finishes,
It will be in the next release too. Feedback from your instance is very welcome. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I don't know why I'm getting this error in PP-gpt:
Of course this correspondent alredy exist from previous OCR runnings and applying the existing correspondent did not fail previously, so why out of a sudden, am I getting this error now instead of just using the existing one?
The spelling is slightly different though, GPT tries to create MONTANA Energieversorgung, however, the existing correspondent reads: Montana Energieversorgung. May this be the source of the error?
All reactions