ropengov / finpar Goto Github PK

Quick question – I'm looking at these pages (MP biographies on the Finnish Parliament website), and I can't find a way to impute gender from the information provided.

I wrote some rough imputation code, based on first names and photos, but some first names might fit both males and females.

Needless to say, I don't speak Suomi. Is there an easy way to impute gender from first names? Did someone bother to do this for MPs from recent parliamentary sessions (35-36)?

I'm asking in relation to this repo, which builds legislative cosponsorship networks from the last two sessions of the Finnish Parliament.

Thanks in advance for any pointers!

Thus get rid of R.cache

Check http://www.popoloproject.com/ for data format definitions if we start do define generic classes for parliamentary data

Change travis to use the newly established "language r" mode which is already tested in sorvi at least.

I suggest keeping root folder README minimal, and moving all R code etc. in the vignette. Following the conventions used in the other rOpenGov packages so far (like this: https://github.com/rOpenGov/sorvi). Not critical and can be skipped but if agreed I can do this.

Dear @jlehtoma,

If I remember correctly, you had a few questions about the kind of data I was collecting on the French Parliament.

I have considerably updated my code and have now collected cosponsor names and details for amendments and bills in both chambers.

Here are some slides.

Please let me know if the same kind of data exist for the Finnish parliament, as some measures are comparable across legislatures :)

Kansan Muisti will release version 2.0 of the database on March 17. I wonder if this would imply changes to the R interface. To be checked.

All endpoints have an item limit of 20 items by default. Each endpoint has a specific total item count that is usually more than 20 items. The total count is included in the response meta section, e.g. for /api/v1/member/ meta gives a total count of 432.

meta: {
    limit: 20,
    next: "/api/v1/member/?limit=20&offset=20",
    offset: 0,
    previous: null,
    total_count: 432
}

Now function wrapping the endpoints use hard coded limit parameters, get the limit directly from meta.