management of lookup code values in EA

[Peter_321]

I would like to find out if EA could be used as master repository to manage lookup code (reference data) lists.

We're using different types of lookup codes (eg. Country_Code_ISO3, for which there exists an enummerated list of possible values BEL,FRA,GER,...).

How could this information be implemented/stored through EA to support the governance of this reference data by a data steward ?

Anyone experience with this ?

Thanks in advance for your response.

[dana n]

I'm also interested to know if this is possible.

I am designing dozens of domain/lookup tables in EA, and it would be nice to store values along with the tables.

I'm thinking this may be beyond EA's capabilities.

[«Midnight»]

AFAIK EA does not support data domains.

This is not quite what you are talking about, though somewhat related. I just wanted to make you aware that you won't be able to accomplish that either.

The bad (worse) news is that there is no explicit support for values in tables. The closest you might come is creating a stored procedure to populate these tables. But you still won't be able to use the values in your model.

Perhaps in future, but there are several popular features - in the sense that they are often requested - that might be on the list first.

Sigh...

David

[dana n]

Thanks David.

A colleague of mine suggested using "domain constants" in EA as one possible solution.

I don't know if what I'm asking for is unreasonable in a product like EA. Is EA not as feature-rich for database design as other tools like ERWin, etc? Certainly it doesn't seem as database-design centric as other products. Of course it could be (and likely is) lack of knowledge on my part.

I'm relatively new to modeling with UML, so that's a stumbling block for me. Know any good books on database design that are UML-centric?

Dana

[«Midnight»]

Hi Dana,

See my reply to your other thread here: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1213360383/3#3

David

[B3ip]

Probably too late ... how about an enumerating class?