Update facility data labels to the new data dictionary

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)
[x] Does this have a dev link been provided in the design?
[x] Is this traceable to a feature, epic, or PI?

User Story

As a CAMPD user I want the facility data labels to be consistent with the EPA data dictionary so that I can understand the data

Acceptance Criteria

Given that a user has made a GET request to a facility API endpoint with the file type set to JSON When data is returned Then the JSON labels are consistent with Master data label dictionary (see context)

Given that a user has made a GET request to a facility API endpoint with the file type set to csv When data is returned Then the csv labels are consistent with the Master data label dictionary (see context)

Given that a user has selected preview data on the custom data download for facility/ unit attributes data When the functionality is displayed Then the data labels are consistent with the Master data label dictionary (see context)

Given that a user has navigated to the facility swagger page When the example schema is displayed for the facility/ unit attributes endpoint Then the values contain a description AND the description is consistent with the Master Data Dictionary (see context)

Development Notes

Facility endpoints include the following: /api/facility-mgmt/facilities /api/facility-mgmt/facilities/ attributes /api/facility-mgmt/facilities/ attributes / applicable /api/facility-mgmt/facilities {id}

the scope of this ticket also includes updating the api endpoint parameters and adding descriptions (see context)

Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context

Final_CAMPD_Master Data Labels List_EPA CAMD_v1.0

1. Confirm or change name for parameters:	Keep/Change
unitType	Keep
unitFuelType	Keep
controlTechnologies	Keep
program	change name to programCodeInfo
sourceCategories	change name to sourceCategory
opHoursOnly	change name to operatingHoursOnly

2. Need parameter descriptions for:	New Description
unitFuelType	Primary or Secondary fuel types combusted by the unit.
controlTechnologies	Method or equipment used by the combusion unit to minimize Hg, NOx, PM, or SO2 emissions.
beginDate	Begin date for a given period of a unit's emissions.
endDate	End date for a given period of a unit's emissions.
opHoursOnly	Indicator of whether or not a request should return only data for hours where a unit operated.
sourceCategories	Unit classification in terms of its primary function.
transactionBeginDate	Begin date for a given period of an account's allowance transaction history.
transactionEndDate	End date for a given period of an account's allowance transaction history.
page	Page number of data being requested
perPage	Number of results per page

Testing

Test Case: TC395 Tester: @JanellC

Definition of Done

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

US-EPA-CAMD / easey-ui