Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
Critical
-
DeepL API key provided on customer lvl now applied as for DeepL Language Resource as to Term Collection related to it
Description
Should be solved together with the 2 linked issues
https://jira.translate5.net/browse/TRANSLATE-3498
https://jira.translate5.net/browse/TRANSLATE-3518
We introduced DeepL API key on customer config lvl
But in fact we have Term Collections that may be connected to DeepL resource
And in reality we now have no way to bind customers Term Collection with Customers DeepL
Need to think a way to do so.
DeepL language resource glossaries id | hash | lrId | glossaryId -------------------------- 1 APIKEY - LR1 - glossaryId 2 APIKEY - LR2 - glossaryId Unique hash + lrId TODOS: 1. On create you add the link in the table 2. On search you fetch from the db by lrId and hash 3. Remove the default glossaryId from lr specific data 4. Migration script to update the "link" table with the specific data glossaries
Attachments
Issue Links
- blocks
-
TRANSLATE-3518 Infrastructure for using "translate5 language resources" as training resources for MT
- Selected for dev
- is blocked by
-
TRANSLATE-3898 Change tmx import to be able to use html multipart fileupload
- Selected for dev
- relates to
-
- Done
