Feature: Support value ranges for numerical fields in custom metadata blocks
Open
Nobody has claimed this yet.
Feature: Metadata
Original size: 10
Type: Feature
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview
- Currently, we don't support the ability for numerical metadata fields to specify a value range.
- For example, a metadata field called
average student gradecould be a floating point value between 0 and 100. - This feature is needed to support
Reviewdatasets whose associated rubrics may have floating point scores that range between two values.Reviewdatasets share these scores as CroissantQuantitativeValueobjects that support aminValandmaxVal. Custom metadata blocks forReviewswill need to shareminValandmaxValin the Croissant they produce.
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
No files or tests are named. Locate the custom metadata block handling and existing numerical-field serialization, then trace how Croissant QuantitativeValue objects are produced; done means numerical fields can expose the requested minVal and maxVal range for Review datasets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100