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

Refactor TBX Import due several structural problems

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • None
    • None
    • TermPortal
    • High
    • Refactored old Import methods and Optimised for new TBX structure.

    Description

      Problem

      • The TBX import is very chaotic in data storage and saving. That results in 3 save calls per term.
      • internal delete calls are not addicted to the term collection only to the termEntryID: This must not be!
      • saving of the descGrp depends on the position in the XML, if its before the term it is saved, if it is after the term the describGrp is ignored.
      • the method validateTbxLanguages is making mostly nonsense
      • the BLOCKSIZE stuff (performance optimized bulk term saving) is missing

      Solution

      • Refactoring of the whole TBX import when adding new features

      What should be fixed with refactoring:

      • Values from normativeAuthorization typed termNote have precedence over administrativeStatus typed notes when saving to term.status
      • Something strange is happening with term attribute data, on my machine the term attributes were created with ID 1 on 18.8.2018, two days before I run tests which should also create term_entries (and at least increase the AUTO_INC), this was obviously not the case.

      Attachments

        Issue Links

          Activity

            People

              marcmittag Marc Mittag [Administrator]
              tlauria Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: