IQSS / IQSS/dataverse-frontend
Dataverse collection thumbnail in addition to Logo Image as banner (SPA)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
Allow dataverse collection admins to add a distinct thumbnail image in conjunction to a Logo Image in rectangle format to display as a banner for their collection.
Note : this issue is the same for SPA that this issue for JSF
The screenshots/mock up are with the current UI logic and visuals, but are not strict specifications and could be adapted to a redesigned UI.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse collection admins
What inspired the request?
Rectangle logos may result in very ugly featured collection thumbnails.
Any brand new behavior do you want to add to Dataverse?
Have two distinct images for the featured collection thumbnail :
And the logo, that can be used as a banner :
Suggested implementation in the Theme and Widget page (the depositing field would not appear if the logo is used as thumbnail) :
Any open or closed issues related to this feature request?
Prerequisite:
Same issue implemented in JSF anc corresponding PR:
On the logo deposit part :
- #268 (cf. next line)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing prerequisite issue #10194 and the JSF counterpart #10291 with pull request #10433, then inspect the SPA Theme and Widget page. Confirm how collection logos are currently handled and define separate thumbnail and banner behavior. Done means collection admins can provide distinct images and the featured thumbnail and banner display correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100