Open Palollo opened 7 months ago
This is how ACL page looks like now:
It doesn't look much like the proposal :( Appearance as a form is important for readability!
[Title] Who can see the dataset (the metadata): [Content/response] As a public dataset it is visible to anyone (even unregistered users)
--> Note "unregistered users" is the term used in the rest of application, is more clear than "users without an account".
[Title] Who can use the dataset (access to the contents): [Content/response] Registered users that either have joined the project or added to the ACL.
[Title] Access control list (ACL): [Content] ...
That way is more clear, direct and easy to read ;)
@Palollo Your proposal uses too much space for a static message. It matters when something changes a lot like access date or something
This is how ACL page looks like now: It doesn't look much like the proposal :( Appearance as a form is important for readability!
To make the application more intuitive and avoid the user to go to documentation to undersand who can access to his/her dataset, we can take advantage of the new ACL page to show that info. The proposal is just to include some text above the current ACL list. The text is different depending on the state of the dataset: