Reg\Register an Operation - External User can select "Registration Purpose\Electricity Import Operation" to see a simplified version of registration

[andrea-williams]

Dependencies

• Blocked by figuring out what to do if the user changes purpose?
• Blocked by #1694
• Blocking

Description:

EIOs are a somewhat unique type of operation in the sense that they don't have the concept of a facility, so we need to modify the registration workflow to suit them.

Acceptance Criteria:

Given I am an authenticated external user When I select "Electricity Import Operation" as my registration purpose (step 1) Then I see a simplified version of the registration workflow with only the data fields that are relevant to EIOs (a stripped-down version of the Operation form, no Facility form at all)

Development Checklist:

• [ ] EIO wireframe for Operation section of form
• [ ] depending on the add operation feature has previously been implemented, either create a new json form schema for EIOs and use it conditionally, or add conditional fields to the existing one
• [ ] update the Facility db model to have a "Electricity Import" type
• [ ] wherever necessary, update Operation and Facility db models to allow nulls for the fields that don't apply to EIOs.
• [ ] on form submit: -- [ ] new Operation record is created in the db for the EIO (submit button already calls the POST endpoint but may need to tweak to accommodate EIO) -- [ ] remove "Facility Information" step in the registration workflow UI (see how new entrant/opt-in steps are conditionally added/removed as an example) -- [ ] but a new Facility is still created in our database for the EIO (facility name should be set to the operation's name; facility type is "Electricity Import"; facility address should be set to the operation's address; lat/long of largest emissions can be empty (set to optional in db)
• [ ] To still ensure all necessary data is provided, create new django-ninja schemas for ElectricityImportOperationIn and ElectricityImportOperationOut (don't make a new endpoint, use custom validation, see comment below)
• [ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Notes:

[BCerki]

@Sepehr-Sobhani , were you involved in the writing of this one? Do you know if those TBDs are decided yet?

[Sepehr-Sobhani]

I was not involved, and I am not quite sure about the first TBD, but for the second one, I think we can adjust our schemas and add some custom validation logic to enforce required fields based on the purpose.

[andrea-williams]

for the first TBD (but a new Facility is still created in our database for the EIO (facility name should be set to the operation's name; facility type is "Electricity Import"; facility address should be set to the operation's address; lat/long of largest emissions - TBD)) - this may be a question for the business area. Possible solutions I can think of are:

• we ask the external user to provide lat/long coordinates for their operation in addition to their address
• we make the lat/long coordinates optional in the database so that the "facility" for the EIO just doesn't have lat/long coordinates associated with it
• we use something like the Google Maps API (other brands are available) to fetch lat/long coordinates for a provided address.

cc'ing @hannavovk and @zoeyli-46

[patrickisaac]

Aug. 13 Refinement Notes:

• Need additional information/refinement with developers
• Hanna to seek additional information from BA

[hannavovk]

Confirmed with business area that lat/long coordinates are not needed for EIOs. BA is in agreement with making lat/long coordinates optional in the database so that the "facility" for the EIO just doesn't have them, as long as the SFOs and LFOs still have to enter them. (cc @andrea-williams, @zoeyli-46 )