• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 191 subscribers
  • Views 2418 views
  • Users 0 members are here
Options
Related

Filter problem: term condition refers back to entry level?

Bruno Ciola

Hi all,

I'm stuck with a filtering problem.

Assuming you have a termbase with entries containing terms with different status information (new, approved, rejected) and would like to filter only entries with terms having the status "new" (but not those with approved or rejected terms).

When you define a filter like: any term with status "new" AND any term with status NOT "approved" etc., Multiterm nevertheless filters out also entries with a "rejected" and an "approved" term, as if the condition AND was not referred to the term level but the entry level.

Anyone experienced this issue?

Regards,

Bruno Ciola
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi ,

    I knocked up a small and simple example and for me the filters work as expected. I used your descriptions and tried to mirror what you have said and it all works as expected. Can you provide bit more information here please?

    - what version of MultiTerm are you referring to?
    - can you show screenshots?
    - even better can you provide a small sample termbase and steps to follow?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0
    I'm just having the same problem :(
    I'm trying to export "all terms which do not have 'deprecated' status"... so I create filter for "All languages" where term field "Status" does not equal "deprecated". Fairly straightforward, I believe... Then I run export to TBX, applying this filter. So I expect to NOT find anything with status 'deprecated' in the export... so for example if an entry has 10 terms (10 languages) and 2 of them are deprecated, I expect to find that entry in the export, but with only 8 terms (8 languages). I suppose I'm not missing anything here...
    But the damned MultiTerm actually leaves out only items where ALL TERMS for the ENTIRE ENTRY have the status deprecated!... so the example entry is still present in the export with all 10 terms! :(

    So what's going to happen?! SDL suggesting me to "submit an idea" (really?! fix the terrible bug, pretty please... what a brilliant "idea"! :-\ ) and NEVER bother about it... because hey, Multiterm is free, so what... :-\

    Sorry guys, but this is really terribly frustrating... elementary functionlity not working even after MANY years of development... :-\
  • 0 in reply to Evzen Polenka
    Hi Evzen,

    I think your situation is slightly different from mine. I was referring to the status information attached to the term and the fact that when using two AND conditions they would not relate to the same language but any language in the entry.
    Regarding your case I think it is known that when exporting you can handle only the entire entry, so even if the condition applies to one of the terms, Multiterm will not be able to split the entry. You need to further edit the export file (e.g. using regex that delete certain terms) or use third party tools like Multiterm Excelling where you can apply further filtering.

    Regards,
    Bruno
  • 0 in reply to Bruno Ciola
    Well, overpriced tools with weird user experience like Excelling MultiTerm are not my cup of tea...
    And I still believe that the core cause of the problem is the same as in your case.
    And I'm not really buying that "known" argument... it is certainly not known to me after ~15 active years in localization... is it CLEARLY documented anywhere? Is it anyhow obvious from the filter configuration GUI?
  • 0
    Hi Bruno,

    I know exactly what you're referring to. This is happening because MultiTerm is a concept-based database. So it cannot run its filters on terms only and runs it on entries instead. If you entry, for example, had only approved terms, the filter would seem like it's working correctly. If, however, a single entry contains both the rejected and approved terms, both will show up. It's a current limitation of MultiTerm, one they are aware of.