Wikidata:Properties for deletion/Archive/2022/1
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion. |
Contents
- 1 demonym (P1549)
- 2 doctoral student (P185)
- 3 student (P802)
- 4 opponent during disputation (P3323)
- 5 has edition or translation (P747)
- 6 mountain range (P4552)
- 7 P7335 (P7335)
- 8 political ideology (P1142)
- 9 religion or worldview (P140)
- 10 political alignment (P1387)
- 11 P4883 (P4883)
- 12 liturgical rank (P9002)
- 13 P3043 (P3043)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- No consensus. After a multi-year discussion, there's no consensus to delete or keep this, but the !votes are leaning towards keep (8 for delete, 12 for keep). In particular, there's no clear migration plan, and the information stored using this property is used a lot in infoboxes and elsewhere. Thanks. Mike Peel (talk) 19:03, 21 January 2022 (UTC)
demonym (P1549): (delete | history | links | entity usage | logs | discussion)
I think this property could be replaced with one that links to senses (e.g. sense 1 of Kenyan (L35249)); this would be especially useful for words with lots of conjugations. I have not created a new property proposal because it would be more appropriate to have the discussion in one place.
I've already created 161 English noun lexemes which would be able to replace current uses; it would also be necessary to create equivalent items for adjectives, as well as to create the relevant senses for the noun and adjective lexemes (I've only added a sense to L35249 so far). —Jc86035 (talk) 10:33, 4 November 2018 (UTC)
Notified 94 contributors to the property and its talk page: User:Nikki User:Abián User:Jura1 User:VIGNERON User:Tubezlob User:Jheald User:Lockal User:Infovarius User:Putnik User:Laddo User:Kalogeropoulos User:Innocent bystander User:Event User:Jakec User:Vinhtantran User:MaGa User:Labant User:K175 User:Autom User:Robin van der Vliet User:Matěj Suchánek User:Janezdrilc User:Ctschiebout User:Kevin Scannell User:Maria zaos User:Horcrux User:Soued031 User:Metsavend User:Obaid Raza User:İncelemeelemani User:Pinky sl User:Andreasmperu User:Рөстәм Нурыев User:Pmt User:Gustavo Rubén User:Oriciu User:Mr. Ibrahem User:زكريا User:ToJack User:Taravyvan Adijene User:Arnaugir User:MisterSynergy User:AmaryllisGardener User:Beta16 User:Mahir256 User:Спасимир User:Asierog User:Avatar6 User:Wylve User:Şêr Jc86035 (talk) 10:39, 4 November 2018 (UTC) User:Krupolskiy Anonim User:YMS User:ಶಿವಕುಮಾರ್ ನಾಯಕ್ User:Hibm98 User:GAllegre User:Epìdosis User:Jklamo User:David1010 User:SR5 User:Máté User:Ślimaczek User:HakanIST User:FocalPoint User:Allen4names User:Mbch331 User:Zygimantus User:Fnielsen User:Peppepz User:Geraki User:Supaplex User:Thierry Caro User:NMaia User:Loischantada User:ANDROBETA User:Marklar2007 User:Kikos User:Raid5 User:Doostdar User:Palapa User:Octahedron80 User:Милан Јелисавчић User:Frokor User:Rippitippi User:Conny User:Qllach User:Miguillen User:יונה בנדלאק User:Liuxinyu970226 User:桂鷺淵 User:Bjankuloski06 User:Thomas11 User:Ayack User:Чаховіч Уладзіслаў User:Александр Сигачёв Jc86035 (talk) 10:41, 4 November 2018 (UTC)
- Eventually, but maybe we should have the discussion at one place: Wikidata:Property_proposal/demonym_of. --- Jura 12:00, 4 November 2018 (UTC)
- Oh, I didn't realize there was already such a proposal. Jc86035 (talk) 14:56, 4 November 2018 (UTC)
I would like to note that the property is used as label for country of citizenship (P27) at huwiki. If the property is deleted, the current data needs to be imported into the newly accepted structure, and huwiki needs to be notified to create a workaround to the new structure if possible. Ideally, the new structure should make it possible. – Máté (talk) 12:10, 4 November 2018 (UTC)
- This is also the case for WD powered templates at svwiki, frwiki and probably many more. /Autom (talk) 13:13, 4 November 2018 (UTC)
- @Máté, Autom: Where is it used on huwiki/svwiki/frwiki? Those are not listed in the box on the talk page, perhaps the script which looks for property usage can be improved. @Jc86035: Please notify the projects using this property too. - Nikki (talk) 14:52, 4 November 2018 (UTC)
- @Nikki: hu:Sablon:Személy infobox of the top of my head. – Máté (talk) 14:58, 4 November 2018 (UTC)
- @Nikki: On svwp, it is used by the module Wikidata2, which in invoked by a lot of templates (like Faktamall biografi WD in biografies). I know frwiki had a similar system a year ago (it's possible it has change since then). /Autom (talk) 18:25, 4 November 2018 (UTC)
- @Autom: Do you have any specific place where this spcific property is used on svwiki? I see many potential problems with this property in the Swedish language, so at least I have never tried to use or even edit it. Sextvå.tvånoll.ettsjunoll.sjufyra (talk) 17:03, 19 April 2019 (UTC)
- @Sextvå.tvånoll.ettsjunoll.sjufyra: It is used to display nationality in Faktamall biografi WD (via Wikidata2). In the article Bill Gates, the template does not return "USA" but "Amerikan", which is the value of demonym (P1549) [common (Q1305037), singular (Q110786)] of United States of America (Q30) (the country of citizenship (P27) of Bill Gates (Q5284)). /Autom (talk) 14:11, 20 April 2019 (UTC)
- @Autom: Do you have any specific place where this spcific property is used on svwiki? I see many potential problems with this property in the Swedish language, so at least I have never tried to use or even edit it. Sextvå.tvånoll.ettsjunoll.sjufyra (talk) 17:03, 19 April 2019 (UTC)
- @Nikki: On svwp, it is used by the module Wikidata2, which in invoked by a lot of templates (like Faktamall biografi WD in biografies). I know frwiki had a similar system a year ago (it's possible it has change since then). /Autom (talk) 18:25, 4 November 2018 (UTC)
- @Nikki: hu:Sablon:Személy infobox of the top of my head. – Máté (talk) 14:58, 4 November 2018 (UTC)
- @Máté, Autom: Where is it used on huwiki/svwiki/frwiki? Those are not listed in the box on the talk page, perhaps the script which looks for property usage can be improved. @Jc86035: Please notify the projects using this property too. - Nikki (talk) 14:52, 4 November 2018 (UTC)
- Delete but probably wait some weeks/months until Lexemes are more stable. Cdlt, VIGNERON (talk) 12:17, 4 November 2018 (UTC)
- I agree that we should eventually replace the existing property with lexemes, but we shouldn't delete this until people are able to switch to using lexemes. We still need to decide how we want to link things together. - Nikki (talk) 14:52, 4 November 2018 (UTC)
- Delete The property demonym of (P6271) has been created. This one can now be deleted (first declare obsolete, move content, then delete).--Micru (talk) 17:30, 19 December 2018 (UTC)
- Comment If this property is being used in an infobox or by a Lua module, it will need to be retained and to go on having its values added to and extended, at least and until such time as inverse property values become obtainable via Lua - as at present they are not. Jheald (talk) 18:09, 19 December 2018 (UTC)
- On hold. I agree with Jheald that we need a place -> demonym property to keep infoboxes working. We should keep this property until we have a new Item -> Lexeme "demonym" property, migrate all existing uses and infoboxes, then delete P1549. Deryck Chan (talk) 15:52, 11 January 2019 (UTC)
- Delete Very barely used, and replacement is even available for these not more than 100 usages. --Liuxinyu970226 (talk) 12:44, 16 March 2019 (UTC)
- On hold. Until infoboxes (as happens in cawiki) can be transformed after have access via LUA module. Thanks, Amadalvarez (talk) 12:47, 26 March 2019 (UTC)
- Comment. As noted, 1) there is no wikibase client for lexemes, 2) there is no Lua function available for backlinks or API queries, pending of phab:T185313 that it seems silently declined for a year now. There is not any path from a wiki page like w:fr:Paris to reach Parisien (L26359). If these blockers are solved, there are still some concerns. How to deal with Parisien (L26359) or Parisienne (L25620)? How to obtain the demonym for a given language and a lexical category? At the end, it will be one more, or several, arbitrary access and it is expensive in Lua time usage that has limitations in infoboxes powered by Wikidata. --Vriullop (talk) 07:52, 27 March 2019 (UTC)
- Keep Keep this property because with this property is very easy to add some data. --Manu1400 (talk) 21:43, 18 August 2019 (UTC)
- Keep Very helpful, easy to use. HarryNº2 (talk) 12:07, 19 November 2019 (UTC)
- Keep Useful. --Obsuser (talk) 14:14, 25 November 2019 (UTC)
- Neutral
KeepHow to call an inhabitant of a neighborhood? We must also think of other languages. Nothing can replace it, for the moment. Examples: Germanopratin in Saint-Germain-des-Prés (Q604717), Planpalistain in Plainpalais (Q2546289). —Eihel (talk) 09:59, 26 November 2019 (UTC)- @HarryNº2, Obsuser: Please do not just say "keep" for things that are under deletion discussions as simple and confusing "useful", P5130 (P5130) (landmass) was also useful until we have consensus for its deletion. --Liuxinyu970226 (talk) 15:09, 28 November 2019 (UTC)
- Delete Doesn't useful, replacement available. --2409:8902:9001:6CE0:781B:941D:E99A:2367 00:16, 4 December 2019 (UTC)
- Keep Used in Wikipedias, no replacement for infoboxes seems to be available. Michael FV (talk) 03:00, 9 January 2020 (UTC)
- @Manu1400, HarryNº2, Obsuser, Eihel, Michael FV: Why do you all can't agree with demonym of (P6271) as replacement? --Liuxinyu970226 (talk) 00:34, 10 January 2020 (UTC)
- I already put a comment on my opinion Liuxinyu970226, so I return 2 questions to you: How to assemble planpalistain with Plainpalais (Q2546289) since planpalalistain does not exist? How to add Saint-Germain-des-Prés (Q604717) in germanopratins (Q3104247) without this page appearing in Wikidata:Database reports/Constraint violations/P6271? With demonym (P1549), it's possible without error. —Eihel (talk) 01:48, 10 January 2020 (UTC)
- Opinion changed —Eihel (talk) 06:18, 2 March 2021 (UTC)
- I already put a comment on my opinion Liuxinyu970226, so I return 2 questions to you: How to assemble planpalistain with Plainpalais (Q2546289) since planpalalistain does not exist? How to add Saint-Germain-des-Prés (Q604717) in germanopratins (Q3104247) without this page appearing in Wikidata:Database reports/Constraint violations/P6271? With demonym (P1549), it's possible without error. —Eihel (talk) 01:48, 10 January 2020 (UTC)
- @Manu1400, HarryNº2, Obsuser, Eihel, Michael FV: Why do you all can't agree with demonym of (P6271) as replacement? --Liuxinyu970226 (talk) 00:34, 10 January 2020 (UTC)
- Delete Use demonym of (P6271) instead. --117.136.54.109 22:33, 20 January 2020 (UTC)
- Keep: it is used in too many places and its replacement is immature. Palotabarát (talk) 23:57, 26 January 2020 (UTC)
- Delete: With demonym of (P6271) we have now a good option to link from lexeme senses to locality items and since the items work without demonyms, but the words/lexemes are literally filled with sense, the connection should come from that end. --CamelCaseNick (talk) 01:41, 22 February 2020 (UTC)
- Keep: I think this one is very simple to maintain. I didnt very much understand the point for suppression?
- Too complicated to query both Qid and Lexemes.Infobox should be looking only on Qid not on lexemes. Bouzinac (talk) 09:45, 25 June 2020 (UTC)
- Delete Replacement available. --111.32.68.231 02:35, 9 May 2020 (UTC)
- Delete Having the information on the country makes country items that are already quite big bigger. The information is much better stored as sense. ChristianKl ❪✉❫ 21:32, 18 May 2020 (UTC)
- Keep: Designating the inhabitants of a place by a specific name can be useful. Otherwise should we replace it with a longer expression ? Cquoi (talk) 10:49, 7 June 2020 (UTC)
- On hold : the comments of Jheald and Vriullop sound pretty relevant to me, there are blocking points, so keep it for now. --FoeNyx (talk) 23:13, 15 November 2020 (UTC)
- Keep useful to designate inhabitants of a place. PAC2 (talk) 20:05, 10 January 2021 (UTC)
- Keep Using lexeme senses is a poor replacement since there will be one claim per language instead, severely bloating the item. It's better that the sense links to an item like we do today. Ainali (talk) 15:15, 12 February 2021 (UTC)
- Keep Extremely useful when translating label, descriptions, including in wikipedia templates.--Mikey641 (talk) 02:04, 9 March 2021 (UTC)
- Keep This is good for Wikidata but bad for infoboxes: Inverse properties is problematic, since is harder to code templates or modules to emulate the expected behaviour with inverse properties, and most of the nominators of those deletion request don't even address the problems that leads this deletions. One of the warnings says clearly:
Validate the property isn't being used in other projects (using
{{ExternalUse}}
)- and if it is leave a message in Village pump of those projects! and this is an obvious case of potential use, and as this is already used, this request should be speedy closed. This should be discussed on other projects like Wikipedia first! --Amitie 10g (talk) 17:46, 15 July 2021 (UTC)
- Keep Nouns of countries are usually well known, Gentilés could be a question. I cannot understand how "Gentilé of" would help to find the gentilé of a country or a place. --Pa2chant.bis (talk) 07:35, 15 September 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. From the discussion it seems clear that while the data is redundant, the inverse is still important for uses of the data. Thanks. Mike Peel (talk) 19:13, 21 January 2022 (UTC)
doctoral student (P185): (delete | history | links | entity usage | logs | discussion)
Generally too many. Inverse should be sufficient --- Jura 17:59, 12 July 2019 (UTC)
- Keep because it appears in infobox templates. Sensitivedonkey (talk) 07:32, 18 July 2021 (UTC)
Keep: useful IMHO. Nomen ad hoc (talk) 18:03, 12 July 2019 (UTC).Delete: in reflection, could probably be replaced by doctoral student (P185). Nomen ad hoc (talk) 11:31, 17 July 2019 (UTC).- You are suggesting to replace doctoral student (P185) with doctoral student (P185)? Haansn08 (talk) 06:06, 14 December 2021 (UTC)
Delete: redundant with doctoral advisor (P184). Ghouston (talk) 21:33, 12 July 2019 (UTC)- ? doctoral advisor (P184) for 'teacher', doctoral student (P185) for 'student'. What proposed mechanism of replacement in templates? --Dim Grits (talk) 12:12, 15 July 2019 (UTC)
- I voted delete because I don't like redundancy in databases. But you are right, if it's used in templates then there's no proper mechanism for obtaining inverse properties. It's a technical flaw and the inverse properties may be needed. I'd have to look at it in more detail before voting. Ghouston (talk) 22:43, 23 February 2020 (UTC)
- Keep Because pair p184-p185 oldest and specialized than universal student (P802), student of (P1066). @@Deryck Chan: It's clear for me (and You). I asked about mechanism of merging. And seeing propose souris + suricate now. For why? Because they Tetrapoda :) --Dim Grits (talk) 15:05, 18 July 2019 (UTC)
- Delete: redundant with doctoral advisor (P184). Moreover, "student" word does not make understand that the activity of a PhD is the one of a researcher, "PhD candidate" would have been more convenient --Lupin~frwiki (talk) 11:50, 16 July 2019 (UTC)
- Delete: It is true. Redundant with doctoral advisor (P184). --İncelemeelemani (talk) 19:24, 17 July 2019 (UTC)
- Delete - redundant with doctoral advisor (P184). Many-to-one database relationships should be one-directional in Wikidata. Kaldari (talk) 15:15, 9 September 2019 (UTC)
- Keep @Kaldari, İncelemeelemani, Lupin~frwiki, Ghouston: it isn't redundant, it is an opposition to that item. As Dim Grits said, doctoral advisor (P184) is for "teacher", but doctoral student (P185) is for student! Sincerely, Nadzik (talk) 13:30, 23 February 2020 (UTC)
- @Nadzik: Of course they mean different things, that's obvious. I meant that it's a redundant database relationship. As an analogy, we don't list all the species that fall under a genus item in Wikidata, instead we list the genus from the species item. Many-to-one database relationships should be one-directional in Wikidata. Kaldari (talk) 16:01, 25 February 2020 (UTC)
- Comment this may also sometimes be a many-to-many relationship as one student can have multiple advisors. --Hannes Röst (talk) 01:28, 10 June 2020 (UTC)
- @Nadzik: Of course they mean different things, that's obvious. I meant that it's a redundant database relationship. As an analogy, we don't list all the species that fall under a genus item in Wikidata, instead we list the genus from the species item. Many-to-one database relationships should be one-directional in Wikidata. Kaldari (talk) 16:01, 25 February 2020 (UTC)
- @Nadzik, Dim Grits:: I realize I did not gave the international references on which I based my point, thank you for making me remind this: doctoral advisor (P184) and doctoral student (P185) do not designate the usual context of professor (or teacher) and student, since "PhD candidates are persons professionally engaged in R&D" (researchers) as stated in the Euraxess Charter & Code principles (https://euraxess.ec.europa.eu/sites/default/files/am509774cee_en_e4.pdf page 28-29). They details "The term Early-Stage Researcher 19 refers to researchers in the first four years (full-time equivalent) of their research activity, including the period of research training". This doc is endorsed by a lot of famous institutions and countries (see https://euraxess.ec.europa.eu/jobs/charter/declaration-endorsement).
Ping Danrok, Zolo. Nomen ad hoc (talk) 07:26, 14 July 2019 (UTC).
- Also @Dim Grits, Hannolans, İncelemeelemani, Emptyfear, AttoRenato:@Lupin~frwiki, Mormegil, Rooiratel, Dumbassman: Those who recently edited this property. --Liuxinyu970226 (talk) 11:47, 15 July 2019 (UTC)
- Also @Cgolds: who opened a related discussion on French Bistro, and who just suggested only keeping student (P802). Nomen ad hoc (talk) 06:46, 17 July 2019 (UTC).
- Keep. Infoboxes about professors often include a short list of prominent doctoral students. The inverse may be sufficient to generate a list of all students who have their own Wikidata items, but this property allows further curation of who are the most important students using ranks. @Lupin~frwiki: "PhD candidate" and "doctoral student" have different boundaries (other kinds of doctorate are not included) and different universities use different names, so I wouldn't advise rescoping the property.
- Ok, I understand. So you would use this property for medicine doctorate for instance, I understand. Then "doctoral candidate" could then be much more convenient than "doctoral student". Do you agree? --Lupin~frwiki (talk) 14:22, 17 July 2019 (UTC)
- Probably not physician (Q39631), but likely to include other kinds of doctorates conferred after academic study: Doctor of Education (Q837184), Doctor of Engineering (Q17119067), Doctor of Laws (Q959320) and the University of Oxford which call their doctors of philosophy "DPhil" rather than "PhD". Deryck Chan (talk) 15:32, 19 July 2019 (UTC)
- If I formulate it differently, you argue that doctoral "student" would be more convenient to use for medicine doctor candidate than doctoral candidate which should be used for research doctor candidate. I understand that either the difference between both people is notable and we should classify medicine doctors as students with field medicine or it is not and we should consider them as candidates.Lupin~frwiki (talk) 11:05, 29 July 2019 (UTC)
- Yes, that's right. Deryck Chan (talk) 10:42, 29 August 2019 (UTC)
- If I formulate it differently, you argue that doctoral "student" would be more convenient to use for medicine doctor candidate than doctoral candidate which should be used for research doctor candidate. I understand that either the difference between both people is notable and we should classify medicine doctors as students with field medicine or it is not and we should consider them as candidates.Lupin~frwiki (talk) 11:05, 29 July 2019 (UTC)
- Probably not physician (Q39631), but likely to include other kinds of doctorates conferred after academic study: Doctor of Education (Q837184), Doctor of Engineering (Q17119067), Doctor of Laws (Q959320) and the University of Oxford which call their doctors of philosophy "DPhil" rather than "PhD". Deryck Chan (talk) 15:32, 19 July 2019 (UTC)
- Ok, I understand. So you would use this property for medicine doctorate for instance, I understand. Then "doctoral candidate" could then be much more convenient than "doctoral student". Do you agree? --Lupin~frwiki (talk) 14:22, 17 July 2019 (UTC)
@Dim Grits: I think doctoral student (P185), doctoral advisor (P184) serve a different purpose from student (P802), student of (P1066). These two SPARQL queries [1][2] show editors have found uses in over 1000 biographical items where distinguishing between doctoral student-teacher relationships and other student-teacher relationships has been helpful. Deryck Chan (talk) 17:33, 16 July 2019 (UTC)
- Comment A big problem imho that also concerns student (P802) has been to establish an inverse property constraint. The property would be totally valid as a way to store the main students or Phd candidates of a teacher. Currently most of the student of (P1066)/doctoral advisor (P184) relationships that I have filled during the past years have been also reversed (either by bot or by well-meaning users attempting to "correct" an apparent error) making the student (P802)/doctoral student (P185) information meaningless. I would agree to keep this property along with student (P802) if the constraint is entirely lifted. Alexander Doria (talk) 18:40, 16 July 2019 (UTC)
- @Alexander Doria: I tend to agree that student of (P1066) and student (P802) should be inverse properties. Importance can be marked using rank, rather than removing unimportant (but truthful) entries. Deryck Chan (talk) 15:32, 19 July 2019 (UTC)
Agree too. Only mentioning "notable" students is IMHO too arbitrary... especially if "notability" isn't properly defined. Nomen ad hoc (talk) 15:38, 19 July 2019 (UTC).- Agree tooLupin~frwiki (talk) 11:05, 29 July 2019 (UTC)
- Consistency can be assured but some work is needed. We can get the same information without this property. Use this kind of property to distinguish some items of the set does not seem a good idea since the choice of each item can be discussed and different in every country, field, etc. This selection should be let to each wikipedia page imho. --Lupin~frwiki (talk) 14:22, 17 July 2019 (UTC)
- @Alexander Doria: I tend to agree that student of (P1066) and student (P802) should be inverse properties. Importance can be marked using rank, rather than removing unimportant (but truthful) entries. Deryck Chan (talk) 15:32, 19 July 2019 (UTC)
- Delete as redundant. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:22, 23 July 2019 (UTC)
- Delete A Wikipedia that only wants notable students via reverse lookup can simply only display students for which they have an article. ChristianKl ❪✉❫ 10:07, 8 August 2019 (UTC)
- @ChristianKl: Reverse lookup is hideously difficult in Lua... It's better to have a property to curate a list of notable students separately. Many infoboxes (e.g. w:en:Template:Infobox academic) include a "notable students" field, which if implemented using Wikidata should be P185 with preferred rank. Deryck Chan (talk) 10:42, 29 August 2019 (UTC)
- Keep People that consider it is redundant with doctoral advisor (P184), may be doesn't know that is impossible to get information via backlinks from LUA module and, of course, from infoboxes and any kind of wiki templates. SPARQL is a partial solutions for the real uses of WD, nowadays. If I'm wrong and somebody has a solutions to make some kind of haswbstatement from wiki templates or LUA Modules, please just tell me. Thanks. Amadalvarez (talk) 16:16, 12 August 2019 (UTC)
- Listeria can provide you with such lists. --- Jura 17:21, 17 October 2019 (UTC)
- Comment Not within a Infobox or any other template. Listeria must be applied article by article because it contains (written inside the SPARQL code) the specific Qid related with a specific item. So, it can't be used in a template that act with the Qid of the present article. Amadalvarez (talk) 17:31, 11 November 2019 (UTC)
- @Amadalvarez: Shouldn't you change your second
{{Keep}}
to{{Comment}}
or other suitable template, to avoid "multiple voting" problems? --Liuxinyu970226 (talk) 11:35, 20 November 2019 (UTC). Done, excuse me.Amadalvarez (talk) 15:55, 20 November 2019 (UTC)
- @Amadalvarez: Shouldn't you change your second
- Comment Not within a Infobox or any other template. Listeria must be applied article by article because it contains (written inside the SPARQL code) the specific Qid related with a specific item. So, it can't be used in a template that act with the Qid of the present article. Amadalvarez (talk) 17:31, 11 November 2019 (UTC)
- Delete Redundant inverse. --Yair rand (talk) 19:46, 15 September 2019 (UTC)
- Neutral to Keep As mentioned in the P802 deletion discussion below, I'm not so sure the breakage of "inverse" is a good idea based on any of the comments shared above. It was introduced once and I have a feeling it would be reintroduced. If the problem is that doctoral student (P185) is overused, relevance should be enforced harder. On the other hand, I think student (P802) is a better property for "famous apprentice". Jagulin (talk) 17:00, 17 October 2019 (UTC)
- doctoral student (P185) is not overused. It's just defined as an inverse of its inverse. --- Jura 17:21, 17 October 2019 (UTC)
- Keep At least on zhwiki, the Listeria datas can't work well, it only pollutes with English-only text, and has no easy way to translate. --Liuxinyu970226 (talk) 03:40, 6 November 2019 (UTC)
- Delete or change to something more specific. Infoboxes don't show all doctoral students, do they? Michael FV (talk) 03:07, 9 January 2020 (UTC)
- Keep At least in Vietnamese, you really can't make confusions between nghiên cứu sinh (doctoral student) and cố vấn tiến sĩ (doctoral advisor). By following these vote-deleters' comments, it looks like some users are misleaded by their wrong translations of P184 and P185, a translation review is needed, note that I've corrected the Vietnamese translations. --117.136.54.109 22:43, 20 January 2020 (UTC)
- I don't think the people who are saying they are redundant think they are the same thing. They are saying that the two-way database relationship is redundant. Kaldari (talk) 17:37, 25 February 2020 (UTC)
- Keep: useful IMHO.--Cbyd (talk) 20:55, 19 February 2020 (UTC)
- Keep Has language conflicts. --111.32.68.231 02:37, 9 May 2020 (UTC)
- This could be an additional argument for deletion. --- Jura 10:10, 21 November 2020 (UTC)
- Comment please note that for many Wikipedias it would more useful to list noteable students and postdoctoral researchers, therefore for articles about a professor it would be important to have a list of all personnel that s/he advised (students, postdocs, research associates etc). Some students switch fields after their PhD and their postdoc advisor is much more important for their career than their PhD advisor (at least in my field where long postdocs are common). Therefore it may make sense to change the categories to a advisor/advisee relationship that is more broad than doctoral student/advisor only. --Hannes Röst (talk) 01:33, 10 June 2020 (UTC)
- @Hannes Röst: this is merely for "doctoral students". The inverse will still be available at "doctoral advisor" Property:P184. Correct referencing is probably more easily done on the later. --- Jura 10:10, 21 November 2020 (UTC)
- Keep - I can not see any cause for a deletion. Ofcourse such relationships are two-way-relationships. This must be always and in every data set. Either what we're doing here is serious work or not. If so - then it has to stay. If not, we can stop the whole Wikidata project. -- Marcus Cyron (talk) 22:16, 10 June 2020 (UTC)
- @Marcus Cyron: Why would we need to repeat the inverses of thousands of "doctoral advisor" Property:P184 statements? This doesn't seem to be serious. --- Jura 10:03, 21 November 2020 (UTC)
- @Jura1: - we do this in a lot of other cases too. You always need also the inverse data. How should you know about it, if you can't see it? We talk about seeing and reading, not about a querry request! -- Marcus Cyron (talk) 11:36, 21 November 2020 (UTC)
- @Marcus Cyron: frequently we don't do this when there are 1-to-many relations. Some people are even reluctant to do it when it's a 1-1 relation (or 1 to few). I'm not really sure where one would want to read the list at Q982962#P185. How would you go about it? Where would you read it? I think one would generally query the underlying data. --- Jura 16:05, 21 November 2020 (UTC)
- @Jura1: - we do this in a lot of other cases too. You always need also the inverse data. How should you know about it, if you can't see it? We talk about seeing and reading, not about a querry request! -- Marcus Cyron (talk) 11:36, 21 November 2020 (UTC)
- @Marcus Cyron: Why would we need to repeat the inverses of thousands of "doctoral advisor" Property:P184 statements? This doesn't seem to be serious. --- Jura 10:03, 21 November 2020 (UTC)
- Keep - Useful relation. Slightly different semantics between "is/was-student-of" and "has/had-doctoral-student". In an ideal world this would be a bidirectual-many-to-many-relation. In script reality this relation seems useful. Praxis example for usefulness (use-case): "Mathematics Genealogy Project", NDSU + Am.Math.Soc. This is what Wikipedia should have for every academic profession. Best, --Christianvater (talk) 12:49, 11 June 2020 (UTC)
- @Christianvater: The inverse is "doctoral advisor" Property:P184. That usecase is still covered. --- Jura 10:03, 21 November 2020 (UTC)
- Keep Used by 35+ templates, clearly has user-case.--Jklamo (talk) 15:59, 2 January 2021 (UTC)
- Keep, an important property for science.--Arbnos (talk) 14:57, 28 April 2021 (UTC)
- Keep--Ferran Mir (talk) 07:45, 16 May 2021 (UTC)
- Keep There are both doctoral advisors (typically professor or adjunct professor/docent) and doctoral students. Kindly note that in many fields doctoral students are not Ph.D. students, as the title awarded is not Ph.D. but e.g. Ed.D., Psy.D., Mus.D., LL.D., Eng.D., etc. --Paju~wikidatawiki (talk) 00:06, 19 May 2021 (UTC)
- Keep See my above comment at #demonym (P1549), or find a solution that covers usage on other projects like Wikipedia, namely templates and modules. --Amitie 10g (talk) 17:49, 29 May 2021 (UTC)
- Delete, a redundant inverse property, often causing bloat to an entry unnecessarily. A better approach would be to press developers to improve access to backlinks. — Martin (MSGJ · talk) 13:45, 21 October 2021 (UTC)
- Keep Reverse/backlink/Listeria does not work within a Infobox or any other template. --Luamssuk (talk) 15:15, 2 December 2021 (UTC)
Translation issues?!
@Kaldari: If the problem 117.136.54.109 pointed is correct, I believe that there can in fact result some users to wrongly daydream that two properties are having same meanings in their L1(or L2?)-speaking languages, and say that "X can be simply replaced by Y" even incorrect. as of 10:04, 1 April 2020 (UTC) the translations are:
lang | P184 | P185 | P802 | P1066 |
---|---|---|---|---|
af | Doktorale student | Doktorale adviseur | student | student van |
aln | student i doktoraturës | N/A | N/A | N/A |
ar | طلاب الدكتوراه | مشرف الدكتوراه | طلاب | تتلمذ على يد تتلمذ على يد, تعلم لدى, تتلمذ على, تتلمذت على يد |
ast | N/A | direutor de tesis direutora de tesis |
estudiante discípulu, discípula, alumnu, alumna, maestru de, maestra de, profesor de, profesora de |
N/A |
az | N/A | elmi rəhbəri | tələbəsi tələbə, tələbələr, tələbələri |
müəllimi |
ba | аспиранттар | ғилми етәксе | уҡыусылар уҡыусы, студент, студенттар |
кемдә уҡыған уҡытыусы, уҡытыусылар |
be | аспіранты / дактаранты аспіранты, дактаранты, кіраўнік у |
навуковы кіраўнік | вучні вучань, студэнт |
студэнт каго Навуковы кіраўнік, настаўнік, уплыў |
be-tarask | асьпірант | навуковы кіраўнік кіраўнік |
вучаньстудэнты, вучні, студэнт | чый студэнт |
bg | аспирант докторант |
научен ръководител | студент | ученик на |
bn | N/A | N/A | ছাত্র | শিক্ষক |
br | N/A | rener-tezenn | N/A | bet studier |
bs | doktorant | savjetnik za izradu doktorata | student-asistent | student |
ca | estudiant doctoral | director de tesi director doctoral, supervisor doctoral |
estudiant alumne, mestre de, deixeble |
mestre alumne/a de, professor |
cs | doktorand | vedoucí disertační práce vedoucí práce, učitel |
student učitelem (koho), učitelkou (koho), studenti |
učitel učitelé, žákem (koho), student (koho) |
cy | myfyriwr doethurol myfyrwraig ddoethurol |
ymgynghorydd y doethor | disgybl myfyrwraig, myfyriwr |
disgybl y canlynol ahro, darlithydd, arwr |
da | doktoratsstuderende | doktoratsrådgiver | elev studerende, student |
elev af lærer, underviser, porfessor, mentor, mester |
de | Doktorand Doktoranden, Promovend, Promovendin, Doktorandin |
Promotionsbetreuer Doktorvater, Gutachter, Doktormutter |
Schüler Student |
Schüler von Lehrer |
el | διδακτορικός φοιτητής | διδακτορικός σύμβουλος | 内容单元格 | 内容单元格 |
en | doctoral student supervise |
doctoral advisor advisor, doctoral supervisor, supervisor, PhD advisor, promotor |
student students, teacher of, pupil, pupils, disciple, disciples, teacher to |
student of teacher, professor, pupil of, supervisor, academic supervisor, disciple of, studied under, master, mentor, advisor, tutor |
en-ca | N/A | N/A | 内容单元格 | student of |
en-gb | doctoral student | doctoral supervisor | student students, teacher of, pupil, pupils, disciple, disciples |
student of teacher, professor, pupil of, supervisor, academic supervisor, disciple of, studied under, master, mentor, advisor, tutor |
eo | doktorigito | doktoriginto | studento(j) | studento de |
es | doctorando estudiante doctoral |
supervisor doctoral directora de tesis, director de tesis, asesora doctoral, supervisora doctoral, asesor doctoral |
discípulo discípula, pupilo, pupila, alumno, alumna, aprendiz |
alumno de estudiante de, discípulo de, profesor, supervisor, mentor, tutor, aprendiz de |
et | N/A | doktoritöö juhendaja | õpilased | on (oli) ... õpilane |
eu | doktorego ikaslea | tesi zuzendaria | ikaslea | honen ikaslea irakasle |
fa | دانشجوی دکتری | استاد راهنمای تز دکترا | شاگردان | از دانشجویانِ |
fi | tohtoriopiskelija | väitöstyön ohjaaja ohjaava professori |
oppilas | oppilaana opettaja, mestari, mentori, ohjaaja |
fr | doctorant étudiant de thèse |
directeur de thèse directrice de thèse, responsable de thèse, thèse |
élève étudiant, maître de, professeur de, élève, disciple, apprenti |
élève de professeur, enseignant, étudiant chez, apprenti de, maître |
frr | N/A | N/A | student | student faan |
ga | N/A | comhairleoir dochtúireachta stiúrthóir dochtúireachta |
mac/iníon léinn | mac/iníon léinn de chuid |
gl | doutorando doutoranda, doutorandos, doutorandas, estudante de doutoramento, estudantes de doutoramento |
director de tese directora de tese |
docente de | alumno de |
gu | N/A | N/A | વિદ્યાર્થી | આ વ્યક્તિનો વિદ્યાર્થી |
ha | N/A | N/A | dalibi | N/A |
he | מונחה לדוקטורט דוקטורנט |
מנחה לדוקטורט | תלמיד תלמידה, תלמידים |
תלמיד של תלמידה של |
hr | student na doktoratu | mentor na doktoratu | student | 内容单元格 |
hsb | N/A | N/A | šuler student, šulerjo, studenća |
N/A |
hu | doktorandusz | témavezető | tanítvány diákjai, diák |
tanár tanítványa neki, professzor |
hy | ասպիրանտներ / դոկտորանտներ | գիտական ղեկավար | աշակերտներ | աշակերտել է ուսուցիչ |
ia | doctorando | director de these | N/A | N/A |
id | murid doktoral | penasihat doktoral | murid | murid dari |
ilo | doktoral nga estudiante | doktoral a nagbalbalakad | N/A | N/A |
is | doktorsnemi | doktorsleiðbeinandi | N/A | N/A |
it | studente di dottorato ha supervisionato, ha studente di dottorato, è stato supervisore di dottorato di |
direttore di tesi ha avuto come direttore di tesi, è stato supervisionato da |
studente discepolo, allievo, scolaro, maestro di, insegnante di, docente di, studenti, discepoli, allievi, scolari |
studente di allievo di, discepolo di, scolaro di |
ja | 博士課程指導学生 博士課程指導学生, 指導学生 |
博士論文指導教授 指導教員, 博士課程指導教授, 博士論文指導教授, 指導教授 |
弟子 教え子, 門下生 |
師匠 恩師, 教師 |
ka | დოქტორანტი | სამეცნიერო ხელმძღვანელი | სტუდენტი სტუდენტები |
ვისი მოსწავლე |
kn | N/A | N/A | ವಿದ್ಯಾರ್ಥಿ | N/A |
ko | 다음 박사과정 학생들을 지도함 박사과정, 박사과정학생, 지도 중인 박사과정, 지도했던 박사과정, 지도 중인 박사과정 학생, 지도했던 박사과정 학생, 지도 중인 박사과정학생, 지도 학생, 지도학생, 박사과정 학생, 이 교수가 지도해 준 박사과정 학생들, 이 교수가 지도해 준 박사과정 학생, 다음 박사과정 학생을 지도함, 다음 학생을 지도함, 이 교수가 지도해 준 학생들, 이 교수가 지도해 준 학생 |
박사과정 당시 지도교수 박사논문 지도교수, 지도 교수, 지도교수, 논문지도교수, 논문 지도교수, 박사과정 지도교수, 박사과정시절 지도교수, 박사과정 학생 시절 지도교수, 박사과정 학생시절 지도교수, 박사과정 시절 지도교수 |
다음의 스승이었음 학생들, 학생, 제자들, 다음을 제자로 두었음, 다음의 스승이었음, 제자, 다음의 선생이었음, 다음의 스승임, 다음의 선생임, 다음의 스승, 다음의 선생, 다음의 선생님임, 다음의 선생님 |
다음의 제자였음 선생, 교수, 지도교수, 지도 교수, 담임, 담임 교사, 담임교사, 담임선생, 다음의 제자임, 다음 교수의 제자임, 다음 선생의 제자임, 다음 교사의 제자임, 다음의 학생이었음, 스승, 스승들, 선생님, 선생님들, 선생들, 다음의 학생임, 다음의 제자, 다음의 학생 |
ksh | Dokterant Doktorand |
Doktervatter | N/A | N/A |
ku (include variants) | N/A | N/A | xwendekar | xwendekarê |
la | N/A | N/A | discipulus | praeceptor |
lb | N/A | Dokterpapp Doktermamm |
Schüler | Schüler vu(n) |
lfn | N/A | N/A | studiante | N/A |
lt | N/A | N/A | studentas | yra mokinys mokytojas |
lv | N/A | N/A | studenti skolēni |
N/A |
mg | N/A | mpitondra tezy | N/A | N/A |
mk | докторски аспирант | докторски ментор | ученик | учел кај |
ml | N/A | N/A | വിദ്യാര്ത്ഥി | N/A |
mr | N/A | N/A | विद्यार्थी | चा विद्यार्थी शिक्षक, प्रोफेसर, लेक्चरर, चा शिष्य, मास्तर |
ms | anak didik kedoktoran | penasihat kedoktoran | pelajar murid, anak didikan, mendidik, membimbing, mengajar, guru kepada, cikgu kepada, pendidik kepada, pembimbing kepada, pengajar kepada |
N/A |
nb | doktorgradsstudent | doktorgradsveileder | elev student |
elev av mentor, læremester, studerte under |
nds | N/A | Doktervader | N/A | Schöler von |
nl | promovendus | promotor | student leerling, leraar van |
student van leerling van, leermeester, leraar |
nn | doktogradsstudent | doktorgradsrettleiar | N/A | elev av |
nqo | N/A | ߞߎߡߘߊߞߎ߲ (ߕߍߛ) ߗߋߕߌ߮ | N/A | N/A |
oc | estudiant de tèsi | director de tèsi | N/A | N/A |
or | N/A | N/A | ଛାତ୍ର | N/A |
pl | doktorant nadzorowani studenci |
promotor doktoratu promotor, promotor doktorski |
student uczeń |
uczył się u studiował u, uczyła się u, studiowała u |
pt | doutorando | orientador de doutoramento | estudante aluno |
estudante de aluno de |
pt-br | doutorando | orientador de doutorado | N/A | estudante de aluno de |
ro | studenți la doctorat conducător de doctorat pentru, conducător de doctorat al, doctoranți |
conducător de doctorat conducătorul doctoratului |
studenți profesor pentru, profesor al, discipol, elev, elevi, discipoli, student |
elev al profesor, învățător, discipol al, școlit de, învățat de, student al, școlită de, învățată de, studentă a, elevă a |
ru | аспиранты / докторанты руководитель у, аспиранты, докторанты |
научный руководитель научрук, руководитель |
ученики ученик, ученица, студент, студентка, студенты |
обучался у чей студент, ученик кого, учитель, учился у, студент кого, был учеником, проходил обучение у, учителя |
sa | N/A | N/A | N/A | अस्य शिश्यः अध्यापकः, गुरुः, आचार्यस्य छात्रः |
scn | studenti di dutturatu | rilaturi dâ tesi di dutturatu | studenti | studenti di prufissuri, maistru, nsignanti |
sco | doctoral student | doctoral advisor | student | student o |
sd | N/A | N/A | شاگرد | N/A |
se | N/A | N/A | studeanta oahppi, stuđeanta |
N/A |
sl | doktorski študenti doktoranti |
doktorski mentor doktorski profesor |
študenti učenci, učil |
učenec od |
smn | N/A | N/A | uáppee | N/A |
sms | N/A | N/A | mättʼtõõtti | N/A |
sq | student i doktoraturës | këshilltar të doktoraturës mbikëqyrësi i doktoraturës |
N/A | student i |
sr (include variants) | студент на докторском раду | ментор на докторском раду | студент/student | студент код/student kod |
sv | doktorand | handledare | student | student till |
ta | முனைவர் பட்ட மாணவர் | முனைவர் பட்ட ஆலோசகர் | மாணவர்கள் | N/A |
te | N/A | N/A | విద్యార్థి విద్యార్ధులు |
ఎవరి విద్యార్థి |
tg | N/A | N/A | шогирдон | аз донишҷӯёни |
th | N/A | N/A | ศิษย์ ลูกศิษย์, นักเรียน, นักศึกษา |
N/A |
tr | doktora öğrencisi | doktora danışmanı danışman, doktora sorumlusu, sorumlu |
öğrenci | kimin öğrencisi |
ts | xichudeni xa tidyondzo tavudokodela | mutsundzuxi wa nkanelo ya tidyondzo talehenhla mutsundzuxi |
muchudeni machudeni |
xichudeni xa |
tt (include variants) | N/A | фәнни җитәкче | шәкертләр | N/A |
uk | аспіранти / докторанти здобувач ступеня |
науковий керівник | відомі учні учень, учні, студент, студенти, вчитель (для кого:) |
навчався в вихователь, керівник, ментор, професор, учитель, навчався в, навчалася в, був студентом, була студентом, був учнем, була учнем |
ur | ڈاکٹورل شاگرد | ڈاکٹورل مشیر | شاگرد طالب علم |
استاد |
vi | nghiên cứu sinh giám sát |
cố vấn tiến sĩ cố vấn, giám sát tiến sĩ, giám sát viên, Cố vấn tiến sĩ, người ủng hộ |
sinh viên giáo viên của, học sinh, đệ tử |
sinh viên của giáo viên, Giáo sư, học trò của, giám sát viên, giám sát học tập, đệ tử của, học theo, bậc thầy, người hướng dẫn, cố vấn, gia sư |
yi | דאקטאראנט | דאקטאראט-מענטאר | תלמיד | N/A |
yo | N/A | N/A | akẹ́ẹ̀kọ́ | akẹ́ẹ̀kọ́ ti ọ̀gá akẹ́ẹ̀kọ́ |
yue | N/A | 博士導師 | 學生 | 老師 師傅 |
zh (include variants) | 博士生 学习指导/學習指導 |
博士生导师/博士生導師 导师/導師, 顾问/顧問, 博士生顾问/博士生顧問 |
學生/学生 徒弟, 弟子, 门徒, 門徒 |
老師/老师 师傅/師傅, 師/师, 导师/導師, 教师/教師 |
--Liuxinyu970226 (talk) 10:04, 1 April 2020 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Same as for the discussion of doctoral student (P185), it seems clear that while the data is redundant, the inverse is still important for uses of the data, and it's not clear that the property could be merged with another. Thanks. Mike Peel (talk) 19:17, 21 January 2022 (UTC)
student (P802): (delete | history | links | entity usage | logs | discussion)
Same as for doctoral student (P185): generally too many, and redundant with the reverse property. The most prominent students could be referenced with significant person (P3342) (and a role qualified as student (Q48282)) instead. —Nomen ad hoc (talk) 19:38, 28 July 2019 (UTC)
- Delete per nomination. Nomen ad hoc (talk) 19:39, 28 July 2019 (UTC).
- Delete Idem. student (P802) was originally supposed to keep only the main students but has been used in practice as an inverse property for student of (P1066) (notably after the inception of an inverse contraint). I agree that using the property properly wasn't that obvious (sources rarely differentiate the main and secondary students of a person). Anyway, it is currently cumbersome to maintain and do not bring anything new. Alexander Doria (talk) 18:47, 29 July 2019 (UTC)
- Delete - Premeditated (talk) 07:55, 5 August 2019 (UTC)
- Neutral leaning toward Delete as it's indeed redundant wuth the inverse and it's a one-to-many relationship. Pinging the top 5 users of this property: @Simon Villeneuve, Yamaha5, Aiaiaiaiaia, Villy Fink Isaksen, AttoRenato:. Cheers, VIGNERON (talk) 06:15, 8 August 2019 (UTC)
- @VIGNERON: Is there any rule or recommendation against one-to-many or did I misunderstand why you mentioned that? I suppose student of (P1066) is also one-to-many (so actually I'd say the concepts are many-to-many). Removing student (P802) would supposedly remove also inverse claim, but it should first be investigated what that claim means in machine understanding of the property. I think many properties do enforce inverse property today, and even if it's cumbersome to maintain it might be re-added later if we can't make clear why it shouldn't. Jagulin (talk) 05:00, 17 October 2019 (UTC)
- Neutral Will somebody move the present values of P802 to P3342 ?. We access to P802 in template:infotaula persona of cawiki. I have no problem to change, but without lose the contents. Thanks,Amadalvarez (talk) 15:59, 12 August 2019 (UTC)
- We would ask a bot. Cheers, Nomen ad hoc (talk) 16:12, 12 August 2019 (UTC).
- Let me know when this should be moved. I can create a script for this. Edoderoo (talk) 17:37, 18 August 2019 (UTC)
- Thanks dear Edoderoo. Well, when (and if) a reasonable consensus will be reached? Best, Nomen ad hoc (talk) 18:26, 18 August 2019 (UTC).
- Right now, nobody is against deletion (if data is moved, which is an obvious requirement to me). Lets give it some time, it's holidays season, and there is no need to rush. Edoderoo (talk) 18:06, 19 August 2019 (UTC)
- All right. Nomen ad hoc (talk) 18:17, 19 August 2019 (UTC).
- I assume that the data moved will incorporate a qualifier object of statement has role (P3831) = schoolchild (Q48942) or similar, because P3342 is a generic property and need the person role which is implicit in the P802. Thanks !,Amadalvarez (talk) 18:18, 31 August 2019 (UTC)
- All right. Nomen ad hoc (talk) 18:17, 19 August 2019 (UTC).
- Right now, nobody is against deletion (if data is moved, which is an obvious requirement to me). Lets give it some time, it's holidays season, and there is no need to rush. Edoderoo (talk) 18:06, 19 August 2019 (UTC)
- Thanks dear Edoderoo. Well, when (and if) a reasonable consensus will be reached? Best, Nomen ad hoc (talk) 18:26, 18 August 2019 (UTC).
- Let me know when this should be moved. I can create a script for this. Edoderoo (talk) 17:37, 18 August 2019 (UTC)
- @Nomen ad hoc: Did I misunderstand that the proposition was mainly a means to remove the less prominent/relevant student-relations. Are you suggesting to move each current claim as a first step, to prevent new students added and the "relevance" evaluated over time, or that the evaluation of relevance performed before the move? Isn't the problem in that case that student of (P1066) will still be overused?
- @Nomen ad hoc: Did you also have feedback on these questions? Jagulin (talk) 16:49, 17 October 2019 (UTC)
- @Amadalvarez, Edoderoo: When you say "without loss", are you disagreeing that the student property is overused or do you just want to make sure that the important students are not lost? Would it be feasible to use student of (P1066) in infobox if that was complete enough? Jagulin (talk) 05:00, 17 October 2019 (UTC)
- We would ask a bot. Cheers, Nomen ad hoc (talk) 16:12, 12 August 2019 (UTC).
- @Jagulin: I understant this kind of properties actually mean "remarkable students", not "all the students in his/her whole life". So, if it has been overused, clean it is not a problem to me and even better for infoboxes, which must be a summary, not a list. However, may not be necessary to move to another property, but just clean it. My "do not lose" was refered to the effect of change the property, not to clean their not rellevant content. Thanks, Amadalvarez (talk) 07:18, 17 October 2019 (UTC)
- Delete, but please make sure that no data is lost (including qualifiers and sources) during the transition. --Yair rand (talk) 19:44, 15 September 2019 (UTC)
- I made a request at WD:RBOT, if there is no issue brought up I will do this task in the coming weeks, to finish this request afterwards. Edoderoo (talk) 14:49, 28 September 2019 (UTC)
- Keep if it's meant to be moved to a property other than student of (P1066). --- Jura 15:54, 28 September 2019 (UTC)
- @Jura1: I think it has been assumed that the inverse property is already matching, but you have a point in that this should be confirmed first. Do you agree that student (P802) has been overused (for non-relevant students) and should those "mistakes" be transferred to student of (P1066) by bot or removed first? I interpret your vote here as "moving to another claim will change nothing", but I'm unsure if you also mean "we should instead monitor data (e.g. relevance) and clarify the usage instructions" or "there is no problem with current usage". Jagulin (talk) 05:00, 17 October 2019 (UTC)
- Delete if moved to student of (P1066). --- Jura 15:54, 28 September 2019 (UTC)
- Keep I base this on reading the discussions here. Currently it hasn't been made clear what removal of the property would solve. I've asked for clarifications which may change my view. Current position: Monitoring data relevancy is better than making the statements more complex as a means to get less data. If "inverse constraints" are not to be used (always cumbersome to maintain), that should probably be a bigger discussion rather than per property. Jagulin (talk) 05:00, 17 October 2019 (UTC)
- Discuss @Nomen ad hoc: Did you already have a successful case with doctoral student (P185) to tell about? How did the community react to the change and what kind of bot-work was done? Jagulin (talk) 05:00, 17 October 2019 (UTC)
- Please see #Property:P185 above. Nomen ad hoc (talk) 08:07, 17 October 2019 (UTC).
- I see, so no experience yet. I suggest to not rush this change, but learn from PhD first. Jagulin (talk) 16:49, 17 October 2019 (UTC)
- Please see #Property:P185 above. Nomen ad hoc (talk) 08:07, 17 October 2019 (UTC).
- Keep: clearer relationship than anything else especially in relations from earlier centuries Palotabarát (talk) 10:39, 20 October 2019 (UTC)
- Delete Clearly-than-god no consensus to keep such old-school schema. Replacement is now available. --Liuxinyu970226 (talk) 04:54, 1 January 2020 (UTC)
- Delete too many, information should be stored by inverse. Michael FV (talk) 03:16, 9 January 2020 (UTC)
- Keep nghiên cứu sinh (doctoral student) is different by sinh viên (student) in Vietnamese. --117.136.54.109 23:11, 20 January 2020 (UTC)
- Keep Has language conflicts. --111.32.68.231 02:39, 9 May 2020 (UTC)
- Delete per nomination. --Tinker Bell ★ ♥ 03:19, 20 May 2020 (UTC)
- Keep Useful for historical people whose students are not PhD.--Midleading (talk) 04:20, 27 September 2020 (UTC)
- Keep, an important property for science.--Arbnos (talk) 14:58, 28 April 2021 (UTC)
- Keep, I watched Welcome to Demon School! Iruma-kun (Q91092801), Naberius Kalegostudent (P802)Iruma Suzuki
educated at (P69)Babyls Demon School and Iruma Suzukistudent of (P1066)Naberius Kalego educated at (P69)Babyls Demon School is valid statement--林勇智 02:38, 2 May 2021 (UTC) - Keep See my above comment at #demonym (P1549), or find a solution that covers usage on other projects like Wikipedia, namely templates and modules. --Amitie 10g (talk) 17:49, 29 May 2021 (UTC)
- Keep I use this property to record the apprenticeships of artists. - PKM (talk) 00:18, 15 October 2021 (UTC)
- Keep Important to have pupils and teachers on artist items. Many fuzzy attributions are based on these relationsips. Jane023 (talk) 12:06, 21 October 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept No consensus for deletion --Emu (talk) 00:03, 30 January 2022 (UTC)
opponent during disputation (P3323): (delete | history | links | entity usage | logs | discussion)
Too precise IMHO (less than 50 use cases); reviewed by (P4032) could be used instead (with a qualifier) —Nomen ad hoc (talk) 18:05, 10 May 2020 (UTC)
@Jura1: FYI. Nomen ad hoc (talk) 18:05, 10 May 2020 (UTC).
- Also, @Jonathan Groß, Marcus Cyron, Frank Schulenburg, Tusculum, Pigsonthewing, ChristianKl: Nomen ad hoc (talk) 18:11, 10 May 2020 (UTC). @ArthurPSmith, WiseWoman, DerHexer: Nomen ad hoc (talk) 18:11, 10 May 2020 (UTC).
- We debated a property called "proponent during disputation" why do we now have one called "opponent during disputation"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:37, 10 May 2020 (UTC)
- Because the translation of the official term “adversariorum partes suscipient” suggests opponent. ;) Best, DerHexer (talk) 18:52, 10 May 2020 (UTC)
- The proposal mentioned no such term. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:52, 10 May 2020 (UTC)
- Because the translation of the official term “adversariorum partes suscipient” suggests opponent. ;) Best, DerHexer (talk) 18:52, 10 May 2020 (UTC)
I can't see any cause for a deletion. It's of great importance for science history. But not always easy to figure out. To delete it would be definetly work against the Wikidata mission. -- Marcus Cyron (talk) 21:01, 10 May 2020 (UTC)
- Keep Clear counterpart to doctoral advisor (P184) Vojtěch Dostál (talk) 10:04, 19 July 2020 (UTC)
- Keep, an important property for science.--Arbnos (talk) 14:59, 28 April 2021 (UTC)}}
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this, as it's well used and the inverse is still important for uses of the data. Thanks. Mike Peel (talk) 19:24, 21 January 2022 (UTC)
has edition or translation (P747): (delete | history | links | entity usage | logs | discussion)
The property is not needed as we have the inserve Property:P629. ChristianKl ❪✉❫ 17:28, 15 May 2020 (UTC)
- Delete, agree. Nomen ad hoc (talk) 19:48, 15 May 2020 (UTC).
WikiProject Books has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.. Nomen ad hoc (talk) 19:49, 15 May 2020 (UTC).
- For many books, I think things would be considerably easier if entities for such works were closer to the way lexemes work, i.e. with sub-entities for editions.
The above property is a step in that direction. (Obviously, for works with many editions, the property isn't that useful). --- Jura 09:00, 16 May 2020 (UTC) - @ChristianKl: Der Nutzen der Eigenschaft wird unter Wikidata:WikiProject Books erläutert. Auf der dortigen Diskussionsseite könnte man diskutieren, falls sie überflüssig ist oder klarer beschrieben werden soll. --Kolja21 (talk) 19:38, 18 May 2020 (UTC)
- @Kolja21: Es ist Konvention auf Wikidata die Diskussion, ob Eigenschaften gelöscht werden auf dieser Seite zu führen. ChristianKl ❪✉❫ 20:59, 18 May 2020 (UTC)
- @ChristianKl: since when is having inverse a reason for deletion? There is "child" too. I don't know why inverse exists, there might be reasons, but then it should be stated why any of the reasons do not apply here. MrProperLawAndOrder (talk) 21:04, 18 May 2020 (UTC)
- @MrProperLawAndOrder: Since we have had the relateditems gadget it's a reason we used to delete properties. You might want to read through the archive if you are sincerely interested. There are valid uses of unknown value (sometimes with object named as (P1932)) and no value for child (P40). ChristianKl ❪✉❫ 21:26, 18 May 2020 (UTC)
- @ChristianKl: "but then it should be stated why any of the reasons do not apply here" MrProperLawAndOrder (talk) 19:43, 19 May 2020 (UTC)
- We don't have any policy (or general norm) that suggests the need for a long post to start a deletion discussion that goes through detailed analysis. You haven't provided any reasoning for why the tradeoffs of introducing a new norm are worthwhile here. ChristianKl ❪✉❫ 20:22, 19 May 2020 (UTC)
- @MrProperLawAndOrder: Since we have had the relateditems gadget it's a reason we used to delete properties. You might want to read through the archive if you are sincerely interested. There are valid uses of unknown value (sometimes with object named as (P1932)) and no value for child (P40). ChristianKl ❪✉❫ 21:26, 18 May 2020 (UTC)
- Delete. --Tinker Bell ★ ♥ 03:10, 20 May 2020 (UTC)
- @ChristianKl: For the time being, I would be hesitant to support the deletion of this property. The property should eventually no longer be necessary, but there isn't yet sufficient support within other parts of MediaWiki for handling object-to-subject queries (even though Wikidata itself and third-party reusers would not be adversely affected by its deletion). As such, since inverse properties may still be used by other Wikimedia projects, I would suggest waiting until phab:T167521 and phab:T209559 have been resolved in a satisfactory manner. Are there any properties which have already been deleted due to being inverse properties? Jc86035 (talk) 17:06, 21 May 2020 (UTC)
- Keep I agree with Jc86035, until the Wikibase datastructure changegs, this should not be deleted. I also don't like this redundancy, but I think we need to wait. Germartin1 (talk) 07:38, 1 June 2020 (UTC)
- Temporary Keep per Jc86035, needs technical changes before deletion. --Liuxinyu970226 (talk) 22:55, 3 June 2020 (UTC)
- Delete --Haansn08 (talk) 02:04, 7 June 2020 (UTC)
- Temporary Keep per Jc86035. --Epìdosis 15:58, 8 June 2020 (UTC)
- Keep I am not a big fan of inverse properties, but this one is reasonably populated and mainly used by 9+ templates across multiple wikis. Is there any alternative for these templates? --Jklamo (talk) 16:24, 8 June 2020 (UTC)
- Keep. Very useful. How to easily find editions of some book from other edition? e.g. how to find bulgarian translaiton of The Raven (Q22726) from one of czech translations? see also phab:T128173. JAn Dudík (talk) 09:53, 15 June 2020 (UTC)
- Neutral. Think this makes sense here Mozilla Public License (Q308915) though I guess I can see how it is a bad crutch ... so neutral. Iwan.Aucamp (talk) 21:28, 7 July 2020 (UTC)
- Keep As long as complementary properties do not automatically work on both sides, it is necessary to mirror them in the inverse property. --ŠJů (talk) 23:52, 11 July 2020 (UTC)
- Keep Deleting it would be premature. Why rush? Antoine2711 (talk) 16:59, 30 October 2020 (UTC)
- Keep per Jklamo and ŠJů Vojtěch Dostál (talk) 14:30, 5 November 2020 (UTC)
- Comment having to add both sides of any inverse relationship is a PITA, and having the ability to add a linkage from either side is a far better means, unidirectional only means will suck, especially when you are usually creating the item on the other side of a relationship. — billinghurst sDrewth 04:23, 24 January 2021 (UTC)
- Keep until we implement a project wide policy of not having any bidirectional properties, this deletion request seems really arbitrary since it's just as useful as any other. Ainali (talk)
- Keep at the moment, there is no efficient way to query the reverse property efficiently for sister projects... --Hsarrazin (talk) 20:56, 12 January 2022 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this. Thanks. Mike Peel (talk) 19:25, 21 January 2022 (UTC)
mountain range (P4552): (delete | history | links | entity usage | logs | discussion)
Too specific (not universal) alternative of geomorphological unit (P4688). These both can be merged with located in/on physical feature (P706) which is the most universal, and its aliases indicate that it is intended also for similar nature-geographical location (geomorphological features/units and standing bodies of water). continent (P30) is also redundant. Various parallel types of division we can manage through qualifiers.
The localisation should be universal and hierarchic as well as located in the administrative territorial entity (P131) is. —ŠJů (talk) 23:37, 11 July 2020 (UTC)
- Keep. It's just a way too important property for all sorts of items. Thierry Caro (talk) 08:45, 4 September 2020 (UTC)
- Keep until better ways of retrieving and filtering statements are developed on wikis Vojtěch Dostál (talk) 14:29, 5 November 2020 (UTC)
- Keep Not used in Template:Infobox mountain at the English Wikipedia but referenced at its documentation. Please discuss at the Village Pump first. --Amitie 10g (talk) 00:03, 30 May 2021 (UTC)
- Keep This is a very important property for various items(glaciers comes to mind), so before merging it with another property lets open a discussion on the talk page and ping relevant projects. Abbe98 (talk) 13:02, 7 June 2021 (UTC)
- Keep as discussed above --Gerd Fahrenhorst (talk) 15:59, 10 July 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this. Thanks. Mike Peel (talk) 19:27, 21 January 2022 (UTC)
P7335 (P7335): (delete | history | links | entity usage | logs | discussion)
Mixer became defunct in July 2020, and it's no longer a working property - it leads to the Mixer closure landing page. —CrystallineLeMonde (talk) 16:37, 1 September 2020 (UTC)
- Why delete a valid property? The data is potentially useful for joining to other databases or through archives. Keep but deprecate. BrokenSegue (talk) 17:09, 1 September 2020 (UTC)
- Marked as Wikidata property for a discontinued website (Q60457486). --Liuxinyu970226 (talk) 23:04, 2 September 2020 (UTC)
- Keep It's useful to see which games that were available on Twitch vs Mixer.--Trade (talk) 20:51, 12 September 2020 (UTC)
- Comment @BrokenSegue, Liuxinyu970226, Trade: Please read the description of Wikidata property for a discontinued website (Q60457486). Your opinions leave me a little skeptical. —Eihel (talk) 01:06, 13 September 2020 (UTC)
- @Eihel: And why your comment isn't? I just added such a mark, if you think I did wrong, why not revert me? And I have no opinions on vd or not this. --Liuxinyu970226 (talk) 01:09, 13 September 2020 (UTC)
- @Eihel: The statement on that page re: deletion is bad and I doubt represents policy or concensus or even was the result of discussion. Don't delete possibly useful data. BrokenSegue (talk) 01:10, 13 September 2020 (UTC)
- Delete per nomination. See also a similar situation with YouTube Gaming shutdown. Regards Kirilloparma (talk) 01:31, 13 September 2020 (UTC)
- @Kirilloparma: Would your opinion change if I told you a large amount of mixer is archived? BrokenSegue (talk) 20:38, 13 September 2020 (UTC)
- Unfortunately, not really. Well, there are some incomprehensible links that you provided, I have opened them and nothing has changed, since there is no link to the archive itself, only some incomprehensible files that need to be downloaded to my PC ... What are they for and how can they help Wikidata? As for the site itself, Mixer (just like Youtube Gaming) simply offered the user nothing more than a streaming service. So the question is, why should we have empty links to defunct streaming service? I would understand if this happened to IGDB site, since archived links to it would contain a lot of useful information for Wikidata (see example), but in the case of Mixer on the contrary, just empty links which once led to a streaming service, but now they no longer work and are no longer needed, so yeah, I am not changing my opinion at this point and still think this property should be removed. Regards Kirilloparma (talk) 22:06, 14 September 2020 (UTC)
- The files you didn't download are Web ARChive (Q7978505)s and the primary way websites are archived in bulk. Why should we have links to a dead site? We shouldn't. We should remove the links. But the identifiers remain meaningful (they provide meaning to those archives and allow us to join to other databases that may have stored Mixer game ids). Still nobody has explained what harm these identifiers are doing. I mean what value did you think having this identifier provided when the website was up? It's the same value now except you have to go to the WARC files. BrokenSegue (talk) 02:27, 15 September 2020 (UTC)
- Unfortunately, not really. Well, there are some incomprehensible links that you provided, I have opened them and nothing has changed, since there is no link to the archive itself, only some incomprehensible files that need to be downloaded to my PC ... What are they for and how can they help Wikidata? As for the site itself, Mixer (just like Youtube Gaming) simply offered the user nothing more than a streaming service. So the question is, why should we have empty links to defunct streaming service? I would understand if this happened to IGDB site, since archived links to it would contain a lot of useful information for Wikidata (see example), but in the case of Mixer on the contrary, just empty links which once led to a streaming service, but now they no longer work and are no longer needed, so yeah, I am not changing my opinion at this point and still think this property should be removed. Regards Kirilloparma (talk) 22:06, 14 September 2020 (UTC)
- @Kirilloparma: Would your opinion change if I told you a large amount of mixer is archived? BrokenSegue (talk) 20:38, 13 September 2020 (UTC)
- Neutral
Why skeptical? Why is this property valid if it no longer fulfills the function for which it was created, BrokenSegue? Which database will use Wikidata IDs for a closed site, BrokenSegue? Can we still see games available on Mixer to compare them to another site, Trade? When a site is closed therefore the property attached to the site is obsolete: Label, P1630, Base URL… and Q60457486. Consensus and discussion are the basis of the preliminary debate to the creation of the property, and serve as a policy. What is rightly debated is whether the "data is possibly useful". As these are external ids, you need to have archives. The link to your archive.org page consists of meta-information and are not saved pages that can be used to replace property IDs. And although archives can be found, this was a site offering streaming… whose server is also on the SLD. So an archive will go to an empty page of interesting content, but filled with advertising. Clearly unnecessary. So deletion is the only solution, there is no mysterious utility. Cordially. —Eihel (talk) 16:49, 14 September 2020 (UTC){{Vd}}
- @Eihel: Respectfully you are mistaken. The link to the archive.org data I provided is not just meta-information. It is saved pages. If anyone goes through those archives they will be glad we didn't delete this property. Further, I'm unclear what value deleting this property achieves or what harm keeping it does. The value of an external identifier is not merely the URL it takes you to (as evidenced by the identifiers that have no URL). BrokenSegue (talk) 16:56, 14 September 2020 (UTC)
- Hello BrokenSegue Ok. Let's say I'm looking for Arabian Nights (Q1145946) infos (Item taken completely at random, but valid in most cases) that was available on Mixer, where can I find it? Please. —Eihel (talk) 05:59, 18 April 2021 (UTC)
- @Eihel: To find a particular video game I would have to download the entire corpus from the archive which I'm not doing for you (it's much more than 1TB). But I downloaded one at random and looked for game ids. The downloads of the channel information from mixer includes the ID of the game currently being played (in this case it was 70323=Fortnite (Q349375)). You can replicate this by downloading this 8GB file [3] and searching for "70323" to find all the linked data. If you downloaded any warc file though it would be evident it's not just metadata as you claimed. BrokenSegue (talk) 14:48, 18 April 2021 (UTC)
- I can not do better —Eihel (talk) 19:39, 18 April 2021 (UTC)
- @Eihel: To find a particular video game I would have to download the entire corpus from the archive which I'm not doing for you (it's much more than 1TB). But I downloaded one at random and looked for game ids. The downloads of the channel information from mixer includes the ID of the game currently being played (in this case it was 70323=Fortnite (Q349375)). You can replicate this by downloading this 8GB file [3] and searching for "70323" to find all the linked data. If you downloaded any warc file though it would be evident it's not just metadata as you claimed. BrokenSegue (talk) 14:48, 18 April 2021 (UTC)
- Hello BrokenSegue Ok. Let's say I'm looking for Arabian Nights (Q1145946) infos (Item taken completely at random, but valid in most cases) that was available on Mixer, where can I find it? Please. —Eihel (talk) 05:59, 18 April 2021 (UTC)
- Tend to Keep since their values are archived by archive.org, which may give a way to replace its URL scheme. --Liuxinyu970226 (talk) 21:45, 27 September 2020 (UTC)
- Comment There seems to be decent archiving in the Wayback machine, so I went ahead and added a formatter URL (P1630) accordingly. Jean-Fred (talk) 14:19, 29 September 2020 (UTC)
- Keep unless it shouldn't have been added in the first place --- Jura 07:20, 15 October 2020 (UTC)
- Keep: it can still be used to extract data from the internet archive. --Shisma (talk) 18:12, 5 February 2021 (UTC)
- Keep If the deceased don't lose their names even when those names fall out of use centuries later, why should we deny an association between former users and their previously associated Mixer ids? If anything, I will argue that this information is necessary to not only link further information, but also to be able to identify previous information such as clips from the ArchiveTeam Mixer collection, a point which was already raised by BrokenSegue and (talk)Shisma (talk). Themadprogramer (talk) 08:47, 27 March 2021 (UTC)
- Keep Mixer was an important piece of video game streaming history, I don't think we should delete the data just because the website is down. AntisocialRyan (talk) 18:46, 9 May 2021 (UTC)
- Keep Dead website should be never a valid reason for deleting a property. Better solutions exists as proposed above. --Amitie 10g (talk) 02:19, 29 August 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this. Thanks. Mike Peel (talk) 19:29, 21 January 2022 (UTC)
political ideology (P1142): (delete | history | links | entity usage | logs | discussion)
Now duplicates with P8929 (P8929) —Nomen ad hoc (talk) 19:26, 7 December 2020 (UTC)
- I don't think it doublicates it. social democracy (Q121254) is not a world-view in the sense anthroposophy (Q184719) and atheism (Q7066) are. The example are along what German law considers as the religion/world view category and social democracy (Q121254) is not that kind of thing.
- ideology (Q7257) doesn't subclass world view (Q49447) and shouldn't. ChristianKl ❪✉❫ 18:27, 9 December 2020 (UTC)
- Ahem. Does this new property only apply to German law? Nomen ad hoc (talk) 19:48, 9 December 2020 (UTC).
- Do you think there are other cases where both of those things get bundled together? ChristianKl ❪✉❫ 11:19, 26 December 2020 (UTC)
- Ahem. Does this new property only apply to German law? Nomen ad hoc (talk) 19:48, 9 December 2020 (UTC).
- Keep Not a duplicate; the new property better handles things that were abuses of political ideology (P1142) for non-political philosophies. ArthurPSmith (talk) 14:30, 28 December 2020 (UTC)
- Keep, not a duplicate.Arbnos (talk) 14:37, 24 May 2021 (UTC)
- Keep. P8929 (P8929) may comprise complex ideologies. For instance, Alice is a Christian nationalist. Bob is a Christian Socialist. Charlie is a Social Democrat. Bob and Charlie ought to share a property Alice does not share, and political ideology (P1142) reflects this more appropriately. Ari T. Benchaim (talk) 23:31, 21 June 2021 (UTC)
- Keep This is a meaningful property, P8929 (P8929) is unclear and conflates (frequently) different concepts. Salpynx (talk) 21:45, 22 August 2021 (UTC)
- KeepPer Salpynx . --Pa2chant.bis (talk) 07:24, 15 September 2021 (UTC)
- Keep per ChristianKl. --Waldyrious (talk) 20:15, 9 December 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this. Thanks. Mike Peel (talk) 19:30, 21 January 2022 (UTC)
religion or worldview (P140): (delete | history | links | entity usage | logs | discussion)
Now duplicates with P8929 (P8929) —Nomen ad hoc (talk) 19:27, 7 December 2020 (UTC)
- the proposer of P8929 (P8929) specifically said they didn't want this deleted saying "P140 is more appropriate e.g. when describing places of worship, because a marginal number of them are agnostic or atheist. P1142 is based on the clearly-defined same-name class Q12909644 and I would not consider it redundant." Some other commenters on the property creation discussion explicitly wanted to keep these. I think this new property was probably a mistake because we don't have clear picture of what we're doing now. BrokenSegue (talk) 15:24, 8 December 2020 (UTC)
- Keep Not a duplicate, the new property better handles things that are philosophies and not religions. ArthurPSmith (talk) 14:31, 28 December 2020 (UTC)
- Comment Assuming that the reason for differentiating between this property and P8929 (P8929) is so that this one can be used for places of worship, I would suggest that "for the religion or denomination" more clearly expresses the function of this property (and would more clearly differentiate the two properties). I've added "denomination" here because sometimes the values for this property are not religions but subdivisions of ones – Baptists (Q93191), Reform Judaism (Q1133485), etc. Ham II (talk) 18:31, 30 April 2021 (UTC)
- Keep, not a duplicate, but an important property for religious buildings and structures, and for other aspects too.Arbnos (talk) 14:23, 24 May 2021 (UTC)
- Keep widely in use in several templates and modules at some Wikipedias. --Amitie 10g (talk) 00:03, 30 May 2021 (UTC)
- Keep Serves a clear purpose in infoboxes. The difference between religion and political affiliation is meaningful for most of the biographies that use them. Deryck Chan (talk) 14:45, 15 August 2021 (UTC)
- Keep This is a meaningful property, P8929 (P8929) is unclear and conflates (frequently) different concepts. Salpynx (talk) 21:47, 22 August 2021 (UTC)
- Keep P8929 (P8929) is not exactly the same. --Looperz (talk) 19:19, 19 January 2022 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Clear consensus to keep this. Thanks. Mike Peel (talk) 19:31, 21 January 2022 (UTC)
political alignment (P1387): (delete | history | links | entity usage | logs | discussion)
May now be redundant with P8929 (P8929) —Nomen ad hoc (talk) 04:05, 12 December 2020 (UTC)
- definitely Keep here. this property is very narrowly scoped. BrokenSegue (talk) 04:56, 26 December 2020 (UTC)
- Keep. This property has a very narrow scope as you can see in the value constraint and is useful for it. Daask (talk) 13:27, 3 May 2021 (UTC)
- Keep, not a duplicate.Arbnos (talk) 14:40, 24 May 2021 (UTC)
- Keep This is a meaningful property, Property:P8929 is unclear and conflates (frequently) different concepts. Salpynx (talk) 21:43, 22 August 2021 (UTC)
- Keep. The scope is clear, and actually better defined that that of P8929 (P8929) --Waldyrious (talk) 20:08, 9 December 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Consensus to delete — Martin (MSGJ · talk) 11:55, 31 January 2022 (UTC)
P4883 (P4883): (delete | history | links | entity usage | logs)
The website was heavily changed, and now all IDs lead to the main page. Therefore the property is useless now. Steak (talk) 08:32, 18 December 2020 (UTC)
- P4886 (P4886) has also been affected by this change. Have replacement properties been created? Peter James (talk) 09:19, 20 December 2020 (UTC)
- is there a way to do a 1:1 mapping to their new schema (if there is one)? Looks like archive.org got most of them so at the very least move the property to pointing there. BrokenSegue (talk) 20:13, 20 December 2020 (UTC)
- I added an archive.org formatter so Keep until someone has a better idea. BrokenSegue (talk) 20:17, 20 December 2020 (UTC)
- A proposal on a new property can be found here. --Hadibe (talk) 00:26, 31 December 2020 (UTC)
- All of the 57 template:FFF.fr usages in German Wikipedia have been changed to the new IDs and could be imported automarically to Wikidata. --Hadibe (talk) 08:58, 1 January 2021 (UTC)
- I added an archive.org formatter so Keep until someone has a better idea. BrokenSegue (talk) 20:17, 20 December 2020 (UTC)
- Question Have all the old IDs been transferred to their new ID of the new property, @Steak:? —Eihel (talk) 06:07, 18 April 2021 (UTC)
- Answer All the ID of P4883 (P4883) and P4886 (P4886) have been transferred into their new ID of FFF.fr player ID (P9264). There is, in my opinion, no further obstacle to the deletion of the two deprecated properties —Kwayst (talk) 11:56, 24 May 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Kept. Consensus to keep this. Thanks. Mike Peel (talk) 19:35, 21 January 2022 (UTC)
liturgical rank (P9002): (delete | history | links | entity usage | logs | discussion)
Created by Vogone by ignoring the need for support votes on property that wasn't labeled as ready and without engaging with the proposal page the way we usually do when creating properties. —ChristianKl ❪✉❫ 12:54, 1 January 2021 (UTC)
- The creation is still in process (as you can see, obviously not all steps of the creation process have been completed, yet) and there were no outstanding issues on a months-old proposal. I would argue all four creation criteria were met in this case, and the proposal was mentioned in multiple other places over the course of the past half year to seek further input. --Vogone (talk) 13:53, 1 January 2021 (UTC)
- Template:Speedy delete please ask a property creator to look into it once issues are sorted out. --- Jura 14:31, 1 January 2021 (UTC)
- It would be helpful to know which issues are outstanding. On the proposal itself none were raised, bar a question whether this property could be used for other religions where applicable, and this question was affirmed. I will delete the property if there is indeed an issue left that I have missed. --Vogone (talk) 14:39, 1 January 2021 (UTC)
- The issue of how this property behaves outside of Christian tradition seems to be open. ChristianKl ❪✉❫ 15:52, 1 January 2021 (UTC)
- As MF-Warburg already pointed out twice it is applicable for every religion which has a similar concept of religious feasts. I'd like to add that this is a nonproblem simply by the fact that no other religion is known to have such a sophisticated liturgy. – KPFC 💬 16:05, 1 January 2021 (UTC)
- Yes, seconded - I don't know others that would need it, but I also don't see a problem with them using it. --MF-W 17:43, 1 January 2021 (UTC)
- Apriori I think it's possible that while other religions not have the same concept of religious feasts as Christianity, they have similar holy days that are somehow labeled with something like a rang. Narrowing this to religious feasts when another religion doesn't think of their holy days as being about feasts can complicate reuse. That's why it makes sense to look at the needs of other religions before creating the property. – The preceding unsigned comment was added by ChristianKl (talk • contribs).
- We are not discussing about feast day (P841) here, which references "feast days". We are talking about an additional aspect for this already existing, widely used property. If such a hypothetical calendar of another religion comes up, they can use "liturgical rank" as well. If the term "liturgical rank" is not fit for them, it can surely be changed to something more general (en:liturgy is however already not a Christianity-specific term). --MF-W 11:37, 2 January 2021 (UTC)
- Apriori I think it's possible that while other religions not have the same concept of religious feasts as Christianity, they have similar holy days that are somehow labeled with something like a rang. Narrowing this to religious feasts when another religion doesn't think of their holy days as being about feasts can complicate reuse. That's why it makes sense to look at the needs of other religions before creating the property. – The preceding unsigned comment was added by ChristianKl (talk • contribs).
- Yes, seconded - I don't know others that would need it, but I also don't see a problem with them using it. --MF-W 17:43, 1 January 2021 (UTC)
- As MF-Warburg already pointed out twice it is applicable for every religion which has a similar concept of religious feasts. I'd like to add that this is a nonproblem simply by the fact that no other religion is known to have such a sophisticated liturgy. – KPFC 💬 16:05, 1 January 2021 (UTC)
- The issue of how this property behaves outside of Christian tradition seems to be open. ChristianKl ❪✉❫ 15:52, 1 January 2021 (UTC)
- It would be helpful to know which issues are outstanding. On the proposal itself none were raised, bar a question whether this property could be used for other religions where applicable, and this question was affirmed. I will delete the property if there is indeed an issue left that I have missed. --Vogone (talk) 14:39, 1 January 2021 (UTC)
- Keep There were 2 supporting comments in the proposal discussion, although neither one used the support template to express that, which is unusual. Vogone was one of the two, however, so should have requested the proposal be created by an independent property creator. Please check how other property creations are done before creating another one, thanks. ArthurPSmith (talk) 19:12, 1 January 2021 (UTC)
- @ArthurPSmith: I don't think that comments from people who don't know the property creation process well enough to use the support template should be seen as demonstrating consensus for creation when there are people who are familiar with our process that still point to open issues. Our policy does say "i.e. an opposing voice with no thought behind it should not block creation, but a single reasonable opposing voice against many supporters may do so". ChristianKl ❪✉❫ 10:57, 2 January 2021 (UTC)
- @ChristianKl: But there weren't any opposing voices either, reasonable or unreasonable. All questions raised had been addressed. Not sure what your point is here. ArthurPSmith (talk) 19:08, 4 January 2021 (UTC)
- @ArthurPSmith: I don't think that comments from people who don't know the property creation process well enough to use the support template should be seen as demonstrating consensus for creation when there are people who are familiar with our process that still point to open issues. Our policy does say "i.e. an opposing voice with no thought behind it should not block creation, but a single reasonable opposing voice against many supporters may do so". ChristianKl ❪✉❫ 10:57, 2 January 2021 (UTC)
- For ease of access, here is the original proposal. --MF-W 11:37, 2 January 2021 (UTC)
- Keep as one of the supporting persons in the proposal. Also I fail to see any open issues – KPFC 💬 20:38, 7 January 2021 (UTC)
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Consensus that this identifier can be deleted without loss of information — Martin (MSGJ · talk) 22:09, 3 February 2022 (UTC)
P3043 (P3043): (delete | history | links | entity usage | logs)
Scoresway.com does not exist any more. Their website says Scoresway has a new home at soccerway.com. So now the links redirect to Soccerway website, which means it's a duplicate to Soccerway player ID. Other Scoresway IDs need deleting aswell, but are possibly not duplicated. Pelmeen10 (talk) 10:52, 2 April 2020 (UTC)
- Delete on this and the others - but you should probably not remove id's until there's a consensus reached here. ArthurPSmith (talk) 18:09, 2 April 2020 (UTC)
A little Keep, please confirm that if there's online archives (e.g. from archive.org) for Scoresway.com or not. --Liuxinyu970226 (talk) 01:10, 3 April 2020 (UTC)- @Liuxinyu970226: Soccerway.com covers all the soccer (football) articles with the exact same content +updates, so online archives are not needed here. Pelmeen10 (talk) 12:05, 3 April 2020 (UTC)
- @Liuxinyu970226, Pelmeen10: A ping without a new ~~~~ is not a ping. —Eihel (talk) 17:17, 3 April 2020 (UTC)
- Delete By my recent searching of archive.org, there's indeed no archives of those URLs. --Liuxinyu970226 (talk) 12:14, 22 April 2020 (UTC)
- @Liuxinyu970226: Soccerway.com covers all the soccer (football) articles with the exact same content +updates, so online archives are not needed here. Pelmeen10 (talk) 12:05, 3 April 2020 (UTC)
- Keep 72000 uses. --- Jura 08:09, 10 April 2020 (UTC)
- @Jura1: What's the point when Soccerway ID covers it 100% (I've checked the archived pages). The ID's are even the same. User:Zyxw recently added Soccerway ID's to all that had Scoresway ID's. So no information is lost here and archives not needed. But he also did the opposite - adding Scoresway ID's based on their Soccerway ID's, I don't know why. Pelmeen10 (talk) 12:44, 11 April 2020 (UTC)
- I added IDs for Soccerway player ID (P2369) and P3043 (P3043) since any player with one of those should have the other, until such time as the Scoresway property is deleted (if it is deleted). -- Zyxw (talk) 08:10, 12 April 2020 (UTC)
- @Jura1: What's the point when Soccerway ID covers it 100% (I've checked the archived pages). The ID's are even the same. User:Zyxw recently added Soccerway ID's to all that had Scoresway ID's. So no information is lost here and archives not needed. But he also did the opposite - adding Scoresway ID's based on their Soccerway ID's, I don't know why. Pelmeen10 (talk) 12:44, 11 April 2020 (UTC)
- Delete, after ensuring that all entities with the Scoresway property have the equivalent Soccerway property and any templates using Scoresway are updated to use Soccerway. Both websites were/are owned by Perform Group and displayed the same data. The main difference was that Scoresway used a common formatter URL for players, managers, and referees (www.scoresway.com/?sport=soccer&page=person&id=$1) while Soccerway uses different URLs (int.soccerway.com/players/$1/, int.soccerway.com/coaches/$1/, int.soccerway.com/referees/$1/). The old Scoresway player URLs such as http://www.scoresway.com/?sport=soccer&page=person&id=783 now redirect to the main Soccerway.com page (not the player page). On a related note, it might make sense to add new properties for Soccerway coach/manager ID and Soccerway referee ID, similar to how Soccerbase has Soccerbase player ID (P2193), Soccerbase manager ID (P2195), and Soccerbase referee ID (P7465). -- Zyxw (talk) 08:10, 12 April 2020 (UTC)
- Delete Germartin1 (talk) 09:09, 3 May 2020 (UTC)
- Keep The benefit is in being able to resolve the identifier, not just the linked content. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:10, 25 May 2020 (UTC)
- @Pigsonthewing: It's already confirmed unable to resolve this identifier. --Liuxinyu970226 (talk) 12:59, 2 June 2020 (UTC)
- Not so; if a user has the ID value "783", they can currently access Wikidata to resolve that value to Gary Caldwell (Q334628). If we delete the property, that will no longer be the case. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:05, 2 June 2020 (UTC)
- @Pigsonthewing: It's already confirmed unable to resolve this identifier. --Liuxinyu970226 (talk) 12:59, 2 June 2020 (UTC)
- One of the properties should be deleted, however the text portion of Soccerway IDs are meaningless and not necessary (as shown by the current URL for P3043 (P3043)). Therefore, I believe any items with Soccerway player ID (P2369) but not P3043 (P3043) should have the ID transferred over, and then Soccerway player ID (P2369) should be deleted. This would make Soccerway IDs far easier to work with (for example in queries), as sometimes the text portion of Soccerway IDs are trimmed or malformed when imported to Soccerway player ID (P2369). S.A. Julio (talk) 17:37, 27 October 2020 (UTC)
- Delete and should be merged with Soccerway player ID (P2369) and as explained by S.A. Julio the text portion should be removed from the id. Instead the format URL of the current P3043 (P3043) should be used. --Hannes Röst (talk) 15:01, 13 January 2022 (UTC)