You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The coding for the tables is saved in an Information Division folder; this is a website team project though, so the coding should really be stored in GitHub or Google drive.
Completion criteria
Best place to store the coded tables is determined (discuss with @patphongs and @rfultz who came up with this prototype)
Code is uploaded to that place.
The text was updated successfully, but these errors were encountered:
The codes have been uploaded into the "E&J Codes" folder within the content folder. In addition, URLS that pointed to http:/sers.fec.gov were updated to https://sers.fec.gov and URLs that pointed to transition files were updated to the current location.
Summary
What we are after:
As a legal researcher, I need to review explanations and justifications for regulations.
The content team updates the E&Js whenever a new regulation is released. This is a tedious process involving much manual html coding and many html tables. The manual tables were our first iteration just to get the migration of those tables done. (For an example, take a look at the tables on https://www.fec.gov/legal-resources/regulations/explanations-and-justifications/citation-index-part-109/#part-109-subpart-b-independent-expenditures. There are many more like this and many of them are more dense.)
The coding for the tables is saved in an Information Division folder; this is a website team project though, so the coding should really be stored in GitHub or Google drive.
Completion criteria
The text was updated successfully, but these errors were encountered: