| Name | Document |
|---|---|
| Entity Type | Table |
| Description | A document can be any document that is required to be stored in an electronic format. Examples of this could be daily drilling reports, drilling schematics, or material quality analysis reports. |
| Submodel | Utility |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Name , Document_Type , Document_Format , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Contributor | STRING64 | NA |
An entity responsible for making contributions to the content of the resource. Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity. (DCMI) | No |
VARCHAR2(64) |
| Coverage | STRING255 | NA |
The extent or scope of the content of the resource. Coverage will typically include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and that, where appropriate, named places or time periods be used in preference to numeric identifiers such as sets of coordinates or date ranges. (DCMI) | No |
VARCHAR2(255) |
| Creator | STRING64 | NA |
An entity primarily responsible for making the content of the resource. Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. (DCMI) | No |
VARCHAR2(64) |
| Document_Body | BLOB | NA |
This attribute contains the body of the document in BLOB format for those documents which are smaller than the maximum BLOB size allowed by your operating system/database combination. For others it will contain the first of multiple segments of the blob with the others stored in Document_Body_Part. | No |
BLOB |
| Document_Date | DATE | NA |
A date associated with an event in the life cycle of the resource. Typically, Date will be associated with the creation or availability of the resource. (DCMI) | No |
DATE |
| Document_Folder_Id | Document_Folder |
|
The ID of the folder to which this document belongs | No |
NUMBER(38) |
| Document_Format | R_Document_Format |
|
The data format that the document is in, for example, JPEG, GIF, text, comma delimited, etc. | Yes |
VARCHAR2(64) |
| Document_Identifier | STRING128 | NA |
An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN). (DCMI) | No |
VARCHAR2(128) |
| Document_Type | R_Document |
|
A code or mnemonic that identifies the type of document such as Production Spreadsheet, Site Photo, etc. | Yes |
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) |
| File_Size | NUMBER | No_Unit |
The size in Bytes of the file | No |
NUMBER |
| 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) |
| Media_Type | CODE | NA |
The type of media upon which the document was stored. For example Tape, CDROM etc. | 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_Path | FILE_NAME_STR | NA |
Fully qualified path name of the original directory from which the document was extracted. | No |
VARCHAR2(999) |
| 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) |
| Path | FILE_NAME_STR | NA |
Fully qualified path name of the directory in which the document resides. For Web based documents this could be the URL to the holding directory. | No |
VARCHAR2(999) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Publisher | STRING64 | NA |
An entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. (DCMI) | No |
VARCHAR2(64) |
| Relative_Size_Indicator | CODE | NA |
An indicator of the relative size of the BLOB (Binary Large OBject) in the Document_Body 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. | No |
VARCHAR2(64) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| Rights | STRING128 | NA |
Information about rights held in and over the resource. Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource. (DCMI) | No |
VARCHAR2(128) |
| 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) |
| Source_Language | STRING64 | NA |
A language of the intellectual content of the resource. Recommended best practice is to use RFC 3066 [RFC3066], which, in conjunction with ISO 639 [ISO639], defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian, and "en-GB" for English used in the United Kingdom. (DCMI) | No |
VARCHAR2(64) |
| Subject | STRING128 | NA |
The topic of the content of the resource. Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme. (DCMI) | No |
VARCHAR2(128) |
| Title | STRING255 | NA |
A name given to the resource. Typically, a Title will be a name by which the resource is formally known. | 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) |
| Viewer | R_Document_Viewer |
|
The viewer to be used for this particular document | No |
VARCHAR2(64) |
| Cardinality | Entity |
|---|---|
| One | Log_Image |
| One | NDC_Document |
| One | Report_Image |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Document_Body_Part | Document | The document to which this part belongs. | Cascade | Yes |
| Document_Parameter | Document | The Document that generated this document parameter value. | Cascade | Yes |
| Entity_Doc_Involvement | Document | The document that is to be associated with an Entity | Cascade | Yes |
| Log_Image_Part | Log_Image | The image of which the section is a part. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Document_Type | R_Document | A code or mnemonic that identifies the type of document such as Production Spreadsheet, Site Photo, etc. | Restrict | Yes |
| Viewer | R_Document_Viewer | The viewer to be used for this particular document | Restrict | No |
| Document_Folder | Document_Folder | The ID of the folder to which this document belongs | Cascade | No |
| Document_Format | R_Document_Format | The data format that the document is in, for example, JPEG, GIF, text, comma delimited, etc. | Restrict | Yes |