Feature Request/Idea: Allow to choose which fields should be pre-filled from user profile at dataset or collection creation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Currently many fields (name, affiliation, dataverse name...) are pre-filled with information from the user's profile.
While this feature makes sense in most cases, it would be nice to be able to switch it on or off depending on the needs, for ex. through a parameter configurable from api/admin/settings.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
All
What inspired the request?
We would have liked to have the affiliation field blank at dataset creation. But I feel it's only a specific need into a larger and more generic possible functionality.
What existing behavior do you want changed?
See overview.
Any brand new behavior do you want to add to Dataverse?
No, just configuration parameters.
Any related open or closed issues to this feature request?
Not found.
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
Review the existing user-profile prefill behavior and the api/admin/settings configuration entry points mentioned in the request. Map which dataset and collection creation fields are currently pre-filled, then define and verify configuration behavior for selecting those fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100