Jump to content

Wikipedia:Templates for discussion/Log/2019 March 14

From Wikipedia, the free encyclopedia

March 14

[edit]
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was keep. Primefac (talk) 00:33, 25 March 2019 (UTC)[reply]

Proposing merging this with {{Infobox settlement}}. Taken directly from the Infobox settlement documentation: It should be used to produce an Infobox for human settlements (cities, towns, villages, communities) as well as other administrative districts, counties, provinces, et cetera. Precedent also established with the merging of Infobox Belgium settlement (tfd) & Infobox Hungarian settlement (tfd). Zackmann (Talk to me/What I been doing) 22:05, 14 March 2019 (UTC)[reply]

  • Keep. Used in 30,000+ articles, substituting this wrapper has the following disadvantages (which I also gave at Wikipedia:Templates_for_discussion/Log/2019_March_7#Infobox_settlement_wrappers:
    • Loss of consistency between articles about similar topics (municipalities of Austria, settlements of Cape Verde, etc.), e.g. links to higher administrative divisions. Several wrappers link to higher administrative divisions and use specific detailed pushpin maps based on their official geographic code
    • Loss of country-specific maintenance tools: several infobox wrappers place articles with (unintentional or vandalic) bad infobox content (like "state = disneyland") in a maintenance category
    • Loss of the facility to update population data for hundreds of settlements in one edit, see also this discussion. Markussep Talk 22:17, 14 March 2019 (UTC)[reply]
  • Keep, per all the arguments I stated on the Infobox German location TfD below.--eh bien mon prince (talk) 12:47, 15 March 2019 (UTC)[reply]
  • Keep Abstain because of the two examples given. Editors recall that they saw a certain template used in a certain situation, or they figure there must be such a template, so they search for it. But the template about, say, Belgium has been merged with a template without a single mention of Belgium. This is why we leave behind a redirect when we merge one page into another. Neither one of the given examples of templates for discussion (TFD) gave enough weight about the above two cases where people search for the appropriate template by what they have seen before. One of the TFDs resulted in a merge and the other resulted in a deletion. However, neither left behind a redirect! It seemed to me like some editors thought leaving behind a redirect gave too much validity to the previous template. I'm all for simplification, and in general I think the idea of working towards one template that can cover a lot of ground—here, someone literally—could be the best idea. But that's only true if these merges investigate the meanings behind the parameters to make sure they make sense to merge and then leave redirects or soft redirects (which might be better in this case; the "Keep side" should not make the same mistakes if merge succeeds by demanding to have a redirect if it might cause problems). Sorry that I have to dump this info out of my head and run, but if I can come back I will. However, since I could not take the time to refine my argument, I'm changing my "keep" to "abstain". PS. I'd love to see a spreadsheet that compares the parameters of both templates in question and examine whether there is a one-to-one correspondence for each parameter in the original template. It would show the kind of research that has been done. And in my mind that's a necessary level of research. Geekdiva (talk) 21:03, 16 March 2019 (UTC)[reply]
  • Strong keep. This has France-specific parameters, and if you merge it into infobox settlement, you force editors to start using an infobox that's becoming ever more complex. Start thinking of editors who use infoboxes on a daily basis instead of deciding that they're all close enough to merge. Nyttend (talk) 23:50, 16 March 2019 (UTC)[reply]
  • Keep (original nominator) Well time to admit when I'm wrong. Markussep makes a few excellent points. I think that we currently have far too many custom wrappers for {{Infobox settlement}} but I have been painting with too broad a brush. This template is a perfect example of when wrappers SHOULD be used. I would withdraw the nomination but I actually think it will carry more weight if to let this TFD play out to the inevitable keep. Happy to address any other questions/concerns about my change of heart! --Zackmann (Talk to me/What I been doing) 17:20, 18 March 2019 (UTC)[reply]
  • Keep Specialised templates for specialised articles requirements is what is needed. scope_creepTalk 00:51, 20 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was keep. Primefac (talk) 00:34, 25 March 2019 (UTC)[reply]

Proposing merging this with {{Infobox settlement}}. Taken directly from the Infobox settlement documentation: It should be used to produce an Infobox for human settlements (cities, towns, villages, communities) as well as other administrative districts, counties, provinces, et cetera. Precedent also established with the merging of Infobox Belgium settlement (tfd) & Infobox Hungarian settlement (tfd). Zackmann (Talk to me/What I been doing) 22:03, 14 March 2019 (UTC)[reply]

  • Keep. Used in 10,000+ articles, substituting this wrapper has the following disadvantages (which I also gave at Wikipedia:Templates_for_discussion/Log/2019_March_7#Infobox_settlement_wrappers):
    • Loss of consistency between articles about similar topics (municipalities of Austria, settlements of Cape Verde, etc.), e.g. links to higher administrative divisions. Several wrappers link to higher administrative divisions and use specific detailed pushpin maps based on their official geographic code
    • Loss of country-specific maintenance tools: several infobox wrappers place articles with (unintentional or vandalic) bad infobox content (like "state = disneyland") in a maintenance category
    • Loss of the facility to update population data for hundreds of settlements in one edit, see also this discussion. Markussep Talk 22:18, 14 March 2019 (UTC)[reply]
      Markussep, Appreciate you restating the arguments against. The TFD you referenced above was a bit of a cluster because it involved SO MANY different templates. Zackmann (Talk to me/What I been doing) 22:28, 14 March 2019 (UTC)[reply]
      Zackmann08, I would appreciate it if you would show the advantages of substituting these (widely used!) wrappers. I asked the same question here, and haven't seen an answer yet. You quoted above "It should be used to produce an Infobox for human settlements (cities, towns, villages, communities) as well as other administrative districts, counties, provinces, et cetera". Well, these wrappers do use {{Infobox settlement}}, and substituting them doesn't change anything on the "front end" of the articles that transclude them. Markussep Talk 08:30, 18 March 2019 (UTC)[reply]
      Markussep, that is a very good point. I'm going to be honest with you... I've been completely turned around on this and French Commune. Given the huge number of articles using these wrappers, I actually now think they should stay. I would withdraw the TFD but I think it will carry more weight if the full discussion plays out resulting in keep. Zackmann (Talk to me/What I been doing) 17:17, 18 March 2019 (UTC)[reply]
  • Keep. I can say, to add to the points stated by Markussep above, that based on the precedents of Infobox Town AT and similar recent nominations, deleting wrappers increases the maintenance burden, instead of reducing it.
    • Austrian articles are now using outdated population figures, despite updated ones being available on Wikidata, and in order to do anything to change that there is now a need to go through a lengthy bot approval procedure.
    • Even once the change is implemented, it will be harder to keep track of the way specific fields are populated, and how consistently they draw data from a correct and up do date source.
    • Far from making anything easier, the change added a further bureaucratic layer to achieve what could previously be done in a single edit. I don't wish to see the same happen to Germany articles.
    • Rather than standardizing infoboxes (which are already wrappers anyway), we should strive to standardize data, encouraging the use of Wikidata as a central repository for reliable statistics. I feel that deleting wrappers is achieving the opposite result.--eh bien mon prince (talk) 12:40, 15 March 2019 (UTC)[reply]
  • Keep Agree with the above comment. Moving to a generic wrapper is a waste of time. scope_creepTalk 19:32, 15 March 2019 (UTC)[reply]
  • Question: How does the proposer suggest dealing with the large amount of custom code and custom parameter work that specifically supports German-language parameters and German locations? I wouldn't want to see this code inserted into Infobox settlement. – Jonesey95 (talk) 06:56, 16 March 2019 (UTC)[reply]
  • Strong keep per Jonesey. It's beyond time to stop merging all infoboxes into massive complex generic ones. Nyttend (talk) 23:54, 16 March 2019 (UTC)[reply]
  • Keep (original nominator) Well time to admit when I'm wrong. Markussep and Jonesey95 make excellent points. I think that we currently have far too many custom wrappers for {{Infobox settlement}} but I have been painting with too broad a brush. This template is a perfect example of when wrappers SHOULD be used. I would withdraw the nomination but I actually think it will carry more weight if to let this TFD play out to the inevitable keep. Happy to address any other questions/concerns about my change of heart! --Zackmann (Talk to me/What I been doing) 17:19, 18 March 2019 (UTC)[reply]
    • Thanks for changing your mind! Do you also agree now that {{Infobox Town AT}} (see Tfd) was valuable too, and should be restored? Meanwhile, Underlying lk has been uploading 2018 population data for Austrian municipalities to Wikidata (with reference), see for instance Frauenkirchen. If they are ready with that, and there are no copyright issues provided the reference is given as well (@Septembermorgen:?), we could implement retrieving population data from wikidata for Austrian municipalities. Markussep Talk 09:55, 19 March 2019 (UTC)[reply]
The copyright issue should be discussed in Wikidata. Statistcs Austria does not publish under PD (CC0), so it might be (in my opinion it is) a problem to upload these data sets in Wikidata. --Septembermorgen (talk) 12:50, 19 March 2019 (UTC)[reply]
    • Markussep, I am not above having my mind changed. :-) With regards to {{Infobox Town AT}} I standby my feelings there. There were a number of differences. One of the big deciding factors for me changing my mind here was your point about this being use on 10,000+ articles (13,367 transclusions at the moment). AT was MUCH smaller. Plus the fact that they have already been converted, etc... I wouldn't object to you opening a new discussion about it obviously, but my feelings on that one have not changed. Zackmann (Talk to me/What I been doing) 18:36, 19 March 2019 (UTC)[reply]
AT was not that much smaller, with 2,400+ transclusions. If I had had more time I would have opposed stronger against some of the incorrect arguments that were given for deletion. The infobox didn't only exist to facilitate non-English parameters (it also created consistent maps and links to higher administrative divisions, fed articles with invalid content to a maintenance category, fetched population numbers from a subtemplate), it wasn't a mess, it was easy to use and well documented. Yes, they have been converted, which makes it more tedious to revert it. Markussep Talk 19:56, 19 March 2019 (UTC)[reply]
Good suggestion, that should be an easy improvement. Markussep Talk 08:52, 21 March 2019 (UTC)[reply]
Markussep & Darwinek let me know if that is something you would like me to tackle. Zackmann (Talk to me/What I been doing) 00:35, 22 March 2019 (UTC)[reply]
It's done. Markussep Talk 10:44, 22 March 2019 (UTC)[reply]
Thank you--Darwinek (talk) 01:39, 23 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was keep. (non-admin closure) DannyS712 (talk) 19:05, 28 March 2019 (UTC)[reply]

Proposing converting all of these to use {{Infobox settlement}}. Taken directly from the Infobox settlement documentation: It should be used to produce an Infobox for human settlements (cities, towns, villages, communities) as well as other administrative districts, counties, provinces, et cetera (emphasis added by me). I don't see any reason why this shouldn't use the same template as everything else. Zackmann (Talk to me/What I been doing) 21:53, 14 March 2019 (UTC)[reply]

Why isn't a DELETE announcement added inside the TALK section of the proposed deleted article? • SbmeirowTalk17:45, 23 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. Plastikspork ―Œ(talk) 22:29, 21 March 2019 (UTC)[reply]

Unused player table Zackmann (Talk to me/What I been doing) 21:34, 14 March 2019 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. Plastikspork ―Œ(talk) 22:31, 21 March 2019 (UTC)[reply]

Single use raw link. No reason for a template. Zackmann (Talk to me/What I been doing) 20:54, 14 March 2019 (UTC)[reply]

Delete - provides a broken link to an article in Gazeta Tema. Nigej (talk) 07:42, 20 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. (non-admin closure) Zackmann (Talk to me/What I been doing) 17:27, 21 March 2019 (UTC)[reply]

Unused. Article prose should not be put into a template. cymru.lass (talkcontribs) 16:50, 14 March 2019 (UTC)[reply]

  • Delete. The template is incorrectly constructed, invoking itself somewhere in the process (a "template loop"), so it can't really do anything. See this revision of WP:SAND, where I transcluded the template amid a little bit of text; it produces two sentences (1.9.0 was a major update for Bedrock Edition, released on February 5, 2019. It added some features from the Village and Pillage update that weren't added in 1.8.0.) and several technical errors. Regardless of whether article prose belongs in a template, this would have to be completely re-done in order to work. Nyttend (talk) 00:27, 17 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. (non-admin closure) Zackmann (Talk to me/What I been doing) 17:27, 21 March 2019 (UTC)[reply]

