Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

Load the 2020 11 CFR into e-regs #502

Closed
7 tasks done
Tracked by #139
dorothyyeager opened this issue May 26, 2020 · 9 comments · Fixed by #506
Closed
7 tasks done
Tracked by #139

Load the 2020 11 CFR into e-regs #502

dorothyyeager opened this issue May 26, 2020 · 9 comments · Fixed by #506

Comments

@dorothyyeager
Copy link
Contributor

dorothyyeager commented May 26, 2020

What we are after

Making sure the newest version (2020) of 11 CFR is parsed into e-regs

GPO links to different formats: https://www.govinfo.gov/app/details/CFR-2020-title11-vol1/

@dorothyyeager Put in changes in for the new regs so we know what to look for. - DONE BELOW

Changed regulations: (in many of these cases, the change is to remove a reference to the Secretary of the Senate)

Completion criteria

  • Regs loaded onto dev
  • Regs loaded onto stage
  • New regulations are loaded to the live website (Regs loaded onto prod)

Tech considerations

--Right now @jason-upchurch is the only one who has the parser working on his local

  • Reload the regulations in dev and stage
  • Test in dev and stage with content team
  • Reload regulations in prod
  • Have team verify the regulations are updated in production
@dorothyyeager
Copy link
Contributor Author

I've updated ticket with the regs that changed in the 2020 11 CFR. Most (not all) of the changes related to removing references to the Secretary of the Senate. So the list may look more scary than it really is. @jason-upchurch Please feel free to add me as a reviewer/tester if you want to doublecheck that we got all the revisions in.

@jason-upchurch
Copy link
Contributor

2020 regs not completely parsing locally, so working on debugging. Verified with @pkfec and @fec-jli.

@jason-upchurch
Copy link
Contributor

@dorothyyeager I've made some headway in parsing the regs, but I am getting this "Purpose and scope" (section 1.1) showing up. We don't currently show it (we start with 1.2 for some reason). Just wondering if you knew whether or not it was okay to have it.

Screen Shot 2020-06-04 at 9 23 45 AM

@jason-upchurch
Copy link
Contributor

Actively working on debugging the regparserand demo'd parsing about 30 of the regulations for 2020 (some misformatted). Expect this to move to Sprint 12.6.

@jason-upchurch
Copy link
Contributor

team call today at 1:00 pm to go over next steps now that regs are loaded locally.

@jason-upchurch
Copy link
Contributor

@dorothyyeager the 2020 regs are loaded on dev here:
https://fec-dev-eregs.app.cloud.gov/regulations/

@jason-upchurch
Copy link
Contributor

Once regs are verified on dev, need to load onto stage and then prod

@dorothyyeager
Copy link
Contributor Author

@jason-upchurch Left you a comment on the PR about the regs on dev. There's a few things to fix.

@jason-upchurch jason-upchurch linked a pull request Jun 18, 2020 that will close this issue
2 tasks
@dorothyyeager
Copy link
Contributor Author

@jason-upchurch Tested on stage. The things I caught on dev were fixed (I left a similar comment in the PR) and it looks good as far as the content team goes. Thank you for your work on this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants