>>5160031

Lifted your fukkin' sweet pepe .gif and using here so that you'll see the post, 5:5. Hope you don't mind.

—

Fantastic that you got 2018 in there!

It looks like we could be missing 2008 though (unless we've got an off-by-one labeling thing going on here, ie 2009-2018 -vs- 2008-2017 ???), can you add 2008 to the JSON once back from dinner? danks.

cat fd.json| jq ".[].Member" | grep -i year | sort -u

"Year": "2009",

"Year": "2010",

"Year": "2011",

"Year": "2012",

"Year": "2013",

"Year": "2014",

"Year": "2015",

"Year": "2016",

"Year": "2017",

"Year": "2018",

>>5160524

ugh, >>5160031 (lb), is last bread - sorry for the mislabeling.

Sleep beckons… I need to get me a sleepy pepe for these occasions.

>>5160524

>>5160031 (pb)

>>5160194 (pb)

Here's the filing type to uri-slug map. Only "P" appears to be a special case.

I completed it by randomly sampling 3-4 records of each filingType and comparing to the link clerk.house.gov provided.

filingTypeMap = {

"A": "financial-pdfs",

"B": "financial-pdfs",

"C": "financial-pdfs",

"D": "financial-pdfs",

"E": "financial-pdfs",

"G": "financial-pdfs",

"H": "financial-pdfs",

"N": "financial-pdfs",

"O": "financial-pdfs",

"P": "ptr-pdfs"

"R": "financial-pdfs",

"T": "financial-pdfs",

"W": "financial-pdfs",

"X": "financial-pdfs",

}

We should still sweep through and dispatch HEADs against the batch to see what 200s, 404s, etc.

Another thing to consider would be making the FilingType in the JSON an object, containing a Label and Value pair.

You know, something for vanity; cuz I couldn't really tell you what type of form an 'X' is, etc. Thoughts?

>>5160524

some moar bits for you, fren.

Briefly segway'd to the next section of the clerk.house.gov, Foreign Travel Reports.

If it's deemed worthy to pull these records at a later point, these might yield some shortcuts for data extraction.

http://clerk.house.gov/public_disc/foreign/index.aspx

> Electronic Files of Foreign Travel Reports

> Reports from 1994 through the current quarter are printed in the Congressional Record.

https://www.congress.gov/congressional-record/congressional-record-index/

> Please note that some entries may be incomplete. We are currently working to address this issue.

> In the meantime, please visit govinfo, a service of the U.S. Government Publishing Office, to access the Congressional Record Index in its entirety.

https://www.govinfo.gov/app/collection/cri - need to look at it some moar, going to table-top for now.