This is the fourth piece in our series on terminology lifecycle management, you can catch up here, here and here.
Earlier we elaborated a bit on various aspects of terminology governance and conceptualization as a method of constructing a self-maintained ecosystem. And now that we have all angles covered, there’s no reason to labour the point, let’s say thank you and good night.
Fortunately for all of us with an inkling to solve problems, once the terminology processes are kicked off and localization is in full swing, issues of different nature are bound to crop up.
The topic du jour is still terminology lifecycle management, specifically governance and maintenance – if you missed the first part, you can catch up here.
Last week we have cut the development and architecture bits short, because they are intertwined with the concept of governance. If you wish to see all the work put into creating, authoring and structuring last another day, factor in roles, responsibilities, communication structure, collaboration model, permissions and transparency.
We hope you are already famished for another LABS post after last week’s hiatus. With all the terminology talk in the industry on best practices, database creation and concepts, there’s no immediate urge for us to add to the sea of discussions. Not that we already have a silver bullet for all the issues, but there are two topics where the eloquence seems to be subsiding. Interoperability and lifecycle management are not hitting the charts, but they are key issues for integrated, flexible solutions, so we try to say a few words edgeways this week about our experiences.
We had our share of excursions into E-Learning in the past few weeks, today it is time to recap and look into the attitude differences in the international business sector. We have very briefly touched on the happy variety of localization practices, so in our current post, we take a peek at the needs of organizations in a bit more detail.
Broadly speaking, E-Learning targets range from materials for internal use to assets devised for public audiences. It is not by any means a universal rule, but there is a pattern that the required level of adaptation corresponds to the objectives, and the degree of localization gets toned down as the focus shifts from external to organization-wide application.