Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-3899

Overwritten DeepL API key produces error with related Term Collection

Details

    • 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

          Task - A task that needs to be done. TRANSLATE-3518 Infrastructure for using "translate5 language resources" as training resources for MT

          • Done
          causes

          Bug - A problem which impairs or prevents the functions of the product. TRANSLATE-4546 GroupShare TMs can not by synchronized

          • Releasable
          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. TRANSLATE-3883 Make TMX export run as stream

          • Done
          relates to

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-3790 Overwrite DeepL API key per client

          • Done
          mentioned in

          [translate5 Confluence] Page Page No Confluence page found with the given URL.

          Activity

            [TRANSLATE-3899] Overwritten DeepL API key produces error with related Term Collection
            tlauria Thomas Lauria made changes -
            Link New: This issue causes TRANSLATE-4546 [ TRANSLATE-4546 ]
            tlauria Thomas Lauria made changes -
            Resolution New: Done [ 6 ]
            Status Original: Releasable [ 10901 ] New: Done [ 10000 ]
            aleksandar Aleksandar Mitrev made changes -
            Fix Version/s New: translate5 - 7.8.0 [ 14201 ]
            sylviaschumacher Sylvia Schumacher made changes -
            Status Original: Front-end testing [ 11001 ] New: Releasable [ 10901 ]
            sylviaschumacher Sylvia Schumacher made changes -
            Description Original: 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.
            {code:java}
            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 {code}             		New:  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.
            {code:java}
            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 {code}
            aleksandar Aleksandar Mitrev made changes -
            Status Original: Final pull request [ 10005 ] New: Front-end testing [ 11001 ]
            sanya@mittagqi.com Sanya Mikhliaiev made changes -
            Status Original: In Progress [ 3 ] New: Final pull request [ 10005 ]
            sanya@mittagqi.com Sanya Mikhliaiev made changes -
            Status Original: Selected for dev [ 10100 ] New: In Progress [ 3 ]
            marcmittag Marc Mittag [Administrator] made changes -
            Start Date [Gantt] Original: 03/Jun/24 11:00 AM New: 06/Jun/24 9:00 AM
            marcmittag Marc Mittag [Administrator] made changes -
            Start Date [Gantt] Original: 31/May/24 3:00 PM New: 03/Jun/24 11:00 AM

            People

              sanya@mittagqi.com Sanya Mikhliaiev
              sanya@mittagqi.com Sanya Mikhliaiev
              Aleksandar Mitrev, Leon Kiz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: