Board Thread:New Features/@comment-24739709-20150929231108/@comment-24473195-20160204215613

Gaarmyvet wrote: Well, if you can pull a list of pages that don't have an infobox and I know you can (Insights) and if you can pull a list of redirects and I know you can (redirects show in italics in ALL PAGES) then show me A minus B. Whose "favorite report" are you talking about?

I don't really know your schema or I'd try to write the code, not that it would do me any good.

If the Insights leveraging is a Wikia product, then leverage it so it works for the greatest number of people. I'm having trouble getting past the idea that everything Wikia is doing is based on making wikis look good to the casual user instead of making it easier for those of us who labor to keep the wheels from falling off. If you know how to use javascript, then it is quite easy to generate numerous reports using the Mw:API:Query api. It is also possible to produce the reports that you want by changing and filtering the results. In fact, I've been using a slightly modified report script created by User:452 called [Maintenance] that generates custom daily reports that are easier to manage.

Changing the defaults can mean very time consuming and inefficient queries. For example, Lyrics wikia has more than a million pages, and if each of those contains something that needs to be reported, that's a considerable issue processing that many pages so many times. In fact, it is highly likely that some reports are deactivated on some wikis because of the effect on the servers (e.g. English wikipedia).

Anyway, as far as infoboxes, images and insights are concerned. Images from templates are also sometimes not useful to include in the reports because some wikis do include images in their stub or "notice" templates that aren't related to the article and not useful  for readers.