Wikidata:Property proposal/7digital United Kingdom artist ID

From Wikidata
Jump to navigation Jump to search

7digital United Kingdom artist ID[edit]

Originally proposed at Wikidata:Property proposal/Authority control

   Not done
Descriptionidentifier for an artist on 7digital United Kingdom music site
Represents7digital United Kingdom (Q64556123)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Basshunter (Q383541)basshunter
Example 2Stromae (Q313453)stromae
Example 3Sean Paul (Q200577)sean-paul
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usePutting value to musical artists available from the 7digital United Kingdom site.
Expected completenessalways incomplete (Q21873886)
Formatter URL$1
See alsoKKBox artist ID (P5154)


Missing property. Other properties needed include 7digital United Kingdom release ID or 7digital Sverige artist ID. Eurohunter (talk) 15:51, 11 June 2019 (UTC)


  • Symbol support vote.svg Support David (talk) 07:03, 12 June 2019 (UTC)
  • Pictogram voting comment.svg Comment Is there a way to make the 7digital identifiers region-independent, or does each regional site have its own distinct identifiers for the same artists? Mahir256 (talk) 23:56, 12 June 2019 (UTC)
    • @Mahir256: It's like iTunes. Every country has their independent releases but with the same id. So as I said in motivation I think we need to have separate id for 7digital United Kingdom, 7digital Sverige, 7digital Deutschalnd, 7digital France, 7digital Italia etc. to distinguish se. uk. de. fr. it. in url. In addition iTunes on Wikidata need separate id for other countries like Sweden and UK because it has only US version of url so I never make it to work to add other versions like Swedish or British versions of iTunes. Eurohunter (talk) 07:35, 13 June 2019 (UTC)
If they have the same ID, then we should have only one property. You can set several formatter URL's with qualifiers (not that the UI understands this, but it's at least human-interpretable) or use the third-party formatter URL property if that makes more sense. ArthurPSmith (talk) 17:30, 18 June 2019 (UTC)
@ArthurPSmith: Can you show example? Eurohunter (talk) 18:34, 18 June 2019 (UTC)
The properties listed here are ones where the third-party formatter URL is used, for example Library of Congress authority ID (P244). Tennis Temple player ID (P4544) is an example of a property with different formatter URL's for different languages. ArthurPSmith (talk) 20:10, 18 June 2019 (UTC)
@ArthurPSmith: But there is no example for French version at Tennis Temple player ID. Eurohunter (talk) 20:14, 18 June 2019 (UTC)
@Eurohunter: ArthurPSmith is right, we could make only one property with different formatter URL's for different languages. Even no need use third-party formatter URL property. Regards, ZI Jony (Talk) 06:54, 2 July 2019 (UTC)
@ZI Jony: Can you show example? Eurohunter (talk) 14:48, 2 July 2019 (UTC)
@ArthurPSmith: could you link an example of how to use qualified formatter URL's and I'll update this one. --Ysangkok (talk) 01:43, 9 September 2019 (UTC)
@Ysangkok: I'm not sure what you're asking for, but Tennis Temple player ID (P4544) seemed to me like an example you could follow for this. ArthurPSmith (talk) 17:47, 9 September 2019 (UTC)
  • Pictogram voting comment.svg Comment I would agree that instead of various regional properties this can just be one property with multiple formatter URLs qualified by region/language. Would support this proposal if it was updated as such. --SilentSpike (talk) 15:27, 24 March 2020 (UTC)

No consensus, so marked as "not done", with no prejudice to a proposal for a unified property, per SilentSpike. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:07, 25 June 2020 (UTC)