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

Support modification of owners/editors of a resource #92

Open
zhiyuli opened this issue Oct 31, 2018 · 8 comments
Open

Support modification of owners/editors of a resource #92

zhiyuli opened this issue Oct 31, 2018 · 8 comments
Assignees

Comments

@zhiyuli
Copy link
Member

zhiyuli commented Oct 31, 2018

Support modification of owners/editors of a resource

@zhiyuli
Copy link
Member Author

zhiyuli commented Nov 9, 2018

adding this:
manage resource access control over a Group

@ghost ghost assigned zhiyuli and ghost Feb 13, 2019
@ghost
Copy link

ghost commented Feb 13, 2019

@zhiyuli is this a showstopper or a nice-to-have? Can you provide more detail on the need and its impact to CZO work? Can they just edit in the database?

@zhiyuli
Copy link
Member Author

zhiyuli commented Feb 13, 2019

@cuahsimarko @martinseul @Lizabrazil
I think the priority of this ticket depends on what Alva's group of group can do.
Currently, in CZO project we create each resources using a specific "czo_XXXX" account, but all resources should be owned by "czo_national" account as well.
So 2 options here:

  1. do it in migration script by using the new rest api and hs_restclient requested in this ticket
  2. do it on UI using Alva's groups of group feature

@ghost
Copy link

ghost commented Feb 13, 2019

In that case, I'd lean toward the script performing the action by whatever means necessary or as part of manual remediation. Let's make that our task.

@ghost
Copy link

ghost commented Feb 13, 2019

@zhiyuli If you accept this, can you close this Issue with label "wontfix"?

@zhiyuli
Copy link
Member Author

zhiyuli commented Feb 13, 2019

@cuahsimarko
a second thought --- the "authoring tool" which we will be talking about in next 1 or 2 week would need to use HS rest api (probably hs_restclient as well if clowder team uses python) for everything such as create, edit and manage access over a hs resource.

So rest api mentioned here is needed sooner or later anyway...

@ghost
Copy link

ghost commented Feb 13, 2019

Understood. So this GH Issue #92, we're asking Martin to assign to Alva? Side note, I think Scott may have some role in ownership/oversight in this repo, unless I'm mistaken.

@ghost
Copy link

ghost commented Feb 13, 2019

Or maybe you're asking a new ticket be created in hydroshare/hydroshare for Alva & Co to work, and this #92 gets asked of Scott to work?

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

No branches or pull requests

1 participant