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

Allow users more control over the resource item buttons #461

Open
jrdh opened this issue Feb 26, 2020 · 1 comment
Open

Allow users more control over the resource item buttons #461

jrdh opened this issue Feb 26, 2020 · 1 comment
Assignees

Comments

@jrdh
Copy link
Member

jrdh commented Feb 26, 2020

Overview
On the dataset/package page a list of resources is shown. Besides each resource, we present a "View" button and another button which is controlled by the logic in this snippet. Most of the time this button will either say "Download" or "Go to resource". For resources that are simply just links and have no real need for the resource view to be navigated to (i.e. what happens when you click the "View" button) it may make sense to alter the logic and only show the "Go to resource" button.

Possible Solutions
There are a few ways we could do this:

  • give the dataset owner the ability to specify in each resource's settings whether to show a "View" button or not.
  • attempt to automatically determine whether to show the "View" button based on the resource. Initial thoughts would be that if the resource is a URL resource with no defined views it can probably have the "View" button removed in this list. We may wish to also predicate on whether the resource has a description or format too?

Anything Else?
This came off the back of how this dataset currently works: https://data.nhm.ac.uk/dataset/the-art-of-3d-insects.
The resource items look like this:
image
The "Go to resource" button is the useful one as it takes you to the URL of the resource whereas the "View" button just takes you to an empty resource view page:
image

@jrdh
Copy link
Member Author

jrdh commented Sep 16, 2024

Comment from recent meeting between @alycejenni and I - perhaps this should be implemented in the vds?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked
Development

No branches or pull requests

2 participants