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: Custom home pages for subcollections #10252

Open
sergejzr opened this issue Jan 23, 2024 · 4 comments
Open

Feature Request/Idea: Custom home pages for subcollections #10252

sergejzr opened this issue Jan 23, 2024 · 4 comments
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Type: Feature a feature request UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@sergejzr
Copy link

Dear Dataverse developers.
Dataverse has a possibility to define a custom_homepage as branding for the whole Dataverse installation. This is also what we did for our bonndata. It shows features like overall statistics, recent and popular datasets, etc.
Overview of the Feature Request
Now, the admins of our subcollections would like to obtain similar landing pages for their collections. To do this, at the moment, we would need to generate a header and a footer for these collections as well.
More naturally would be to be able to add a custom branding for a subcollection in the similar way as the main landing page is added.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Superusers of the Subdataverse

What inspired the request?
User requests

What existing behavior do you want changed?
Same as with http://localhost:8080/api/admin/settings/:HomePageCustomizationFile
but for a specified collection

Any open or closed issues related to this feature request?
I may have overlooked something, but I did a research and could not find similar requests

@sergejzr sergejzr added the Type: Feature a feature request label Jan 23, 2024
@pdurbin pdurbin changed the title Feature Request/Idea: Landing pages for subcollections Feature Request/Idea: Custom home pages for subcollections Jan 26, 2024
@yjyale
Copy link

yjyale commented Apr 5, 2024

This feature will be very useful. Looking forward to having this feature available soon!

@pdurbin pdurbin added 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 Apr 9, 2024
@pdurbin
Copy link
Member

pdurbin commented Apr 9, 2024

I noticed the discussion at https://groups.google.com/g/dataverse-community/c/8bh76NnF_m8/m/xwP2dbVGAAAJ

Yes, this would be a nice feature but we are in the process of rewriting the UI of Dataverse in React and are trying to touch the old frontend code (in this repo) as little a possible. Please feel free to open an issue at https://github.com/IQSS/dataverse-frontend

@yjyale
Copy link

yjyale commented Apr 10, 2024 via email

@pdurbin
Copy link
Member

pdurbin commented Apr 10, 2024

@yjyale yes, the new UI will someday replace the old UI. It will be a long process but you can watch these videos to see the progress: https://github.com/IQSS/dataverse-frontend#demo-videos

The new UI will not allow customized branding for the differences among main header and sub-collections' headers. However, you are welcome to create an issue in that repo.

Basically, the strategy with developing the new UI is to replicate what is in the old UI. So because the feature you want isn't in the old UI, it will not be implemented in the new UI unless there's an issue that is prioritized.

I hope this helps!

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. Type: Feature a feature request 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

3 participants