Aug 14 2019
I hadn't noticed that the default presentation has suddenly been changed from User to "User+Spider".
Jun 2 2019
Jul 10 2018
@GoranSMilovanovic, thanks for your replies. I now have a better understanding of the hub-tabs. After some pondering I feel the most useful parameter would be: the number of links divided by the total number of links for the target wiktionary. In connection with this approach, it would be better not to add a percentage of the total number of pages for the target wiktionary but present the percentage of the total number of links instead. So I amend my original suggestion made Jul 9, 11:03 PM. This would make the different presentations more consistent with one another. The amount of pages without any wikilinks has often to do with specific choices made by a wiktionary, like putting flected forms or different spelling or script on separate pages or not. These choices are not very relevant for interwikilinks and when comparing numbers of interwikilinks I expect more meaningful results when we ignore them.
Jul 9 2018
Finally the Links Dataset. I understand why the lines are duplicated. Unfortunately the search function operates on all columns, making it difficult to create useful lists.
- Assuming that the search-function is able to discern interpunction symbols, would it be possible to add a colon to all the language codes in the first column and a period to the codes in the second column (e.g. en: and en.)? It would still be possible to search on the present two or three letter codes, but by adding the colon or the period you could select "clean" lists.
- To expand on this proposal: some of the two letter codes are part of the three letter codes. So it is impossible to select 'an' without selecting 'ang' en 'zh_min_nan' too. Using a semicolon and comma for codes having over two letters would create the possibility to select an: without selecting 'zh_min_nan;'
The "Hub tabs" are a little overcrowded. I suspect that most of the lines all are connected to the same top or bottom wiktionaries by size. Maybe it would be more informative if we could adjust for the size of the wiktionaries involved. What I forgot in my earlier remarks: wiktionaries are not just different in size, but they may also differ in the number of pages without any wikilink. On the other hand: although it is nice to know, I don't see a real practical use for this type of information anyway. Maybe we should just enjoy the pictures.
The My Wiktionary tab is interesting. Presently it only shows the absolute number of links. To me it would be useful if this was also expressed as a percentage of the number of "Good pages" in [http://wikistats.wmflabs.org/display.php?t=wt this table]: sometimes a high number is mainly the result of the target wiktionary having many pages, sometimes it really has to do with a strong overlap between projects, which would be indicated by differences in the percentages.
@GoranSMilovanovic I was referring to the additional request by Pamputt. It could be realised as a kind of filter on the results of "I miss you" showing only links to pages that contain a word in the language of the selected wiktionary. But I don't know whether this information is accessible in the Cognate database, because the interwikilinks only need the page title, not the page content.
@GoranSMilovanovic Thanks a lot! The "I miss you"-page is what I hoped for. Would it be possible to give the dashboard a format that could be transcluded in a Wiktionary page?
Mar 14 2018
Thx, I'm starting to understand now.
There was another update, showing 1 stripped tag en 0 for both the misnested and obsolete tags. Only the Missing end tag remains stubbornly at 11, while the subpage is showing the correct number, 8.
Mar 12 2018
The main page Special:LintErrors on Dutch Wiktionary has been updated this morning, showing as a new find an old page with both a misnested tag and an obsolete tag, which of course have been corrected by now. What puzzles me is that the counter for "Missing end tag" was and is at 11 pages, with the corresponding subpage only showing the 8 pages that have become our baseline. If it had been 10 I would consider it the result of rounding, but how do we get to 11?
Mar 10 2018
For the record, looking at Special:LintErrors on Dutch Wiktionary the lag between a correction and an update presently seems to be 138 hours (nearly six days), while the subpages for particular errors are updating immediately.
Oct 28 2017
Aug 25 2017
May 4 2017
Thanks for the interim solution. I have informed the WikiWoordenboek community and I will see if there is a fast way to purge all the pages involved.
At the moment editing a page on Dutch Wiktionary has the effect of removing all interwikilinks of that page. Both Cognate and the datacenter switch were presented with assurances that everything was well-prepared. The message concerning the datacenter switch mentioned that a big team was standing by to solve unexpected problems. I strongly support making this "Unbreak now!"