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

TermPortal as terminology management solution

    XMLWordPrintable

Details

    • High
    • Hide
      Due the new TermPortal all terminology data is migrated to a new database structure, this may run a long time depending on the size of the term databases. The progress can be watched in the transalte5 system log.

      The config values runtimeOptions.tbx.termLabelMap.* are merged into one config runtimeOptions.tbx.termLabelMap

      The config values runtimeOptions.tbx.termImportMap.* (which maps custom to valid TBX term status value) are moved into a own configuration table.
      If the previoulsy confiuration was completly in DB all is fine, conversion is done automatically. If such config was still/again in installation.ini, then migratation must be done by hand. Unknown status values are logged on TBX import.
      Show
      Due the new TermPortal all terminology data is migrated to a new database structure, this may run a long time depending on the size of the term databases. The progress can be watched in the transalte5 system log. The config values runtimeOptions.tbx.termLabelMap.* are merged into one config runtimeOptions.tbx.termLabelMap The config values runtimeOptions.tbx.termImportMap.* (which maps custom to valid TBX term status value) are moved into a own configuration table. If the previoulsy confiuration was completly in DB all is fine, conversion is done automatically. If such config was still/again in installation.ini, then migratation must be done by hand. Unknown status values are logged on TBX import.
    • Introduced the brand new TermPortal, now completely usable as terminology management solution.

    Description

      General idea

      • Rebuild GUI with ExtJs
      • Extend current functionality (browse terms, propose new terms) to a full terminology management solution
      • Browsing terms should stay as simple and fast, as it currently is
      • Browsing terms should still work well on a mobile. More complex functionality does not have to.
      • More complex features than browsing terms are only visible with the correct user rights

      GUI structure and features

      The following screen dummy explains the overall GUI design and gives an impression of most of the features:

      Some features in more detail

      Features and GUI components role-based

      The translate5 ACL-model defines for some things, if they are available and usable via API for a user.

      Details see here: TRANSLATE-1407 - New and changed system roles for TermPortal Selected for Development

      Adding, editing and rejecting terms and adding and editing termEntries

      The GUI dummy shows, where this functionality is located.

      These issues shows, what it does: TRANSLATE-1408 - Adding of termEntries, terms and attributes Selected for Development TRANSLATE-1409 - Editing of termEntries, terms and attributes / Accepting and rejecting proposals Selected for Development

      Filter

      TRANSLATE-2486 - Filtering for attributes Selected for Development

      Edit an attribute for multiple occurences at once

      TRANSLATE-2487 - Edit an attribute for multiple occurrences at once Selected for Development

      Change GUI label of attribute

      TRANSLATE-2489 - Change of attribute label in GUI Selected for Development

      General structure of terminology

      Regarding the general structure of terminology and TBX please keep in mind (probably also relevant for data structure in DB):

      • A transaction group containing creator/modifier and date information can occur on termentry, language and term-level and in a description-group (e. g. referring to a definition)
      • Same is true for a source information containing information about the source of the information it refers to
      • Images must only be on termEntry or language level (there might be language specific images)
      • A crossreference must only occur on termEntry or term-level

      Mapping images to term status

      status icon
      admittedTerm dot icon
      preferredTerm green check icon
      deprecatedTerm block icon
      supersededTerm block icon

       

       

      Attachments

        Issue Links

          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. TRANSLATE-1410 Refactor TBX Import due several structural problems

          • Selected for dev
          is duplicated by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. TRANSLATE-189 terminology management

          • Done
          relates to

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-1436 Add or propose terminology directly from translate5 task

          • Done

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-1272 Import translate5 task into termCollection

          • Backlog

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-1406 TermPortal: Match-resource like server-side interface

          • Backlog

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-1614 Trados Studio Plugin to connect Term-Resources from translate5

          • Backlog
          mentioned in

          Page Loading...

          Activity

            People

              pavelperminov Pavel Perminov
              marcmittag Marc Mittag [Administrator]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: