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

organize resources into "Groups" #18

Open
samperd opened this issue Mar 5, 2015 · 4 comments
Open

organize resources into "Groups" #18

samperd opened this issue Mar 5, 2015 · 4 comments

Comments

@samperd
Copy link

samperd commented Mar 5, 2015

User Story

As a user, owner,admin
I want to create separate group to collect all of my web resources
So I am not distracted by resources I am not concerned about.

Discussion

This feature would allow a single instance of GeoHealthCheck to server multiple stakeholders in a organized fashion within a large organization (such as a government with multiple departments). Adds some enterprise'ness' to it all

proposal

Provide a hierarchy such as

  • Group (eg. an organization or a user)
    • Service Type (CSW, FTP)
      • Resource (individual web resources)

Access Control

  • allow a user to "admin" a group by adding more group admins or users
  • registered users can request to JOIN a group
  • visibility of a group may be configurable for viability to everyone, logged in users, group user etc
  • allow Groups within groups? eg
    • Government of Canada (parent group)
      • Environment Canada (sub group)
        • Service Type
          • Web Resource
      • Natural Resources Canada (sub group)
        • Service Type
          • Web Resource
@hannesaddec
Copy link
Collaborator

+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
Copy link
Contributor

+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
Copy link
Member

justb4 commented Sep 22, 2016

+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
Copy link
Member

justb4 commented Feb 8, 2017

@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.

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

4 participants