Data Dictionary

[Typia]

Hi guys,
I would like to know if it's possible to a data dictionary, not only for documentation or reporting but which could also be used as a central reference for structure in the project so we can control that modelers don't use a slightly different name for the same field across the whole project for example.

Many thanks

[qwerty]

What is a "field" in your terminology?

q.

[Geert Bellekens]

There are two ways to approach this.

You can use the build-in Glossary, which is basically flat list of terms and definitions.
Advantage of the Glossary is that, if you use a known term from the glossary in a notes field, it gets underlined, and you can see the definition in the tooltip.

The other approach is to model a logical data model (or domain model). This can be much more then a flat list. I can become the very center of your complete model. It can be used to drive the database, drive the message definitions (XML or JSON Schema's), the reports, the backend code etc...

I personally prefer the logical data model approach.

Geert

[Typia]

Hi, thanks a lot for your answers

What is a "field" in your terminology?

q.

By field I mean database field.

I want a central repository where common database fields like client_name or so would be defined to avoid having the same notion referred by 2 differents fields (typo error in the name, or different string length ..) across the project

[qwerty]

I guess the only way to go here is to write a script in helping to check consistency. An add-in would be even better as it can intervene on creation/editing of new class attributes (or what you call fields). It takes a bit more effort for setup, but then again it will save lots of time in the future (what one calls ROI).

q.