Registration
- a multi-step form has been created to guide external users through the registration process. Only operations that aren't yet fully registered will be listed as options from the operation dropdown. If an operator wants to update information about a registered operation, they must do so via the "Operations" tile in the Administration module
- internal users do not need to "Approve" or "Decline" operation registrations, but they do need to issue BORO IDs and BCGHG IDs to registered operations (that don't already have one) by manually clicking buttons in the operation's registration form. (i.e., these numbers will not be automatically issued upon the external user's completion of the registration form, but will be auto-generated once the internal user reviews the registration form and confirms they want to issue a BORO ID and/or BCGHG ID to the operation). Only users with the role of "cas_director" will have the option to assign BORO or BCGHG IDs
- an operation only needs to be registered once. If an operation is transferred to another operator, the operation will still be considered "registered" under the new operator
- once an operation's registration data has been submitted, the operation's status will automatically be changed to "Registered". Industry users will no longer be able to go through the registration workflow with their registered operations, but all data included in Registration will now be visible in the Administration module in Operation Details (essentially shows the multi-step registration form as a one-page form).
When registering an operation, external users must specify what category or "registration purpose" their operation falls under. The registration purpose selected determines some of the data fields shown later in the registration workflow (as well as affecting the fields in the annual report in Reporting).
A user will only be permitted to select exactly one option for registration purpose. The selected registration purpose will be saved in the pertinent operation's data.
The diagram below describes the relationships between the 6 available options for registration purpose. For example, any operation that is registered as "OBPS Regulated Operation" can also be considered a Reporting Operation.
All operations categorized as "Reporting" operations will be expected to submit annual emissions reports.
Users who select "EIO" as their Registration Purpose will be shown a simplified version of the registration workflow that doesn't prompt them for Facility Information (to avoid confusion on the part of external users), since EIOs don't have facilities. However, when an EIO is registered, a facility for the operation will be created in the BCIERS database, largely using the operation's information. This is necessary because the Reporting module relies on facility information when constructing reporting forms.
If an industry user selects "Opted-in Operation" as their operation's registration purpose, a related record called OptedInOperationDetail will be created and stored in the database, for the purpose of storing their responses to questions specific to opted-in operations. There is also an opt_in boolean flag on the operation record that will be set to True for operations registered as Opted-In. This is for the purpose of making filtering opted-in operations in Metabase more user-friendly.