Wikidata:Properties for deletion

Properties for deletion
This is the page for requesting the deletion of a property (for items, with IDs beginning with "Q", please use requests for deletions). To nominate a property for deletion, complete the following steps:
  • Place the {{Property for deletion}} template on the property talk page.
  • Open the discussion by typing the property number below and pressing "Add a new request".
  • Transclude the subpage under #Requests below.
  • Notify the user who originally proposed the property and the property creator who created it on their respective talk pages.
  • Check if the property is being used in other projects (using {{ExternalUse}}) and if it is, leave a message on a project discussion page by notifying the participants.

Requests may be closed after 7 days, but may be extended if consensus is not reached. If an extended discussion becomes stale and has been left unclosed, a request for closure can be made at the administrators' noticeboard. If the request is uncontroversial, for example "accidentally created with wrong datatype", please use the faster-moving requests for deletions instead.

Properties for deletion may be used:

  1. To merge a property to another, or request to deprecate a property in favor of another.
  2. To change the data type of a property currently being used.
  3. Rarely, to delete a property with no replacement (e.g. it refers to an external website that is closed and/or not suitable for Wikidata).

Properties for deletion should not be used:

  1. To change the scope or purpose of a property; these should be discussed at the talk page of the property, project chat, or requests for comment.
  2. To request of undeletion of a property. To challenge a recently closed properties for deletion, you may use administrators' noticeboard; otherwise, you may repropose the property.


On this page, old requests are archived. An overview of all archives can be found at this page's archive index. The current archive is located at Wikidata:Properties for deletion/Archive/2022/11. player ID (former scheme) (P6615)Edit player ID (former scheme) (P6615): (delete | history | links | entity usage | logs | discussion)

Kicker changed its website, and all the IDs that we have stored are invalid now. Therefore this property is not useful anymore. Steak (talk) 15:38, 16 September 2020 (UTC)

many of the id's links are archived. e.g. this one. though the link format is broken at the moment. deprecate and mark as obsolete but keep. here's a list of archived entries. BrokenSegue (talk) 16:51, 16 September 2020 (UTC)
If this property is deleted, the non-numeric identifiers should be transferred to the new property prior to being removed. S.A. Julio (talk) 17:28, 27 October 2020 (UTC) player ID (actual scheme) (P8912) has been created. Pamputt (talk) 21:29, 4 December 2020 (UTC)
I would love to say Symbol delete vote.svg Delete, @BrokenSegue: to me the scheme has been largely changed, results the former property can't compatible with the current scheme entirely, probably the core algorithm of this service has re-written. --Liuxinyu970226 (talk) 14:48, 10 December 2020 (UTC)

Bashkir encyclopedia (Russian version) ID (former scheme) (P4211)Edit

Bashkir encyclopedia (Russian version) ID (former scheme) (P4211): (delete | history | links | entity usage | logs | discussion)

In 2019 Bashkin Encyclopedia opened a new websize, opened a new website, where versions in Russian, Bashkir and English were combined under a single code (Property:P9222). When switching to the old version of the site, there is a notification that the Bashkir Encyclopedia has moved to a new address. Therefore, I ask the Wikidata administrators to remove both properties — Timur Rossolov (talk) 17:40, 27 July 2021 (UTC)

Bashkir encyclopedia (Bashkir version) ID (former scheme) (P4210)Edit

Bashkir encyclopedia (Bashkir version) ID (former scheme) (P4210): (delete | history | links | entity usage | logs | discussion)

In 2019 Bashkin Encyclopedia opened a new websize, opened a new website, where versions in Russian, Bashkir and English were combined under a single code (Property:P9222). When switching to the old version of the site, there is a notification that the Bashkir Encyclopedia has moved to a new address. Therefore, I ask the Wikidata administrators to remove both properties —Timur Rossolov (talk) 17:39, 27 July 2021 (UTC)

This in addition to the 1057 uses of Bashkir encyclopedia (Russian version) ID (former scheme) (P4211) mentioned above and its catalogue.
Oddly the two aren't kept in synch (maybe identifiers for both properties (or all three) could be added to these. ID (P9222) is hardly used (45 uses almost a year after creeation) and doesn't have a Mix'n'match catalogue.
I don't think we should delete the properties before the Mix'n'match question is resolved. I don't have much of an opinion of any of the three properties are worth keeping.
@Visem, З. ӘЙЛЕ, Kareyac, Magnus Manske, Epìdosis: @Movses, Avatar6, Russian Rocky, SCIdude, Vesihiisi: @Saint Johann: who worked on either catalogue in MxM.
@putnik, ShinePhantom, Carn, Ghuron: @Wikisaurus, Сидик из ПТУ, Serhio Magpie, Arbnos: who participated in the proposal discussion for the new property. --- Jura 13:40, 8 January 2022 (UTC)
  • It would be better if someone can change data for new version. --Visem (talk) 17:15, 8 January 2022 (UTC)
