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

Feature Request/Idea: Increase maximum resolution of dataset thumbnail images #9418

Open
jakobmolandergeus opened this issue Mar 2, 2023 · 4 comments
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: DOI & Handle Feature: Search/Browse Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@jakobmolandergeus
Copy link

Overview of the Feature Request

Increase the maximum resolution, but not necessarily the display area, of uploaded dataset thumbnail images.

With modern day bandwith and high resolution screens, a resolution of 48 x 48 seems to restrictive. A resolution of 96 x 96, 128 x 128 or even 256 x 256 would be preferable.

Another possibility is to add the option to store two versions of the thumbnail image:

  1. One in 48 x 48 to be used in the list view
  2. One in a higher resolution only to be used in the detail view.

What kind of user is the feature intended for?

All users

What inspired the request?

The finer details of our thumbnail images are not discernible in the extremely low resolution. A small increase in resolution could make them more usable without harming the responsiveness too much.

@pdurbin
Copy link
Member

pdurbin commented Mar 2, 2023

@jakobmolandergeus absolutely. "Make thumbnails larger" is part of this issue:

Fun fact: the API for creating thumbnails already accepts an arbitrary "width" parameter. So this is really about changing the frontend to call it with a larger size.

You may or may not be aware that we are embarking on a significant rewrite of the UI: https://dataverse.org/blog/restructuring-dataverse-ui-single-page-application

For that reason, it would probably make sense to put effort into the new UI (React) rather than the old one (JSF).

@jakobmolandergeus
Copy link
Author

@pdurbin thank you for letting me know. It is good to hear, that it is something you are aware of.

Is there a timeline for the new UI (React)?

@pdurbin
Copy link
Member

pdurbin commented Mar 2, 2023

Not really. We're just getting started! 😅

@pdurbin
Copy link
Member

pdurbin commented Oct 9, 2023

@jakobmolandergeus there's a video you can watch: https://github.com/IQSS/dataverse-frontend#demo-videos

(And we're working on another one soon).

@pdurbin pdurbin added Feature: Search/Browse Type: Suggestion an idea Feature: DOI & Handle User Role: Guest Anyone using the system, even without an account Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF labels Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: DOI & Handle Feature: Search/Browse Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF
Projects
None yet
Development

No branches or pull requests

2 participants