Modeler: 14/GlrOptions

From CaseTalk Wiki
< Modeler:14
Revision as of 04:27, 13 December 2024 by Admin (talk | contribs) (Created page with "Model transformations may be required for certain artifact generations. The dialog to set how to transform the model is displayed here. File:GlrOptions12.png = Before = * '''Derive data types'''. Once enabled the label datatypes are derived from the population, if not yet set. * '''Clear population'''. Erases all example population. * '''Clear entity schema'''. Erase schema names from otft's before transformation starts. If name clashes occur, the schema is prefix...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Model transformations may be required for certain artifact generations. The dialog to set how to transform the model is displayed here.

GlrOptions12.png

Before

  • Derive data types. Once enabled the label datatypes are derived from the population, if not yet set.
  • Clear population. Erases all example population.
  • Clear entity schema. Erase schema names from otft's before transformation starts. If name clashes occur, the schema is prefixed to the name.
  • Transitional
  • Temporal
  • Art. Key
  • Localize

Well-formedness

  • Allow validation warnings
  • Show only errors and warnings

Project Files

  • Overwrite known IGG Files
  • Warn before saving IG file
  • Copy Active Diagrams

Transformations

  • Group. Grouping roles together. Selecting proposal merely checks the options and performs no real grouping. Performing a step-by-step enables you to manually go through the grouping process. Derived subtypes enables grouping for subtypes which are marked as "derivable".
  • Lexicalize. This step of lexicalizing makes sure every role is played by a label type. This is a requirement for database script generation.
  • Reduce. If the population is already present under different fact types, we may reduce the fact types which contain duplicate or obsolete storage for them.

Namings

  • Naming Conventions
  • Column Names. Database column names can be chosen by different naming algorithms. They vary from the full conceptual path down to numbered label types. Depending on your preferences you may choose any of them. They all create unique names, see also: Column Names.
  • Column Fix Type Names

Options

  • Automatic primary key
  • Assume wide UC
  • Assume wide TC

After

  • DBMS types

Diagrams

  • Show subsets
  • Hide labeltypes
  • Show primary UC