| Name | Rock_Sample_Depth_Adjust |
|---|---|
| Entity Type | Table |
| Description | Rock sample depth adjustment is the activity of making an adjustment to the depth values specified for a rock sample in the ROCK_SAMPLE.TOP_DEPTH and ROCK_SAMPLE.BASE_DEPTH columns. Examples of the type of depth adjustments that can be made are: 1) adjustments to convert from one depth type to another (ex: loggers depth to drillers depth) 2) adjustments to convert from one depth reference to another (ex: from Kelly bushing to sea level) 3) adjustments to handle core shifts. |
| Submodel | Rock_Sample |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Rock_Sample_Id , Top_Depth , Base_Depth , Adjusted_Top_Depth , Adjusted_Base_Depth , Existence_Kind , Version |
| Generalizations | IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Adjusted_Base_Depth | double | Depth m |
Adjusted depth of the base of the core interval. | Yes |
NUMBER |
| Adjusted_Depth_Reference | CODE | NA |
The working reference datum associated with the adjusted depth measurements specified in ADJUSTED_BASE_DEPTH and ADJUSTED_TOP_DEPTH. Examples include Kelly Bushing, and Derrick Floor. | Yes |
VARCHAR2(64) |
| Adjusted_Depth_Type | CODE | NA |
A value that specifies whether the depth measurements are in terms of loggers depth or drillers depth. Valid values: LOGGERS, DRILLERS, TVD (for True Vertical Depth). | No |
VARCHAR2(64) |
| Adjusted_Top_Depth | double | Depth m |
Adjusted depth of the top of the core interval. | Yes |
NUMBER |
| Author | OWNER_NAME | NA |
The responsible party for the rock sample depth adjustment. (i.e., the person who made the interpretation for this transformation.) | No |
VARCHAR2(255) |
| Base_Depth | double | Depth m |
Acquisition measured depth of the base of the core interval being adjusted. | Yes |
NUMBER |
| Depth_Adjustment_Date | DATE | NA |
The date on which the depth adjustment was made. | No |
DATE |
| Depth_Adjustment_Reason | R_Depth_Adjustment_Reason |
|
A value that identifies the purpose for the change in acquisition depth measurement system. | No |
VARCHAR2(64) |
| Depth_Adjustment_Remarks | REMARKS_STR | NA |
Free form text comments regarding the depth adjustment interpretation. | No |
VARCHAR2(999) |
| Depth_Correction | double | Depth m |
The depth correction used to adjust to the new datum. | Yes |
NUMBER |
| Depth_Shift_Datum | R_Vertical_Reference |
|
Identify the type of vertical reference used in the correction of the datum | No |
VARCHAR2(64) |
| 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) |
| Rock_Sample_Id | Rock_Sample |
|
The identifier of the rock sample whose depth measurements are being adjusted. | Yes |
NUMBER(38) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Top_Depth | double | Depth m |
Acquisition measured depth of the top of the core interval being adjusted. | Yes |
NUMBER |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Plug_DOV | Depth_Adjustment | READ ONLY: Unique identifier for the rock sample depth adjustment. | Cascade | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Rock_Sample | Rock_Sample | The identifier of the rock sample whose depth measurements are being adjusted. | Cascade | Yes |
| Depth_Shift_Datum | R_Vertical_Reference | Identify the type of vertical reference used in the correction of the datum | Restrict | No |
| Depth_Adjustment_Reason | R_Depth_Adjustment_Reason | A value that identifies the purpose for the change in acquisition depth measurement system. | Restrict | No |