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 articles
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 articles
Makes sense to include with the current design. Only thing showing in the archives (here and
old template talk) is your 2015 suggestion to add the same (
within this thread)—which predates the 2016 redesign of the template. I'm not sure how many watch this page, so will drop a post in
WT:MED for more opinions.
Little pob (
talk) 21:20, 29 April 2023 (UTC)reply
Do we really want |etymology= or perhaps just an |eponym= option?
A typical etymology would sound like "leukos (λευκός), meaning white + haima (αἷμα), meaning blood", and if the name is longer than one word, it could be unwieldy. I don't think that this would be useful for something like
Myocardial infarction, whose etymology might sound like "from Greek myo for muscle + Latinized Greek kardia for heart and from Latin infarcire "to stuff into".
WhatamIdoing (
talk) 21:50, 29 April 2023 (UTC)reply
We could do what |treatment= does, if we wanted the option of allowing either eponym or etymology?
I'm happy to add the {{TPER}} tag, but want to check where should the new parameter be placed?
MOS:MED says eponyms go in the history section, and an etymology section goes at the bottom of the page, which would suggest it should be placed last within the infobox?
And do we feel the parameter name needs wikilinking? (i.e. do we need to explain what an
eponym is?)
Little pob (
talk) 10:30, 11 May 2023 (UTC)reply
Can you name a few articles in which you'd like the infobox to include the (usually Greek) etymology?
WhatamIdoing (
talk) 14:58, 13 May 2023 (UTC)reply
No. My intent was more to note that an either/or parameter could be done, as you'd be unlikely to need both in the same article.
Little pob (
talk) 15:52, 13 May 2023 (UTC)reply
I agree with you that we would not need both in the same article. However, since I don't think we really have a desire for a non-eponym etymology, I'm inclined to leave out |etymology= entirely.
I agree with you about putting it at the end of the infobox, and I think that linking to eponym would be helpful. We could also use the simpler label of "named after".
WhatamIdoing (
talk) 02:17, 17 May 2023 (UTC)reply
Edit request
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
This doesn't support passing the class= attribute for file links to the Lua module to add CSS classes to them, which is required for hiding them from being chosen by
mw:Extension:PageImages to be shown in
mw:Page previews. See
phab:T301588. Preview images now show up not only in Popups but autogen search results in the new skin and in related article suggestions in MobileFrontend. Some med images such as the one with someone's partly-necrotic intestine being surgically everted could perhaps be left out of these.
47.155.41.104 (
talk) 07:18, 1 September 2023 (UTC)reply
Well
MediaWiki:Bad image list has been a thing for a long time. The issue is page previews just suddenly show up for readers, like when they mouseover a link, or do a search now with the new skin, or in mobile article suggestions. (The overwhelming majority of WP's traffic today is mobile.)
WP:GRATUITOUS suggests avoidance of showing readers things they weren't expecting, which can easily happen when search or mobile suggestions show stuff to them just because an article's title substring-matches something else unrelated.
If people think there should be a discussion on when and where to use the feature sounds good to me. Best to wait until after
US holiday is over.
47.155.41.104 (
talk) 04:32, 2 September 2023 (UTC)reply
Deactivating request pending consensus. I also agree with WhatamIdoing that this isn't a good idea.
* Pppery *it has begun... 01:39, 3 September 2023 (UTC)reply
Edit request 14 December 2023
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Description of suggested change: Infobox images are currently defaulting to being 36% larger than default, but most of them aren't showing specific detail that needs to be magnified in this way. Exceptions can be overridden at the article level when needed. Testing a template edit in the sandbox, removing both instances of |upright=1.36 looks okay.
Done Instead of removing the upright value, I've added two new parameters, |image_upright= and |image2_upright.
SWinxy (
talk) 00:56, 16 December 2023 (UTC)reply
The use on
Electrolyte imbalance (
permalink to current version of that page) reads Causes: hypocalemia. It's not immediately clear from that whether electrolyte imbalance causes hypocalemia, or hypocalemia causes electrolyte imbalance: the word Causes could be taken either for a present tense, third-person verb, or for a plural noun.
The issue isn't that that page is unclear (if that were the issue, I'd go to
Talk:Electrolyte imbalance instead); the issue is that the template can be used in a way that creates an unclear page. So, perhaps "Causes:" should be deprecated, with uses thereof to be replaced by either "Complications:" or "Caused by:", whichever is appropriate? I think that would be unambiguous?
2A0D:6FC2:6A92:3F00:0:0:0:5F9 (
talk) 19:19, 8 February 2024 (UTC)reply
AIUI hypocalcemia is an electrolyte imbalance, so the infobox just needs to be corrected. "Causes" should include things like diarrhea. It was added by a new editor, who might have mistaken it for the |types= parameter. Would you like to fix it, at least to remove ?
WhatamIdoing (
talk) 00:05, 9 February 2024 (UTC)reply
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 articles
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 articles
Makes sense to include with the current design. Only thing showing in the archives (here and
old template talk) is your 2015 suggestion to add the same (
within this thread)—which predates the 2016 redesign of the template. I'm not sure how many watch this page, so will drop a post in
WT:MED for more opinions.
Little pob (
talk) 21:20, 29 April 2023 (UTC)reply
Do we really want |etymology= or perhaps just an |eponym= option?
A typical etymology would sound like "leukos (λευκός), meaning white + haima (αἷμα), meaning blood", and if the name is longer than one word, it could be unwieldy. I don't think that this would be useful for something like
Myocardial infarction, whose etymology might sound like "from Greek myo for muscle + Latinized Greek kardia for heart and from Latin infarcire "to stuff into".
WhatamIdoing (
talk) 21:50, 29 April 2023 (UTC)reply
We could do what |treatment= does, if we wanted the option of allowing either eponym or etymology?
I'm happy to add the {{TPER}} tag, but want to check where should the new parameter be placed?
MOS:MED says eponyms go in the history section, and an etymology section goes at the bottom of the page, which would suggest it should be placed last within the infobox?
And do we feel the parameter name needs wikilinking? (i.e. do we need to explain what an
eponym is?)
Little pob (
talk) 10:30, 11 May 2023 (UTC)reply
Can you name a few articles in which you'd like the infobox to include the (usually Greek) etymology?
WhatamIdoing (
talk) 14:58, 13 May 2023 (UTC)reply
No. My intent was more to note that an either/or parameter could be done, as you'd be unlikely to need both in the same article.
Little pob (
talk) 15:52, 13 May 2023 (UTC)reply
I agree with you that we would not need both in the same article. However, since I don't think we really have a desire for a non-eponym etymology, I'm inclined to leave out |etymology= entirely.
I agree with you about putting it at the end of the infobox, and I think that linking to eponym would be helpful. We could also use the simpler label of "named after".
WhatamIdoing (
talk) 02:17, 17 May 2023 (UTC)reply
Edit request
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
This doesn't support passing the class= attribute for file links to the Lua module to add CSS classes to them, which is required for hiding them from being chosen by
mw:Extension:PageImages to be shown in
mw:Page previews. See
phab:T301588. Preview images now show up not only in Popups but autogen search results in the new skin and in related article suggestions in MobileFrontend. Some med images such as the one with someone's partly-necrotic intestine being surgically everted could perhaps be left out of these.
47.155.41.104 (
talk) 07:18, 1 September 2023 (UTC)reply
Well
MediaWiki:Bad image list has been a thing for a long time. The issue is page previews just suddenly show up for readers, like when they mouseover a link, or do a search now with the new skin, or in mobile article suggestions. (The overwhelming majority of WP's traffic today is mobile.)
WP:GRATUITOUS suggests avoidance of showing readers things they weren't expecting, which can easily happen when search or mobile suggestions show stuff to them just because an article's title substring-matches something else unrelated.
If people think there should be a discussion on when and where to use the feature sounds good to me. Best to wait until after
US holiday is over.
47.155.41.104 (
talk) 04:32, 2 September 2023 (UTC)reply
Deactivating request pending consensus. I also agree with WhatamIdoing that this isn't a good idea.
* Pppery *it has begun... 01:39, 3 September 2023 (UTC)reply
Edit request 14 December 2023
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Description of suggested change: Infobox images are currently defaulting to being 36% larger than default, but most of them aren't showing specific detail that needs to be magnified in this way. Exceptions can be overridden at the article level when needed. Testing a template edit in the sandbox, removing both instances of |upright=1.36 looks okay.
Done Instead of removing the upright value, I've added two new parameters, |image_upright= and |image2_upright.
SWinxy (
talk) 00:56, 16 December 2023 (UTC)reply
The use on
Electrolyte imbalance (
permalink to current version of that page) reads Causes: hypocalemia. It's not immediately clear from that whether electrolyte imbalance causes hypocalemia, or hypocalemia causes electrolyte imbalance: the word Causes could be taken either for a present tense, third-person verb, or for a plural noun.
The issue isn't that that page is unclear (if that were the issue, I'd go to
Talk:Electrolyte imbalance instead); the issue is that the template can be used in a way that creates an unclear page. So, perhaps "Causes:" should be deprecated, with uses thereof to be replaced by either "Complications:" or "Caused by:", whichever is appropriate? I think that would be unambiguous?
2A0D:6FC2:6A92:3F00:0:0:0:5F9 (
talk) 19:19, 8 February 2024 (UTC)reply
AIUI hypocalcemia is an electrolyte imbalance, so the infobox just needs to be corrected. "Causes" should include things like diarrhea. It was added by a new editor, who might have mistaken it for the |types= parameter. Would you like to fix it, at least to remove ?
WhatamIdoing (
talk) 00:05, 9 February 2024 (UTC)reply