Mila Frerichs milafrerichs

The Problem:

If you follow the open data scene, you'll often hear about how the "feedback loop" for making corrections, comments, or asking questions about datasets is either fuzzy, disjointed, or nonexistent. If I know for a fact that something in a government dataset is wrong, how do I get that record fixed? Do I call 311? Will the operator even know what I am talking about if I say I want to make a correction to a single record in a public dataset? There's DAT. There's storing your data as a CSV in github. These approaches work, but are very much developer-centric. (pull requests and diffs are hard to wrap your head around if you spend your day analyzing data in excel or desktop GIS. The fact of the matter is that most of the people managing datasets in government organizations are not DBAs, data scientists, or programmers.

Idea:

It's basically git for data plus a simple UI for exploration, management, and editing. Users would have to use Github SSO to edit in the UI, and behind the scenes

This is a more wordy, narrative accompaniment to my pretty bare presentation about d3 that I gave to the jQuery DC Meetup.

What is d3?

Not a chart library (though you can make charts with it)
Not a map library (though you can make maps with it)

Which is to say, d3 can be used for building things, but the 'atomic parts' are lower-level than bar graphs or projections or so on. This is a powerful fact. It also means that d3 is a good basis for simple interfaces, like Vega.js, that make its power accessible in other ways.

Not a compatibility layer (it doesn't work with bad browsers)

Communicate between objects using channels

When you have two objects A and B, say two view controllers, that you want to have talk to each other, you can choose from the following options:

NSNotificationCenter. This is anonymous one-to-many communication. Object A posts a notification to the NSNotificationCenter, which then distributes it to any other objects listening for that notification, including Object B. A and B do not have to know anything about each other, so this is a very loose coupling. Maybe a little too loose...
KVO (Key-Value Observing). One object observes the properties of another. This is a very tight coupling, because Object B is now peeking directly into Object A. The advantage of KVO is that Object A doesn't have to be aware of this at all, and therefore does not need to send out any notifications -- the KVO mechanism takes care of this behind the scenes.
Direct pointers. Object A has a pointer to Object B and directly sends it messages when something of interest h

	{
	"name": "phl-property-tax-balances",
	"keywords": ["tax", "property", "delinquent", "deadbeat"],
	"license": "CC0",
	"sources": [{
	"name": "City of Philadelphia",
	"web": "http://opendataphilly.org",
	"email": "data@opendataphilly.org"
	}],
	"resources": [{

	# config/routes.rb
	resources :documents do
	scope module: 'documents' do
	resources :versions do
	post :restore, on: :member
	end

	resource :lock
	end
	end

	# require spec_helper

	Test =
	fn: -> 'result'

	it 'auto-resets sinon fakes', ->
	@stub(Test, 'fn')
	Test.fn()
	Test.fn.should.have.been.called

	// Lefalet shortcuts for common tile providers - is it worth adding such 1.5kb to Leaflet core?

	L.TileLayer.Common = L.TileLayer.extend({
	initialize: function (options) {
	L.TileLayer.prototype.initialize.call(this, this.url, options);
	}
	});

	(function () {

	var self = Ti.UI.createWindow(args);

	// Grab instance of class.
	var egc = new (require('egc'))(self);

	// Add events through the wrapper.
	egc.addEvent('someEvent', function (){});
	egc.addEvent('anotherEvent', function (){});
	egc.addEvent('tresEvent', function (args){});

	# Shoulda activemodel cheatsheet

	# DB
	should have_db_column(:title).of_type(:string).with_options(default: 'Untitled', null: false)
	should have_db_index(:email).unique(:true)

	# Associations
	should belong_to :company
	should have_one(:profile).dependent(:destroy)
	should have_many(:posts).dependent(:nullify)

	/*
	Load Sinon.JS in the SpecRunner:

	<script type="text/javascript" src="lib/jasmine-1.0.1/jasmine.js"></script>
	<script type="text/javascript" src="lib/jasmine-1.0.1/jasmine-html.js"></script>
	<script type="text/javascript" src="sinon-1.0.0.js"></script>
	<script type="text/javascript" src="sinon-ie-1.0.0.js"></script>

	http://cjohansen.no/sinon/
	*/