Having only just seen this - I thought I would explain how I went about it for multiple customers in a specific field in the dim and distant past. Originally I had separate termbases for each customer, but like you I found having multiple termbases made it very difficult to keep them all up-to-date. In the end, I merged all the customer databases into a single one and used a customer field to separate divergent preferred usage between the customers.

I use this approach with attribute picklists to separate terminology by supervisory divisions - and have a few extra fields e.g. to help with issues about inclusive language and also accessibility. I did find that I did have a lot of superfluous fields after a while, and recently rationalised some of them (e.g. an abbreviation type field - intended for a mothballed QA idea I had) as the time needed to be invested was not worth it in the end.

As Paul mentions, the level of overlap is probably going to be key in your decision (e.g. in your example, having Subpodryadchik three times indicates that there might be some terms that are overlapping!)

Having only just seen this - I thought I would explain how I went about it for multiple customers in a specific field in the dim and distant past. Originally I had separate termbases for each customer, but like you I found having multiple termbases made it very difficult to keep them all up-to-date. In the end, I merged all the customer databases into a single one and used a customer field to separate divergent preferred usage between the customers.

I use this approach with attribute picklists to separate terminology by supervisory divisions - and have a few extra fields e.g. to help with issues about inclusive language and also accessibility. I did find that I did have a lot of superfluous fields after a while, and recently rationalised some of them (e.g. an abbreviation type field - intended for a mothballed QA idea I had) as the time needed to be invested was not worth it in the end.

As Paul mentions, the level of overlap is probably going to be key in your decision (e.g. in your example, having Subpodryadchik three times indicates that there might be some terms that are overlapping!)