Building off of the proof of concept work done in #250, we can now build out the database structures for WCI configuration tables to enable us to dynamically create emission reporting forms.
As a developer
I want the models outlined below created in the database
So I can generate forms from configs
AC:
[x] All models below are created in Django & migrated
[ ] The models that require initial data have the correct data
reporting_source_type, fkey to reporting_source_type
reporting_gas_type, fkey to reporting_gas_type
reporting_methodology, fkey to reporting_methodology
reporting_field, ManyToMany (reporting_field)
valid_from, fkey to configuration
valid_to, fkey to configuration
reporting_field:
name, varchar
type, varchar
base_schema:
slug, varchar
schema, json
activity_source_type_base_schema:
activity (fkey to reporting_activity)
source_type (fkey to reporting_source_type)
base_schema (fkey to base_schema)
valid_from (fkey to configuration)
valid_to (fkey to configuration)
Initial Data
reporting_gas_type: - validate with IRC
carbon dioxide from non-biomass not listed in Schedule C.1
carbon dioxide from non-biomass listed in Schedule C.1
carbon dioxide from biomass listed in Schedule C
carbon dioxide from biomass not listed in Schedule C
methane from non-biomass not listed in Schedule C.1
methane from non-biomass listed in Schedule C.
methane from biomass listed in Schedule C
methane from biomass not listed in Schedule C
nitrous oxide from non-biomass not listed in Schedule C.1
nitrous oxide from non-biomass listed in Schedule C.1
nitrous oxide from biomass listed in Schedule C
nitrous oxide from biomass not listed in Schedule C
Carbon dioxide
Methane
Nitrous oxide
Sulfur Hexafluoride
Tetraluoromethane
Perfluoroethane
Difluoromethane
Pentafluoroethane
1,1,1,2-Tetrafluoroethane
reporting_methodology: - validate with IRC
Default HHV/Default EF
Default EF
Measured HHV/Default EF
Measured Steam/Default EF
Measured CC
Measured Steam/Measured EF
Alternative Parameter Measurement
Replacement Methodology
Anode Consumption
Slope method
Overvoltage method
C2F6 anode effects
Inventory
Input/output
Building off of the proof of concept work done in #250, we can now build out the database structures for WCI configuration tables to enable us to dynamically create emission reporting forms.
As a developer I want the models outlined below created in the database So I can generate forms from configs
AC:
Models
We will need the following models:
reporting_gas_type reporting_methodology configuration configuration_element reporting_field base_schema source_type_base_schema
Model structures
reporting_gas_type:
reporting_methodology:
configuration:
configuration_element:
reporting_field:
base_schema:
activity_source_type_base_schema:
Initial Data
reporting_gas_type: - validate with IRC carbon dioxide from non-biomass not listed in Schedule C.1 carbon dioxide from non-biomass listed in Schedule C.1 carbon dioxide from biomass listed in Schedule C carbon dioxide from biomass not listed in Schedule C methane from non-biomass not listed in Schedule C.1 methane from non-biomass listed in Schedule C. methane from biomass listed in Schedule C methane from biomass not listed in Schedule C nitrous oxide from non-biomass not listed in Schedule C.1 nitrous oxide from non-biomass listed in Schedule C.1 nitrous oxide from biomass listed in Schedule C nitrous oxide from biomass not listed in Schedule C Carbon dioxide Methane Nitrous oxide Sulfur Hexafluoride Tetraluoromethane Perfluoroethane Difluoromethane Pentafluoroethane 1,1,1,2-Tetrafluoroethane
reporting_methodology: - validate with IRC Default HHV/Default EF Default EF Measured HHV/Default EF Measured Steam/Default EF Measured CC Measured Steam/Measured EF Alternative Parameter Measurement Replacement Methodology Anode Consumption Slope method Overvoltage method C2F6 anode effects Inventory Input/output
configuration