Not sure how useful this is to have a list of cricketers named in each ICC's team of the year in a navigation template. It's not a true squad template and isn't defining to the players listed. Lugnuts Fire Walk with Me 12:56, 14 March 2019 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. (non-admin closure) Zackmann (Talk to me/What I been doing) 15:31, 22 March 2019 (UTC)[reply]

A navbox that only adds clutter to articles already cluttered with navboxes, without adding any value: the articles it navigates between are a subset of the ones in Template:Pakistani cities, which is structured in the same way (by provinces) and where the capitals are already clearly set off. – Uanfala (talk) 01:10, 14 March 2019 (UTC)[reply]

  • Delete. With a country the size of Pakistan, I'm surprised we have a template for all of the largest cities (it's not a small country like Lithuania, where a single template can easily list all major cities), but as long as we have another template that's serving this purpose, we don't need this template. It would help if the other template set off the capitals clearly; they're just marked with miniature asterisks, which are easy to overlook, unlike, say, bold type. Nyttend (talk) 00:18, 17 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

Beyoncé album track list templates

[edit]
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was keep. Note that this close goes against precedent set by at least three similar discussions. This might indicate a shift in consensus, but should not be read into too much. Primefac (talk) 21:41, 2 April 2019 (UTC)[reply]

Redundant to {{Beyoncé songs}}, which provides navigation to all the songs on these albums in one template, even displaying them by album in track order. StarcheerspeaksnewslostwarsTalk to me 00:22, 14 March 2019 (UTC)[reply]

  • Keep. These four are not redundant to the "Beyoncé songs" template because they serve different purposes. One is a complete Navbox and the other four are list shortcuts which get inserted into song Infoboxes. BLAIXX 11:12, 14 March 2019 (UTC)[reply]
