Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Withdrawn AO issue #1390

Closed
7 tasks done
Tracked by #128
patphongs opened this issue Oct 26, 2017 · 6 comments
Closed
7 tasks done
Tracked by #128

Withdrawn AO issue #1390

patphongs opened this issue Oct 26, 2017 · 6 comments
Assignees
Labels
Milestone

Comments

@patphongs
Copy link
Member

patphongs commented Oct 26, 2017

It appears that a few withdrawn AOs are not showing up as withdrawn within the Date issued column. These AOs include AO 2017-11 and AO 2009-05.

https://www.fec.gov/data/legal/search/advisory-opinions/?type=advisory_opinions&ao_category=W

  • Verify that ao.stage data maps to AO status (0 = pending, 2 = withdrawn, 1 = final)

  • Replace AO is_pending with with ao_status

  • Verify searches still work in API where ao_category=W

  • Test AO search with status parameter

  • CMS - change logic for display date for withdrawn AO's to check AO status, not date = 1/1/1900. This was providing unreliable data.

  • Test AO 2009-05

  • Test AO 2017-11

Thanks @vrajmohan for your help!

@patphongs patphongs added the Bug label Oct 26, 2017
@AmyKort AmyKort added this to the Sprint 4.3 milestone Oct 31, 2017
@lbeaufort
Copy link
Member

@lbeaufort
Copy link
Member

lbeaufort commented Nov 2, 2017

Currently, the AO endpoint has a boolean is_pending parameter, and is searchable for ao_category=W, but it doesn't seem that ao_category is displayed in the output. I think the CMS may need to consume the ao_category data point in order for the display logic to be correct for the "Date Issued" column
here. I'm asking Vraj the best way to address the gaps in the logic above ^^

@lbeaufort
Copy link
Member

It looks like in the database, the stage field corresponds with AO status above. However, one withdrawn AO (2009-05) seems to have been marked Final in the internal database. We can capture those outliers by including AO's with "Withdrawn" in the summary: select ao_no, stage, * from aouser.ao where stage=2 OR ao.summary LIKE 'Withdrawn%';

@vrajmohan
Copy link
Contributor

Unless there is diligence over the AO summary, ao.summary LIKE 'Withdrawn%' seems to be a very wide net.

@lbeaufort
Copy link
Member

@vrajmohan I agree - I don't like programming around inconsistent data. Maybe a better option would be to explore updating the data on our end so Stage = Withdrawn instead of Final for AO 2009-05

@lbeaufort
Copy link
Member

Agreed-upon solution is to hard-code the withdrawn AO that is marked as final in the database until its stage can be changed to withdrawn in the database.

select ao_no, stage, * from aouser.ao where stage=2 OR ao_no='2009-05';

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

No branches or pull requests

4 participants