You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of the committees are subcommittees of others. For instance, the Common Council has subcommittees: Rules Committee, Land Use Committee, Funding Committee, etc.
We want to be able to tie these subcommittees to their parent committee.
We should probably have a parent_id foreign key in the committee table. I'm not sure how we want to display the list of committees, once it's a tree.
The text was updated successfully, but these errors were encountered:
I'm not objecting to a c tree structure if its really needed. But this seems more complex than necessary to solve a simple issue. Why not have separate Council , Rules, John Hopkins, etc committees. Then create a rollup calendar -- City Council (All) -- that includes all of these. I don't think we need to create a parent/child structure unless it's really needed. Seems like we can solve whatever problem we currently have with our existing system.
Many of the committees are subcommittees of others. For instance, the Common Council has subcommittees: Rules Committee, Land Use Committee, Funding Committee, etc.
We want to be able to tie these subcommittees to their parent committee.
We should probably have a parent_id foreign key in the committee table. I'm not sure how we want to display the list of committees, once it's a tree.
The text was updated successfully, but these errors were encountered: