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

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

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.

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