The purpose of each is to navigate to the other songs on the albums. No need for both and there is numerous precedent to delete the track list templates over the navigational boxes. StarcheerspeaksnewslostwarsTalk to me 17:19, 15 March 2019 (UTC)[reply]
Given that Navboxes are not viewable on mobile (which makes up over 50% of Wikipedia's traffic), I'd argue that these track listing templates still serve a purpose to many readers. BLAIXX 18:38, 18 March 2019 (UTC)[reply]
on mobile, you simply click on the album link to see the list of tracks. Frietjes (talk) 16:18, 22 March 2019 (UTC)[reply]
The purpose is to navigate to other songs from the album which only one template does (the navbox, which is even more complete by allowing navigation to songs on other albums as well). The track listing templates aren't even included on all the song articles for the respective album, preventing navigation to and from every song on the album. The navigational box does do that. This has been the precedent that was set over 3 years ago (see WP:TfD/2015 Dec 16). StarcheerspeaksnewslostwarsTalk to me 01:07, 27 March 2019 (UTC)[reply]
You say that the track listing templates aren't included on every song in the album but is there any reason why they cannot be added? Just because a template isn't fully implemented, doesn't mean it's worse nor is it grounds for deletion. Regarding the 2015 discussion, I'd like to point out that consensus can change on Wikipedia, especially over a longer period of time. BLAIXX 12:05, 27 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was relisted on 2019 March 21. Plastikspork ―Œ(talk) 22:32, 21 March 2019 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The following discussion is an archived debate of the proposed deletion of the template below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).

The result of the discussion was delete. (non-admin closure) Zackmann (Talk to me/What I been doing) 17:26, 21 March 2019 (UTC)[reply]

This is a discussion about whether the Novabox Template:Dinah Jane should be reverted or deleted. Feel free to place your thoughts and votes. She currently has only two singles is that enough to hold a stand alone Template? Welcometothenewmillenium (talk) 10:22, 14 March 2019 (UTC)[reply]

  • Comment I've taken the liberty of copypasting the nominator's comments at the corresponding AfD page, where the nominator originally (and erroneously) tried to place the nomination. As for me, having a template for a artist with two singles and no album seems questionable, but I'm insufficiently template-savvy to feel comfortable turning that into a formal !vote. --Finngall talk 15:47, 14 March 2019 (UTC)[reply]
  • Delete This template needs to be deleted ... She has only released two singles. As far as I am aware a strong novabox for it to be considered notable. Needs more than just two singles ... more so four singles plus, maybe an album, a supporting tour date, etc ... all these would qualify as notable for a novabox template. Ms. Jane I am afraid has not released the music that makes her box notable enough.Welcometothenewmillenium (talk) 03:36, 15 March 2019 (UTC)[reply]
  • Delete The items in the navbox already sufficiently link to and from one another without it. StarcheerspeaksnewslostwarsTalk to me 06:40, 15 March 2019 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).