Data Management and Storage#

β„Ή Download images, presentations, files, and documents from DAPwellscienceteam/DataManagement/DataTypes&Storage.

To address potential challenges in collecting, storing, managing, and sharing data collected from the geotermal well, we have created a data management plan (DMP) which can be downloaded from DMPonline. This DMP will be updated as the project moves forward.

Data Storage#

Research data from the geothermal well and monitoring borehole are of high scientific value and must be securely stored and accessible to researchers. To address this in the DMP, we have used Storage Finder and concluded that the TUDelft Project Data Storage (U:) was the most reliable option.

⚠ However, Project Data Drive (U: Drive) lacks access controls needed for modern collaboration:

  • Members have access to the entire folder system,

  • Members have either READ-ONLY or READ-WRITE permission, and

  • Sharing data with external users is cumbersome and (most of the time) frustrating.

Research data is stored in Project Data Drives (from storagefinder.tudelft.nl)

Below is a comparison of the data storage available with pros and cons to help researchers choose what is better for their type of data. Download this file from the DAPwell Team on TEAMS (only authorised members).

Types of data storage at TU delft

U:\DAPWELL_DATA Drive#

All research data produced by the geothermal well project are stored in the Project Storage Drive called U:\DAPWELL_DATA. This is the Master Copy where raw data and unchanged (static) data sets are stored. These data are shared with other researchers and may be input for other workflows.

Researchers have individual project drives to work on their data (dynamic) before depositing them in the U:\DAPWELL_DATA drive as listed below.

Data Stored

Drive

Admin

Monitoring Station DAPGEO-02

U:\DAPGEO02

Susanne Laumann & Phil Vardon

Geothermal well DEL-GT-01 & DEL-GT-02

U:\DAPWELL_DATA

Susanne Laumann & Phil Vardon

Geologic Model (Petrel)

U:\geothermalpetrel

Hemmo Abels

Geology & Petrophysics

U:\DELGTPETRO

Hemmo Abels & Auke Barnhoorn

Reservoir Simulation

U:\DAPWELLSIM

Denis Voskov & Alexandros Daniilidis

Fibre Optics

U:\DAPWELLFO

Guy Drijkoningen

Data Management

U:\EPOSDM

Susanne Laumann

By default, all memebers of U:\DAPWELL_DATA have read-only access to prevent unintentional file modifications. Researchers who wish to store data files in this drive must request read-write access to the drive admin. Once the files have been deposited, access will be restored to read-only.

β„Ή Administrators of Project Data Drives can give access by sending the netID of new members to the service desk or by using UMRA, which is already installed on TU Delft managed computers or it can be downloaded from the Software Centre otherwise.

CLICK here to know how add members to a Project Drive.
  1. Open the UMRA application

  2. Select Change Group Membership and click Next

  3. Selec the Project Drive from the list and click Next

  4. Select the group you wish to modify:

    • CONTRIBUTORS group has read and write permissions (files can be edited; no version control is available)

    • ADMINS group has read and write permissions and can add/remove users

    • READERS group has only read permissions (files can only be downloaded)

  5. The ADMIN user can select the user from the list and click REMOVE

  6. The ADMIN user can click ADD and type the name of the new user and click SEARCH. Then select the user netID from the list and click ADD

  7. To change to the GROUPS list click back or finished

πŸ—ƒοΈ Folder Structure#

We have consulted and implemented Best practices in the management of geothermal exploration data and organised data by research discipline. Other cathegories were added for easy access, such as sample databases and physical storage, photos, etc.:

  • Geologic data,

  • Borehole data,

  • Wireline logging,

  • Geophysical data,

  • Reservoir modelling,

  • Samples, etc.

CLICK here to expand U:\DAPWELL DATA folder structure.

