This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
This template is within the scope of WikiProject Medicine. Please visit the project page for details or ask questions at Wikipedia talk:WikiProject Medicine.MedicineWikipedia:WikiProject MedicineTemplate:WikiProject Medicinemedicine
This page has archives. Sections older than 28 days may be auto-archived by Lowercase sigmabot III if there are more than 4.
Unknown parameter → weird result
|MeshID=C538421 works fine, but someone accidentally entered |MeSH=C538421 on a page. That unknown parameter does not (of itself) display its value, and causes no error message. Furthermore, "any" unknown parameter, such as |flerb=grom, does the same. (Maybe this behavior is expected; I don't know.)
On one page, [Neurodegeneration with brain iron accumulation], entering |MeSH=C538421 instead of |MeshID=C538421 produced a weird broken MeSH link, with incorrect link text and incorrect target URL, but they seemed to use the value of that unknown parameter:
However, the same thing happens (only there) with |flerb=C538421, |MeSH=C123456, or no unknown parameter at all. Even when I reduced that page to nothing but {Medical resources} (in Edit Preview), the same thing happened. So the absence of|MeshID=<something> caused it.
This template collects a value for |MeshID= from Wikidata, but overrides it if |MeshID=<something> is specified locally. (Documentation says "Some parameters' labels are automatically populated from Wikidata; but can be overridden locally.")
This template collects a value for |MeshID= from Wikidata. It received mangled data (C538421, C538421) from Wikidata and failed to de-mangle it. Sorry to report this. -A876 (talk) 16:33, 17 June 2023 (UTC)[reply]
Update: Wikidata:Q16892735 currently shows two MeshID identifiers (with the same value, but different references). (I would fix this after a few days.) Wikidata even shows a little circled exclamation point next to each one, which pops up upon hovering, "This statement has potential issues." (Each one shows a separate link (with correct link text and URL).) This is why Wikidata [appears to be] returning C538421, C538421.
A little coding could: detect and remove the duplicate identifier(s); create multiple links (one for each unique identifier); simply discard the extra identifier(s); take the arithmetic mean of all 'n' identifiers (haha); -or- modify its request so that it gets back only the first identifier. -A876 (talk) 17:04, 17 June 2023 (UTC)[reply]
I'm not sure how many WP:MED editors have this page on their watchlists; so it's probably worth dropping a notification over at the project talk page to confirm the project has opted back-in to WD integration for this nav template (looks that way when I'm skimming the archived posts, but interaction was limited).
WRT: start with the ICD-11 – there has been a recent sandbox effort at doing just this with limited success.
WD has two relevant properties:
d:Property:P7807 which is the unique "linkID" for the online browser
We can get the template to either display the code but have a broken link to the online browser,[1] or a working link that displays the linkID instead of the code.[2]
Could be an easy fix for someone that knows LUA markup, but the doc page for Module:WikidataIB isn't the easiest to understand from my absolute novice approach. I've yet to reach out to a technical expert, however, as it's just as likely that I'm at the wrong page for self–guiding the fix needed.
Umbrella conditions can have multiple applicable ICD codes, yet some QIDs only list the linkID. Compare Coronary artery disease to d:Q844935, for example. So any markup will need to ignore the presence of P7807 alone.
Also, if a QID did have multiple ICD-11 codes listed, the two properties are stored without reference to each other (as far as I can tell). So we might be better trying to get the template to utilise P7329 alone and parse it into the local {{ICD11}} template (which utilises module:ICD11). If that's even possible? Little pob (talk) 16:55, 19 January 2024 (UTC)[reply]
Template-protected edit request on 25 October 2024
This edit request has been answered. Set the |answered= parameter to no to reactivate your request.
Actually, it seems that the old URL does redirect to the new URL but only over HTTP. In any case we should make the change to the new URL. TheDragonFire (talk) 09:41, 1 May 2025 (UTC)[reply]