Data Sources With Data Source and Project Credentials
Some data sources have credentials at both the data source level and at the project level. The Studio data source is an example. The credentials window for these multi-level credential data sources contains a tab for entering the data source credentials and another tab for entering the project credentials.
The following table lists the credentials defined for each supported OpenSpirit data source type.
Data Source Type | Credential | Credential Scope | Required | Description |
---|---|---|---|---|
EPOS |
Preferred WellDB for write |
Project |
Maybe |
This credential is only used when the Use EPOS projects option is enabled in your EPOS 4 data source configuration and if the EPOS project contains more than one well database. Under these conditions, this credential is required. The credential is not required and is ignored if either of these conditions are not True. The credential should contain the name of the well database that new data should be written to. |
Preferred WellDB for read |
Project |
No |
This credential is only used when the Use EPOS projects option is enabled in your EPOS 4 data source configuration and if the EPOS project contains more than one well database. The credential is ignored if either of these conditions are not true. The credential should contain the name of the well database that data should be read from. Data is read from all well databases in the EPOS project if this credential is not present. |
|
Kingdom |
Author |
Project |
Yes |
The Kingdom author to use when connecting to the Kingdom project. |
Username |
Project |
Maybe |
The Kingdom database username. This credential is required if the Kingdom project is stored in Oracle or SQL server. |
|
Password |
Project |
Maybe |
The Kingdom database password. This credential is required if the Kingdom project is stored in Oracle or SQL server. | |
OpenWorks |
Interpreter |
Project |
No |
This credential is used to optionally establish the OpenWorks interpreter to be used when manipulating data in an OpenWorks project. You are not required to select an interpreter, but are strongly encouraged to do so if you intend to create any OpenWorks interpretation data in the project. Following outlines the behavior when setting the Interpreter credential: It affects which default Well Velocity to use for a Well. It affects the retrieval of the Color attribute for a GeologicFault/Horizontable since multiple interpreters can have different colors for the same fault/horizon name. It is used to populate the interpreter attribute in the OpenWorks project when inserting into the following tables:
|
Source Priority |
Project |
No |
The Source Priority credential enables you to optionally create and associate a source priority list with the project. A source priority list defines an ordered list of preferred interpreters used when retrieving like data. It is considered by business logic in the OpenWorks data access libraries. It affects decisions used in determining which well pick is used if picks have the same name but different interpreters. |
|
Petra |
Project Password |
Project |
Maybe |
The Petra project password. This credential is required if the Petra project has been password protected. |
PPDM |
User |
Data source |
Yes |
The Oracle user account name. This credential may have a default value if your OpenSpirit administrator enabled the Use As Default for Users option when configuring your PPDM data source. |
Password |
Data source |
Yes |
The Oracle account password. This credential may have a default value if your OpenSpirit administrator enabled the Use As Default for Users option when configuring your PPDM data source. |
|
Recall |
n/a |
|
|
|
SEGY |
n/a |
|
|
|
Studio |
User |
Data source |
Maybe |
The Oracle or SQL Server database account name. This credential is not needed if the Studio data source was configured to use Windows authentication. Tip: The user credential determines the projects that are visible in all OpenSpirit data source selection Windows. The data source appears not to contain any projects until the user and password credentials have been entered and saved.
|
Password |
Data source |
Maybe |
The Oracle or SQL Server database account password. This credential is not needed if the Studio data source was configured to use Windows authentication. |
|
QA_BusinessProject |
Project |
No |
This optional credential is provided to work around a problem in the Studio SDK that is encountered when Studio has been configured to require quality tags. The value of this credential used as the default value for the Business Project property on Seismic Folder, Interpretation Folder, and Horizon Interpretation domain objects that are automatically created by the Studio SDK. |
|
QA_Comment |
Project |
No |
This optional credential is provided to work around a problem in the Studio SDK that is encountered when Studio has been configured to require quality tags. The value of this credential used as the default value for the Comments property on Seismic Folder, Interpretation Folder, and Horizon Interpretation domain objects that are automatically created by the Studio SDK. |
|
QA_ConfidenceFactor |
Project |
No |
This optional credential is provided to work around a problem in the Studio SDK that is encountered when Studio has been configured to require quality Tags. The value of this credential used as the default value for the Confidence Factor property on Seismic Folder, Interpretation Folder, and Horizon Interpretation domain objects that are automatically created by the Studio SDK. |
|
QA_DataStatus |
Project |
No |
This optional credential is provided to work around a problem in the Studio SDK that is encountered when Studio has been configured to require quality tags. The value of this credential used as the default value for the Data Status property on Seismic Folder, Interpretation Folder, and Horizon Interpretation domain objects that are automatically created by the Studio SDK. |