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
Each billnumber (e.g. 116hr133) may have more than one version. For calculating bill similarity, we are currently processing all of the bill versions, but only storing bill_similarity for one of them (arbitrarily).
Instead, for each bill, we should calculate bill_similarity for the version which has the most recent date. To do this, we can search Elasticsearch for the billnumber. That should retrieve all versions. Then we look in each version to find the date, which will be a string in the form: 2019-01-03. (I just added this to elastic_load.py, so it would require re-running the bills.
This information is also in the fdsys_billstatus.xml file for the bill, in the text_versions element (see below). However, getting the data from the elasticsearch index ensures that we have the version in the index to begin with.
Each billnumber (e.g.
116hr133
) may have more than one version. For calculating bill similarity, we are currently processing all of the bill versions, but only storingbill_similarity
for one of them (arbitrarily).Instead, for each bill, we should calculate bill_similarity for the version which has the most recent date. To do this, we can search Elasticsearch for the billnumber. That should retrieve all versions. Then we look in each version to find the
date
, which will be a string in the form:2019-01-03
. (I just added this toelastic_load.py
, so it would require re-running the bills.This information is also in the
fdsys_billstatus.xml
file for the bill, in thetext_versions
element (see below). However, getting the data from the elasticsearch index ensures that we have the version in the index to begin with.The text was updated successfully, but these errors were encountered: