We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
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

          Activity

            Loading...
            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

                    Activity

                      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:

                          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: