Provide a specification for the new GSQ Lodgement Portal that:

• Accurately defines the business requirements
• Is a key input to software design for a software developer

The primary input into this document is the data model defined in the Resources Industry Report Profile.

Resource authority holders need to submit a range of statutory reports on their activities. Reports include all mineral exploration, geothermal exploration, greenhouse gas exploration, petroleum exploration, petroleum well, seismic survey or airborne geophysical survey, mineral development licence, petroleum lease, and petroleum pipeline licence reports and some other exploration related reporting.

When government issues a permit to a holder, the legislation requires a permit holder to submit reports to the Department when certain activities are performed under the conditions of the permit.

• The reports contain knowledge of the geological resource.
• Historically, industry reports have been lodged through QDEX Reports.
• GDMP will deliver a new lodgement portal to replace QDEX Reports.
• Most industry reports have a confidentiality period before becoming open file.

1. Provide a single portal for industry and GSQ to lodge georesources reports.
2. Provide data validation at point of data entry.
3. Provide a database store to store in-progress and submitted reports.
4. Harvest the submitted metadata, data and datasets for insertion into CKAN, S3 and the GeoProperties Database.
5. Provide search functionality for GSQ staff to search for reports.
6. Replace QDEX Reports.

1. An online lodgement portal to allow industry users to submit reports and upload associated geoscience data files in a structured, itemised format.
   a.Data must be able to be submitted through a human-computer interface
   b.Data must be able to be submitted through a computer-computer interface
2. Automated workflows to process the geoscience data submitted to the geological properties database, and data catalogue and data object store.
3. A method of enabling the upload of large geoscience data files to the data object store.

There are 4 versions of lodgement portal to be built:

1. MVP Lodgement Portal to replace the current lodgement functionality of QDEX reports - described on this page.
2. Version 2 Lodgement Portal that extends the MVP Lodgement Portal to parse the data lodged in the petroleum, coal, and mineral reporting guideline templates - described on Version2-portal-README.MD
3. Multipart lodgement form (per ModulrTech style) for mineral & coal annual report - described on Version3-portal-README.MD
4. Multipart lodgement form (per ModulrTech style) for well completion report - described on Version4-portal-README.MD

It is vital that GSQ exit QDEX Reports by June 30, 2020. Hence, we will iterate through the 4 versions:

1. Analyse, design, build, and deploy Version 1 - the MVP Lodgement Portal. This portal replaces QDEX Reports.
   a. The MVP software (Version 1) provides the platform and "plumbing" for all future versions - i.e. web portal, authentication, authorisation, lodgement form, lodgement database, metadata, CKAN integration, S3 integration, spatial processing.
   b. The MVP software enables data migration out of QDEX Reports into the Lodgement Portal.
   c. The MVP software enables data migration out of QDEX Reports into the Data Catalogue (Open Data Portal, Private Data Portal, and Data Object Store (S3)).
2. Analyse, design, build, and deploy Version 2 - inheriting the functionality of the MVP and building the parsing functionality to populate the Geoproperties database.
3. Analyse, design, build, and deploy Versions 3 and 4.

Figure 1: MVP Lodgement Portal activity diagram

Figure 4: Lodgement Portal conceptual data model

The spatial coverage of the report. If no spatial data is submitted with the report and the report is for a permit(s), the spatial coverage is created based on the permit extents boundary. The geometry is stored in the PostGIS component of the database.

Enables the collection of various data, held as key:value pairs, i.e. report_detail_type:report_detail_value. e.g. tectonic:Kalkadoon

The datasets submitted with the report, e.g. PDF files, wireline logs, CSV files, are stored as objects in S3. Each resource is described with DCAT2-compliant metadata. This table lists all of the dataset resources linked to a report.

The Persistent Identifier (PID) is the unique identifier for a site or survey that is submitted to the department. GSQ needs industry to use this PID when submitting data to the department.

Customers lodge Notice of Intention forms to the department. This means that the borehole or the survey is proposed but not completed.

We need to tell the submitter of the form what the PID is and what it is used for. We can do this by emailing the PID to the submitter after successful submission. We want to do this after the form submission so we don't get orphan PIDs, i.e. PIDs created without the accompanying lodgement metadata.

Figure 2: Lodgement Portal PID minting

When the submitter submits a Notice of completion (or abandonment, etc.) form, we need to tie this lodgement to the proposed borehole or survey record in the GSQ database.

For instance:

• A customer earlier submitted a PA-21A - Notice of intention to carry out seismic survey or scientific or technical survey
• The system gave them the PID of the Survey, e.g. SS36789
• Now the customer lodges a PA-22A - Notice of completion of seismic survey or scientific or technical survey
• The customer enters the PID of the Survey SS36789 so we can tie the completion notice to the intention notice, i.e. tie to the completed survey to the proposed survey.
• The status of the Survey can now be changed to completed.
• When the customer later lodges a Seismic Survey Report - Final, again they enter the PID so that the report is tied to Survey SS36789.

Figure 3: Lodgement Portal PID matching

The following reports will be submitted through the Petroleum and Gas Reporting Template (.xls).

• They will be lodged through the Lodgement Portal with the submitter completing the standard report metdata in the lodgement form.
• The submitter will upload the .xls reporting template through the lodgement form.
• The submitter will upload any additional data files through the lodgement form.
• When submitted, the metadata is written to the Lodgement Portal database. The .xls reporting template and any additional files are stored in S3.
• The .xls file is harvested with the data inserted into the Geoproperties database.
• The report metadata is pushed through to CKAN as a Report dataset with links to the data objects in S3.

The following reports will be submitted through the Mineral Reporting Template or Coal Reporting Template (.xls files).

• They will be lodged through the Lodgement Portal with the submitter completing the standard report metdata in the lodgement form.
• The submitter will upload the .xls reporting template through the lodgement form.
• The submitter will upload any additional data files through the lodgement form.
• When submitted, the metadata is written to the Lodgement Portal database. The .xls reporting template and any additional files are stored in S3.
• The .xls file is harvested with the data inserted into the Geoproperties database.
• The report metadata is pushed through to CKAN as a Report dataset with links to the data objects in S3.
• No PID minting or maching is required.

• They will be lodged through the Lodgement Portal with the submitter completing the standard report metdata in the lodgement form.
• The submitter will upload any additional data files through the lodgement form.
• When submitted, the metadata is written to the Lodgement Portal database. Any additional files are stored in S3.
• There is no data automatically harvested into the Geoproperties database. This will be a manual process by GSQ staff.
• The report metadata is pushed through to CKAN as a Report dataset with links to the data objects in S3.
• No PID minting or maching is required.

The following report types are PDF forms.

• These will be lodged as PDF forms through the lodgement portal.
• The submitter will complete the lodgement form metadata.
• PID minting or PID matching will be performed as defined.

The following report types are no longer current.

• However, the report metadata for these reports is to be migrated from QDEX Reports into the Lodgement Portal.
• Any reports that have not already been published in the Open Data Portal need to be published into the relevant Open Data Portal or Private Data Portal based on the QDEX Reports confidentiality flag. Metadata into CKAN, data objects into S3.

The following report types will be submitted directly to the department, not lodged through the lodgement portal.

• However, the report metadata for these reports is to be migrated from QDEX Reports into the Lodgement Portal.
• Any reports that have not already been published in the Open Data Portal need to be published into the relevant Open Data Portal or Private Data Portal based on the QDEX Reports confidentiality flag. Metadata into CKAN, data objects into S3.

The vocabularies used in this profile are:

1. Georesources Report Type
2. Earth Science Data Category - the category(s) of data contained in the report
3. Data Access Rights
4. Commodity
5. Report detail type.
6. Report status.

The Lodgement Portal requires authentication using the Identity Broker:

• External users authenticate using QGCIDM (QGOV)
• Internal users authenticate using ADFS

The Lodgement Portal requires user authorisation:

• External users have rights to submit lodgement forms
• Internal users have rights to submit lodgement forms or view lodged forms

Figure 5: Lodgement Portal external user authentication and authorisation

The following data is to be migrated from QDEX Reports. Historically, QDEX Reports has been used to publish other types of publications.

• The new lodgement portal will focus on reports lodged by industry (Exploration Reports and Industry Consultative Reports).
• Other types of publications will be published through the Open Data Portal.

• Industry report profile
• Queensland Digital Exploration Reports System Report Lodger User Guide
• Queensland Digital Exploration Reports System Report Lodger User Guide For mining associated and non-associated water reports – Taking of water
• Queensland Digital Exploration Reports System Reporting Guidelines

This code repository's content are licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0), the deed of which is stored in this repository here: LICENSE.

System owner:
Mark Gordon
Geological Survey of Quensland
Department of Natural Resources, Mines and Energy
Brisbane, QLD, Australia
[email protected]

Author:
David Crosswell
Enterprise Architect
Cross-Lateral Enterprises https://crosslateral.com.au