User talk:Mike Peel/Archive 6
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | ← | Archive 4 | Archive 5 | Archive 6 | Archive 7 | Archive 8 | → | Archive 10 |
Please stop automatic addition of Wikidata Infoboxes to Category Pages (!)
A category page is not intended to explain a topic in detail or be presented in an article format. You're cluttering the category views with information that is not primarily relevant (and often plain useless due to lack of data in wikidata) for users seeking an organized media index.
Please by all means, let editors do the choice manually when to add infoboxes to category pages. There are few where this actually makes sense.
Also note that some category pages with navigation toolbars completely broke in layout due to the addition of the wikidata infobox (!). They showed unusual extra height that was not shown without the infobox. While you may argue in these cases that there is something weird in the navbar templates that should be fixed (and I agree), the argument remains that you should not potentially break the layout of pages without a review process of the result. Your bot does not seem to include this process.
While the last paragraph gave technical reasons, the stronger argument is that the wikidata infoboxes are displaced on category pages and blur the focus from the subject matter more often than not.
I do not say these Infoboxes are generally useless, but they mostly are within that (cat) namespace's context. I'd suggest to enhance Gallery or Article Pages with them, but within the scope of category pages they are misfits, mostly.
Greetings --84.135.124.25 19:42, 6 September 2018 (UTC)
- Most people seem to like them, e.g. see [1]. Particularly for their multilinguality. They were designed specifically for category space, although they can be used in galleries as well if people want. The bot deployment shouldn't be causing problems with navbar templates, if you see cases where it is (or where there are any other technical problems) then please let me know and I'll investigate. Thanks. Mike Peel (talk) 21:44, 6 September 2018 (UTC)
- I'm one of those. The infobox shows a map (I work many cats that are about a place) and other handy details. Yes, sometimes it makes a mess of a layout. So, I fix the layout. Jim.henderson (talk) 22:15, 6 September 2018 (UTC)
- I usually find Wikidata Infoboxes on the category pages I'm interested in quite helpfull too and prefer having them there, rather than on gallery pages.--Hjart (talk) 23:59, 6 September 2018 (UTC)
- I also like them. --Jarekt (talk) 17:31, 7 September 2018 (UTC)
- I usually find Wikidata Infoboxes on the category pages I'm interested in quite helpfull too and prefer having them there, rather than on gallery pages.--Hjart (talk) 23:59, 6 September 2018 (UTC)
- I'm one of those. The infobox shows a map (I work many cats that are about a place) and other handy details. Yes, sometimes it makes a mess of a layout. So, I fix the layout. Jim.henderson (talk) 22:15, 6 September 2018 (UTC)
- I also like them. :-) But is there or could there be set some CSS that makes it possible not to display them perhaps? --Marsupium (talk) 19:57, 7 September 2018 (UTC)
- From the template's documentation: "It can be hidden by adding
#wdinfobox { display: none;}
to Special:MyPage/common.css." Thanks. Mike Peel (talk) 20:13, 7 September 2018 (UTC)
- From the template's documentation: "It can be hidden by adding
- Again, there's no point in repeating wikidata content on category pages. You still miss the point of what category pages are about - they're not meant to explain a topic, they're rather indices to a topic. If you plaster the category pages with infoboxes you're effectively ruining the way data has been organized for decades now. Another of you guys will pop up and say: Hell, we got infoboxes, why not copy+paste some article abstracts to the category page as well (and on and on..).
- You need to obey the structure as it was designed instead of redesigning it. The whole purpose of this namespace separation is to organize data in a particular way. You are blurring this separation and additionally you're slowing down the navigation through the category system (after all your bot is non-moderated and plasters an infobox on each and every cat page it sees fit. The concept of the infobox itself was designed for article pages, the templates to help side navigation in the cat multitree are navbars instead (with maybe a small logo, but else strictly text).
- People had been annoyed even by having these navigation bars in the cat pages for exactly this reason: Some years ago, they feared this would be the start to add other stuff like these boxes.
- The problem is not that these infoboxes are not useful, but they are a misfit in the place (cat pages) they are currently used (and using automation to drop them is another misfit (!) - bots should fix spelling mistakes or aid in fixing links, but you're using them to dictate content and layout that is otherwise moderated and edited by humans for a reason (!) ). Thanks! --84.135.112.208 01:43, 8 September 2018 (UTC)
- We clearly have different philosophies here, then. I'm not so purist - categories are there to be useful, and adding context makes them more useful, which the infoboxes do. People have been adding context to categories for a very long time, but in a monolingual way - a few description lines at the top of the category, for example, that only work in one language. The infobox does that in a much more multilingual way, so that you no longer need to know English to browse Commons. Plus it shows a map. Plus it auto-adds categories for people/monuments/etc. Plus it sorts out interwikis where needed. ... While there are quite a few cases where more info needs to be added to Wikidata so sometimes it doesn't display much, hopefully it helps draw attention to where editors can add some more info to make it more useful, which wouldn't happen if it wasn't being bot-added/always displayed. Thanks. Mike Peel (talk) 22:25, 10 September 2018 (UTC)
Wiki Loves Monuments ti aspetta, con centinaia di nuovi comuni fotografabili
Gentile Mike Peel, ti ringraziamo ancora una volta per la tua passata partecipazione a Wiki Loves Monuments (WLM). Il più grande concorso fotografico del mondo si svolge anche questo settembre per documentare e promuovere il patrimonio culturale italiano, con una licenza copyright libera.
Quest'anno è doppiamente facile partecipare: gli oggetti fotografabili coprono quasi 1000 comuni in più, grazie all'adesione di centinaia di nuovi enti fra cui Roma, e alla possibilità di fotografare circa 2000 alberi monumentali. Controlla le liste di monumenti fotografabili! Carica tutte le foto che hai e magari organizza una visita presso i monumenti che ancora non hanno una foto.
Quest'oggi il Parlamento europeo ha respinto la proposta di estendere la libertà di panorama. E allora scattiamo e pubblichiamo tutte le foto che possiamo, almeno per questi monumenti per cui ci è legalmente consentito!
Grazie, Nemo 16:08, 12 September 2018 (UTC)
Sorry I'm behind with WikidataIB
Hi Mike,
Sorry, I've been away for the last three days visiting friends. I'm also away for the next two days at a WMUK Board meeting, so I can't do much before Sunday. If you can hold the fort until then, I'll try to catch up when I'm back home. Cheers --RexxS (talk) 22:26, 13 September 2018 (UTC)
- @RexxS: I've been feeling like I owe you an apology for not keeping up with making complete use of the new functionality you keep adding at my request! I don't think there's anything outstanding that's very urgent, so don't worry about it, and have a good(?) board meeting! Thanks. Mike Peel (talk) 10:23, 14 September 2018 (UTC)
Global messages
m:Wikimedia Forum#Commons will soon stop accepting some GFDL-only media
I think all wikis that allow local uploads should be informed so they can adjust bots that move files to Commons and things like that. Is there some way to have a bot deliver a message or something? - Alexis Jazz ping plz 15:45, 14 September 2018 (UTC)
- @Alexis Jazz: I don't know, sorry. I thought there was a page for this at m:Global notifications, but it seems my knowledge about that is rather out of date! Maybe ask for it to be mentioned in m:Tech/News, or in en:WP:SIGNPOST? Thanks. Mike Peel (talk) 16:05, 14 September 2018 (UTC)
I'm using a pic of yours :)
Hey Mike, I'm leaving this message just to let you know I'll be using this picture you took & uploaded in one of my lectures at the university. Thanks for sharing such amazing images! ESM (talk) 17:03, 14 September 2018 (UTC)
- @ESM: Thanks for letting me know! Out of curiosity, which topic/university did you use at? Thanks. Mike Peel (talk) 22:53, 14 September 2018 (UTC)
@Mike Peel: I'm teaching contemporary architecture for Art History undergrads at Universitat de Lleida this semester and (maybe it's a bit overkill) I'm using this picture in the first session, when I'll mention that the Industrial Revolution was a turning point for architecture too :) Cheers! ESM (talk) 09:36, 15 September 2018 (UTC)
- That's great, best of luck with the course! Thanks. Mike Peel (talk) 10:35, 17 September 2018 (UTC)
New discussion on Commons talk:Structured data
When we wikidata infobox'd did we de-creator?
Hi. I have had a long habit of adding {{Creator}} to author categories. With the recent push for [[tl|Wikidata infobox}} did we remove the template from the categories? If we didn't, do you believe that we should? My gut feel is that having both would be redundant, and if we are having one, then uniformity would say infobox. — billinghurst sDrewth 03:27, 23 September 2018 (UTC)
- @Billinghurst: Everything that's in the creator template *should* be in the infobox as well, so I'd say it's redundant, and only one should be present. I'd suggest just having the infobox, but I'm biased. ;-) Thanks. Mike Peel (talk) 11:17, 23 September 2018 (UTC)
- Which was my (obviously too subtle) point, the infobox is more universal. Hmm, and I thought they were more universal in addition, clearly I don't pay enough attention. In addition to the two aforementioned templates, I am also seeing {{Interwiki from Wikidata}} and {{Wikidata person}} which all seem to do similar things. I would have thought that apart from Creator, the others could/would/should have their functionality merged, though I guess that I am missing some intricacy. @Jarekt: do you want to chime in here? Can these be merged so we can just apply the one template? I would prefer the simplest possible means to manage. — billinghurst sDrewth 11:37, 23 September 2018 (UTC)
- The infobox auto-includes {{Interwiki from Wikidata}} where it's needed, so that shouldn't need to be manually added any more. For the other one, see Template_talk:Wikidata_person#Migrate_uses_to_Wikidata_Infobox?. I can very easily bot-migrate current uses of {{Wikidata person}} to the infobox, but there doesn't seem to be consensus to do that yet. Maybe that needs a template deletion discussion... Thanks. Mike Peel (talk) 11:41, 23 September 2018 (UTC)
- Which was my (obviously too subtle) point, the infobox is more universal. Hmm, and I thought they were more universal in addition, clearly I don't pay enough attention. In addition to the two aforementioned templates, I am also seeing {{Interwiki from Wikidata}} and {{Wikidata person}} which all seem to do similar things. I would have thought that apart from Creator, the others could/would/should have their functionality merged, though I guess that I am missing some intricacy. @Jarekt: do you want to chime in here? Can these be merged so we can just apply the one template? I would prefer the simplest possible means to manage. — billinghurst sDrewth 11:37, 23 September 2018 (UTC)
Tweaks
- Would you please be able to make {{Wikidata infobox}} behave better in mobile view. The categorised information should probably take priority over the infobox. People have come for the content, not the infobox. Noting that one does not get the option to hide the infobox in the mobile view. Thanks. — billinghurst sDrewth 12:20, 23 September 2018 (UTC)
- Dealing better with circa dates. At Category:Alfred Odgers we see a person who was born sometime in late June or early July 1844, however, the use of circa there has thrown out the categorisation for birth. — billinghurst sDrewth 13:01, 23 September 2018 (UTC)
- @Billinghurst: Can you post these at Template talk:Wikidata Infobox please? I'm happy to make changes, but some of them will need other people's involvement, and it's easier to keep track of there. Thanks. Mike Peel (talk) 13:26, 23 September 2018 (UTC)
- That said, I've disabled showing the infobox on the mobile version in the infobox sandbox - try Category:Torbenfeldt Slot as an example. Thanks. Mike Peel (talk) 13:33, 23 September 2018 (UTC)
Missing infoboxes
Hi Mike, I see some areas on commons where a lot of infoboxes are missing. For example: Category:Streets in Paris by arrondissement. Rudolphous (talk) 13:05, 26 September 2018 (UTC)
- @Rudolphous: It's deliberate to try to reduce the number of empty infoboxes. Pi bot currently checks for instance of (P31)=Wikimedia category (Q4167836), and doesn't add the infobox unless category's main topic (P301) is present. Thanks. Mike Peel (talk) 14:09, 26 September 2018 (UTC)
- A shame if any cats with category combines topics (P971) were excluded. That information, translated, might be quite useful for international readers. Jheald (talk) 14:18, 26 September 2018 (UTC)
- @Jheald: That's a good point - I've modified pi bot to look for P971 values and to add the infobox in those cases, running now. Thanks. Mike Peel (talk) 14:38, 26 September 2018 (UTC)
- A shame if any cats with category combines topics (P971) were excluded. That information, translated, might be quite useful for international readers. Jheald (talk) 14:18, 26 September 2018 (UTC)
- Oke, that's why. The new taxobox looks great btw. Regards, Rudolphous (talk) 19:14, 26 September 2018 (UTC)
Structured Data - upcoming changes to viewing old file page revisions
Gadget-VIAFDataImporter
- Help:Gadget-VIAFDataImporter
- https://commons.wikimedia.org/w/index.php?title=Category:Alisha_Boe&diff=322202890&oldid=322195875
- https://www.wikidata.org/w/index.php?title=Q19609745&diff=754318422&oldid=754305458
- https://commons.wikimedia.org/w/index.php?title=Category:Alisha_Boe&diff=next&oldid=322206530
You can connect the dots of what I'm trying to say. - Alexis Jazz ping plz 20:37, 28 September 2018 (UTC)
- @Alexis Jazz: If you want to start an RfC/discussion about disabling that gadget, I'd be happy to support it, and/or co-author it if you want. I've probably led enough discussions about this kind of thing so far this year. ;-) Thanks. Mike Peel (talk) 22:57, 28 September 2018 (UTC)
- Actually I'm not sure about the best course of action. User talk:CallyMc#VIAF asked if there was a side panel gadget for this. The addition of VIAF is useful, but the information should be added to Wikidata instead. I imagine few people leisurely browsing Wikidata, so maybe VIAFDataImporter can be reworked. Maybe some info from https://commons.wikimedia.org/w/index.php?search=hastemplate%3A%22Authority+control%22&title=Special%3ASearch&profile=advanced&fulltext=1&ns14=1 can be imported into Wikidata. - Alexis Jazz ping plz 23:31, 28 September 2018 (UTC)
- @Alexis Jazz: I don't know the answer in that case. I'd suggest asking about this at d:Wikidata:Project chat. I thought most human authority control had already been imported into Wikidata a few years ago... Thanks. Mike Peel (talk) 23:37, 28 September 2018 (UTC)
- Actually I'm not sure about the best course of action. User talk:CallyMc#VIAF asked if there was a side panel gadget for this. The addition of VIAF is useful, but the information should be added to Wikidata instead. I imagine few people leisurely browsing Wikidata, so maybe VIAFDataImporter can be reworked. Maybe some info from https://commons.wikimedia.org/w/index.php?search=hastemplate%3A%22Authority+control%22&title=Special%3ASearch&profile=advanced&fulltext=1&ns14=1 can be imported into Wikidata. - Alexis Jazz ping plz 23:31, 28 September 2018 (UTC)
Structured Data - IRC office hours today, 4 October
Structured Data - search prototype
Categories ready to connect to wikidata
Hi Mike, harvested another ~ 2000 pages: [2]. Kind regards, Rudolphous (talk) 11:06, 5 October 2018 (UTC)
- @Rudolphous: Done. Thanks. Mike Peel (talk) 00:27, 6 October 2018 (UTC)
- Hi @Mike Peel: , another one is ready: [3]. Have a nice weekend. Rudolphous (talk) 04:13, 7 October 2018 (UTC)
- Hi Mike, did you miss my message? Rudolphous (talk) 05:46, 9 October 2018 (UTC)
- @Rudolphous: Sorry, I've been travelling. Done now. Thanks. Mike Peel (talk) 11:51, 9 October 2018 (UTC)
- Thanks a lot, connected infoboxes to when possible. Rudolphous (talk) 09:08, 10 October 2018 (UTC)
- @Rudolphous: Sorry, I've been travelling. Done now. Thanks. Mike Peel (talk) 11:51, 9 October 2018 (UTC)
- Hi Mike, did you miss my message? Rudolphous (talk) 05:46, 9 October 2018 (UTC)
- Hi @Mike Peel: , another one is ready: [3]. Have a nice weekend. Rudolphous (talk) 04:13, 7 October 2018 (UTC)
Wikidata infobox logo language
Why am I not seeing the English logo? (I use Commons in English) - Alexis Jazz ping plz 14:21, 10 October 2018 (UTC)
- @Alexis Jazz: The infobox uses the first logo it fetches from Wikidata, not looking at the language. I'll see if I can modify that soon. BTW, it's best to raise this kind of issue at Template talk:Wikidata Infobox to keep them all in one place. Thanks. Mike Peel (talk) 14:51, 10 October 2018 (UTC)
"header" at wikisource
I am here to see if I can interest you in a task at source.
I have been working on a wikidata set for a multi-volume set of books. I have made use of the "follows" and "followed by" properties at wikidata for the first part of the first volume. I did this for the purpose of not manually inputting the values in the sources header template.
I was told that I cannot do this (different from "no one can do this" or "it cannot be done"), which is true as I seem to be on Permanent Autopatrol there -- which is fine by me.
Additionally, a much bigger task of generating a Table of Contents, as one was not included in the edition that is at source.
wikidata:Q56760778, Part 1 has the main "sections" (in this case, plant families) and all have the follows and followed by properties. The first seven families (found in "Part of", each with series ordinals) have been subdivided into mostly the species included but some have genus -- as was depicted in the book.
I can make links to templates and such at wikisource, if you are interested....--RaboKarbakian (talk) 14:19, 13 October 2018 (UTC)
Can you check?
Hello, just to let you know, I did that in order to list the pages where there is a generated gallery, wrong or right? Christian Ferrer (talk) 17:39, 14 October 2018 (UTC)
- @Christian Ferrer: It looks OK, although it's going to be added to the same page multiple times rather than just once, which isn't ideal. I can't think of a better way to do it though - it could be added to Template:Wikidata list, but that's also used for non-gallery pages. Thanks. Mike Peel (talk) 10:49, 15 October 2018 (UTC)
Hello Mike,
What category did {{VNNoDisplay}} add ?
BR Liné1 (talk) 19:40, 19 October 2018 (UTC)
- @Liné1: The idea is that the code demo'd at User:Mike Peel/VN returns nothing (so that the infobox line is then blank), but it adds the page to several categories right now, namely Category:Biology pages with wikidata item specified in VN and Category:Interwiki from wikidata. "nocat" doesn't seem to disable those. It would be useful if it at least disabled the first category (it can be added elsewhere in the infobox if needed). The "interwiki from wikidata" part is actually redundant with code elsewhere in the infobox that adds {{Interwiki from Wikidata}} where necessary, so an option to disable that completely would be good. Thanks. Mike Peel (talk) 22:54, 19 October 2018 (UTC)
- Hello Mike. Understoud. I will try my best. Cheers Liné1 (talk) 16:44, 20 October 2018 (UTC)
Pi bot
Hi Mike, it seems pi bot is out of inspiration. Maybe you can inspire him :-) Rudolphous (talk) 06:37, 21 October 2018 (UTC)
- It's going to be a bit intermittent until next week, as I'm currently traveling and it seems that the raspberry pi crashed... Thanks. Mike Peel (talk) 07:41, 21 October 2018 (UTC)
Structured Data - IRC office hour today, 1 November
Structured Data - IRC office hour today, 1 November
Structured Data - copyright and licensing statements
New category for Wikidata Infobox
Hi, Mike. I know I normally complain about misplaced locations and coordinates to Wikidata Infobox, but this time I'm not. Is there any way you can lure the bot to Category:Pine Hollow Cemetery (Oyster Bay, New York)? I've even got the coordinates listed informally below the National Register of Historic Places tag. ----DanTD (talk) 15:31, 4 November 2018 (UTC)
- @DanTD: It didn't seem to have a Wikidata item to be matched to, so I've created a new one at Pine Hollow Cemetery (Q58219137) and added the infobox. How does that look? Thanks. Mike Peel (talk) 21:42, 4 November 2018 (UTC)
- So far, so good. The geotag is definitely on target. I thought I saw a link to that site last week, but I forgot what it was. I'll keep looking. ----DanTD (talk) 22:30, 4 November 2018 (UTC)
History of religion
Timeline facts historical ancient egyptian — Preceding unsigned comment was added by 142.169.78.95 (talk) 03:54, 9 September 2018 (UTC)
Removing scholarly articles from Distributed game?
I am getting an unusual number of fuzzy suggestiosn to scholarly articles on the distributed game for commons cats. Do you think you could exclude them? There aren't many situations where those are going to be matched, and if they are: its probably something we could solve with some other workflow (like doi matching or a petscan queue for categories that are in the cat tree for academic articles). Sadads (talk) 02:14, 20 November 2018 (UTC)
- @Sadads: I've made a tweak so that results with instance of (P31)=scholarly article (Q13442814) are no longer shown. They are still in the database, so I can reverse that if needed. See how that goes? Pinging @Joostik, Spinster, BMacZero, and Pigsonthewing: as other big players of the game for info (and thank you all for playing the game!). Thanks. Mike Peel (talk) 21:48, 21 November 2018 (UTC)
“Adding” {{Wikidata Infobox}}
Incnis Mrsi (talk) 15:22, 25 November 2018 (UTC)
Removing categories with (seedlings)
Could you remove categories with the suffix (seedlings) from the set: they are intersection categories of two concepts and keep getting matched against every species and subspecies. They are never going to match discrete concepts on Wikidata. Sadads (talk) 04:40, 1 December 2018 (UTC)
- @Sadads: This one is done. I'm working on the other one. Thanks. Mike Peel (talk) 13:51, 1 December 2018 (UTC)
Adding a filter to work on only matches against names (surnames and given names) and taxons
Could you create some filters based on what wikidata class the fuzzy matches are pointing too? For example, I think i could be very efficient if I were only matching name wikidata items and taxons - helping make less bad matches in the fuzzy matches for other categories for things like people. Right now those are polluting other kinds of class matches. Sadads (talk) 04:49, 1 December 2018 (UTC)
- @Sadads: This is now done, but I'm not sure how long it will take to show up. At some point, a set of buttons should appear below the description that let you select 'Any', 'Taxon' and 'Person'. Be warned that the taxon one is very slow to load, though, as there aren't as many candidate matches for those as there are for people. Thanks. Mike Peel (talk) 14:46, 1 December 2018 (UTC)
- It's showing up for me now, hopefully you can also see it. Thanks. Mike Peel (talk) 16:30, 1 December 2018 (UTC)
- Nice! This is great: I was actually thinking it would be more efficient if surnames/given names were seperated from the people even if they are a small set. The person queue is better but the names are still a thing in and of themselves. Sadads (talk) 18:36, 1 December 2018 (UTC)
- It's possible, but it would probably run too slowly to be of use. At the moment, the game code checks each possible tile before presenting it, and e.g. for people it just skips ones that don't have instance of (P31)=human (Q5). I could cache the info in the database, which would speed things up a lot, but that's a bigger rewrite/restructuring. Thanks. Mike Peel (talk) 20:28, 1 December 2018 (UTC)
- Ah, right that makes sense. Thanks for the thoughtful use of the game. Sadads (talk) 16:16, 2 December 2018 (UTC)
- It's possible, but it would probably run too slowly to be of use. At the moment, the game code checks each possible tile before presenting it, and e.g. for people it just skips ones that don't have instance of (P31)=human (Q5). I could cache the info in the database, which would speed things up a lot, but that's a bigger rewrite/restructuring. Thanks. Mike Peel (talk) 20:28, 1 December 2018 (UTC)
- Nice! This is great: I was actually thinking it would be more efficient if surnames/given names were seperated from the people even if they are a small set. The person queue is better but the names are still a thing in and of themselves. Sadads (talk) 18:36, 1 December 2018 (UTC)
Removing (house number) from the set
Hey Mike -- I am getting a lot of very bad fuzzy matches to numbers around categories with "(house number)" as the suffix -- I expect that we don't have those included in the Wikidata concepts its another one of those intersections that I don't think we will represent anytime soon on Wikidata. Sadads (talk) 03:04, 4 December 2018 (UTC)
- @Sadads: Those matches should not appear any more. Thanks. Mike Peel (talk) 18:33, 4 December 2018 (UTC)
Wikidata : Seoul National University Museum
Hi Mike. I'm sorry, but the image you put here is not the good one. The building is older. I found only this photography [4]. It's necessary to put the good one or nothing, because it's allways a big mistake, for the students, on the campus, they don't know where is the Seoul National University Museum where they can find archaeology and korean old painting (all "chef-d'oeuvres"). Best Regards. (Ismoon (talk) 17:20, 4 December 2018 (UTC))
- @Ismoon: I don't think I added it? You can remove/replace it from Seoul National University Museum of Art (Q7451680) if you want. It looks like it's also used in the English and French Wikipedias. Thanks. Mike Peel (talk) 18:31, 4 December 2018 (UTC)
Multilingual captions beta testing
The Structured Data on Commons team has begun beta testing of the first feature, multilingual file captions, and all community members are invited to test it out. Captions is based on designs discussed with the community[5][6] and the team is looking forward to hearing about testing. If all goes well during testing, captions will be turned on for Commons around the second week of January, 2019.
Multilingual captions are plain text fields that provide brief, easily translatable details of a file in a way that is easy to create, edit, and curate. Captions are added during the upload process using the UploadWizard, or they can be added directly on any file page on Commons. Adding captions in multiple languages is a simple process that requires only a few steps.
The details:
- There is a help page available on how to use multilingual file captions.
- Testing will take place on Beta Commons. If you don’t yet have an account set up there, you’ll need one.
- Beta Commons is a testbed, and not configured exactly like the real Commons site, so expect to see some discrepancies with user interface (UI) elements like search.
- Structured Data introduces the potential for many important page changes to happen at once, which could flood the recent changes list. Because of this, Enhanced Recent Changes is enabled as it currently is at Commons, but with some UI changes.
- Feedback and commentary on the file caption functionality are welcome and encouraged on the discussion page for this post.
- Some testing has already taken place and the team are aware of some issues. A list of known issues can be seen below.
- If you discover a bug/issue that is not covered in the known issues, please file a ticket on Phabricator and tag it with the “Multimedia” tag. Use this link to file a new task already tagged with "Multimedia."
Known issues:
- Search is not currently working on Beta Commons. Search is not needed for testing captions, but service should be restored soon.
- Language name display inconsistencies in multilingual file captions
- Language names for multilingual File captions can run into the caption value in the mobile view
- Deleting a caption field that has text that exceeds the limit does not re-enable the "publish" button
- "Edit" tab for past revisions should be "restore"
- When using the back button, recently added captions sometimes don't display in Chrome
- File Captions can't be edited on mobile browsers
- Wrong font weight for some language labels on SDC captions box
Thanks!
-- Keegan (WMF) (talk), for the Structured Data on Commons Team 20:42, 17 December 2018 (UTC)--See my comments.--Rajesh Unuppally 16:13, 23 December 2018 (UTC)
Category:Uses_of_Wikidata_Infobox_providing_interwiki_links has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you! |
151.36.133.52 03:16, 30 December 2018 (UTC)
Happy 2019
Hi Mike, I see that we reached 2M mark. What a work, and really cool we achieved it :-). Happy 2019 and all the best wishes. Rudolphous (talk) 20:00, 31 December 2018 (UTC)
- @Rudolphous: Happy new year! We're getting there, only another 4 million or so categories to go! Thanks. Mike Peel (talk) 05:45, 1 January 2019 (UTC)
- @Rudolphous: "This category has the following 200 subcategories, out of 2,019,001 total." - I think I'll leave it around that for the day. :-) Thanks. Mike Peel (talk) 09:20, 1 January 2019 (UTC)
- Hi Mike, not sure what you meant with the first part of your comment. Rudolphous (talk) 09:28, 1 January 2019 (UTC)
- See wikidata:User:Jheald/commons - there are circa 6.7 million Commons categories. Thanks. Mike Peel (talk) 09:30, 1 January 2019 (UTC)
- Ah I see. Nice total for today by the way :-). Rudolphous (talk) 09:33, 1 January 2019 (UTC)
- See wikidata:User:Jheald/commons - there are circa 6.7 million Commons categories. Thanks. Mike Peel (talk) 09:30, 1 January 2019 (UTC)
- Hi Mike, not sure what you meant with the first part of your comment. Rudolphous (talk) 09:28, 1 January 2019 (UTC)
Wikidata infobox code
Hi, Mike Peel. Happy 2019! I've read several times {{Wikidata infobox}} is crosswiki compatible. Is that true? I was wondering... would the code need many fixes in order to be adapted, for example, to es.wikipedia categories? Cheers. Strakhov (talk) 18:56, 31 December 2018 (UTC)
- @Strakhov: The code should just work on another wiki, the main issue at the moment is the number of dependencies on different templates/modules that it currently has. There are also some things, like the autocategorisation code, that probably aren't wanted on other wikis, but they should be straightforward to remove from the code. Thanks. Mike Peel (talk) 19:02, 31 December 2018 (UTC)
- Thanks! I'll give this a look in the following days. I guess it'll take me a few days figuring out what to do with every embedded module, but I hope I'll work it out. Strakhov (talk) 19:17, 31 December 2018 (UTC)
- Cool, let me know if there's anything you need help with. Thanks. Mike Peel (talk) 19:19, 31 December 2018 (UTC)
- Thanks! I'll give this a look in the following days. I guess it'll take me a few days figuring out what to do with every embedded module, but I hope I'll work it out. Strakhov (talk) 19:17, 31 December 2018 (UTC)
- Hi. es:Plantilla:Wikidata infobox. I managed to get it work, after creating... 19 modules&templates (I came to think there was no end). Thing is... I did not achieve the template working in categories. here OK and here not OK. Not loading much data from "third party items" except images and official website, it seems. Do you know what fix would be needed? And... well, in the long run it would be nice stripping out the authority control or at the very least (if it's easier) having it collapsed by default. With regard to autocategorisation, I would include only the "Uses of Wikidata Infobox" ("Usos de Wikidata Infobox" after translation) one. Would it work... just removing every unwanted ":Category:" from the code? Thanks! Strakhov (talk) 21:23, 2 January 2019 (UTC)
- @Strakhov: Nice! Sorry for how many you needed to copy over! You missed [7], it now works for non-humans as well. I've also tweaked the infobox code there so that authority control is collapsed by default. See how that goes? Thanks. Mike Peel (talk) 21:40, 2 January 2019 (UTC)
- Hi. es:Plantilla:Wikidata infobox. I managed to get it work, after creating... 19 modules&templates (I came to think there was no end). Thing is... I did not achieve the template working in categories. here OK and here not OK. Not loading much data from "third party items" except images and official website, it seems. Do you know what fix would be needed? And... well, in the long run it would be nice stripping out the authority control or at the very least (if it's easier) having it collapsed by default. With regard to autocategorisation, I would include only the "Uses of Wikidata Infobox" ("Usos de Wikidata Infobox" after translation) one. Would it work... just removing every unwanted ":Category:" from the code? Thanks! Strakhov (talk) 21:23, 2 January 2019 (UTC)
- Thanks for the fix! It looks better now. No red link, no party. Now a few more have appeared :) I'll continue trying to fix the map thing too. Strakhov (talk) 21:50, 2 January 2019 (UTC)
Wikidata list
Hello Mike, I don't manage make a list with {{Wikidata list}} for the query quoted at User:Christian Ferrer/sandbox4. Can you help me please? (if yes, you can edit the sandbox) Christian Ferrer (talk) 22:37, 2 January 2019 (UTC)
- @Christian Ferrer: Since you already had the query, I just added the rest of the wikidata list output code around it, and that's worked. Thanks. Mike Peel (talk) 08:42, 3 January 2019 (UTC)
- No, I managed to do that, the query give me the author labels (see), but I'm not able to retrieve those labels in a wikidata list. Note that I don't especially want a gallery, a list would be sufficiant. Christian Ferrer (talk) 08:52, 3 January 2019 (UTC)
- @Christian Ferrer: Ah, right. That won't work with the gallery setup, since that just uses the QIDs. I've turned it into a regular list, is that more what you were after? Thanks. Mike Peel (talk) 09:04, 3 January 2019 (UTC)
- Yes, very great. Thanks you very much! Christian Ferrer (talk) 09:05, 3 January 2019 (UTC)
- @Christian Ferrer: Ah, right. That won't work with the gallery setup, since that just uses the QIDs. I've turned it into a regular list, is that more what you were after? Thanks. Mike Peel (talk) 09:04, 3 January 2019 (UTC)
- No, I managed to do that, the query give me the author labels (see), but I'm not able to retrieve those labels in a wikidata list. Note that I don't especially want a gallery, a list would be sufficiant. Christian Ferrer (talk) 08:52, 3 January 2019 (UTC)
Adding "Defaultsort=no" for items in Category:Pages with DEFAULTSORT conflicts
Hi Mike,
I would like to let you know, that I reverted your (bot-)addition of "defaultsort=no" to Category:Paul Gauguin. The cause for this Defaultsort-conflict this morning was vandalism to Wikidata's family name-item Q47240376 linked in Paul Gauguin`s own Q37693.
This leads me to the considerations, if it is really useful to simply add "defaultsort=no" to categories rather than reviewing the actual cause and correcting that.
Another group of cases show up in Category:Pages with DEFAULTSORT conflicts under the letter "Q"; those are cases where no English description to the family name Q-item is maintained yet.
And, of course, there is regular vandalism to "Given name" Q-items on Wikidata where IP-users try to make funny statements out of proper names. Also these show up (in masses) in maintenance category "Pages with DEFAULTSORT conflicts", some times with more than 100 entries for the same, single vandalism to a Q-item. Recent subjected examples have been Q18002623 , Q4677161 , Q19729888 and Q18061657 . How do you handle these conflicts ?
Best regards, --Archie02 (talk) 17:04, 4 January 2019 (UTC)
- @Archie02: Thanks for catching that. Adding "defaultsort=no" adds the category to Category:Uses of Wikidata Infobox with defaultsort suppressed, so that it dosen't clutter up the defaultsort-conflict category. I figure that there's no great loss in not having the auto-generated defaultsort in these categories since there is a manual one there already, but sorting through them at some point would definitely be good (and QIDs should never be in the defaultsort string - if you know of examples of these, please let me know and I'll investigate them). I'm tempted to propose removing the manual defaultsorts where they are the same as the auto-generated ones, but there is the concern about the vandalism on Wikidata that could affect quite a few categories at once, so I've held off doing that for now. I do run through the defaultsort-conflict category making null edits before setting "defaultsort=no", to make sure it's not cached vandalism, but that doesn't help with vandalism that hasn't yet been reverted. Bottom line: it's a temporary solution in these cases, and I welcome ideas for handling things better here! Thanks. Mike Peel (talk) 19:06, 4 January 2019 (UTC)
- @Mike Peel: Many Thanks for the explanation. Unfortunately I have no suitable proposal to improve handling at the moment, but will keep thinking about it. Thanks, --Archie02 (talk) 22:05, 4 January 2019 (UTC)
- @Archie02: Another option I forgot to mention before is to absorb defaultsort into the infobox completely - so
{{Wikidata Infobox}}{{DEFAULTSORT:Blah}}
would become something like{{Wikidata Infobox|sort=Blah}}
. That way, I could use code within the infobox to use the manual sort key where available, which would avoid creating any conflicts. It would require quite a lot of bot edits to do that, though, and may be best done at the same time as removing manual sort keys that are the same as those that can be automatically generated... Thanks. Mike Peel (talk) 17:15, 5 January 2019 (UTC)- This indeed sounds interesting. --Archie02 (talk) 18:12, 5 January 2019 (UTC)
- @Mike Peel: An example of what I mentioned earlier ...: Warning: Default sort key "Q60367533, Henri" overrides earlier default sort key "Klagmann, Henri". in Category:Henri Klagmann is caused by item Q60367533 (= the independent item for family name "Klagmann" linked in Henri Klagmann's own Q60367494) is missing a description in language EN (only French language is maintained).
- Btw, if I switch Commons to French language, then there is no Defaultsort-conflict anymore. --Archie02 (talk) 15:23, 6 January 2019 (UTC)
- Weird. @RexxS: wasn't there a switch in place at some point to avoid QIDs being returned in these cases? I'm particularly puzzled by the way it goes away when switching to French, as everything should have "lang=en" set. The code's using Module:CheckWikidataID, but I think that's something I hacked together to check if the wikidata item exists or not, for reasons I can't remember now, and for some reason separately from WikidataIB... Thanks. Mike Peel (talk) 16:02, 6 January 2019 (UTC)
- No Mike, I'm afraid that we don't set lang=en for everything as we want users' own language preferences to be used when displaying labels, sitelinks, numbers, etc. Just because the site language is English, it doesn't mean we should override other languages on this multi-lingual wiki. We do create categories in English as that's the convention here, but that's an exception. If you really want to have no default sort key when the family name has no English label, then I can code it, but I thought we were using the lack of an English label as a prompt to update the Wikidata info? Remember that en is the fallback for all languages. Let me know.
- BTW, Module:CheckWikidataID really doesn't check whether the Wikidata item exists or not; it only checks whether the ID would be valid as an entity-id or property-id:
- Q99999999 (doesn't exist)
{{#invoke:CheckWikidataID|checkValidity|Q99999999}}
→ true{{#invoke:CheckWikidataID|checkValidity|Q42}}
→ true{{#invoke:CheckWikidataID|checkValidity|q42}}
→ true{{#invoke:CheckWikidataID|checkValidity|42}}
→ false{{#invoke:CheckWikidataID|checkValidity|P26}}
→ true{{#invoke:CheckWikidataID|checkValidity|P0}}
→ false
- You may have been using it to filter out instances of P0, which we used as a place-holder, because that isn't a valid id. --RexxS (talk) 17:05, 6 January 2019 (UTC)
- @RexxS: On "lang=en", I meant that
{{#invoke:WikidataIB | getValue | rank=best | P734 | linked=no | name=forename | qid=Q60367494 | spf={{{suppressfields|}}} | fwd=ALL | osd=no | noicon=yes | lang=en}}
should always be the English label, but it returns the QID or French depending on the language set: Klagmann. I think I did checkWikidataID to see if the returned value looked like a QID, and only used it if it was... Thanks. Mike Peel (talk) 17:41, 6 January 2019 (UTC)- (Edit conflict) Post-script: I can see what you were trying to do: filter out values where #property:P734 returns a Qid instead of a label. Unfortunately, whitespace is significant in unnamed parameters, so:
{{#property:P734 | from=Q60367494}}
→ Klagmann{{#invoke:CheckWikidataID | checkValidity | {{#property:P734 | from=Q60367494}}}}
→ false{{#invoke:CheckWikidataID | checkValidity |{{#property:P734 | from=Q60367494}}}}
→ false
- So your filter won't ever trap Qids unless you remove the space (or I modify checkValidity to trim whitespace). The reason it works in French, of course is that
{{#invoke:CheckWikidataID | checkValidity |Klagmann}}
→ false
- And that depends on the behaviour of #property in French, which I don't have any control over. --RexxS (talk) 17:45, 6 January 2019 (UTC)
- Aah, that's it, thanks @RexxS: . I've fixed that in the infobox sandbox. While we're here, could the checkValidity function be moved over to WikidataIB so that we have one less dependency, please? Thanks. Mike Peel (talk) 18:56, 6 January 2019 (UTC)
- I've implemented checkValidity in WikidataIB/sandbox and fixed it so it ignores whitespace. You don't have to remove all those nice spaces if you use this version:
{{#invoke:WikidataIB/sandbox|checkValidity | Q99999999}}
→ true{{#invoke:WikidataIB/sandbox|checkValidity | Q42}}
→ true{{#invoke:WikidataIB/sandbox|checkValidity | q42}}
→ true{{#invoke:WikidataIB/sandbox|checkValidity | 42}}
→ false{{#invoke:WikidataIB/sandbox|checkValidity | P26}}
→ true{{#invoke:WikidataIB/sandbox|checkValidity | P0}}
→ false{{#invoke:WikidataIB/sandbox | checkValidity | {{#property:P734 | from=Q60367494}}}}
→ false{{#invoke:WikidataIB/sandbox | checkValidity |{{#property:P734 | from=Q60367494}}}}
→ false
- Further: I've looked at the behaviour of how we fetch non-linked items. If there is a label in the language specified by
|lang=
, it uses that. Otherwise it looks for a label in the default language, and uses that if it exists, otherwise it uses the QID. That maximises the chance of returning a label (which is what I expected us to want).{{#invoke:WikidataIB | getValue | rank=best | P734 | linked=no | qid=Q60367494 | fwd=ALL | osd=no | noicon=yes | lang=en}}
→ Klagmann{{#invoke:WikidataIB | getValue | rank=best | P734 | linked=no | qid=Q60367494 | fwd=ALL | osd=no | noicon=yes | lang=fr}}
→ Klagmann{{#invoke:WikidataIB | getValue | rank=best | P734 | linked=no | qid=Q60367494 | fwd=ALL | osd=no | noicon=yes | lang=}}
→ Klagmann
- However, I think you're asking for the function to return either the label in the language specified by
|lang=
or the QID if the label doesn't exist, rather than falling back to the user's preference. Is that correct? --RexxS (talk) 19:28, 6 January 2019 (UTC)- Thanks! I think checkValidity will do the job here, so no need to change the behaviour of the language setting right now. Thanks. Mike Peel (talk) 19:34, 6 January 2019 (UTC)
- @Archie02: The fix is now live, please let me know if you spot it happening again. Thanks. Mike Peel (talk) 07:07, 7 January 2019 (UTC)
- I've implemented checkValidity in WikidataIB/sandbox and fixed it so it ignores whitespace. You don't have to remove all those nice spaces if you use this version:
- Aah, that's it, thanks @RexxS: . I've fixed that in the infobox sandbox. While we're here, could the checkValidity function be moved over to WikidataIB so that we have one less dependency, please? Thanks. Mike Peel (talk) 18:56, 6 January 2019 (UTC)
- (Edit conflict) Post-script: I can see what you were trying to do: filter out values where #property:P734 returns a Qid instead of a label. Unfortunately, whitespace is significant in unnamed parameters, so:
- @RexxS: On "lang=en", I meant that
- Weird. @RexxS: wasn't there a switch in place at some point to avoid QIDs being returned in these cases? I'm particularly puzzled by the way it goes away when switching to French, as everything should have "lang=en" set. The code's using Module:CheckWikidataID, but I think that's something I hacked together to check if the wikidata item exists or not, for reasons I can't remember now, and for some reason separately from WikidataIB... Thanks. Mike Peel (talk) 16:02, 6 January 2019 (UTC)
- This indeed sounds interesting. --Archie02 (talk) 18:12, 5 January 2019 (UTC)
- @Archie02: Another option I forgot to mention before is to absorb defaultsort into the infobox completely - so
- @Mike Peel: Many Thanks for the explanation. Unfortunately I have no suitable proposal to improve handling at the moment, but will keep thinking about it. Thanks, --Archie02 (talk) 22:05, 4 January 2019 (UTC)
Wikidata Infobox on enwiki
Just a quick heads-up, in case you hadn't noticed: the Wikidata Infobox has now been copied to English Wikipedia, and is in use on three articles for now. Not by me, I hasten to add. I've cleaned out the self-referential Wikpedia sitelink and the authority control as the two most obvious focal points for complaint, but I'm expecting the usual backlash at some point. You may want to keep your head down if gets as nasty as it usually does. --RexxS (talk) 16:25, 9 January 2019 (UTC)
- @RexxS: Thanks, it seems to be working OK in at least those three articles, but probably there'll be the usual backlash (particularly about unreferenced info). I'm wondering if it would be worth having a configuration wrapper - so most of the code currently at {{Wikidata Infobox}} would move to {{Wikidata Infobox/core}}, and then the main infobox template would have a set of parameter pass-throughs with the option to set the default values (onlysourced=yes/no, but also authoritycontrol=yes/no etc.), do you think that would be worth doing? (It's also on eswp btw, see the discussion at the top of this page at the moment). Thanks. Mike Peel (talk) 16:29, 9 January 2019 (UTC)
- Once it starts being used on different Wikis, you're going to need the ability to alter many of the defaults to suit local conventions, so I'm pretty sure you'll have to move to a wrapper that sets all the localised stuff and a core that contains all of the code common to everybody. That will make life so much easier for those updating the local versions at the cost of one more template to copy initially. We really should make an effort to reduce the number of dependencies as well. I'll see if I can make a usable fork of part of Module:Complex date that encapsulates most of the code but leaves the internationalisation to a single sub-module. In the meantime, is there any more functionality that we could import into WikidataIB? --RexxS (talk) 17:29, 9 January 2019 (UTC)
- @RexxS: I think @Strakhov: probably has the best idea of which modules are needed / most annoying to install - any comments? From my perspective, Template:Wikidata ID is probably the messiest that could do with lua-ising (it's also quite stable, although it'd be good if it could be modified to display multiple values for the same ID at some point). @Laddo's latest change needs checking / moving over from the WikidataIB and infobox sandbox, then I'll try to start working on the wrapper. Thanks. Mike Peel (talk) 20:54, 9 January 2019 (UTC)
- Once it starts being used on different Wikis, you're going to need the ability to alter many of the defaults to suit local conventions, so I'm pretty sure you'll have to move to a wrapper that sets all the localised stuff and a core that contains all of the code common to everybody. That will make life so much easier for those updating the local versions at the cost of one more template to copy initially. We really should make an effort to reduce the number of dependencies as well. I'll see if I can make a usable fork of part of Module:Complex date that encapsulates most of the code but leaves the internationalisation to a single sub-module. In the meantime, is there any more functionality that we could import into WikidataIB? --RexxS (talk) 17:29, 9 January 2019 (UTC)