Good afternoon! Bashwiki needs help :) We would like, if one of the programmers could help, to change all the old data to new ones with one click, if this is not possible, notify us so that we do everything manually. In the previous site, the index of articles in Russian and Bashkir was different, in the new site they are the same. We will be grateful for any help: practical or theoretical :) --З. ӘЙЛЕ (talk) 05:47, 20 January 2022 (UTC)
@З. ӘЙЛЕ: If you can supply the mappings between the old ids and the new ones, you might want to make a request at Wikidata:Bot requests. These can then be added to Wikidata and Mixnmatch. --- Jura 18:34, 11 February 2022 (UTC)
What is the problem? If it's discountinued project just modify url with archived version to Wayback Archive to property or just update to new url if project was just moved. Don't remove properties just becasuse they are unavailable - use archived version instead. Eurohunter (talk) 16:05, 4 August 2022 (UTC)

English Vikidia ID (P7829)Edit

English Vikidia ID (P7829): (delete | history | links | entity usage | logs | discussion)

Several Non-French article ids (P7829, Italian Vikidia ID (P7822), Spanish Vikidia ID (P7827), Basque Vikidia ID (P7832), Armenian Vikidia ID (P7841), German Vikidia ID (P7843), Catalan Vikidia ID (P9123), Russian Vikidia ID (P9124)) can be merged to French Vikidia ID (P7818), like Fandom article ID (P6262). Take Vikidia (Q3051048) as an example, its French Vikidia ID (P7818) is Vikidia, it can also be refered to as en:Vikidia which in fact points to the English Vikidia.

@Tinker Bell, Pintoch, Jura1, Trade, Eihel: What's your idea? —Kethyga (talk) 09:04, 10 April 2022 (UTC)

Vladimir Alexiev (talk) 11:59, 13 March 2017 (UTC) GerardM (talk) 15:58, 26 March 2017 (UTC) Jonathan Groß (talk) 17:52, 26 March 2017 (UTC) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits Jneubert (talk) 13:47, 29 April 2017 (UTC) Framawiki (please notify !) (talk) Sic19 (talk) 20:42, 12 July 2017 (UTC) Wikidelo (talk) 21:15, 8 May 2018 (UTC) ArthurPSmith (talk) 19:52, 22 August 2018 (UTC) PKM (talk) 19:40, 23 August 2018 (UTC) Ettorerizza (talk) 06:44, 8 October 2018 (UTC) Fuzheado (talk) 03:47, 19 December 2018 (UTC) Daniel Mietchen (talk) 16:30, 7 April 2019 (UTC) Iwan.Aucamp (talk) 21:48, 3 October 2019 (UTC) Epìdosis (talk) 23:49, 22 November 2019 (UTC) Sotho Tal Ker (talk) 00:52, 1 May 2020 (UTC) Bargioni (talk) 09:48, 02 May 2020 (UTC) Carlobia (talk) 14:34, 11 May 2020 (UTC) Pablo Busatto (talk) 03:22, 23 June 2020 (UTC) Matlin (talk) 10:53, 6 July 2020 (UTC) Msuicat (talk) 21:57, 27 August 2020 (UTC) Uomovariabile (talk) 10:04, 27 October 2020 (UTC) Silva Selva (talk) 17:21, 30 November 2020 (UTC) 1-Byte (talk) 15:52, 14 December 2020 (UTC) Alessandra.Moi (talk) 17:26, 16 February 2021 (UTC) CamelCaseNick (talk) 21:20, 20 February 2021 (UTC) Songceci (talk) 18:45, 24 February 2021 (UTC)]] moz (talk) 10:48, 8 March 2021 (UTC) AhavaCohen (talk) 14:41, 11 March 2021 (UTC) Kolja21 (talk) 17:37, 13 March 2021 (UTC) RShigapov (talk) 14:34, 19 September 2021 (UTC) Jason.nlw (talk) 15:15, 30 September 2021 (UTC) MasterRus21thCentury (talk) 20:22, 18 October 2021 (UTC) Newt713 (talk) 08:42, 13 March 2022 (UTC) Pierre Tribhou (talk) 08:00, 20 March 2022 (UTC) Powerek38 (talk) 17:21, 14 April 2022 (UTC) Ahatd (talk) 08:34, 4 August 2022 (UTC) JordanTimothyJames (talk) 00:54, 31 August 2022 (UTC) Pictogram voting comment.svg Notified participants of WikiProject Authority controlKethyga (talk) 14:29, 10 April 2022 (UTC)

Alexa rank (P1661)Edit

Alexa rank (P1661): (delete | history | links | entity usage | logs | discussion)

Alexa is retired and the current data is outdated, incomplete, and inconsistent. —GZWDer (talk) 17:40, 11 May 2022 (UTC)

  • Values with a point in time qualifier should be kept for historical purposes. Not sure what to do about entries with no date qualifier. ArthurPSmith (talk) 20:45, 11 May 2022 (UTC)
    How about the date when the property was added or check Internet Archive (Q461)? Kethyga (talk) 03:49, 13 May 2022 (UTC)
    What's the actual goal here? Add the last known Alexa rank? Add the yearly ranks? Monthly? Daily? Just some random date? @Kethyga:--Trade (talk) 01:31, 28 May 2022 (UTC)
    Just the time when the property was added to a Wikidata item if Internet Archive (Q461) has a backup. Kethyga (talk) 01:37, 28 May 2022 (UTC)
    @ArthurPSmith: We may change it to "Last Alexa rank" but it will open the door to scam and misleading because you don't have the main reference (the website shut down) and we can't ensure the rank is right or not--Ibrahim.ID (talk) 13:40, 27 July 2022 (UTC)
  •  Support Alexa is closed in May 2022, there is no useful use of outdated data and not even for historical purposes. --Ibrahim.ID (talk) 13:40, 27 July 2022 (UTC)
  •  Support is now closed and there is no point in keeping past records.--Mugenpman (talk) 04:21, 10 August 2022 (UTC)
  • Vigorous  Oppose Historical data with an associated time is still useful, and a low Alexa rank is a very useful indication that a website was of significant interest at the time. However, entries without "point in time" should be deleted, as they are now meaningless. It may be possible to use the Internet Archive to retrieve historical data, and to use a bot to popuate these with new, dated, values. A moment's searching finds extensive backups of at least the top 50, see , and there is also data accessible for the top 500 if we look deeper; see, for example, . This data has also been used to drive web crawling activities by the IA, who may also have archived data that can be mined for this. See, for example, The Anome (talk) 11:08, 10 August 2022 (UTC)
  • Symbol keep vote.svg Keep I agree with opinion of The Anome. --Gymnicus (talk) 11:53, 19 August 2022 (UTC)
  • Symbol keep vote.svg Keep. A lot of Alexa rankings are very clearly able to be dated and confirmed using the Internet Archive, and damn near every single one of those is useful. Telaneo (User talk page) 05:06, 7 September 2022 (UTC)
  • Symbol keep vote.svg Keep per The Anome. Retired website is not a valid reason to remove the property. In this case, we should preserve the historical data. Ranks can still be used by looking at the archives (example). Regards Kirilloparma (talk) 00:33, 9 September 2022 (UTC)
Symbol keep vote.svg Keep, but remove any non-dated values and deprecate any new additions that are not clearly referenced to IA. Vicarage (talk) 06:17, 26 September 2022 (UTC)
  • Symbol keep vote.svg Keep dated values only.
The Erinaceous One 🦔 07:07, 27 November 2022 (UTC)


BadmintonLink player ID (P3623): (delete | history | links | entity usage | logs | discussion)

Used only for 14 players, site already a long time dead, even archived pages are only available after a lot of clicks through —Florentyna (talk) 08:30, 4 June 2022 (UTC)

  • Yes, it makes sense to delte it. Symbol delete vote.svg Delete ChristianKl❫ 19:20, 7 June 2022 (UTC)
  • Symbol delete vote.svg Delete The website is not working either. It's better to delete it rather than having an archive url. Toghrul R (talk) 06:52, 16 June 2022 (UTC)
  • Symbol delete vote.svg Delete Low usage, dead page. --Jklamo (talk) 16:48, 26 August 2022 (UTC)


KIT Linked Open Numbers ID (P5176): (delete | history | links | entity usage | logs | discussion)

Per Property_talk:P5176, this is not really an ID. —GZWDer (talk) 09:05, 16 June 2022 (UTC)

Symbol keep vote.svg Keep It's as much of an ID as all those other sites that use some form of a person's name as their ID's. ArthurPSmith (talk) 13:24, 16 June 2022 (UTC)
The talk page include two unresolved disputes:
  1. Should items like RSA-370 (Q15990672) have this property?
  2. How should this property be labeled?
--GZWDer (talk) 19:54, 17 June 2022 (UTC)
Actually, I don't see any unresolved dispute. The KIT Linked Open Numbers (Q51279230) website provides data about 999,999,999,999 natural numbers (from 1 to 999,999,999,999), so the answer to the first question is "no". The answer to the second question is "the current one": any label that aims to generalize the property would make the property itself coincide with numeric value (P1181).
I think the only question we should ask ourselves is: is KIT Linked Open Numbers a valid resource deserving to be linked? --Horcrux (talk) 20:58, 17 June 2022 (UTC)


DBLP event ID (P10692): (delete | history | links | entity usage | logs | discussion)

dblp computer science bibliography (Q1224715) does not have such an external identifier. This was brought up in the creation proposal by MRA but went on to be ignored. It seems they are considering and working on something like that but it currently does not exist. The formatter URL (P1630) for this property currently can link to a whole host of different things are that not in fact events, e.g., ACM Inroads, Volume 13, The dblp Advisory Board. Further, the things it was envisioned to link to are conference events but instead the links are to proceedings contents which can be sticky as they frequently are not one-to-one with the events themselves, not to mention proceedings are often published as parts of journals and books series so the "identifiers" for such an event might not match DBLP venue ID (P8926), e.g., Conference on Philosophy and Theory of Artificial Intelligence (Q105698572) -> DBLP venue ID (P8926) conf/ptai is great but Philosophy and Theory of Artificial Intelligence, PT-AI 2011, Thessaloniki, Greece, October 3-4, 2011 (Q106332070) DBLP event ID (P10692) series/sapere/sapere5 does not really match since the proceeding is published in a book series. —Uzume (talk) 02:43, 22 June 2022 (UTC)

@Florian.Reitz: FYI. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:26, 24 July 2022 (UTC)

Property:P6624Edit skater ID (P6624): (delete | history | links | entity usage | logs | discussion)

From December 1, 2019, the Internet project about figure skating in Russia is closed. The skaters' pages have also been removed. So I'm making a request to remove this property with its Wikidata child. —MasterRus21thCentury (talk) 23:02, 6 August 2022 (UTC)


ISOCAT id (P2263): (delete | history | links | entity usage | logs | discussion)

The external links for this property have been broken for over a year, and it is not clear what these identifiers referred to or if they will ever be resolveable. Middle river exports (talk) 18:43, 7 August 2022 (UTC)


Microsoft Academic ID (P6366): (delete | history | links | entity usage | logs | discussion)

Does not link to anything; retired service Middle river exports (talk) 07:37, 21 August 2022 (UTC)

