Expose settings via Info API (static lookup mapping in the Info API)
@GPortas is already working on this.
Since Oct 27, 2023.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
New settings are now required by the SPA (hasPublicStore, getAllowedExternalStatuses) and others will be necessary during the development of the SPA.
Since reading settings will be usual for the SPA, we may need to redesign the way we expose them through API. It may be interesting to follow the approach described on https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714120660 and complemented on https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714153633 and https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714177290
What kind of user is the feature intended for?
API User
What inspired the request?
- SPA needs
- https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714120660
- https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714153633
- https://github.com/IQSS/dataverse/pull/9881#issuecomment-1714177290
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
New mechanism to retrieve settings via API
Any open or closed issues related to this feature request?
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.
Assessment
This issue has not been assessed yet.