-
Notifications
You must be signed in to change notification settings - Fork 12
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
Display access permissions for models on model detailed view #192
Comments
Why do you need write permission to run a test on a model? |
To be more accurate... running the test does not require write, but to register the new results (POST) we require write permission. |
Why? |
If the model is See table here: http://hbp-validation-client.readthedocs.io/en/master/#general-info |
This is as per the current implementation. Found an example of this last week. |
No permissions should be required to post test results (the user just needs an HBP account). If there are related data, then the user should specify a collab for which he/she has permission to write to the storage. Even if writing to storage fails, however, the result should still be registered. |
On the topic of the issue, I agree it would be useful to display a small box that explains the permissions. |
This continues to be a problem... should we take this up on priority? |
Partly related to #191
As a user cannot edit/update all the models that they see in the model catalog, it would be useful to have icons (maybe inside a "Permissions" box?) that indicate whether a user has only READ permissions for that specific model, or both READ and WRITE.
Often it is not easy to identify why you don't see the "EDIT" options for some of the models. Also, you cannot run a test on any model that you see in the model catalog. You need to have WRITE permissions for these models.
For APIs,
READ = GET
WRITE = PUT/POST
@apdavison : Go ahead with this?
The text was updated successfully, but these errors were encountered: