Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate some Jamendo results which are only 'preview' quality files #1319

Open
zackkrida opened this issue Dec 14, 2022 · 5 comments
Open
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: catalog Related to the catalog and Airflow DAGs 💬 talk: discussion Open for discussions and feedback

Comments

@zackkrida
Copy link
Member

Description

Unfortunately, Jamendo appears to include two kinds of CC-licensed audio files in their service:

  1. Tracks fully licensed using a CC license: https://www.jamendo.com/track/1411230/dogu-comme-demain
  2. Tracks where only a lower-quality, 'preview" file is CC licensed, and the higher-fidelity version requires a paid commercial license: https://www.jamendo.com/track/26967/batman-loves-my-dog

The differences between these two tracks are evident in the UI. Here are screenshots of the 'paid' track:

CleanShot 2022-12-14 at 14 20 57

CleanShot 2022-12-14 at 14 21 00

Jamendo refers to the later paid licenses as "official", which sadly seems to imply that CC licenses are somehow "unofficial'. I don't love the spirit of that.

To resolve this, we need to decide:

  • Do we think the second type of tracks belong in Openverse?
  • Is there a way to differentiate between these types of tracks?
  • Can we provide instructions to our users about how to download Jamendo images and navigate this obscure language and UI?
@zackkrida zackkrida added 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix labels Dec 14, 2022
@xolotl
Copy link

xolotl commented Dec 14, 2022

There's an additional point that Jamendo may have removed license filters from its search capabilities.

@dhruvkb dhruvkb added 🟨 priority: medium Not blocking but should be addressed soon 🕹 aspect: interface Concerns end-users' experience with the software 💬 talk: discussion Open for discussions and feedback and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Dec 16, 2022
@dhruvkb
Copy link
Member

dhruvkb commented Dec 16, 2022

I've also assigned the "💬 talk: discussion" label here because it seems like there are some questions that we need to discuss and come to a conclusion about.

@obulat obulat added the 🧱 stack: catalog Related to the catalog and Airflow DAGs label Feb 23, 2023
@obulat obulat transferred this issue from WordPress/openverse-catalog Apr 17, 2023
@heyakyra
Copy link

heyakyra commented Aug 18, 2023

License filters are broken, so it's probably time to revisit removing it entirely until/unless there's a way to scrape the library, grab the license info, and maintain an index of it. Sad, since I remember a decade and a half ago, it was the best place to go for freely licensed music.

My comment on the linked ticket:

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 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]:

Screenshot 2023-08-18 at 10-15-33 CC Search Portal
Screenshot from 2023-08-18 10-14-54

And either way, the filters for removing noncommercial and non-derivative licensed results don't work.

So as it stands, the old Jamendo contains music that can be modified, downloaded, and reused (Personal use).

And the site licensing.jamendo 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 else we redirect to old Jamendo

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)

@obulat
Copy link
Contributor

obulat commented Aug 18, 2023

@heyakyra, Openverse collects the data from its sources using their APIs, so we are not affected by the Jamendo UI filters. The data that is already in Openverse has the appropriate licenses that the media used when we ingested it from the API. So, if you want to search for Jamendo audio on Openverse, try searching for cat with 'Use commercially' and 'Modify or adapt' filters applied: https://openverse.org/search/audio?q=cat&license_type=commercial,modification&source=jamendo

The snapshots you shared are from the old "CC Search". If your issue is related to the search on https://search.creativecommons.org/, you should report it in the CC repository.

@heyakyra
Copy link

Oops, thanks for clarifying that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: catalog Related to the catalog and Airflow DAGs 💬 talk: discussion Open for discussions and feedback
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants