-
Notifications
You must be signed in to change notification settings - Fork 1
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
Whats the plan for these ETL scripts? #2
Comments
@ondrae these integrations (repo and deployment) should live with the Brigade imo. I'm hesitant to encourage folks to merge endpoints into a central place, because a big benefit of Citygram's architecture is that the adapters can be written in any language. |
(following up on this) I was thinking about adding some more SF datasets for CodeAcross this weekend and thought it would be nice to see if we could turn on Citygram SF. |
ping @bigfleet |
... and he shall appear! I am the operator of citygram.org and went through this process when I brought Charlotte live. Can you select icons from this collection? https://github.com/codeforamerica/citygram/tree/master/app/assets/img/publishers/icons Operationally, I need a collection of stanzas like this:
Also, I'd love to be able to add the ability to request a dataset be made live to codeforamerica/citygram, but that's probably not in scope for tomorrow's Code Across. We could collaborate on getting SF turned on, though. |
@bigfleet - super helpful information, thanks :) What's the best way to submit those stanzas? Open an issue for each one on the Citygram repo? And if so, would that be the CfA/citygram repo, the citygram/citygram-services repo, or somewhere else? Thanks so much! |
Generalizing this discussion: The process for getting new data onto Citygram.org. |
Hey @invisiblefunnel
We've started a few transform scripts for Citygram SF. What was the plan for these? Do we eventually merge these scripts into https://github.com/codeforamerica/citygram or do we point you to our endpoints somewhere?
You may have explained this before, yet it would be nice to have it explained in the README so people not at hacknight know whats up.
@seanius @mertonium
The text was updated successfully, but these errors were encountered: