-
Notifications
You must be signed in to change notification settings - Fork 433
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
Visual differentiation needed for Access Status #2402
Comments
@paulo-graca I like the idea...but talking about color design always seems to me like a pandora's box! :) There are 4 status to cover: OA, Embargo, Restricted and Metadata only. Maybe it would be possible by following a simple color code (green for OA, red for restricted, etc.), like this: My concern is that on a result page, it can look like fireworks: |
Please bear in mind that the four states are simply names for combinations of starting and ending dates for ResourcePolicy instances. Other combinations are possible. Here we have two types of embargo: limited (maximum of two years) and unlimited (can be embargoed "forever"). Collections use one or the other as required. |
Not against this idea, but priority is uncertain. It might be possible to simply make it easier for sites to color each status button differently via CSS...instead of defaulting to a specific color scheme (which can be a "pandora's box" as @pilasou notes) For now, moving this to backlog as priority is unclear to me. |
Concluding, to avoid fireworks It would be better to add specific stylesheet classes, perhaps based on the access status itself, like: <span class="badge badge-secondary access-status-value open-access">Open Access</span> then, anyone can custom it as it pleases. |
@pilasou @mwoodiupui @tdonohue I've just created this tiny PR to address this: |
Describe the bug
Currently, when displaying different access status like open access, restricted access, ... there is no visual differentiation.
all look the same.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I hoped to have a visual differentiation for different access status. Could be something based on a different color, a specific style class. Of course I can theme that component and do that on my side, but I think it makes more sense to have it like that for all implementations.
The text was updated successfully, but these errors were encountered: