Challenge Overview
Challenge Overview
The objective of the Megahack is simple, the development of a search portal that allows users to perform a search against pending EPA laws and regulations based on search criteria that aren’t available today, and see if and how it is related to Clean Air Act enforcement as well as show linkages from the laws or regulations to programs that might be related.
Contest Objective
---Integrate the Frontend with Nodejs backend server
Requirements
---Backend server uses nodejs 6.x
---Frontend server uses AngularJs
This is the final contest and will integrate the frontend (AngularJs) and the Nodejs backend server. The frontend and backend applications will be provided forum, as all other needed documentation. The nodejs backend uses the API definition found here.
The following missing features should be added to the backend server:
1. Use XML parser to match NAICS and Program against proposed rules
Item III is partially done. It should be verified and fixed if necessary.
2. More details Tab in frontend details page should be populated with the matched regulations, like this:
NAICS and Substance input should allow autocomplete, but it must not restrict user input. Use the API lookup endpoints.
Any other issue found in the frontend or backend server should also be fixed. The final submission should be a fully working application as described in the provided documents.
Reference Documents
---Will be posted in the contest forum.
The objective of the Megahack is simple, the development of a search portal that allows users to perform a search against pending EPA laws and regulations based on search criteria that aren’t available today, and see if and how it is related to Clean Air Act enforcement as well as show linkages from the laws or regulations to programs that might be related.
Contest Objective
---Integrate the Frontend with Nodejs backend server
Requirements
---Backend server uses nodejs 6.x
---Frontend server uses AngularJs
This is the final contest and will integrate the frontend (AngularJs) and the Nodejs backend server. The frontend and backend applications will be provided forum, as all other needed documentation. The nodejs backend uses the API definition found here.
The following missing features should be added to the backend server:
1. Use XML parser to match NAICS and Program against proposed rules
I- If NAICS is provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch NAICS using code provided by search frontend with XML parser
c) Filter the data in a) with the CFR parts returned by regulations associated to NAICS
d) Present data from b) and d)
II- If NAICS is NOT provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch NAICS using CFR part from a) with XML parser
c) Present data from a) and b)
III- If Program provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch Program using name provided by search frontend with XML parser
c) Filter the data in a) with the CFR parts returned by regulations to Program
d) Present data from b) and d)
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch NAICS using code provided by search frontend with XML parser
c) Filter the data in a) with the CFR parts returned by regulations associated to NAICS
d) Present data from b) and d)
II- If NAICS is NOT provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch NAICS using CFR part from a) with XML parser
c) Present data from a) and b)
III- If Program provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch Program using name provided by search frontend with XML parser
c) Filter the data in a) with the CFR parts returned by regulations to Program
d) Present data from b) and d)
IV- If Program is NOT provided:
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch Programs using CFR part from a) with XML parser
c) Present data from a) and b)
a) Search Regulations.gov API and fetch proposed rules (including details - CFR part)
b) Fetch Programs using CFR part from a) with XML parser
c) Present data from a) and b)
Item III is partially done. It should be verified and fixed if necessary.
2. More details Tab in frontend details page should be populated with the matched regulations, like this:
40 CFR Part 50
1- TITLE FOR FIRST REGULATION MATCH (should be a hyperlink if URL is present)
2- TITLE FOR SECOND REGULATION MATCH (should be a hyperlink if URL is present)
….
1- TITLE FOR FIRST REGULATION MATCH (should be a hyperlink if URL is present)
2- TITLE FOR SECOND REGULATION MATCH (should be a hyperlink if URL is present)
….
NAICS and Substance input should allow autocomplete, but it must not restrict user input. Use the API lookup endpoints.
Any other issue found in the frontend or backend server should also be fixed. The final submission should be a fully working application as described in the provided documents.
Reference Documents
---Will be posted in the contest forum.
Final Submission Guidelines
---Zip file with the integrated frontend
---Deployment and usage instructions should be included in a README.md file