| Name | Ref_Code_Alias |
|---|---|
| Entity Type | Table |
| Description | Alternate names or codes assigned to a reference code, usually defined by a company for local use or by an external organization for worldwide use. The name may or may not be globally unique but is unique for a code within the context of the namespace (i.e., the Alias Type). |
| Submodel | Reference |
| Entity Scope | Shared |
| Primary Key | Id |
| Natural Key | Alias_Type , Ref_Table_Name , Code , Existence_Kind , Version |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Alias_Name | STRING255 | NA |
An alternate name or identifier for the code. | No |
VARCHAR2(255) |
| Alias_Type | CODE | NA |
Defines the valid type of alias provided by a given source of aliases. | No |
VARCHAR2(64) |
| Code | CODE | NA |
The code for which an alias is provided. | No |
VARCHAR2(64) |
| Description | STRING2000 | NA |
A textual definition of the alias, which may include the purpose and use. | No |
VARCHAR2(2000) |
| End_Date | DATE | NA |
End time of the association | No |
DATE |
| Existence_Kind | REF_EXISTENCE_KIND | NA |
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. | Yes Actual |
VARCHAR2(64) |
| GUID | STRING128 | NA |
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. | No |
VARCHAR2(128) |
| Id | ID | No_Unit |
Unique identifier for this entity. | Yes |
NUMBER(38) |
| Insert_Date | DATE | NA |
Date the entity was created in the repository | No |
DATE |
| Insert_User | STRING64 | NA |
The name of the user responsible for the creation of this entity in the repository. | No |
VARCHAR2(64) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Ref_Table_Name | TABLE_NAME | NA |
The name of the reference table in which the code resides that is aliased. | No |
VARCHAR2(30) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Source | CODE | NA |
The person, company or application that defined or specified the data (content) for this instance and is considered to be responsible for it. For example, POSC, EPSG, API, ISO, etc. | No |
VARCHAR2(64) |
| Start_Date | DATE | NA |
Start time of the association. | No |
DATE |
| Update_Date | DATE | NA |
Date of the most-recent modification to the entity. | No |
DATE |
| Update_User | STRING64 | NA |
The name of the user responsible for the last modification to this entity. | No |
VARCHAR2(64) |
| Version | STRING255 | NA |
The form or variant of the entity. | Yes 1 |
VARCHAR2(255) |