Today a network can only be associated with a single 'type', which is captured as an array of 'parents' today. Here's an example of a network entry in the database:
The 'community_profiles' section is used because the same network name may exist in multiple cities and can have different profile properties in each city.
The nav.edit_network.html page would need to be modified to allow for selecting multiple parents, and the controller would need to support it as well.
Then, in the new 'Networks' page, if a network is associated with multiple parents (ie. 'Accelerators' and 'Coworking Spaces') then it should be displayed multiple times, once per category.
[x] Update Networks page to list networks in multiple categories if applicable
[x] Be sure networks are not duplicated in the left-have navigation list
Today a network can only be associated with a single 'type', which is captured as an array of 'parents' today. Here's an example of a network entry in the database:
The 'community_profiles' section is used because the same network name may exist in multiple cities and can have different profile properties in each city.
The nav.edit_network.html page would need to be modified to allow for selecting multiple parents, and the controller would need to support it as well.
Then, in the new 'Networks' page, if a network is associated with multiple parents (ie. 'Accelerators' and 'Coworking Spaces') then it should be displayed multiple times, once per category.