-
Notifications
You must be signed in to change notification settings - Fork 494
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: Set featured collections through Native API #10242
Comments
@Asbjoedt good idea. For anyone who's unfamiliar with this GUI-only feature, it's described here: https://guides.dataverse.org/en/6.1/user/dataverse-management.html#featured-dataverse-collection |
Hi asbjoet, tanks for the issue ! |
Sure, we would be interested in that. |
Is this something your organisation is planning on adding to Dataverse by the way ? |
Not at the moment. We need to finish going from test to production. I am trying to raise awareness in our organisation about the value of contributing back to the community. |
We'd definitely be interested in a pull request. We'll need this functionality for the new frontend some day, which operates over APIs: https://github.com/IQSS/dataverse-frontend |
As we would also greatly benefit from this feature, we will propose a pull request to address it in a few weeks. |
Overview of the Feature Request
Hello
We want to automate our installation through Ansible and create Dataverses using Native API, which works fine.
However, we cannot set featured collections using the Native API and hence cannot automate this configuration.
What kind of user is the feature intended for?
Sysadmin
What inspired the request?
Automation.
What existing behavior do you want changed?
Native API.
Any brand new behavior do you want to add to Dataverse?
Expand functionality of Native API to allow setting featured collections.
Any open or closed issues related to this feature request?
Couldn't find any.
The text was updated successfully, but these errors were encountered: