Display and DB-storage of proposals (new and changed terms and attributes)

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • None
    • Affects Version/s: None
    • Component/s: TermPortal

      Handling of terms

      In the TBX specification a term attribute for the workflow status of the term exists: processStatus. It has the allowed values

      • unprocessed
      • provisionallyProcessed
      • finalized

      New proposals of terms will get the processStatus "unprocessed".

      If a term is proposed to be changed, on database level a new proposal will be added to a separate proposals table, and with the processStatus "unprocessed".

      Handling of attributes

      For attributes no processStatus flag exists in the TBX-specification. Yet in translate5 on database level proposed attributes will also get the flag "unprocessed", while all finalized attributes or those coming from an import will get the flag "finalized".

      If an attribute is proposed to be changed, on database level the new/changed attribute value will be added to the attribute-proposal table with the processStatus "unprocessed".

      Display of proposals in the GUI

      In the GUI proposals of terms and attributes are highlighted with yellow color.

      In case of proposed changes of existing terms or attributes (those linked to a non-unprocessed one on DB-level), both are shown in the GUI: the original term/attribute and the proposal. The proposal is highlighted and the existing one is highlighted and striked-through.

      This is true where ever the terms are shown: In the search results of the left column or in the details view in the center-right of the TermPortal. 

            Assignee:
            Aleksandar Mitrev
            Reporter:
            Marc Mittag [Administrator]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: