| Name | Seismic_Record |
|---|---|
| Entity Type | Table |
| Description | A data record to store header or trace of seismic data of geophysical inventory item. |
| Submodel | Seismic |
| 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 |
|---|---|---|---|---|---|
| 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) |
| Geophysical_Inventory_Id | Geophysical_Inventory |
|
Geophysical inventory (seismic data file) associated with the seismic record data. | Yes |
NUMBER(38) |
| 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) |
| Length | int | No_Unit |
Number of bytes in the record. | No |
NUMBER(10) |
| 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) |
| Offset | int | No_Unit |
Byte offset from the beginning of the file. | No |
NUMBER(10) |
| 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) |
| Record_Data | BLOB | NA |
Holds the data of seismic record | No |
BLOB |
| Relative_Size_Indicator | CODE | NA |
An indicator of the relative size of the BLOB (Binary Large OBject) in the Record_Data attribute. The possible values are "Small", "Medium", and "Large". When the partitioning option is selected for a Seabed database, different storage areas (i.e., tablespaces in Oracle) are created to handle different sized objects more efficiently. The relative size indicator helps determine which storage area to use within the partitioning scheme. Note that the Length attribute cannot be used to support partitioning as the current implementation in Seabed supports only List partitioning, not Range partitioning. | 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) |
| Sequence_Number | int | No_Unit |
Sequence number of the record in relation to other records of the geophysical inventory. | No 1 |
NUMBER(10) |
| 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) |
| Type | STRING255 | NA |
Record type. Ex: EBCDIC_HEADER, BINARY_HEADER, TRACE_HEADER | No |
VARCHAR2(255) |
| 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 |
|---|---|---|---|---|
| Geophysical_Inventory | Geophysical_Inventory | Geophysical inventory (seismic data file) associated with the seismic record data. | Cascade | Yes |