I don’t know if this was discussed earlier in the list. I tried searching
its archives, but could not find any.
Let me describe you the problem :
Our organization is in the process of implmenting a reporting system in six
different regions. We have designed the BO universes centrally and we’ll
be sending them out for deployment to these regions. Now, these regions
want to name the objects a little bit differently than what the central
team has called it.
For E.g., A dimension called Doctor might be referred to as Caregiver,
Practitioner or Healthcare provider in different regions, based on the
comfort in using these names.
We would not like to maintain 6 different versions of the base universe for
these different regions with each region having a different name for this
dimension. This would be a maintenance nightmare.
I thought of deriving a region specific universe in which I could change
the name of just this object. But, a derived universe does not allow one
to change the name of any objects from the base universe.
Does anybody know of a solution to this problem without having to maintain
a lot of different versions of the base universe ?
I thought of deriving a region specific universe in which I could change
the name of just this object. But, a derived universe does not allow one
to change the name of any objects from the base universe.
There is a tool - I have never used it, but I did notice it on their web site the other
day - called SolvGlobalize at http://www.solvcentral.com/addons/solvglobalize.htm that
you might want to take a look at. If nothing else, it will give you some ideas. The tool
currently doesn’t support sub-classes, so it might be of limited use. But the idea is
that they extract the text (like class and object names) and provide you the ability
to “translate” the text into another language.
Maybe you could use the tool to do what you’re looking for.
Could you create multiple entries for these objects (e.g., doctor, provider,
caregiver . . .) in the same universe and then use Supervisor to suppress
the synonyms?
I’ve worked with a similar situation before… We had a kernel universe with
whatever names we wanted and then derived universe for each region. The objects
that needed region-specific names pointed to the BO objects in the kernel. We
hid those kernel objects. The objects that could use the same name just stayed
visible.
There’s more than one way to skin a cat, but this worked nicely for us.
There is a tool - I have never used it, but I did notice it on their web
site the other
day - called SolvGlobalize at http://www.solvcentral.com/addons/solvglobalize.htm that
you might want to take a look at. If nothing else, it will give you some
ideas. The tool
currently doesn’t support sub-classes, so it might be of limited use. But
the idea is
that they extract the text (like class and object names) and provide you
the ability
to “translate” the text into another language.
Me:
We use such a tool like “solvglobalize” (partly written by a BO-consultant)
to translate Dutch universes into French versions. We can handle subclasses
and ‘translate’ even more: descriptions, the SQL of the objects and the
selfjoins on all the lookup tables. It’s not that difficult. The initial
translation of a universe can be done a couple of minutes but maintenance
can take a lot of time. I’m afraid this is the only way to ‘translate’ a
universe to different regions.