We need 2 tables to hold a report's operation and facility data.
Most of that data will be copied over from the registration data when the report is started
This card is about creating the tables to store that data
Acceptance Criteria:
Given I am a developer
When a user starts a new report for their operation
Then I have a report_operation and a report_facility table to house the data for operations and facilities.
Given I am a developer
When I store data in the report_operation table
Then I have the following columns:
operator_legal_name
operator_trade_name
operation_name
operation_type
operation_bcghgid
boro_id
operation_representative_name
Given I am a developer
When I store data for the reporting activities and the regulated products of the operation
Then I can associate them to the report-operation data through a report_operation_activities table
Given I am a developer
When I store data in the report_facility table
Then I have the following columns:
facility_name
faciliry_type
bcghgid
Given I am a developer
When I store data for the reporting activities and the regulated products of the facility
Then I can associate them to the report-facility through a report_facility_activites and report_facility_products tables
Development Checklist:
[ ] We should have Django declare a many-to-many relationship between products/report_operation and activities/report_operation
[ ] Checklist item
[ ] Checklist item
[ ] 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
Description:
We need 2 tables to hold a report's operation and facility data. Most of that data will be copied over from the registration data when the report is started
This card is about creating the tables to store that data
Acceptance Criteria:
Given I am a developer When a user starts a new report for their operation Then I have a
report_operationand areport_facilitytable to house the data for operations and facilities.Given I am a developer When I store data in the
report_operationtable Then I have the following columns:Given I am a developer When I store data for the reporting activities and the regulated products of the operation Then I can associate them to the report-operation data through a
report_operation_activitiestableGiven I am a developer When I store data in the
report_facilitytable Then I have the following columns:Given I am a developer When I store data for the reporting activities and the regulated products of the facility Then I can associate them to the report-facility through a
report_facility_activitesandreport_facility_productstablesDevelopment Checklist:
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
Definition of Done (Note: If any of these points are not applicable, mark N/A)
Notes:
-