creativecommons / creativecommons/search
[bug] Reconsider inclusion/function of Jamendo, terms and filtering are misaligned
- Dominant language
- CSS
- Stars
- 27
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
## Description
_Originally posted by @heyakyra in https://github.com/creativecommons/search/issues/124#issuecomment-1684080259_
>
> > Also, the search returns the "invalid search result: https://www.jamendo.com/search?q=fq" because of the malformed search query.
> >
> > The malformed query may be due to the fact that the [Jamendo](https://www.jamendo.com/search?q=cat) site may have been updated and their search query format updated as well, implying that we may need to update ours in return so as to get expected results.
>
> The current state is broken still, and results in queries like so, where the search terms become `[query-nc] [-nd]` instead of `[query] [-nc] [-nd]`:
>
> 
> 
>
> And either way, the filters for removing noncommercial and non-derivative licensed results don't work.
>
>
> > So as it stands, the [old Jamendo](https://www.jamendo.com/start) contains music that can be modified, downloaded, and reused (Personal use).
> >
> > And the site [licensing.jamendo](https://licensing.jamendo.com/en/royalty-free-music/search) contains music that can be used for commercial purposes and played in public places.
> >
> > […] So for example, if the user checked the "use for commercial purposes" checkbox, we redirect to [licensing.jamendo](https://licensing.jamendo.com/en/royalty-free-music/search) else we redirect to [old Jamendo](https://www.jamendo.com/start)
>
> This is incorrect, and therefore the solution implemented in #137 is backwards. Jamendo has adopted the language of the music industry oligopoly: "can be used commercially" actually means you can't use it commercially until you buy a license. "can be used personally" means you can use it personally (and maybe commercially too, but it's not in our financial interest to inform you)
## Resolution
- [ ] I would be interested in resolving this bug.
Contributor guide
Assessment
This issue has not been assessed yet.