• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 190 subscribers
  • Views 2409 views
  • Users 0 members are here
Options
Related

Input-model that will NOT allow changing the sequence in which descriptive fields are entered

Lucy Matticoli-Mason

We have improved the ‘Definition’ of our current TB by adding new descriptive fields that reflect the growth that has occurred in our product line. This improvement provides ‘options’ for translators to set ‘preferred’ versus ‘forbidden’ terms based on the product family to which each term belongs. So, for example, a translation can be ‘preferred’ in PrdFmlyA but that same translation can be ‘forbidden’ in PrdFmlyB, or PrdFmlyC, etc. Creating an Input Model seemed to be the answer to provide a neat and consistent ‘template’ to enter terms with their corresponding descriptive fields always in the same sequence – none of them ‘Mandatory’ –: • ProductFmly (picklist of PrdFmlies) • Term Status(picklist of preferred/forbidden) • Term Definition • Part of Speech • Context (example of use) • Notes • Related Terms (to set X-References).    

What is happening is that this input model appears in this desired order when TargetTerm1 is entered, but if synonyms are entered (TargetTerm2, TargetTerm3) under the same entry number, then the input model template doesn’t appear anymore; instead the translator can choose from a dropdown list in no specific order. 

Please suggest how to provide to a team of several translators an organized input-model that will NOT allow changing the order in which descriptive fields display. Maybe the solution is not via 'input model' but via a customized 'layout'? 

Also, please share any info on available videos or any other material that can offer more in depth training on how to efficiently combine the use of Input Model and Layouts in the most efficient manner? Thank you in advance, Lucy MM
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi Lucy,

    I think it would be helpful to have a small sample termbase (just with enough terms to demonstrate the point), and perhaps a small sample text to best illustrate this.  I just spent a little time trying to replicate what you are saying with a sample termbase, creating input models and different layouts, but it's quite complicated to know exactly what you mean.

    So the more you can provide as s starting point the better.  It doesn't have to be real data of course... just make it up.   But most importantly keep it small so it's easy to play with.

    On available videos or other material... I'm not sure there is any.  In fact if we get some links here from others I'd be very pleased to see it.

    I attached my effort to replicate the problem before I really needed to move onto something else... so even use this if it's easier (assuming I this part right!!)

    Lucy Matticoli-Mason.zip

    Just a termbase and sample text... all inocuous.  I think as I re-read your post I can see how my demo is not exactly what you did as I have not based this on product family as you said, but please take a look and see if you can make it a bit easier to help,

    Regards

    Paul

    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 in reply to Paul

    Hello Paul: Thank you for the quick response and for the example you sent. Your example actually shows the issue we are having. Let's use your TB and go ahead an enter another term; notice how the target-term1 will show all the descriptive fields, but as you try to enter a synonym (target-term2) that structure of descriptive fields is not there any longer; meaning that you can enter descriptive fields in a diff sequence creating a diff look between these two terms. This sounds like someone being too 'picky' but when dealing w/a huge amount of information a consistent sequence for all entries makes it easier for the reader to find relevant info. Is there a way to have a fixed structure (input model) that doesn't allow changing the sequence of the descriptive fields on each synonym entered under the same entry-number? Let me know what you think.
  • 0 in reply to Lucy Matticoli-Mason

    We resolved this issue by clicking on the "Full Form" button, which can be found below the 'Input Model' drop down list. When 'Full Form' is activated, the descriptive fields in the input model will continue to display always in the same sequence for all entered synonyms.

    More info: Full and Short Form in Input models