DE: Implement Data Preview for Fuel Type

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story

As a CAMPD custom data download user I want to preview filter criteria for fuel type so that I can confirm that my dataset includes my desired fuel type(s)

Acceptance Criteria

Given a user has selected fuel type filter criteria When they select Preview Data Then the filter criteria is reflected in the result

Context

Wireframes

Filter tags and functionality were completed in ticket Restructure Filter Components for Reusability Across All Data Types #1435

Data Preview Trigger: A user has entered, at a minimum, the required parameters, and selected the option to preview data. For each record that matches the criteria, the system will display in a tabular format:

Refer to CAMPD_DataLabels_AggregatedEmissions_5-10_2021 for column display names

For each record that matches the criteria, the system will display in a tabular format in the following order and ordered by Facility > Unit > Date STATE FACILITY_NAME ORISPL_CODE UNITID ASSOC_STACKS OP_DATE SUM_OP_TIME COUNT_OP_TIME GLOAD SLOAD SO2_MASS SO2_RATE NOX_MASS NOX_RATE CO2_MASS CO2_RATE HEAT_INPUT PRIMARY_FUEL_INFO SECONDARY_FUEL_INFO UNIT_TYPE_INFO SO2_CONTROL_INFO PART_CONTROL_INFO NOX_CONTROL_INFO HG_CONTROL_INFO PRG_CODE_INFO

Results will display total record count (Viewing the first 100 of X records) Results in preview are limited to the first 100 records Results in preview will have a scroll functionality to show all columns/rows Results columns are are sortable in ascending and descending order (alphanumeric order) . Sort is limited to the original 100 results

Testing

Test Case: Tester:

Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

US-EPA-CAMD / easey-ui