Symbol keep vote.svg Keep. MAG have an open downloadable dataset that can be imported some time in the future.--GZWDer (talk) 13:39, 23 August 2022 (UTC)
Symbol keep vote.svg Keep the MAG identifiers have effectively been subsumed in to openalex. it would be best to update all entities to have a matching openalex identifier before deleting the old MAG identifiers Blnewbold (talk) 01:15, 13 September 2022 (UTC)
What I means is not to remove MAG IDs at all even if OpenAlex ID is present - since MAG is a stable dataset. GZWDer (talk) 23:43, 13 September 2022 (UTC)
Symbol keep vote.svg Keep discontinued website, but widely used and we have somehow working formatter (through --Jklamo (talk) 14:11, 19 October 2022 (UTC)
Hopefully the downloadable dataset mentioned above is available at some point, since has often never indexed the ID from what I have seen. عُثمان (talk) 00:00, 21 October 2022 (UTC)
Symbol keep vote.svg Keep per above BrokenSegue (talk) 01:28, 5 November 2022 (UTC)


Olympic Committee of Serbia athlete ID (archived) (P4547): (delete | history | links | entity usage | logs | discussion)

Currently, a property has been created to replace the one being removed - Olympic Committee of Serbia athlete ID (new) (P10978). Since 2020, the above site has stopped working and now all identifiers are not in the form of numbers, but in the form of a first and last name. —MasterRus21thCentury (talk) 14:57, 26 August 2022 (UTC)

Winterthur Glossar URL (DEPRECATED) (P6107)Edit

Winterthur Glossar URL (DEPRECATED) (P6107): (delete | history | links | entity usage | logs | discussion)

Deutsch: Es gibt mit Winterthur Glossar ID (P10677) eine Nachfolgeeigenschaft, die inzwischen überall vorhanden ist (ausser für gewisse Referenzen, die URL's sind eh nicht mehr gültig.)
English: With Winterthur Glossar ID (P10677) there is a successor-property, which is implemented anywhere by now (expect for some references, where the URL's aren't valid anymore, anyway.)

Fundriver (talk) 09:00, 8 September 2022 (UTC)

surrounds the enclave (P10613)Edit

surrounds the enclave (P10613): (delete | history | links | entity usage | logs | discussion)

See Wikidata:Property proposal/surrounds the enclave. I was the proponent, but before the property was accepted I figured out a better modelling: I use direction relative to location (P654) with qualifier inside (Q109810863). Nobody uses this property. The one use on emirate seat (Q111668946) is aberrent; it should be has part(s) (P527) instead. —GrandEscogriffe (talk) 17:10, 27 September 2022 (UTC)

Symbol delete vote.svg Delete - Nikki (talk) 18:57, 7 November 2022 (UTC)


enclave within (P501): (delete | history | links | entity usage | logs | discussion)

Also RFD this too as the same information can be expressed using shares border with (P47). —GZWDer (talk) 17:57, 27 September 2022 (UTC)


exclave of (P500): (delete | history | links | entity usage | logs | discussion)

As long as located in the administrative territorial entity (P131) is correctly interpeted as "located in and part of" (e.g. Llívia (Q13745) located in the administrative territorial entity (P131) Cerdanya (Q12787) and not Llívia (Q13745) located in the administrative territorial entity (P131) Pyrénées-Orientales (Q12709)), we does not need another property to cover the same information. Previous request: Wikidata:Properties_for_deletion/Archive/2017#Property:P500GZWDer (talk) 18:05, 27 September 2022 (UTC)


Hmoegirl ID (P10724): (delete | history | links | entity usage | logs | discussion)

Lacking notability. 10:26, 3 October 2022 (UTC)

There are 5 entries and all added on the same date by @C933103. That looks indeed like lack of notability. Mbch331 (talk) 15:13, 3 October 2022 (UTC)
The intent of this property is to complement the main property of Moegirlpedia ID to achieve comprehensive correspondence, as this site function as a backdrop for content deported from the main Moegirlpedia site due to Chinese regulatory rules, however the uptime of the H-moe site have been far from best in recent months, hence it would be pretty difficult for anyone to try to add new entries for the site into Wikidata in the past few months, which explain its current relative low usage. C933103 (talk) 10:14, 5 October 2022 (UTC)

Situation update: It is now commonly believed that (no official proofs), members, editors, and other persons related to Hmoe pedia are starting to be taken by Chinese polices starting from roughly July this year, and starting from September the site is rendered totally inaccessible until now, and many on Chinese internet estimated that this likely mean the site is not going to return, although archive of the site remain available on like Internet Archive. Chinese Wikipedia have voted to delete their article covering this site on notability ground on September 10 while speculating the site's fate.

I think for the time being it might make more sense to edit the property so that it link to internet archive instead, and to complete the collection of pages that have been archived by the internet archive engine.

C933103 (talk) 15:58, 9 October 2022 (UTC)

  • Symbol delete vote.svg Delete Gibberish contents with nothing given even small notabilities. --Liuxinyu970226 (talk) 07:03, 16 October 2022 (UTC)
    "gibberish" to people who do not want to see content against Chinese law I guess C933103 (talk) 17:47, 20 October 2022 (UTC)
  • Symbol delete vote.svg Delete barely used identifier of spin-off of user-generated narrowly focused database. --Jklamo (talk) 14:17, 19 October 2022 (UTC)
    narrowly focused? C933103 (talk) 17:46, 20 October 2022 (UTC)
  • Pictogram voting question.svg Question Do we really need to delete the subject item Q111607789? Wasn't it part of Moegirlpedia? Laftp0 (talk) 11:27, 25 October 2022 (UTC)
    That is for another discussion. After the site being made unavailable since earlier last month, and then earlier this month rumor on Twitter surfaced that claim contributors from China being taken away by Chinese government, Chinese Wikipedia judged the the Chinese Wikipedia article did not meet notability guideline despite expecting situation might change in short term, and hence deleted the article. With the Chinese Wikipedia article deleted, the Wikidata item no longer have any Wikipedia link and likely being deleted because of it not meeting notability criteria #1. Yet, as far as this Prperty P10724 remain in existence, I think it still meet notability criteria #3, and thus shouldn't be deleted.
    It was not officially part of Moegirlpedia but more like a complementary site to it. In the early day HMoegirl shared account database and other resources with the main Moegirlpedia site, but such arrangement have been problematic as Moegirlpedia progressively move into Chinese server and subject the wiki to Chinese government regulation, while Hmoegirl continue to host content that are against Chinese law in multiple aspects. Hence as of summer of year 2022 the official stance is no official relationship between the two sites, despite editors and contents across the sites. C933103 (talk) 12:58, 26 October 2022 (UTC)


France Musique person ID (P5654): (delete | history | links | entity usage | logs | discussion)

France Musique identidier never existed. Actually it's duplicate of Radio France person ID (P10780). Eurohunter (talk) 16:00, 5 November 2022 (UTC) —Eurohunter (talk) 16:00, 5 November 2022 (UTC)

France Musique website did exist but Radio France recently (beginning of 2022) modified websites of its radio so that they now all redirect to All sstatement using P5654 should be migrated to Radio France person ID (P10780) before deleting this property. Pamputt (talk) 18:53, 5 November 2022 (UTC)
See also Wikidata:Properties for deletion/P5654. Pamputt (talk) 18:54, 5 November 2022 (UTC)


MangaDex title ID (P10589): (delete | history | links | entity usage | logs | discussion)

The website MangaDex is a website for scanlation (Q557923) and therefore gives people access to copyright protected works for free without holding a license to publish it or consent of the copyright holder. The website infringes copyrights and I don't see any reason why wikidata should link items to such a website.

See also: Wikidata:Project_chat#Mangadex?

Christian140 (talk) 07:58, 7 November 2022 (UTC)

  • BA candidate.svg Weak oppose Linking to a website doesn’t mean endorsing its practices. The question in this case would be whether the benefits of having this site linked outweigh the concerns about legal issues. --2A02:8108:50BF:C694:E0F2:7F6B:7EAD:26F9 10:12, 7 November 2022 (UTC)
Symbol delete vote.svg Delete in the past Japanese publisher sent cease and desist letters to aggregators for Scanlation. Having this property might essentially makes us an aggregator for Scanlation and thus opens up the possibility of legal threads against Wikimedia. I think it's ideal if your community can self regulate in this regard and delete the property without needing to interact with Wikimedia legal. ChristianKl❫ 15:12, 7 November 2022 (UTC)
(Japanese publishers having sent cease and desist letters for scanlation sounds … interesting given that it’s not their – arguably monetary – rights infringed upon, but those of the author, and in Japan itself it wasn’t possible until a few years ago to take legal actions on behalf of a third party against copyright violations. Just as an aside. --2A02:8108:50BF:C694:E0F2:7F6B:7EAD:26F9 15:53, 7 November 2022 (UTC))
Scanlation websites are seldomly located in Japan, so the details of Japanese law don't matter here. ChristianKl❫ 00:15, 10 November 2022 (UTC)
Admittedly yes, therefore an aside (basically saying that they are taking advantage of another country’s legal provisions where this would not be possible in their own country – indeed not of interest here). --2A02:8108:50BF:C694:1432:F47C:55CC:B105 19:37, 12 November 2022 (UTC)
Symbol delete vote.svg Delete I created this property honestly not knowing it was a scanlation website or what scanlation was. Linking to a website that distributes copyrighted material is basically assisting in that distribution which is illegal. Lectrician1 (talk) 20:18, 7 November 2022 (UTC)
Symbol delete vote.svg Delete As for scanlation sites, Japanese and U.S. publishers declared in a joint statement in 2010 that they are illegal. By making them available for free, they are infringing on the financial benefits that copyright holders rightfully deserve. Afaz (talk) 04:01, 9 November 2022 (UTC)
While this is undoubtedly true, there are no financial benefits for copyright holders anyway if nobody publishes their work commercially in a country. If there is no “official” translation that is sold in, e.g., the US, anyone who wants to read it (in English) there has to resort to “unofficial” translations, which have no choice but to infringe on copyright. I don’t want to endorse copyright violations, in no way, but the “financial” point of view doesn’t get us anywhere here. That said, what was the point of creating links to the specific site discussed here in the first place? What benefits were seen in linking it? --2A02:8108:50BF:C694:E83C:EBFF:49AF:23CC 10:18, 9 November 2022 (UTC)
As far as the laws are concerned people can import Japanese comics whether or not they are translated. The Berne convention exists to give mutual recognition of copyright and not require products to be marketed in a country to be protected in that country. ChristianKl❫ 00:13, 10 November 2022 (UTC)
That’s not the point. There are probably many people in the world who want to read Japanese comics, but cannot read Japanese. That’s the reason why scanlation (and regular translation) exists in the first place. Of course it would be better if they paid the original authors, but the author doesn’t get any money regardless of whether someone abroad reads their comic in scanlation form (without paying) or doesn’t read it at all. Hence the “financial” point of view doesn’t get us anywhere here. There’s more to copyright than remuneration (and the Berne convention presumably exists regardless of financial considerations). --2A02:8108:50BF:C694:E83C:EBFF:49AF:23CC 12:45, 10 November 2022 (UTC)
Copyright is driven by actual laws. You might disagree with those laws but they exist. Scanlation clearly creates deriviative works of copyrighted works. In the US context where Wikimedia has it's legal home, that's forbidden by copyright law unless you have permission or can argue for fair use. Courts have made many rules on copyright and have developed a concept of financial interests in the process. You might not like it or disagree with it, but that's still the law of the land. ChristianKl❫ 12:20, 12 November 2022 (UTC)
Neither do I disagree with copyright laws (where did I claim that?) nor do I deny that scanlation violates them. All I’m saying is that it does not hurt the authors financially and that the claim by Afaz that they infringe on “the financial benefits that copyright holders rightfully deserve” is therefore misleading. Of course they have “financial interests” – they are selling their works in Japan, after all –, but that’s different from “financial benefits”. (Easy example: A greengrocer has a financial interest in getting vegetables sold, but no financial benefit if nobody buys them – a reason for which might be that all the people who would like to buy them live in another city. Does this make stealing the vegetables from the greengrocer and giving them away for free in that other city legal? Obviously not. Does the greengrocer have a financial damage? No, he doesn’t receive money for the vegetables anyway.) But let’s stop this pointless discussion here – both of us agree that scanlation is a copyright violation, while we seem to disagree on why it is (or maybe not; the deriviative work argument is independent of financial aspects, and I’m not sure the US context is actually necessary for it, but anyway). The reason why it derailed was probably my justification for the continuing widespread existence of scanlation despite its illegality – which is unnecessary for the point I wanted to make, I think (now). --2A02:8108:50BF:C694:29E6:BE9C:1625:78C8 20:07, 12 November 2022 (UTC)
The reason why I’m so nit-picky about this is that it often gets mixed up. If remuneration were the problem, scanlators could solve it by taking money from their “customers” and using it to pay the original authors – but in the absence of permission to do so this would still be a copyright violation. That there is more to copyright than remuneration can also be seen in the advent of Creative Commons licences, where copyright holders waive their right to remuneration without (necessarily) waiving other rights they deserve, such as proper attribution (a misconception many have: “It’s free, so I can use it any way I want”). --2A02:8108:50BF:C694:29E6:BE9C:1625:78C8 20:33, 12 November 2022 (UTC)
  • Pictogram voting question.svg Question I see questions of copyright here but if this was actually an issue of concern with wiki projects merely linking, then wouldn't this be a major issue with wiki projects linking to the Internet Archive (Internet Archive ID (P724) and the works there that are still under copyright? If there isn't an issue with that I dont see the issue here. -Jeanjung212 (talk) 20:51, 18 November 2022 (UTC)
@Jeanjung212: Can you link any item there where the site infringes the copyright? On the first look, all the content looks like public domain and creative commons as well as previews. Also, not that copyright is not the problem. There are also links to Netflix. Copyright infringement is the problem. --Christian140 (talk) 07:58, 19 November 2022 (UTC)
This website (linked from Tetris (Q71910)), for example, doesn’t seem to be public domain, so technically (ianal) the Internet Archive is infringing on the creator’s copyright by making a copy of it available. (It’s just that no one bothers to sue the Internet Archive, I think.) --Data Consolidation Officer (talk) 21:11, 21 November 2022 (UTC)
Hmmm. But on all websites where every user can upload content, copyright infringement happens. On wikipedia and commons, too. Just, eventually it gets deleted. However, for mangadex, copyright infringement is the core of the website. For internet archive, they have this site: Rights – Internet Archive Help Center. So, you could report content you think that infringes copyright. But here, I am actually not sure if it is copyright infringement. A lot of old software is made available for free and you can download them from many serious websites. --Christian140 (talk) 08:01, 22 November 2022 (UTC)
Internet Archive, or archiving in general, might even be covered by Fair Use (I simply don’t know). And given the large number of pages archived there, reporting copyright violations would be a Sisyphean task. As I stated below, I don’t think there’s a legal issue with mere linking, but P10589 is very dispensable anyway. --Data Consolidation Officer (talk) 20:23, 22 November 2022 (UTC)
  • Pictogram voting comment.svg Comment Linking doesn’t mean endorsing, afaik, so the site’s copyright violations alone wouldn’t be valid grounds for deletion of this property. Having a look at the property proposal discussion, however, it seems that the property was created without thorough discussion, basically because “I think properties for it would be useful”. Wikidata should, imho, be extremely restrictive with respect to which external databases it chooses to systematically link, given the considerable effort of maintaining such link collections, avoiding inconsistencies and so on. That’s why I’d tend to vote for deletion at the moment, unless someone provides a good reason why having external identifier links to the site in question is essential. --Data Consolidation Officer (talk) 21:03, 21 November 2022 (UTC)
    It's 100% endorsing. You're exposing the copyrighted works to a wider audience by linking to them. You're clearly assisting in their distribution. Lectrician1 (talk) 21:30, 21 November 2022 (UTC)
    Sorry, I should have made clearer that I was specifically talking about legal issues. There can of course be ethical issues with linking (depending on intention), but afaik (and ianal, so please correct me if I’m wrong) courts in various contries have established that website operators cannot be held liable for criminal violations by other sites they merely link, so Wikimedia Foundation could not be (successfully) sued for those links or something like that. Anything else is a question of whether we, as a community, want those links, but as I said, I don’t really see any reason anyway why we should. --Data Consolidation Officer (talk) 20:12, 22 November 2022 (UTC)
    There's a difference between having a simple link to MangaDex and having a system on Wikidata that tells Wikidata users for every manga, the exact page where they can download a copyright violating copy of that manga. Having a link to every single manga, is like torrent websites that link to individual content and torrent websites do face legal problems. ChristianKl❫ 11:12, 27 November 2022 (UTC)
    Which all the more raises the question why Wikidata would want such a system in the first place; a question the answer to which I still don’t see. Given that it took nine months (the property was created in early April) until someone noticed that there are copyright violations linked, I wouldn’t consider any claim about copyright infringement endorsement intentions plausible (in contrast to torrent sites; and indeed those links will have been created in good faith in most cases), but let’s the lawyers fight that out (or not). --Data Consolidation Officer (talk) 19:36, 27 November 2022 (UTC)
    Symbol delete vote.svg Delete, as indicated, on the grounds that there has been no good reason given why having external identifier links to the site in question is essential. --Data Consolidation Officer (talk) 19:36, 27 November 2022 (UTC)


preceding halt on service (P10808): (delete | history | links | entity usage | logs | discussion)

Not a single statement since creation per this query💬✒️💛 14:03, 6 November 2022 (UTC)

Seems use of this property have started in some qualifyers. No longer asking deletion. Bouzinac💬✒️💛 09:27, 23 November 2022 (UTC)


following halt on service (P10809): (delete | history | links | entity usage | logs | discussion)

Not a single statement since creation per this query💬✒️💛 14:01, 6 November 2022 (UTC)

Seems use of this property have started in some qualifyers. No longer asking deletion. Bouzinac💬✒️💛 09:27, 23 November 2022 (UTC)

On holdEdit

These discussions have been closed but are awaiting deletion.

IPA number order (BEING DELETED) (P3917)Edit

Implementation notesEdit

Data has been migrated to catalog code (P528) qualified by IPA number (Q110910334). A few templates need to be updated to use the new format. — Martin (MSGJ · talk) 22:38, 13 February 2022 (UTC)

@Amitie 10g: please check my edit to es:Plantilla:Ficha de fonema. Thanks — Martin (MSGJ · talk) 22:49, 13 February 2022 (UTC)

Templates to update:



@putnik: biography pages (BEING DELETED) (P1996) has 2045 statements but member ID (P10428) only has 1935. Are you sure all useful data has been migrated? — Martin (MSGJ · talk) 11:49, 18 May 2022 (UTC)

@MSGJ, yes. biography pages (BEING DELETED) (P1996) has only 1934 unique values. Everything else are duplicate IDs with different links, e.g. commons/mr-nigel-dodds/1388 and commons/nigel-dodds/1388. —putnik 12:36, 18 May 2022 (UTC)
Thank you for clarifying — Martin (MSGJ · talk) 12:39, 18 May 2022 (UTC)

All main statements removed. There are about 85 references using this property still remaining — Martin (MSGJ · talk) 21:20, 23 May 2022 (UTC)




I see clear consensus to delete lunar coordinates (BEING REPLACED) (P8981) and replace it with coordinate location (P625). @Mike Peel: do you have a bot to do that? Multichill (talk) 15:41, 17 October 2022 (UTC)

Thanks for closing it. I should be able to migrate values over soon. Thanks. Mike Peel (talk) 17:48, 18 October 2022 (UTC)


Usage needs to be removedEdit

Usage needs to be removed. You can ping me when that's done so the property can be deleted. Multichill (talk) 16:03, 17 October 2022 (UTC)