| Name | Attribute_Relation |
|---|---|
| Entity Type | Table |
| Description | This intersection table is required to help support attribute-level relations in Seabed. An entity (currently only Uncertainty_System, but may be generalized in the future) makes a reference to a segment (Dimn_1_Min...Dimn_4_Max; more below) of an attribute (the associated attribute) in the entity (Entity_Containing_Attribute). The segment can be given a name when it exists. Segment means a contiguous subarray of an array-valued attribute. For example, the attribute could be a two dimensional array with 0<=dimn 1<=20, 0<=dimn 2<=317. A legal segment could be the entire array, or could be any subrange expressed on either or both dimensions. Examples are 12<=dimn 1<=15, or 12<=dimn 1<=15 and 57<=dimn 2<=84. |
| Submodel | Uncertainty |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Associated_Attribute | STRING32 | NA |
The attribute to which the association is being made. This is typically a pure attribute name (column name in a table) but could also be an association name, e.g. for attributes implemented by association to a bulk_array object. | Yes |
VARCHAR2(32) |
| Dimn_1_Max | int | No_Unit |
Used when the association is used for indexed data. The maximum index value along dimension 1 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. Dimension 1 also applies to multi-values attribute values, e.g. those represented in extension tables. | No |
NUMBER(10) |
| Dimn_1_Min | int | No_Unit |
Used when the association is used for indexed data. The minimum index value along dimension 1 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. Dimension 1 also applies to multi-values attribute values, e.g. those represented in extension tables. | No |
NUMBER(10) |
| Dimn_2_Max | int | No_Unit |
Used when the association is used for indexed data. The maximum index value along dimension 2 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| Dimn_2_Min | int | No_Unit |
Used when the association is used for indexed data. The minimum index value along dimension 2 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| Dimn_3_Max | int | No_Unit |
Used when the association is used for indexed data. The maximum index value along dimension 3 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| Dimn_3_Min | int | No_Unit |
Used when the association is used for indexed data. The minimum index value along dimension 3 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| Dimn_4_Max | int | No_Unit |
Used when the association is used for indexed data. The maximum index value along dimension 4 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| Dimn_4_Min | int | No_Unit |
Used when the association is used for indexed data. The minimum index value along dimension 4 for which this association applies. An n-element array is assumed to be indexed from 0..n-1. | No |
NUMBER(10) |
| 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) |
| Name | ENTITY_NAME | NA |
The name given to any object or data item, e.g. name of Well, name of Field, etc. | No |
VARCHAR2(255) |
| Original_Source | STRING64 | NA |
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" | No |
VARCHAR2(64) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Segment_Name | STRING64 | NA |
The optional name of the segment, mostly for documentation purposes. This is meaningful when the association is to a segment (dense subarray of) dimensional data. For example, the Dimn_1_min=1, Dimn_1_Max=1097 might have meaningful Segment_Names like Overburden, Low_Velocity_Zone or Cenozoic. Segments, when they exist, are defined via dimension limits, so this name is only for annotation. | No |
VARCHAR2(64) |
| Source | STRING64 | NA |
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. | No |
VARCHAR2(64) |
| Uncertainty_System_Id | Uncertainty_System |
|
The Uncertainty_System instance having this attribute-level association. | No |
NUMBER(38) |
| 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) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Entity_Containing_Attribute | Entity | The Entity (subtype) instance containing the attribute associated with this attribute-level association. | Assoc to One | No |
| Uncertainty_System | Uncertainty_System | The Uncertainty_System instance having this attribute-level association. | Cascade | No |