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

Full CRUD on all items #5

Open
noahkoch opened this issue Nov 26, 2013 · 2 comments
Open

Full CRUD on all items #5

noahkoch opened this issue Nov 26, 2013 · 2 comments

Comments

@noahkoch
Copy link
Contributor

I'm assuming we could leave out states and counties from that list. Cities we could also probably seed the DB with.

@trakaus
Copy link

trakaus commented Nov 26, 2013

So we would need methods for the following:

  1. Cities
  2. Boards
  3. Board Members
  4. Board Seats
  5. Members
  6. Admin Members
  7. Agendas - (depends on the integration with http://agendas.dataomaha.com - @mitch-b)
  8. Meeting Minutes

@mitch-b
Copy link
Member

mitch-b commented Nov 26, 2013

Yeah, we'll need to investigate more into what they've already done surrounding agendas. I just think it'd be great if we could tap into that versus redoing all the work they've already done. Then, we can use a third party API for agendas, and leave it out of ours. Of course we'd want to validate if we truly want it to live outside of our system or internally, since we are trying to offer a full-service solution.

Additionally, "Admin Members" could just turn into member Roles. Meeting minutes - would that be included under the Board level? Maybe we also talk about adding in document uploads. Also, how are counties/cities "registered" to start working? "Upcoming Openings" might also be bundled outside of the board schema into its own table. That way we can keep historical information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants