Add data dictionary and draft models

[jwalgran]

No description provided.

[maurizi]

Why does every model have created_at and updated_at? Do we want to pull those fields out into a separate abstract Model?

[steventlamb]

I prefer created and updated.

[jwalgran]

Django maintains will maintain these dates for us, so I thought we might as well add them. @steventlamb If created and updated are more idiomatic, I agree we should change them (_at is the Rails convention)

[jwalgran]

Sorry I trashed some of our conversation with a rebase.

Rick had asked about is_available on the Blockfaces table. There is a requirement that Parks be able to open a blockface for mapping, even if it has been previously surveyed. We could say "if all the Surveys for a Blockface have is_flagged set to True (which means that we do not fully trust them) then allow the Blockface to be mapped." This is more normalized, but complicates the tiler query. I am not sure which way we should go.

[jwalgran]

@RickMohr Parks and TreeKit have not defined the final list of metadata we will be collecting for each tree. I took the fields that are included from the CartoDB table that TreeKit has used in the past, so they are a reasonably good starting point.

[jwalgran]

@RickMohr The spec indicates that attendance at an event counts as "training completed"

[RickMohr]

I prefer created_at and updated_at. created and updated sound like Booleans.

[kdeloach]

Consider using date fields in place of boolean fields. They provide way more data/context and may come in handy later.

[jwalgran]

I like _at too.

[RickMohr]

@kdeloach, they are date fields.

[jwalgran]

@RickMohr Territory (the new name for Turf) is more or less permanent. It represents the collection of blockfaces assigned to a Group. We do not need to worry about expiration and cancelation.

[steventlamb]

I could have sworn that created and updated were more idiomatic, but I can't find evidence. In fact, I found some cases of created_at as well as created. Github search kinda sucks for this type of thing. They can't seem to find "created = ", and give me all instances of %created%

[kdeloach]

I meant other Boolean fields is_flagged, is_banned, etc.

[jwalgran]

@kdeloach The plan, right now, is to bing over Auditable from OpenTreeMap so that the "who" and "when" of flagging and banning is captured, if we care to dig it up, while using a real boolean for the property