Feature Request/Idea: Support for Default Value Property in Metadata Fields of TSV Metadata Blocks
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
Include a new dataset field property in the metadata block TSV file to store the default value of the field. This property would enable these default values to be automatically pre-filled when the corresponding metadata field is used, streamlining the data entry process and ensuring consistency across datasets.
What inspired the request?
We want to create metadata fields for data types comparable to FHIR coding, where attributes such as the system, version, and code are often standardized and could benefit from being pre-filled.
Any brand new behaviour do you want to add to Dataverse?
New property for metadata fields.
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.
Research direction
The request concerns TSV metadata blocks and metadata fields, but names no files or tests. Start by tracing how TSV metadata properties are parsed and how metadata fields are used, then define how a stored default value should be represented and pre-filled for FHIR Coding-style fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100