Feature Request/Idea: Improve name of the Dataverse software's "JSON" metadata export
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
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
API User, Curator, Superuser, Sysadmin
What inspired the request?
Comments from the Dataverse community and new users about metadata export's name, "JSON".
And over the years we've added other metadata exports in JSON, too. So changing the name of the "JSON" export to something more specific should give people a better sense of what the export is.
What existing behavior do you want changed?
Changing the name of the export to something more specific and using that name in the UI, the APIs and the Dataverse Guides
Screenshots
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 locating the existing "JSON" export name in the UI, APIs, and Dataverse Guides. Confirm the replacement name with maintainers, update each occurrence, and verify the export remains available under the new name across those surfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, documentation, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100