Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data for Quebec #26

Closed
AGarrow opened this issue May 29, 2013 · 11 comments
Closed

Data for Quebec #26

AGarrow opened this issue May 29, 2013 · 11 comments
Labels
Data Data sources and ingestion automation

Comments

@AGarrow
Copy link

AGarrow commented May 29, 2013

I have a scraper for Quebec's public bodies (my boss authored it, and wants to contribute). It's written in ruby, and can be seen here. How do we go about integrating this?https://gist.github.com/jpmckinney/5022490

@rufuspollock
Copy link
Member

Can you get a CSV output? Headings should be as per https://github.com/okfn/publicbodies/blob/master/data/eu.csv

If the headings don't fit well with your data please holler as we are iterating on the exact common column set atm.

@AGarrow
Copy link
Author

AGarrow commented May 29, 2013

my current headers are:
organization, name, role, address, voice, fax, tollfree, email, type

I'm working on adapting them to your standards now

@AGarrow
Copy link
Author

AGarrow commented May 29, 2013

@AGarrow AGarrow closed this as completed May 29, 2013
@AGarrow AGarrow reopened this May 29, 2013
@jpmckinney
Copy link

FYI, I'll be taking over this issue. We have public bodies for Canada and all its provinces now.

@rufuspollock
Copy link
Member

@jpmckinney #29 is now done and we have a new standard schema. Would be great to get this in!

@jpmckinney
Copy link

Since my last update, I've noticed that Canadian governments often publish two organizational lists: one for FOI and another for the real government hierarchy. Which is of more interest to this project? Would an FOI list suffice if the full hierarchy is not published?

@rufuspollock
Copy link
Member

Real hierarchy would probably be preferable I guess but we could always start with FoI ...

@jpmckinney
Copy link

Sounds good. I'm going to close this issue for now and open pull requests once the data's ready.

@jpmckinney
Copy link

Actually, I can't close it, but that's my intention :)

@rufuspollock
Copy link
Member

@jpmckinney you're now on the team for this repo and should be able to close issues :-) Please go ahead and close :-)

@jpmckinney
Copy link

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Data sources and ingestion automation
Projects
None yet
Development

No branches or pull requests

3 participants