U:\DAPWELL DATA
β”œβ”€β”€β”€01_geologic_data
β”œβ”€β”€β”€02_borehole_data
β”‚   β”œβ”€β”€β”€drilling_reports
β”‚   β”‚   β”œβ”€β”€β”€Daily Look-Ahead Reports
β”‚   β”‚   β”‚   β”œβ”€β”€β”€daily directional reports
β”‚   β”‚   β”‚   β”œβ”€β”€β”€daily drilling mud reports
β”‚   β”‚   β”‚   β”œβ”€β”€β”€daily drilling reports DDR
β”‚   β”‚   β”‚   β”œβ”€β”€β”€daily geological reports
β”‚   β”‚   β”‚   β”œβ”€β”€β”€daily lithostratigraphic column
β”‚   β”‚   β”‚   └───daily mudlogging-lithologs
β”‚   β”‚   β”œβ”€β”€β”€PVA plots - directional plots
β”‚   β”‚   └───Weekly Reports
β”‚   β”œβ”€β”€β”€end-of-well-report_EOWR
β”‚   β”œβ”€β”€β”€final_aardyn_full_dataset
β”‚   β”‚       β”œβ”€β”€β”€Borehole_tracks
β”‚   β”‚       β”œβ”€β”€β”€Database
β”‚   β”‚       β”œβ”€β”€β”€GeoWellReport
β”‚   β”‚       └───Raw_Data
β”‚   β”œβ”€β”€β”€final_report
β”‚   └───well_design
β”‚       β”œβ”€β”€β”€2021 design freeze
β”‚       β”œβ”€β”€β”€2023 detailed well design
β”‚       └───Drilling programme
β”œβ”€β”€β”€03_core_data
β”‚   β”œβ”€β”€β”€core_gamma_ray
β”‚   β”œβ”€β”€β”€core_initial_description
β”‚   β”œβ”€β”€β”€core_macro_ct_scans
β”‚   β”‚   β”œβ”€β”€β”€DAPWELL_TEST_20230330
β”‚   β”‚   β”œβ”€β”€β”€high-res-tiff
β”‚   β”‚   β”œβ”€β”€β”€low-res_jpg
β”‚   β”‚   └───raw-data
β”‚   β”‚       β”œβ”€β”€β”€extended-scale
β”‚   β”‚       └───normal-scale
β”‚   β”œβ”€β”€β”€core_photos_drillsite
β”‚   └───coring_reports
β”‚       β”œβ”€β”€β”€final coring reports
β”‚       └───individual core reports
β”œβ”€β”€β”€04_sidewall_cores
β”‚   β”œβ”€β”€β”€swc images
β”‚   β”œβ”€β”€β”€swc initial description
β”‚   └───swc photos
β”œβ”€β”€β”€05_sample_databases
β”‚   β”œβ”€β”€β”€core chips
β”‚   β”œβ”€β”€β”€core_plugs
β”‚   β”‚   └───core plugs photos
β”‚   β”œβ”€β”€β”€elabjournal
β”‚   β”‚   └───csv files from elabjournal
β”‚   β”œβ”€β”€β”€old_drillsite sample registration sheets
β”‚   β”œβ”€β”€β”€sample database
β”‚   └───sample requests
β”‚       └───Requests
β”œβ”€β”€β”€06 core storage 00.31
β”œβ”€β”€β”€07_well_logging
β”‚   β”œβ”€β”€β”€interpreted data
β”‚   β”‚   └───Geomechanical study
β”‚   β”œβ”€β”€β”€logging program
β”‚   β”œβ”€β”€β”€processed data
β”‚   β”œβ”€β”€β”€raw data
β”‚   β”‚   β”œβ”€β”€β”€BAKER HUGHES_WIRELINE_DELIVERABLES
β”‚   β”‚   β”‚   β”œβ”€β”€β”€GT01_deliverables
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_BHP
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_CBL
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_SL
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_XMAC-HDIL
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R2_GXPL_UXPL
β”‚   β”‚   β”‚   β”‚   β”‚   └───Run2-1_Processed_GXPL_UXPL
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R3_CN_ZDL
β”‚   β”‚   β”‚   β”‚   └───R3_MREX
β”‚   β”‚   β”‚   β”œβ”€β”€β”€GT02_deliverables
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_FPI
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R2_DD
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R3_BHP
β”‚   β”‚   β”‚   β”‚   └───R3_DCST
β”‚   β”‚   β”‚   β”œβ”€β”€β”€GT02_S1_deliverables
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_BHP
β”‚   β”‚   β”‚   β”‚   β”œβ”€β”€β”€R1_CBL
β”‚   β”‚   β”‚   β”‚   └───R1_XMAC_HDIL
β”‚   β”‚   β”‚   └───GT02_S2_deliverables
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R1_BHP
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R1_CBL
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R1_XMAC_HDIL
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R2_GXPL_UXPL
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R3_CN_ZDL
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R3_MREX
β”‚   β”‚   β”‚       β”œβ”€β”€β”€R3_SL
β”‚   β”‚   β”‚       └───R4_R5_R6_CORING
β”‚   β”‚   └───deviation surveys
β”‚   └───wellcad-files-figures
β”œβ”€β”€β”€08_well_test
β”œβ”€β”€β”€09_geophysical_data
β”‚   β”œβ”€β”€β”€NAM_Monster_3D_R3481
β”‚   └───TNO
β”œβ”€β”€β”€11_reservoir_models
β”‚   └───DAP model_v0 DARTS model
β”œβ”€β”€β”€12_photos
β”‚   β”œβ”€β”€β”€drilling site photos
β”‚   └───drone videos
└───99_archive

