| Name | External_Object_Index |
|---|---|
| Entity Type | Table |
| Description | Contains a table of contents of all class instances eligible for data management features such as QC, Select_List, etc. |
| Submodel | Quality_And_Context |
| 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 |
|---|---|---|---|---|---|
| App_User_Id | App_User |
|
A person who is a user of an automated application system. Note that a user corresponds to a database account. Password validation and connections to the database are maintained and managed by the DBMS (database management system). | No |
NUMBER(38) |
| 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) |
| External_Object_Type | R_External_Object |
|
Type for the instance of external object index, e.g. "well_hdr". | Yes |
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) |
| IT_Object_Id | IT_Object |
|
The object in the database that the external object refers to. | No |
NUMBER(38) |
| IT_Object_Tbl | Meta_Entity |
|
IT_Object type | No |
VARCHAR2(30) |
| 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) |
| Instance_NK | STRING2000 | NA |
Natural key of external object instance, concatenated if necessary | No |
VARCHAR2(2000) |
| Instance_PK | STRING2000 | NA |
The primary object identifier of external object instance. | No |
VARCHAR2(2000) |
| Instance_SK | STRING2000 | NA |
Unique object identifier (or surrogate key) of external object instance | No |
VARCHAR2(2000) |
| 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) |
| 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) |
| Storage_System_Code | R_External_Object |
|
Type for the instance of external object index, e.g. "well_hdr". | Yes |
VARCHAR2(64) |
| Storage_System_Id | Storage_System |
|
This instance of external object index refers to an object physically stored in a named storage system (database SID, schema name) | No |
NUMBER(38) |
| Type_Hint | Meta_Entity |
|
The entity type code that the external object would have if it were persisted in Seabed . Note, that this code is a hint; not in all cases will we find a matching Seabed type. | No |
VARCHAR2(30) |
| 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 |
|---|---|---|---|---|
| QC_Attribute_Value | Object_Instance_Context | The value set in QC_Attribute_Value is defined for an instance of External_Object_Index | Cascade | No |
| Select_List_Item | External_Object_Reference | The item refers to a particular instance of external object index | Cascade | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Storage_System | Storage_System | This instance of external object index refers to an object physically stored in a named storage system (database SID, schema name) | Cascade | No |
| Type_Hint | Meta_Entity | The entity type code that the external object would have if it were persisted in Seabed . Note, that this code is a hint; not in all cases will we find a matching Seabed type. | Nullify | No |
| IT_Object | IT_Object | The object in the database that the external object refers to. | Cascade | No |
| External_Object_Type | R_External_Object | Type for the instance of external object index, e.g. "well_hdr". | Restrict | Yes |
| App_User | App_User | A person who is a user of an automated application system. Note that a user corresponds to a database account. Password validation and connections to the database are maintained and managed by the DBMS (database management system). | Cascade | No |