Inconsistent treatment of missing values in dataset qualities
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
The dataset quality MaxCardinalityOfNumericAttributes is handled differently in datasets 3 and 42:
<oml:quality><oml:name>MaxCardinalityOfNumericAttributes</oml:name><oml:value>null</oml:value></oml:quality>
vs
<oml:quality><oml:name>MaxCardinalityOfNumericAttributes</oml:name><oml:value/></oml:quality>
I think the latter one is better to parse and doesn't require to check for a specific string to be present.
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
Compare the quality records for datasets 3 and 42, focusing on MaxCardinalityOfNumericAttributes. Trace where these dataset XML values are produced or consumed, then standardize missing values on the chosen representation and verify that both records parse consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- data, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100