neume-network / neume-network/data
We often don't comply to our own schema in this repository and we are unaware of it
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- e.g. today we noticed that any track should have a manifestation with an audio mimetype
- or e.g. many tracks don't contain a valid owner field
- and so we should be made aware automatically if the outcomes in the results directory are non compliant with the schema
- a solution could be where a separate github action work flow parses music os accumulator file and check each tracks schema compliance
Contributor guide
No contributing guide indexed for this repository
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 with the music os accumulator file and the outcomes in the results directory; inspect how tracks are represented and where schema checks could run. Define checks for an audio mimetype manifestation and a valid owner field, then consider the proposed GitHub Actions workflow. Done means non-compliant results are reported automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, data, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100