Open alonisser opened 7 years ago
I edited the description to fix the RTL
not sure I understood the problem, could you write some specific example of a problem which will be fixed by this?
No protocol part in Oknesset has speaker_id field populated.. Code isn't handling this. not sure for how long but for quite a while :( None what so ever, at least for committees didn't check for plenum. So this (important) data can't be used in queries and analysis
Example: for previous end of moshav mary wanted to release talking statistics by coalition/opposition for vaadat haksafim
@OriHoch does knesset-data-django has person class or should I pass the available persons from the calling methods
@alonisser knesset-data-django has dependency on Open Knesset so you can use all Open Knesset code from knesset-data-django and vice-versa
however, we strive to drop the dependency of knesset-data-django on open knesset at some point.. so I would like to keep this to a minimum
having said that - feel free to write the code in Open Knesset if it's easier for you at the moment
I'll have a look at this problem because I remember it was working correctly
ok, looks like it's a very old bug (would be interesting to see if it ever worked)
yes, it will be a very good enhancement - to be able to have ID of persons linked to each protocol part
regarding repository - I guess the right place to do it will be knesset-data-django as all relevant logic is already there
This is makes it hard to do data analysis on this data Further explanation of the issue and the solution (from an email correspondence between me and @maryLoi )
Perhaps should be opened in knesset-data/django/python since part of the api moved there