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

Define report types #157

Open
10 tasks
spulec opened this issue Aug 21, 2014 · 3 comments
Open
10 tasks

Define report types #157

spulec opened this issue Aug 21, 2014 · 3 comments

Comments

@spulec
Copy link
Member

spulec commented Aug 21, 2014

On most of the early scrapers, there was a type field that was used quite a bit to describe the type of report (audit, testimony, etc). I think it would be useful to establish a standard list of values for this and then work on applying it to all of the scrapers.

Some types:

  • audit
  • investigation
  • testimony
  • press
  • research
  • performance
  • evaluation
  • inspection
  • congress
  • peer_review
  • semiannual_report
  • management_challenges
  • fisma
  • other

Benefits are two-fold: first, it would allow for projects like oversight.io to be able to apply some nice filtering. Second, it would allow for better QA of our dataset. For example, "Oh, we don't have any Peer Reviews for the SSA. We should issue some FOIA requests for those."

Remaining scrapers without a type field:

  • dhs
  • dod
  • doj
  • eeoc
  • epa
  • gao
  • hhs
  • house
  • labor
  • loc
@konklone
Copy link
Member

Completely agree - this fell by the wayside, and will be very useful, especially now that we have a better understanding of what kinds of reports IGs produce.

@spulec
Copy link
Member Author

spulec commented Aug 22, 2014

Great. I'm not too concerned right now about what the actual list of types is. I'm more concerned with getting something implemented since it should be pretty easy to combine/split/rename things post-implementation. If anyone has opinions on that though, feel free to chime in.

My plan is to go through the scrapers alphabetically and try to apply types to all reports. Anyone else should feel free to jump in too. Once they are all added, I think it makes sense to make type a required field going forward.

@spulec
Copy link
Member Author

spulec commented Sep 2, 2014

I added a bunch of these, but there are 10 remaining that are a bit trickier. I've added them to the issue description.

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

No branches or pull requests

2 participants