Parsers for non-music (or non-canonical) datasets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I'm writing a parser or the [UrbanSound8K dataset](https://serv.cusp.nyu.edu/projects/urbansounddataset/) (because I need it). Would it make sense to include it in this repo?
I know that in principle we're focusing on music datasets (and specifically canonical ones that are in common use by the MIR community), but is there any reason for not including all jams parsers in this repo?
I think this could be useful, especially for the environmental sound community who's starting to produce more and more datasets, which could all, in principle, use JAMS annotations. Alternatively I could start a separate repo for non-music JAMS datasets, but I'm not sure this makes sense?
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
Begin with the linked UrbanSound8K dataset and compare its annotation needs with the repository's existing JAMS dataset parsers. Decide whether this repository should accept non-music datasets or whether a separate repository is appropriate; no implementation target is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100