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

Termcollection DeepL Glossary association and upload partly does not work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • None
    • None
    • LanguageResources

    Description

      To reproduce / original problem

      • Create new client
      • Create new TermCollection. In the "add TermCollection" window select
        • TBX
        • the new client
        • Use as DeepL glossary source
      • Save the new TermCollection
      • Open the new TermCollection: The "DeepL glossary checkbox" is not set
      • Try to set it now and save it. Open again for editing. Checkbox "DeepL glossary source" is still not set

      The reason in this case is, that there is no DeepL language resource so far assigned for the client, to which the TermCollection belongs. Therefore translate5 simply ignores the checkbox, because no connection can be made.

      Further update problems

      In the above context we discovered, that some behavior of the DeepL glossary integration needs to be changed/corrected, which will also solve the update problem.

      Needed back-ground information

      A DeepL glossary resource at DeepL side can not be updated. It can only be created (and filled in the creation process) or it can be deleted and a new one can be created instead of the deleted one.

      Explanation of update/trigger problems 

      Current trigger situation

      Please check, if the following really works

      Currently the update of a DeepL glossary resource (through deletion and recreation) is only triggered, if

      • manual process
        • a user manually unchecks the "DeepL glossary source" checkbox at a termCollection. This deletes the glossary at DeepL
        • a user manually rechecks the checkobx. The glossary is newly uploaded
      • Adding a TBX to an existing TermCollection with "DeepL glossary resource" checked
        . In this case translate5 automatically
        • Deletes the existing DeepL glossary
        • Creates a new one with the updated terminology from the TermCollection
      • Creation of a new TermCollection with "DeepL glossary resource" checked right away
        • If there are DeepL resources belonging to the same client(s):
          • Creates a new glossary

      Make sure, the checkbox "DeepL glossary source" can even be checked, if there is no DeepL language resource available for one of the clients, that are assigned to the TermCollection.

      Triggers of (re)creation

      • Creating a new DeepL language resource / assigning an existing DeepL language resource to a new client
        • if there is a TermCollection with "DeepL glossary source" active, that belongs to the same client, trigger a glossary creation at DeepL
      • Assigning an existing Termcollection to a new client
        • if there is a DeepL language resource of the same client, trigger glossary creation at DeepL
      • Updating, deleting or creating a new term in a TermCollection in TermPortal
        • only if the term itself is updated or newly created (not an attribute of the term)
        • AND only if the processStatus of the term is part of the list of the sys-config param runtimeOptions.terminology.usedTermProcessStatus
        • If this TermCollection is a DeepL glossary source AND if :
          • Deletes the existing DeepL glossary
          • Creates a new one with the updated terminology from the TermCollection
      • Changing processStatus of a term in TermPortal
        • if the old processStatus IS part of sys-config param runtimeOptions.terminology.usedTermProcessStatus AND the new processStatus IS NOT part of the sysconfig param
        • if the old processStatus is NOT part of sys-config param runtimeOptions.terminology.usedTermProcessStatus AND the new processStatus IS part of the sysconfig param

      (Re)creation of glossary

      If one of the triggers in this issue is triggered, a glossary is created and it is used for all tasks / in InstantTranslate

      • if the Termcollection from that the glossary originated belongs to the same client as the task
      • AND if the user in InstantTranslate belongs to the same client as the TermCollection.

      Triggers of deletion

      • Removing client from TermCollection resource
        • delete all DeepL glossaries, that stem from this Termcollection
      • Removing client from DeepL resource
        • delete all DeepL glossaries, that stem from TermCollections, that are only connected to this DeepL resource through the removed client (caution: A TermCollection may still be connected through other clients)
      • Deletion of a TermCollection resource
        • delete all DeepL glossaries, that stem from this Termcollection
      • Deletion of DeepL resource
        • delete all DeepL glossaries, that stem from this DeepL resource

       

       

       

      Attachments

        Issue Links

          Activity

            People

              oleksandrmikhliaiev Oleksandr Mikhliaiev
              sylviaschumacher Sylvia Schumacher
              Aleksandar Mitrev
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 days
                  4d
                  Remaining:
                  Remaining Estimate - 4 days
                  4d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified