added meeting data

[Mearnest]

Aggregated rest of the meetings. Added two fields for building info and website url. Changed meeting_type model to add new fields.

After merch and pull, you will have to run:

mix ecto.drop
mix ecto.create
mix ecto.migrate
mix run priv/repo/seeds.exs

Tried to have seeds do the dropping for you, but something with the foreign keys and id auto incrementing caused a problem with the joining the meeting tables (lot less than should be).

Oh, forgot to prettify the JSON again.

[sethetter]

What's the building field for? And is it common enough in meetings that it constitutes having a field in the main schema? Or could this be something covered with meeting_extra?

[Mearnest]

The building information was part of location, but sometimes that doesn't work in google maps, so I took it off and put it in it's own field. Most of the locations have building information, that's why it's not in extras.

[Mearnest]

Alright, I'll move building and website information over to extras so that the MeetingType model doesn't need to change. We can get rid of this branch. I'll rebranch with prettified json for the next pull request.

[sethetter]

Any way you could run this through a json formatter? Mostly for #10.

You can do python -m json.tool priv/data/meeting_extras.json I believe. That's what I used previously.

[Mearnest]

Yes, I can do that, after we decide on how to proceed here.

[aaronarduino]

I don't have enough experience with the framework to give feedback on the code, yet. But generally speaking, I concur with Seth's comments.

[Mearnest]

There is a question of how much information we really need to show on the website. I was thinking we could link from a meeting list to a full details of the meeting, so they could see a link to the website or meeting agenda, view the description, see the building information (name, floor, room #), and then anything additional.

Or maybe we don't need to link to that stuff. Just enough information to generate an ical event.

[Mearnest]

Regarding the data model:

Necessary fields:
Title, date (year, month, day, hour, minute), and location (street address, wichita, zip)

ical conversion:
Duration: required, defaults to 60 minutes
Email: helpful to have means of contact on email calendars
Url: to meeting agenda or list of agendas

Additional:
type: machine name, made sense in Python for filtering
subtype: some meetings have several types, and the title doesn't reflect this
Description: if we want to show them an explanation of the meeting. This applies to all meetings.
Building: a lot of meetings list building name, floor and sometimes room
Website: can be lots of other information on meeting websites. All meetings have some website.

Then there's potential extra fields we can display, such as lunch cost or link to plat drawings. If this is useful. This is meeting specific.