Difference between revisions of "Column Names"
m (→Unique Path) |
m |
||
| Line 1: | Line 1: | ||
Fact Oriented Modeling requires all fact types to be uniquely named. When a FOM Model is transformed towards a logical model, or implementation, the column names may become too long and elaborate. Therefor CaseTalk and the Viewer allow column names to be formatted using naming conventions. | Fact Oriented Modeling requires all fact types to be uniquely named. When a FOM Model is transformed towards a logical model, or implementation, the column names may become too long and elaborate. Therefor CaseTalk and the Viewer allow column names to be formatted using naming conventions. | ||
A generated | A generated ''Project'' table may contain columns for project, manager and client. | ||
= Full Path = | = Full Path = | ||
The full path will name the full paths from the very first role to the final label type. | The full path will name the full paths from the very first role to the final label type. | ||
* | * Project description_Description | ||
* | * Project number_Number | ||
* | * Manager_Number | ||
* Client_Firstname_Name | |||
* Client_Surname_Name | |||
= Relevant Path = | = Relevant Path = | ||
The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail. | The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail. | ||
* | * Project description | ||
* | * Project number | ||
* | * Manager_Number | ||
* Client_Firstname | |||
* Client_Surname | |||
= Compressed Path = | = Compressed Path = | ||
This compressed path setting starts with the full paths, and then removes repetitive redundant names from it. | This compressed path setting starts with the full paths, and then removes repetitive redundant names from it. | ||
* | * Project description | ||
* | * Project number | ||
* | * Manager_Number | ||
* Client_Firstname | |||
* Client_Surname | |||
= Unique Tail = | = Unique Tail = | ||
The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique. | The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique. | ||
* | * Description | ||
* | * Project number | ||
* | * Manager_Number | ||
* Firstname | |||
* Surname | |||
= Unique Path = | = Unique Path = | ||
This will probably result in the most informative and shortest column names possible. Combining the start and only add secondary information if needed. | This will probably result in the most informative and shortest column names possible. Combining the start and only add secondary information if needed. | ||
* | * Description | ||
* | * Number | ||
* | * Manager | ||
* Client_Firstname | |||
* Client_Surname | |||
= ObjectType (legacy) = | |||
* Project description | |||
* Project number | |||
* Manager | |||
* Client1 | |||
* Client2 | |||
= LabelType (legacy) = | |||
* Description | |||
* Number1 | |||
* Number2 | |||
* Name3 | |||
* Name4 | |||
Revision as of 07:03, 8 June 2023
Fact Oriented Modeling requires all fact types to be uniquely named. When a FOM Model is transformed towards a logical model, or implementation, the column names may become too long and elaborate. Therefor CaseTalk and the Viewer allow column names to be formatted using naming conventions.
A generated Project table may contain columns for project, manager and client.
Full Path
The full path will name the full paths from the very first role to the final label type.
- Project description_Description
- Project number_Number
- Manager_Number
- Client_Firstname_Name
- Client_Surname_Name
Relevant Path
The relevant path setting will skip intermediate fact types names. Naming the first and complimenting that with a unique tail.
- Project description
- Project number
- Manager_Number
- Client_Firstname
- Client_Surname
Compressed Path
This compressed path setting starts with the full paths, and then removes repetitive redundant names from it.
- Project description
- Project number
- Manager_Number
- Client_Firstname
- Client_Surname
Unique Tail
The unique tail setting starts from the label type and work it's way to the table name. Inserting parts until all column names are unique.
- Description
- Project number
- Manager_Number
- Firstname
- Surname
Unique Path
This will probably result in the most informative and shortest column names possible. Combining the start and only add secondary information if needed.
- Description
- Number
- Manager
- Client_Firstname
- Client_Surname
ObjectType (legacy)
- Project description
- Project number
- Manager
- Client1
- Client2
LabelType (legacy)
- Description
- Number1
- Number2
- Name3
- Name4