Implementing a file naming convention was unsuccessful, particularly for data and reports delivered to us by other companies, as communication will always refer to original file names.

πŸ“Metadata#

A description of the data is in readme.txt files, within most of the directories. It is essential to include information to let others understand the file contents, e.g., who and when was data collected, type of data, the level of processing, if any correction was applied, processing methods, parameter selection, software used for processing, etc.

A best practice is to add a readme file when storing data in this drive, to let other researchers make better use of the data. Metadata should be provided by the specialist or the data manager would create it based on the file content otherwise.

Data Access after Research#

Open access data services will be fully compatible and interoperable with the EPOS e-infrastructure. Data will be released publicly no later than at the time of publication of corresponding research papers.

However, data may be embargoed until the primary scientific publication describing the results is published. In some cases the raw data may be embargoed until all publications in the project have been published. Any embargo period will be consistent with the overall EPOS data policy, which is up to two years from the end of the data collection. During the embargo period, metadata will be made openly available. See for example DEL-GT-01 and DEL-GT-02 Wireline Logs.

TU Delft will have ownership of all scientific data collected in the geothermal well project, whereas the well operator will own any operational data collected. During the active phase of research, the geothermal well data manager in consultation with the scientific head and programme manager, will oversee the access to scientific data (and other outputs), as well as any requests for access from external parties. Related projects that require use of the scientific data, (e.g., EASYGO, WARMUP) will be given full access to the relevant data.

Data Licensing#

The geothermal well research data will be published via the institutional repository 4TU.ResearchData under the CC BY 4.0 license, unless other license is more suitable for the type of data. License CC BY 4.0 (Attribution 4.0 International) lets others distribute, remix, adapt, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of licenses, recommended by EPOS and NWO for maximum dissemination and use of licenced materials.

Data Publication Workflow#

When data is collected, the raw data will be stored in the designated storage, metadata will be created at the point of collection if data files do not contain acquisition information embedded. Digital files may be transformed to open file formats for wider dissemination (for example, from LAS to CSV). Raw data can be published at 4TU.ResearchData repository or being further processed and analysed. Documentation must be provided by the researcher in the form of a README file. Download this README.docx file and use it as template. Include as much information as possible to maximise result rerpoducibility and data reusability.

Follow the guidelines from 4TU.ResearchData repository to prepare a data set and publish it.

β„Ή Don’t forget to use the geo-energy vocabulary and add them as keywords to enable EPOS MSL to discover the data set.

Data Workflow