Joshua Tauberer

Go for it. :)

Could you list some bills that cause the errors you're fixing?

Thanks that's helpful. GitHub indicates that there are conflicts now. Could you try resolving that? Happy to merge after.

I wonder if this is fixed by @LindsayYoung's meetings parser update?

This was about the bill status (not text) and roll call vote XML files that would be named data.xml. But this was four years ago and I still haven't gotten...

Could you make these corrections in a pull request? (We'd need to figure out what to do with the ones that have two IDs.)

We could make the icpsr field either a number or, for those MoCs that have multiple, a list of numbers, and not worry about when the different ICPSR IDs were...

I am conservative about data format changes and prefer small diffs, but sure we could do that too. It'll just produce a big diff when all of the existing values...

It'll make the YAML encoding less consistent (potentially more error prone for manual editing) because it'll require that the values be quoted but strings that don't look like numbers don't...

When round-tripping the quotes will come out according to the rules in `rtyaml` (which already improves on the `libyaml` defaults).