organize resources into "Groups" about geohealthcheck

[hannesaddec]

+1 to the proposal - I suggest to add a further subset for machines under a group. My use case would be to have a group NASA with 3 machines with 200 services each.

[archaeogeek]

+1 to the general idea of groups, though I'd start from a more simple idea, which is to allow grouping of resources for display purposes. This would require a method for defining groups, and then an additional dropdown box to choose the group when adding a new resource.

[justb4]

+1 for grouping. One use-case would be linking WWW:LINK Resources to a parent OGC:service endpoint/Resource. See comment in issue: #19 (comment)

[justb4]

@samperd my suggestion is to implement grouping via tagging, at least for Resources. This would be simpler, also given the limited developer-resources we have at the moment and existing components for e.g. tag-clouds. See my comment in #75. The freedom with tagging is that organizations can define naming conventions/patterns via tags. I see grouping for Access Control as a different issue.