Misplaced Pages

:Templates for discussion/Holding cell - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Templates for discussion

This is an old revision of this page, as edited by Blaixx (talk | contribs) at 11:16, 2 August 2019 (To merge: re-categorize). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 11:16, 2 August 2019 by Blaixx (talk | contribs) (To merge: re-categorize)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) Shortcut
Deletion discussions
Articles
Templates and modules
Files
Categories
Redirects
Miscellany
Speedy deletion
Proposed deletion
This page has a backlog that requires the attention of willing editors.
Please remove this notice when the backlog is cleared.

If process guidelines are met, move templates to the appropriate subsection here to prepare to delete. Before deleting a template, ensure that it is not in use on any pages (other than talk pages where eliminating the link would change the meaning of a prior discussion), by checking Special:Whatlinkshere for '(transclusion)'. Consider placing {{Being deleted}} on the template page.

Closing discussions

The closing procedures are outlined at Misplaced Pages:Templates for discussion/Closing instructions.

To review

Templates for which each transclusion requires individual attention and analysis before the template is deleted.

To merge

Templates to be merged into another template.

Arts

I've looked at this merger and found that a lot of the parameters are music service specific. While it sounds easy merging these there would have to be large changes and probably even a specific module which kind of defeats the purpose of the merger. List of parameters and my opinions on them can be found in my sandbox, but I would like others opinions on this. Tagging Gonnym since they have expressed interest in other infobox mergers. -- Trialpears (talk) 13:02, 21 July 2019 (UTC)
So lets start with a general note - a lot of times people that create these infobox aren't thinking about standardization and correct usage, but just copy/paste from some place else and what "feels" good at that moment. Mergers is a good time to clean these templates, not bring those mistakes over. So looking at the logo parameter, you have a |service_logo= one as well. There is absolutely no reason to add it in the merge. With that in mind, you should really check if the alt parameter names are used, and even if they are used, if they are correct. Once you're done cleaning that list, it will be easier to see what's needed. Another tool you should use is hastemplate:"Infobox online music service" insource:/owner*=*/ to see how parameters are being used (and if they are being used). |protocol= has 14 uses, 13 are "HTPPS". Seems a bit pointless as far as parameters go. |avalibility= seems to be misused, with some adding countries, while others dates (and maybe others do something else as I haven't check them all). If you feel you understand these templates enough, create a sandbox version with how you think the merge should go, a version in the /testcases to show that everything works, and post it on the talk page for comments. If no one objects, then just merge it. --Gonnym (talk) 14:02, 21 July 2019 (UTC)
As an additional note - large changes are okay. There are often parameters specific to one template that aren't found in the target template, and they just need to be added in. It's not the end of the world to add a parameter or five to the target template, since it is a "merge"; if the templates were pure duplicates it would be dead-easy to just redirect the old to the new, or create a subst-able wrapper to deal with it. Primefac (talk) 17:20, 24 July 2019 (UTC)
Gonnym I'm a bit confused about the alias problem regarding |service_logo=. I see no problem with adding that as an alias, but if the consensus is to remove most aliases then that I'll do that. I was just under the impression that aliases were cheap and saw no reason to remove any of them. I have now made a new version in the sandbox with my reasoning for additions and removals explained at User:Trialpears/sandbox/online music service. Input would be appreciated as I have never performed a larger infobox merger before. --Trialpears (talk) 16:27, 29 July 2019 (UTC)
There are usually no issues with adding an alias, especially if you're not going to convert into a wrapper first. However, it does make the code cleaner to only have one (or two) parameter names, if only to avoid confusion down the line. Generally when I add an alias it's as a short-term solution until I (or my bot) can remove the old params. Primefac (talk) 16:31, 29 July 2019 (UTC)

Geography, politics and governance

Religion

  • None currently

Sports

  • None currently

Transport

Other

Meta

To convert

Templates for which the consensus is that they ought to be converted to some other format are put here until the conversion is completed.

To substitute

Templates for which the consensus is that all instances should be substituted (i.e. the template should be merged with the article) are put here until the substitutions are completed. After this is done, the template is deleted from template space.

To orphan

These templates are to be deleted, but may still be in use on some pages. Somebody (it doesn't need to be an administrator, anyone can do it) should fix and/or remove significant usages from pages so that the templates can be deleted. Note that simple references to them from Talk: pages should not be removed. Add on bottom and remove from top of list (oldest is on top).

  • None currently

Ready for deletion

Templates for which consensus to delete has been reached, and for which orphaning has been completed, can be listed here for an administrator to delete. Remove from this list when an item has been deleted. See also {{Deleted template}}, an option to delete templates while retaining them for displaying old page revisions.

  • None currently