Closed alonisser closed 7 years ago
after PR #830 is merged - I assume it will only be fixed for future data
do we need to run anything to re-scrape / re-calculate old data?
It would update automatically for 2017, after deploy I need to do something manually on the server to update the periods before
@alonisser what's the status? should I assign for someone else to complete this for the hackathon (which is starting today..)
related but not contradicting issue: hasadna/knesset-data-python#15
@OriHoch as I said it needs to be deployed and then I can run the fix.. was it deployed? the issue was not updated with a deploy
@OriHoch Also not merged. .. so why the status question? After merge and deploy 2017 would be fixed automatically and I need to do something manual (completely manual.. ) to update 2016-2015
I was waiting for you to merge and deploy it.. but I guess we had a misunderstanding.. no problem, I'll merge
deployed, please test
WIll do. later today
Confirmed working, now running 2015-2016 also (And clean web python cache to see results. would happen soon)
Finished and fixed. Sorry for the misunderstanding about deploy/merge
cool, thanks!
Presence parsing (mishkan) was using a redundant and deprecated check if presence should be calculated to a period to mk. this check (mk end_date) is wrong since only "is_current" mks are being processed for presence. and "end_date" for mk is deprecated. (mks can return to knesset after "ending" a previous tenure)