Wikidata:Property proposal/YouTube Topic channel ID
YouTube Topic channel ID
editOriginally proposed at Wikidata:Property proposal/Generic
Not done
Description | identifier for a YouTube Topic channel |
---|---|
Represents | YouTube auto-generated artist channel (Q72108010) |
Data type | External identifier |
Domain | agent (Q24229398) |
Example 1 | Taeyeon (Q233371) → UCwzCuKxyMY_sT7hr1E8G1XA |
Example 2 | Twice (Q20645861) → UCAq0pFGa2w9SjxOq0ZxKVIw |
Example 3 | Red Velvet (Q17466114) → UCHmZYTfdTyVKQEJicLiXEOg |
Expected completeness | always incomplete (Q21873886) |
See also |
|
Distinct-values constraint | yes |
Motivation
editWe do not have a property to separate a normal YouTube channel (Q17558136) and a YouTube auto-generated artist channel (Q72108010). A YouTube auto-generated artist channel (Q72108010) is an automatically generated channel that is created by YouTube that stores the artist's music. This is often called the "YouTube Music channel". You can learn more about their difference here.
We should have a separate property rather than qualifying YouTube channel ID (P2397) because there are likely tens of thousands of artists that have topic channels that have items on Wikidata so this property is relevant enough for a dedicated property.
Lectrician1 (talk) 01:04, 15 February 2022 (UTC)
Discussion
edit- Support This seems like a meaningful distinction. 06:24, 15 February 2022 (UTC) – The preceding unsigned comment was added by Ainali (talk • contribs) at 18:58, 16 February 2022 (UTC).
- Aren't we currently using qualifiers for this? What's wrong with that? BrokenSegue (talk) 03:23, 16 February 2022 (UTC)
- Oppose: in my opinion, not worth creating a completely new identifier property when the URL format is identical to any YouTube channel. Don't see why this can't already be distinguished by adding a qualifier "has quality -> YouTube Topic channel". If your issue is that those who link YouTube topic channels to Wikidata items don't use this qualifier enough, maybe instead look into suggesting a bot that could scrape those channels' pages and correctly add those qualifiers? --Btcprox (talk) 11:22, 16 February 2022 (UTC)
- @BrokenSegue @Btcprox Since when do people optionally add qualifiers? About never. I'm just going to reiterate, there are tens of thousands of topic channels. Yes, I could create a bot that adds qualifiers. But, is that ready right now? No. Are qualifiers a straightforward and consistent data solution like properties are? No. Give data consumers and editors a straightforward way of knowing what a Topic channel is and who has it. Qualifiers don't do that. Lectrician1 (talk) 14:06, 16 February 2022 (UTC)
- people are already using qualifiers on YouTube channel ID (P2397). See for example Q105816235. There is a downside to having a ton of overlapping properties. BrokenSegue (talk) 16:55, 16 February 2022 (UTC)
- @BrokenSegue But, 99% of the time in which qualifiers should be used, they are not. This isn't an "overlapping property". It's simply going to be a subproperty of YouTube channel ID (P2397). People can choose to use this property if they want and people can still query for all YouTube channels normally, regardless of type. At least with this property, people will know when searching for "YouTube channel" properties that there is a way to document that there is a YouTube Topic channel for an agent. With qualifiers, they don't. Lectrician1 (talk) 18:58, 16 February 2022 (UTC)
- people are already using qualifiers on YouTube channel ID (P2397). See for example Q105816235. There is a downside to having a ton of overlapping properties. BrokenSegue (talk) 16:55, 16 February 2022 (UTC)
- @BrokenSegue @Btcprox Since when do people optionally add qualifiers? About never. I'm just going to reiterate, there are tens of thousands of topic channels. Yes, I could create a bot that adds qualifiers. But, is that ready right now? No. Are qualifiers a straightforward and consistent data solution like properties are? No. Give data consumers and editors a straightforward way of knowing what a Topic channel is and who has it. Qualifiers don't do that. Lectrician1 (talk) 14:06, 16 February 2022 (UTC)
- Oppose per Btcprox, here qualifiers should be used. --Hannes Röst (talk) 15:51, 28 March 2022 (UTC)
- @Lectrician1, BrokenSegue, Btcprox, Hannes Röst: Not done —MasterRus21thCentury (talk) 05:33, 8 April 2022 (UTC)