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

Introduce new language resource identifier specificId

    XMLWordPrintable

Details

    • High
    • Hide
      Introduce a new ID field for language resources in available also via ID.
      It should contain an ID generated / coming from the originating data system - if any.
      Show
      Introduce a new ID field for language resources in available also via ID. It should contain an ID generated / coming from the originating data system - if any.

    Description

      todo

      Add a new data field specificId in LEK_languageresources.

      It can be filled with an identifier coming from the connected MicroService, is null by default.

      For GroupShare it is filled with the UUID from GroupShare concatenating the language combination currently stored in specificData. So that each GroupShare TM can be identified in our system with data from GroupShare.

      Therefore the field should be read only via our API.

      The goal is that the flexible specificData specificId field remains internal and should not be used by API.

      For GroupShare a migration script filling the field from specificData must be implemented.

      In the same run the langResUuid field of GroupShare entries must be updated to a random uuid - currently it contains non unique GroupShare UUIDs. Check for usages of that data in the application where it must be updated too.

      Update the REST API Doku in confluence.

      See MittagQI Internal Description for some internal todos.

      Attachments

        Issue Links

          Activity

            People

              pavelperminov Pavel Perminov
              tlauria Thomas Lauria
              Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: