I can understand the desire to reshape the world that is, but I prefer a tool 
that uses the world as already defined.
That way you can be assured that changes do not upset it, since it's already 
coded to allow whatever woolley thing it encounters to be properly understood.

Paying people to clean up your dictionaries just so you can map them, seems 
backward to me.  Better to write a tool that can use the dictionaries as they 
are, and figure out how to map the data from that.

I would suggest that any link that is not already defined clearly in the 
dictionary is probably unimportant at any rate.
And by the way, just to throw a wrench, data mapping is really not the fix to 
anything, without a clear mapping of the processes that create that data, 
rework it, and destroy it.  Mapping the dictionaries doesn't tell you one thing 
about those.

 

 

-----Original Message-----
From: Bill Brutzman <bi...@hkmetalcraft.com>
To: 'U2 Users List' <u2-users@listserver.u2ug.org>
Sent: Tue, Jul 16, 2013 11:05 am
Subject: Re: [U2] UML mapping tool for MV (UniVerse)


I have some heartburn with the words "optional" and "purely" below.  To me,
it is like saying that Daniel Webster was just a door-to-door encyclopedia
salesman.

U2 data dictionaries are key tool.

Why would someone climb on to a Rocket... to explore the UniVerse... without
a map... of the data?

--Bill

-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Hona, David
Sent: Monday, July 15, 2013 8:40 PM
To: U2 Users List
Subject: Re: [U2] UML mapping tool for MV (UniVerse)

Regardless of the toolset, the first hurdle would be to normalise your
database to look like a relational one. Which is likely to be the greatest
hurdle. Data dictionaries in U2/PICK are optional are a purely for reporting
purposes - they can have duplicates and these can be conflicting. Even worse
(as if you thought it could be) - data dictionaries can be incomplete or
wrong. This added to the lack of enforcement of data integrity and
constraints usually causes these toolsets to fail (indeed, even the UV/ODBC
driver fails too!)... so good luck!

Rocket released U2 Metadata Manager to assist in this respect and is
designed to allow forward and backwards capability. Although, support for
this in UV is limited to the latest official release... so your alternative
is UV/ODBC...

For UV/ODBC users

 
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to