if a term proposal is added and then deleted again, the last editor and last change date from the term proposal stays at the term. Yet it should also be resetted to the previous value from before the made proposal
when the termCollection name and the customer name are the same and for both a filter is selected, only one tag in the filter field is shown. Yet also in this situation 2 tags should be shown (this is low prio; please fix last; please fix only, when not much effort)
Change proposals to a termEntry attribute do not show up in the Excel, yet they should (for term attributes it works fine).
when creating a new termEntry or new term, last editor and last edited date are only shown, when refreshing the page or doing a new search. They should be shown right away.
the TBX import currently deletes changes to existing terms, if the term in question is present in the import. This should only happen, if the change date of the term in the TBX is newer than the change date of the proposal. This must also be documented in confluence.
The new flag for deletion of proposals in the pop-up window for the termimport is not visible because the window is to small. Also please check, if this new flag is documented in confluence, if no: Document it. Also please document the usage of this flag in the example config file for the termimport plugin
When setting the filter to "proposed", proposed changes to terms are not found, instead these proposed changes are found, when searching for "finalized".
Following scenario
a user wants to add a term from InstantTranslate to TermPortal and clicks on the respecting button in InstantTranslate
translate5 switches to the TermPortal
normally now the term is directly added to a termEntry, if the source term already exists
but if the same source term exists at 2 different termEntries, than these 2 terms are offered in the left column of the termPortal. If this is the case, in the future a notice should appear, that tells the user, "Please select one of the source terms in the left column. They belong to different term entries. After selection you are able to add your new term translation to translate5 termPortal." / "Bitte wählen Sie einen der Quellbegriffe in der linken Spalte aus. Sie gehören zu verschiedenen Begriffseinträgen. Nach der Auswahl können Sie Ihre neue Termübersetzung zum translate5 termPortal hinzufügen."
if a term is created in a language, for which previously no term existed so far, this language has to be added to the language selection field next to the search field of the termPortal immediately.
If a new term is added from InstantTranslate to TermPortal and the source term does NOT exist so far in translate5, the source term is automatically added to the termPortal. Yet for this source term last editor and last edited date and the creator and the creation date are missing.
Please document in confluence, how to add a cron job to automatically export the Excel with the proposals and send it via mail
Please change „Eintragsbenennungen“ in "Terme" bzw. „Eintragsbenennung“ in "Term" and „Term-Eintrag“ in "Eintrag" bzw. „Term-Einträge“ in "Einträge"
Make the filter field not editable. Adding filter tags should only be possible through the drop-downs. Yet of course remove tags by clicking on them should still be possible
Filterfeld: das Frontend ist verwirrend, weil Suchfeld und Filterfeld genau gleich aussehen. =>Ines-Paulshould change this in a way, that they do not look the same any more. Since the filter field is not editable, a different shade of grey for the currently white area of the filter field may do the job.
When entering a suggestion, in German the comment field is overwritten with the EN term "note". Why? As soon as one saves, it says "Anmerkung" above it, as defined in the DB.
Definitions: SInce the <langSet>-level is not represented in the TermPortal, definitions can only be edited on the TermEntry-level. However, on the Term-level the users need to know that they can edit the definition, too. Solution: show edit-button at the term, but only alert a message there (and allow editing as such on the TermEntry-level only).
Bug