Community Wishlist Survey 2017/Miscellaneous/Provide a tool to efficiently analyze the usage of a template

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Random proposal◄ Miscellaneous

Provide a tool to efficiently analyze the usage of a template[edit]

  • Problem: Like last year, again I want to raise your attention to the fact that working with often used templates and making changes to them is a mess. Why? There is no tool or handy way to get to grips how the template has actually been used and which options one has to consider (or which pages where the template is used need to be edited) when rewriting a template. The tool https://tools.wmflabs.org/templatetiger/ written by User:Kolossos has been helpful for many years, but instead of providing live information it is based on dumps (most half a year old, some two years or even more), and there is no interface (you need to know how to manipulate the URL to filter the information). As someone wrote in last year's survey: While I have big respect to Kolossos' instrument, it's just not enough.
  • Who would benefit: Primarily users who curate and amend templates, secondarily authors who use templates in their articles
  • Proposed solution: Don't know if it is more likely to get Kolossos' tool improved or to get a whole new tool. Solutions that I'd like to see anyway:
    • For the timeliness of data: It'd be nice and a good start if there were at least a monthly update / a monthly dump that reliably gets fed into the tool. Having live data, of course, would be even more helpful.
    • Improving UX and usability: Please provide some interface to facilitate for example searching for a certain text in a certain template parameter, make the table sortable by mouseclick. The dream solution is an interface like the one we know from petscan.
  • More comments:

Discussion[edit]

  • This is a useful tool. Also ping en:User:Bgwhite who might be able to help with updating Enwiki dump to a recent version. Looking at Tools in /data/project/templatetiger/public_html .. there is no entry for enwiki in einspielen.sql .. is this due to disk space constraints on Tools? -- GreenC (talk) 19:58, 14 November 2017 (UTC)Reply[reply]
  • If I want to update the data I have the problem that I lose the database connection after short time. I don't know why.
    We have also a problem with some complex templates in German Wikipedia, which kill the checkwiki script. For my motivation as a user from Germany it would be nice to find a solution for this problem. --Kolossos (talk) 09:42, 15 November 2017 (UTC)Reply[reply]
  • templateparam by Bambots does something similar/related right ? —TheDJ (talkcontribs) 13:43, 15 November 2017 (UTC)Reply[reply]
    • Related: Probably yes. Similar: Not too much. → «« Man77 »» [de] 16:42, 19 November 2017 (UTC)Reply[reply]
      • @Man77: Can you clarify how your request is different than the information provided by templateparam? (I'm not familiar with templatetiger and couldn't figure out how to use it.) Kaldari (talk) 21:01, 20 November 2017 (UTC)Reply[reply]
        • To be honest, I did not know that this tool existed when I posted my request, and so far I have not really understood how to work with it. Stalemate. A tool that only works with the English Wikipedia is, however, absolutely not what I am looking for. → «« Man77 »» [de] 21:32, 20 November 2017 (UTC)Reply[reply]
          • bambots tool only starts collecting information upon request and then only parsing the pages that transclude the actual template. This might require you to wait a bit after initially requesting the information for the first time for a particular template, but afterwards, its more up to date and as a benefit takes significantly fewer resources. The tool also allows you to check validity of param keys and values, by matching them with their TemplateData where possible. Not sure why it's only available for en.wp. Templatetiger seems a more brute force solution that parses all template usage. Both have their advantages, I guess, but both have commonalities as well. It should be noted however, that templatetiger is excluded from backups (quite rare) because of its size. —TheDJ (talkcontribs) 14:59, 21 November 2017 (UTC)Reply[reply]
            • For my purposes having the template information "on request" would be enough, but the support of templates without TemplateData is not a mere nice-to-have. → «« Man77 »» [de] 17:23, 22 November 2017 (UTC)Reply[reply]

Voting[edit]