Template talk:Rotten Tomatoes prose

Consensus?

A standard template for this seems like a great idea in theory, but in practise there is no consensus for how this should be worded, and that has been the case for many years. (Look at WP:RTMC and the talk page if you want to seem many discussions about the minutiae of how it should be worded.) There were plenty of discussions if you search Project Film deep enough. Don't forget about Project Television. It would be a good idea if there was some small amount of consensus from the two major Wikipedia projects who might end up using this template. (Although I fear some editors will object even the notion of having a consistent wording.)

I seem to recall something a lot like this was tried before too. -- 109.76.196.7 (talk) 03:01, 6 April 2021 (UTC)

Per WP:IMPLICITCONSENSUS, "An edit has presumed consensus unless it is disputed or reverted." Do you have a link to those discussions? I don't see anyone raising any issues on here before your comment. See WP:CONACHIEVE. Kire1975 (talk) 03:42, 29 March 2022 (UTC)

Look at WP:RTMC and the talk page

A link to many many arguments about the wording was already provided in the above comment. (Minor arguements about specifc wordings continue below too). -- 109.76.202.80 (talk) 04:03, 28 November 2023 (UTC)

4th parameter

@Koavf, Chompy Ace, and Songwaters (pinged due to recent edits): Should a parameter be added for the critical consensus? It can be optional and can add the "The website's critical consensus reads," so a user will not have to add both the template and the phrase. Some Dude From North Carolina (talk) 00:01, 9 October 2021 (UTC)

• Support. As long as it's optional, I don't see any harm in it. Songwaters (talk) 00:29, 9 October 2021 (UTC)

   Done. {{u|Sdkb}} ^talk 08:07, 4 November 2021 (UTC)

Integrating RT data

Hi @Notsniwiast! I've noticed that you recently introduced {{RT data}}, which seems really cool! This template is already partially integrated with Wikidata (for generating the reference); would it be possible to integrate it further by using RT data as a default fallback if the template user doesn't provide numbers? It'd be really cool to eventually get to the point where all you have to do is add {{Rotten Tomatoes prose}} (without parameters) to a new film article and it'll automatically retrieve everything else needed. {{u|Sdkb}} ^talk 18:36, 15 November 2021 (UTC)

One issue I see (previewing One Child Nation with {{rotten tomatoes prose|{{RT data|score}}|{{RT data|average}}|{{RT data|count}}|consensus=As illuminating as it is accessible, ''One Child Nation'' probes a painful chapter in Chinese history with piercing clarity.|ref=yes|access-date={{RT data|access date}}}} as a sort of test) is that this template adds "%" and "/10", whereas those things are already built in to RT data, so those will have to be made compatible. {{u|Sdkb}} ^talk 19:17, 15 November 2021 (UTC)

What is "average rating"?

Is that the same as "audience score"? Kire1975 (talk) 16:24, 7 January 2022 (UTC)

@Kire1975: If you click the critic score, you will see a summary of the score, the average rating, and the number of critics who gave a review. If you click the audience score, you will see a summary of the score, the average rating, and the number of people who gave a review. Some Dude From North Carolina (talk) 16:49, 7 January 2022 (UTC)

Thank you very much. Kire1975 (talk) 12:54, 10 January 2022 (UTC)

MOS:SLASH out of 10

This template includes the text "an average rating of 7.30/10." MOS:SLASH recommends out of 10 instead of writing / in the text, so that would be "an average rating of 7.30 out of 10."

Was this is a deliberate choice to ignore MOS:SLASH or an oversight? -- 109.76.201.241 (talk) 19:05, 28 January 2022 (UTC)

@109.76.201.241: "An unspaced slash may be used ... in a fraction". Some Dude From North Carolina (talk) 19:21, 28 January 2022 (UTC)

It looks like a deliberate or accidental choice; possibly MOS has changed since this template's wording was established. "7.30/10" is clearly not a fraction or a ratio; if you are reading it out loud, you would never say "average rating of seven point three zero tenths". Instead, you would say "seven point three zero out of ten". I have fixed this template. – Jonesey95 (talk) 06:03, 30 January 2022 (UTC)

MOS:SLASH does not recommend using "out of 10" in place of a slash; just the opposite in fact, as Some Dude From North Carolina points out. Yes, you wouldn't "seven point three zero tenths", but that doesn't make it not a fraction. It's 7.30 out of ten possible points. Use of the slash is more concise anyway. Songwaters (talk) 22:30, 30 January 2022 (UTC)

As you write yourself, It's 7.30 out of ten, which is how we should write it, per MOS. Which section of MOS justifies the use of a slash here instead of the English words "out of" that match how the rating would be read out loud? Please quote and link to the section of MOS that allows this usage in prose. – Jonesey95 (talk) 23:43, 30 January 2022 (UTC)

I never said MOS:SLASH says anything explicitly about whether we should a slash or "out of" in the case of average ratings from Rotten Tomatoes. What I did say was that the average rating should be considered a fraction. Sometimes, we would say "tenths" to describe the average rating, specifically if it's something like 7.00/10, which is easier to say ("seven tenths"). Also, just because we would say "out of" when saying it out loud doesn't mean we should use those words in text; we say "1 8th of a mile" out loud, but we type "1/8 of a mile" in text. Bottom line, let's keep the slash for concision. Songwaters (talk) 00:03, 31 January 2022 (UTC)

I disagree. MOS:SLASH says that slashes in prose can be used for pronunciation, fractions, two-year periods, ratios, and expressions or abbreviations where a different construction would be ambiguous. This situation meets none of those criteria, so a slash should not be used. MOS:SLASH does not allow an exception "for concision". The Rotten Tomatoes pages also use "out of". Click on the "99%" at Casablanca, and you will see "9.40 out of 10 average rating". We should obviously not make up our own twisted "fraction" logic that conflicts with MOS in order to make our articles' prose more difficult for readers to understand. – Jonesey95 (talk) 00:46, 31 January 2022 (UTC)

The denominator is the largest possible score a film can have, and the numerator is the score that film actually has. Being commonly called "A Bth" is not a requisite of it being a fraction; it's also quite common for the slash to be interpreted as "out of". Just because you think my reasoning that the average rating is a fraction is "twisted" doesn't make it so. Also, I fail to see how a slash would make the prose more difficult to read; most people would surely understand what the slash means. The slash has worked just fine on Wikipedia's film articles for years and there's no reason to believe it has caused massive confusion then, let alone now. Songwaters (talk) 01:08, 31 January 2022 (UTC)

Part of the reason I bring it up is that if you look at Rotten Tomatoes itself it labels the number "7.30 out of 10 average rating" (as User:Jonesey95 already noted). It seems strange to both ignore MOS:SLASH and the site itself. Similarly I have seen many articles where an editor insisted on writing "percent" rather than % symbol for the Rotten Tomatoes score (I understand it, but I don't like it, because it seems inconsistent to insist on a word instead of a symbol in a sentence already full of numerals. The option to write percent or even "per cent" instead of % has already been coded into the template but few insist on actually using it). Digging into the edit history (the earliest version of the template didn't mention it[1] and) it was soon changed to the "out of 10"[2] by User:Koavf then shortly after[3] to "/10" by User:Chompy_Ace.

Rules change, we move on (Wikipedia film articles frequently did not even bother to include the number of reviews counted by Rotten Tomatoes, and including the average rating too was itself a relatively recent addition). If this template is going do things a particular way I want to make sure it has been done deliberately at least, and preferably based on consensus, especially when apparently choosing to ignore other Wikipedia guidelines. I don't think there is a clear consensus to ignore MOS:SLASH yet though. (Before anyone suggests "making it an option" I'm only interested in there being consensus for the standard default.) -- 109.79.69.44 (talk) 14:31, 31 January 2022 (UTC)

I'd like to establish one way or the other if there is a consensus to either follow MOS:SLASH or a local consensus for this template to ignore it. (As I alluded to already, it can be argued that it is inconsistent to insist on avoiding symbols like % or / in a sentence already full of numerals. Some have argued against writing "out of 10" to keep the wording more concise, but if really editors wanted to keep this template concise we would omit the words "the review aggregator website" because the keyword Rotten Tomatoes is already linked for anyone who actually needs further explanation.)

What is the best way to get an answer? Should I start an RFC or is there some other process that would be more appropriate to settle the issue one way or the other? (I'm vaguely aware of the Wikipedia RFC process, but I've never used it and there may be a better way to clearly establish consensus.) -- 109.76.199.220 (talk) 17:21, 25 February 2022 (UTC)

Putting a {{Please see}} invite at WT:MOS might draw some additional participants here. If a consensus fails to emerge from that, an RfC would be the next step. {{u|Sdkb}} ^talk 18:38, 25 February 2022 (UTC)

Nothing in the MOS says you have to choose one format over the other for this particular situation, so it really boils down to a stylistic preference. And in that regard, I think Jonesey95 hit it square on the head. The source does not publish it as a fraction, and neither should we, unless it can be shown that an overwhelming number of sources are reporting these numbers as fractions. Is the fraction acceptable? Sure. Necessary? No. An alternate stylistic preference, while acceptable, shouldn't be the default. --GoneIn60 (talk) 07:47, 30 March 2022 (UTC)

I suppose I should note that I appreciated the advice from Sdkb about "{{Please see}} invite at WT:MOS" and was thinking about doing that at some point, eventually. But this all seems like it will be moot when the template is deleted. It would be helpful if these discussions were not deleted along with the Template, as this discussion also applies to WP:RTMC. -- 109.77.199.151 (talk) 15:22, 30 March 2022 (UTC)

Another point to consider that I just thought of... When existing plain text prose using "out of" is overwritten with a slash by the use of this template, it's in violation of MOS:VAR due to the fact that more than one format is acceptable here. At the very least, if the template is kept, there should be a built-in parameter to allow for either preference. --GoneIn60 (talk) 22:06, 30 March 2022 (UTC)

May 2022

Restarting this discussion because wasn't aware of it and made similar amend to template, / to out of, and reverted by @TropicAces:. I'd say consensus in previous discussion leans towards "out of" but far from conclusive. I think the average is not a fraction, and "out of" is easier to read, so shouldn't use a slash. Indagate (talk) 15:09, 14 May 2022 (UTC)

I think you're right. Although the existing wording has been around for a long time we can do better. In this context most readers can easily tell the difference between difference between "one tenth" and "1 out of 10" but they (and dumber systems like text to speech systems) shouldn't have to. I think the extra clarity is more important than brevity in this case. -- 109.76.131.151 (talk) 19:16, 14 August 2022 (UTC)

url-status

Could someone please tweak the template so |url-status= is only included with |archive-url=, to prevent articles from being included in Category:CS1 maint: url-status? (e.g. Super Crooks) Thanks! GoingBatty (talk) 04:23, 30 January 2022 (UTC)

 Done. Drop me line on my user talk page if you need more help with templates and CS1 errors. – Jonesey95 (talk) 05:58, 30 January 2022 (UTC)

It is not clear that the reviews are from critics

RT has two scores, and it is NOT clear which is being used here. Simply putting in "critic" helps to clear this up. @Some Dude From North Carolina: UserTwoSix (talk) 22:40, 6 February 2022 (UTC)

@UserTwoSix: The Rotten Tomatoes score is normally added under a section titled "Critical response". Adding "critic" only makes it wordy and repetitive since it is followed by Metacritic, which already includes "critics". Some Dude From North Carolina (talk) 22:48, 6 February 2022 (UTC)

@Some Dude From North Carolina: I suppose we'll have to wait for someone else to weigh in. I might agree with you if it was 10 or 20 years ago, but the trend has been to give more and more credibility to the general audience/public vs. experts on the internet. UserTwoSix (talk) 22:52, 6 February 2022 (UTC)

As an example I might point to Murderville#Reception which has a section only "Reception" and you can see the wording without the template. UserTwoSix (talk) 22:55, 6 February 2022 (UTC)

I support adding the word "critics" since RT reports two different ratings. Also, the slash should be changed to "out of", per the usage at RT and WP's own MOS (see above). – Jonesey95 (talk) 23:04, 6 February 2022 (UTC)

I'd also support adding the word critic. Yes, technically it's already implied, but Rotten Tomatoes really doesn't emphasize it, whereas they do emphasize the audience score, so it's likely to be a helpful clarification for readers. {{u|Sdkb}} ^talk 23:32, 6 February 2022 (UTC)

Saying "critic score" or "critic reviews" seems unnecessary and verbose since the critics score comes first and has always been the main thing, and Wikipedia does not allow the unreliable Audience scores. (I would also be slightly worried that making the distinction will only encourage the people who continue to frequently add "audience scores" or "audience reviews" to film and television articles.) For any reader that is confused the words Rotten Tomatoes are wiki-linked if they need further clarification. -- 109.78.200.28 (talk) 21:07, 8 February 2022 (UTC)

In my comment above, I thought that we were discussing adding "critic" right before the average rating, not before "reviews". I'm somewhat ambivalent about this (and not sure if the apostrophe is needed either). I wish that Rotten Tomatoes would just focus on their historic core, which is aggregating critics' reviews, rather than trying to become something broader: they currently have the audience score right after the Tomatometer in just as big font, and the average critic rating is extremely hidden since you have to click to get to it. On the one hand, it's not our job to fix their interface/mission, but on the other, it's causing a lot of potential confusion among readers that makes the wording calculus trickier for us. I'll put an invite at WT:FILM to try to get some more eyes here. {{u|Sdkb}} ^talk 23:25, 8 February 2022 (UTC)

WP:TELEVISION should also be consulted if editors are serious about using this template more and getting a wording with a wide consensus. There are already editors who reject using this template on film articles calling it "Unnecessary, badly written"[4]. There was never a clear consensus on what the wording should be, this template barely survived being deleted entirely, and there remains an ongoing risk of the bikeshed effect. -- 109.78.211.92 (talk) 09:30, 9 February 2022 (UTC)

We should definitely not use this in a widespread manner. There is no community consensus to use it that way, and I believe editors should have the flexibility to word the content from RT (and Metacritic as well). Erik (talk | contrib) ^{(ping me)} 13:08, 9 February 2022 (UTC)

Erik could try and propose the template for deletion again if he does not think it should be used, but if it is here people will use it. It is already happening, the template exists, people are using it more and more. It is a predictable and inevitable result of the deletion discussion failing. That was the consensus even if we don't like it, so we have to continue to have these discussion over and over and try to gradually improve the wording as best we can. The only other alternative I can think of is that several people in deletion discussion argued that it should only be allowed as a substitution template, perhaps that is something that could be explored as it would offer a bit more flexibility. (I don't think this template is ideal but it is still better than some of the weirder wordings some editors think are a good idea.) -- 109.79.175.86 (talk) 13:35, 11 February 2022 (UTC)

I find it strange that User:Sdkb has gone ahead and made several changes to this template but in particular added a never substitute warning [5] to the template, despite several people in the deletion discussion expressly argued for the opposite. -- 109.78.203.101 (talk) 17:03, 16 February 2022 (UTC)

IP, that deletion discussion resulted in a consensus to keep. I've made several changes to the template over the past year supported by PAG or consensus—if you have multiple specific objections, name each of them. Regarding substitution, that notice is in the documentation partially because this template doesn't currently have the technical capacity to substitute without introducing technical code we don't want in articles. I think it'd be a bad idea to substitute it, given that that would negate many of the reasons editors !voted to keep this template. {{u|Sdkb}} ^talk 17:21, 16 February 2022 (UTC)

I'm not sure what you mean by PAG, that jargon is obscure to me. On substitution User:Sdkb makes a good point, the suggestions in the discussion that it be made into a substitution template goes against the points User:Sdkb made in that same discussion pointing out the main benefit of this template that it would more easily allow things to be kept consistent. Thanks for clarifying that.

I would name more of the minor complaints I have about this template but the issue I already raised about MOS:SLASH still has not been adequately addressed. It has not been shown that there is any consensus to ignore MOS:SLASH as this template continues to do. -- 109.76.199.220 (talk) 13:45, 25 February 2022 (UTC)

Transclusion count

Based on this, at this time, there are 302 articles that transclude this template. As a reminder, the fact that this template exists does not mean there is consensus to use it in place of written article text. There are no policies, and no general or subject-specific guidelines, that endorse this template's use over written article text. Applying the spirit of MOS:VAR to the style of presenting aggregate scores, there should not be a change from one style to another unless there is some substantial reason for the change. Erik (talk | contrib) ^{(ping me)} 23:47, 16 February 2022 (UTC)

Again the template exists, people are going to use it. People are out there actively converting articles to use this template[6][7] You can try and convince him not to use it but that user is only the most recent one I've seen, there are others. It is happening and it is going to keep happening. Comments on the talk page are not enough. Even banner warning on in the template documentation probably wont stop people from using this template (and I say that because Template:Webarchive has long had a warning against using it that no one pays any notice).

Unless you can convince people to delete this template it is going to keep getting used. It is just too convenient when adding to articles that don't already have the aggregators listed. Frankly I'm going to use it it too, because even though it is flawed in some ways, it beats arguing with certain editors who have even weirder and worse ideas about how to word the aggregators blurb. Maybe you can convince a bot developer to replace uses of this template, but again there are people actively and enthusiastically adding this template (and I'm even grudgingly and unenthusiastically using it because it beats the alternatives). -- 109.76.199.220 (talk) 13:26, 25 February 2022 (UTC)

I've relayed to LancedSoul what I stated above. Furthermore, the template is worse than article text per WP:TMP, "Templates should not normally be used to store article text, as this makes it more difficult to edit the content." Implementing the template does a disservice to the casual editor by keeping the ability to edit the article text hidden away from them. Erik (talk | contrib) ^{(ping me)} 16:01, 25 February 2022 (UTC)

The count has gone up (to 315) not down since Erik started this discussion. I agree in principle when he says "Implementing the template does a disservice to the casual editor by keeping the ability to edit the article text hidden away from them" and it would probably be better if we could stick to those higher principles, if we could discourage editors from raising the barrier to entry by adding complicated templates or obscure jargon or any other difficulties. But RottenBot is already adding many templates for the scores, and using this template is only taking it one step further (there is difference, but not much). Please do put a big clear warning banner in the template documentation, or whatever else you think might help, but this template is not going away and seems unlikely and unrealistic to expect editors not to use it. (In my experience, it has been difficult enough to discourage editors from using Template:Film_ratings and that was a big ugly awkward template, and there used to be strong and clear consensus against using it. Discouraging them from using a much easier and more convenient template like this is going to take considerably more time and effort. The time you're taking to discuss it here is only the tip of the iceberg.)

Erik, you may as well propose this template for deletion again, your logic seems to point that direction anyway. -- 109.76.199.220 (talk) 17:06, 25 February 2022 (UTC)

One month later, the template has been transcluded 357 times. Erik (talk | contrib) ^{(ping me)} 22:56, 16 March 2022 (UTC)

Now it is 398 times. Erik (talk | contrib) ^{(ping me)} 17:31, 16 April 2022 (UTC)

I checked. A majority of the new additions in the past couple weeks are newer film articles that never had a reception section. Editors are choosing to use the template, which is a legit move. The others were in older film articles where the reception summary was poorly written and subsequently overwritten with the template, also a legit move. However, I have come across a few examples where perfectly acceptable prose was getting overwritten unnecessarily, and I usually revert those back on sight. That's an improper use of the template, especially when {{RT data}} is already being used. Count was at 400; now at 397. --GoneIn60 (talk) 17:40, 18 April 2022 (UTC)

I thought the proposed deletion of this template was technically correct and I did expect this template to be gone already. But so long as this template exists it does not seem unreasonable to use it. It can be quite convenient. (I have found the template {{Rotten Tomatoes data|prose|ref=yes}} useful, and if I recall correctly it also increases the usage count of this template. It is especially convenient if I'm on mobile and do not want to type any more than is absolutely necessary.) I think it is reasonable to use this template if editors have failed to provide a proper inline reference, so please do not revert those cases without adding a proper inline reference. I try to use it in cases where editors have not only failed to provide a proper inline reference but also have not listed the number of reviews counted for context, which means the wording requires a certain amount of rewriting anyway. -- 109.78.192.111 (talk) 06:17, 24 April 2022 (UTC)

In cases where the only thing missing is a reference, like the ones I reverted, feel free to add one. You don't need this template for that. Changing the wording unnecessarily is akin to a MOS:VAR concern and should be avoided (or discussed at the very least). I will make a note for future reference to add a citation where one is missing, but the template should not be solely used as a citation hack. --GoneIn60 (talk) 00:58, 27 April 2022 (UTC)

"Template:RT" listed at Redirects for discussion

An editor has identified a potential problem with the redirect Template:RT and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 April 25#Template:RT until a consensus is reached, and readers of this page are welcome to contribute to the discussion. Indagate (talk) 20:10, 25 April 2022 (UTC)

Punctuation in the consensus parameter

Shouldn't the punctuation after the passage The website's consensus reads be a colon instead of a comma? The Manual of Style reads that it is clearer to use a colon to introduce a quotation if it forms a complete sentence, and this should always be done for multi-sentence quotations. However, critics consensus on Rotten Tomatoes are complete sentences (sometimes more than one), usually containing multiple propositions, so it seems to me that this quote from the Manual of Style applies here.

I would have boldly made the edit myself, but since this template is used in over a thousand pages, I thought it was better to discuss it here first. -- Kzkzb (talk) 15:08, 6 April 2023 (UTC)

yeah makes sense. Thanks, Indagate (talk) 15:22, 6 April 2023 (UTC)

Datum

@Epìdosis: Re your recent edit, Rotten Tomatoes has a standard scoring system, which is always out of 10, so is there really any need to check the datum? I worry it's just added complexity. {{u|Sdkb}} ^talk 14:11, 4 June 2023 (UTC)

@Sdkb: Hi, I think it's necessary; since in Wikidata the % and /10 are part of the values of d:Property:P444, if the data are read from Wikidata they should not be added by the template, otherwise they get duplicated. --Epìdosis 14:13, 4 June 2023 (UTC)

Have reverted the edits as they broke the template in articles like Top Gun: Maverick‎ causing the & and /10 to not show at all because P444 is populated in wikidata even if not used in articles. Please test in sandbox. Thanks, Indagate (talk) 14:40, 4 June 2023 (UTC)

However it seems that there is a problem of duplicated & and /10 elsewhere (e.g. Avengers: Endgame#Critical response). I don't know which problem is more frequent. --Epìdosis 18:53, 4 June 2023 (UTC)

Have fixed the issue at Avengers: Endgame#Critical response by using the RT data template with its prose parameter instead of calling the RT data as paremeters of this RT prose template. That was a fixable misuse of template so should be far less frequent. Thanks, Indagate (talk) 19:03, 4 June 2023 (UTC)

100% or 0%

Can someone modify the template's code so that when a film's score is 100% or 0%, the score links to List of films with a 100% rating on Rotten Tomatoes and List of films with a 0% rating on Rotten Tomatoes, respectively? Thanks. InfiniteNexus (talk) 18:14, 13 October 2023 (UTC)

 Done, added to Testcases as well Indagate (talk) 18:42, 13 October 2023 (UTC)

Thanks. InfiniteNexus (talk) 06:10, 15 October 2023 (UTC)

TemplateData

@Sdkb The template also works without the number of critics (see test cases), so I felt that it was a very big suggestion. I think this could motivate users to include all three fields. Aaron Liu (talk) 13:45, 8 November 2023 (UTC)

This needs to be listed as a substonly template

This, along with {{Metacritic film prose}} and {{Metacritic album prose}}, violate the Wikipedia:Template namespace guideline, specifically the first guideline point: Templates should not normally be used to store article text, as this makes it more difficult to edit the content. They should also not be used to "collapse" or "hide" content from the reader. Seeing as that's all this template is doing, {{Subst only}} needs to be added to these template's documentation so the bot can come around and substitute the transclusions. Some further coding adjustments may need to be done to allow this to be subst correctly (I currently tried with the Ralph Breaks the Internet example and it some wikidata calls with the reference). There's nothing wrong with starting out with a "standardized" wording for this information, but again, as the result of the template's purpose is prose creation, it goes against the guideline. I will also notify the template talks of the two I linked above, plus WP:FILM, MOS:FILM, WP:WPMUSIC, and MOS:MUSIC. - Favre1fan93 (talk) 23:40, 21 November 2023 (UTC) Also added WP:ALBUM. - Favre1fan93 (talk) 23:46, 21 November 2023 (UTC)

• For reference, the previous TfD regarding this template is here: WP:Templates for discussion/Log/2022 March 31#Review aggregator prose templates --GoneIn60 (talk) 22:58, 22 November 2023 (UTC)

For what it's worth, this has been discussed multiple times and editors were in favor of keeping it the way it is in order to standardize the language used in articles as well as to keep from introducing errors about the exact methods used, etc. I personally lean that direction, but don't have a strong feeling either way. ―Justin (koavf)❤T☮C☺M☯ 23:44, 21 November 2023 (UTC)

I understand that notion, but the guideline is pretty explicit about this. I can see this as a tool for a starting point for editors, but it still should generate the prose in article. I'm personally of the mind that I don't need this text to be standardized since there can be slight variations that still convey the same info. I know that could be a minority opinion, but for what this is, the text shouldn't be locked behind a template. - Favre1fan93 (talk) 23:48, 21 November 2023 (UTC)

Sure. Also agreed that we shouldn't have rules we don't follow: that helps no one. Would you also be amenable to the rule changing its language? ―Justin (koavf)❤T☮C☺M☯ 23:55, 21 November 2023 (UTC)

No. The fact that wikiprojects and template authors can sometimes get away with breaking a rule for a while doesn't mean the rule is faulty. The real question here is whether this short RT-related sentence really qualifies as what is meant by "article text ... content" in the rule. One could argue that this template serves a similar purpose to {{EB1911}} (and a counter-argument could be made that the latter is citation/attribution template for the sources section which is not defined as part of the article content per se). An argument can also be made that the template can be substituted any time someone feels a powerful need to adjust the text in it in a particular instance, while leaving the rest with the same boilerplate. But why is this something we need boilerplate for? And if we do need it, what is the rationale to change it in some particular case?  — SMcCandlish ☏ ¢ 😼  02:36, 22 November 2023 (UTC)

I didn't suggest that the rule was "faulty" or that is why the rule is faulty. The rules are all conventions that we make up and we can change them at any time if it helps us make an encyclopedia. There is 100% no reason for your weird hostility to me, so stop. As for why we need boilerplate language, one reason why is because of something I wrote above and you maybe didn't even read, which is that it keeps the language around the weight average methods correct instead of individual users mischaracterizing it, which I have seen in the wild before. ―Justin (koavf)❤T☮C☺M☯ 03:16, 22 November 2023 (UTC)

The result of the 2022 TfD (linked above) was "no consensus", which isn't exactly a ringing endorsement against the general guideline. It may actually indicate the need for further discussion, and instead of having "delete" on the table, perhaps the next go at it should focus on "subst-only". --GoneIn60 (talk) 23:08, 22 November 2023 (UTC)

I would also recommend WT:ALBUM. Is there a reason you skipped it, @Favre1fan93:? ―Justin (koavf)❤T☮C☺M☯ 23:45, 21 November 2023 (UTC)

Yup, just added WP:ALBUM. Was just an oversight on my part. - Favre1fan93 (talk) 23:46, 21 November 2023 (UTC)

Not substituting this template allows for quick and easy updates, which for many films happens every day early in their run. -- Michael Bednarek (talk) 00:17, 22 November 2023 (UTC)

The plain text generated by the template, or a slighly edited variant of it, wouldn't be any more difficult to update at the same film article. It's not an argument pro or con in either case.  — SMcCandlish ☏ ¢ 😼  02:36, 22 November 2023 (UTC)

Guidelines on Wikipedia are not divine mandates. They all have underlying rationales, and we should evaluate them in light of that. When the underlying rationales do not apply to a particular situation, we are not only permitted but encouraged to make exceptions.

The template guideline quoted above is helpfully specific about the rationale behind its suggestion: this makes it more difficult to edit the content. So the salient question is whether this snippet of text is something that is frequently going to need to be adjusted/customized to a specific article. And I submit that the answer is a resounding no — this is among the most standardized pieces of text used on Wikipedia, and even edge cases (such as situations where we want to link List of films with a 100% rating on Rotten Tomatoes) can be handled by the template.

As such, there's very little downside, and as Justin highlighted above, there is a lot of upside. It makes updates simple (and in some cases automatable), it encourages more consistent/neutral language, it provides standardization that makes it easier for readers to navigate, etc. As such, I would strongly oppose making it subst-only. Best, {{u|Sdkb}} ^talk 06:11, 22 November 2023 (UTC)

But there is currently no "mandate" (for lack of a better term) to use this template, nor to standardize it. MOS:FILM, at least for the MOS that would apply to this template, makes no mention of this template nor any suggested wording, while the essay WP:AGG has similar wording listed, which just shows that there are multiple ways to present this info. If editors want to have a baseline for others to start off with with this formatting, go for it. I don't see why this template should be an exception to the guideline and ignore it. Editors should be able to access and adjust prose wording within articles and these templates currently don't allow that. - Favre1fan93 (talk) 23:04, 22 November 2023 (UTC)

That guideline has been tested for this and similar templates in TfD before, the parts that are different for individual articles can be easily edited, the rest is boilerplate. Substituting it removes the benefit's that templates like this provides, of consistency if it gets changed and maintainability. Thanks, Indagate (talk) 08:45, 22 November 2023 (UTC)

As I've commented above, no where has this template be set as a "mandate" or standardized wording for this text. It's merely a suggestion, to which some variation can exist outside this template's use and it is still ok. As such, editors should still be able to edit this text, if desired. - Favre1fan93 (talk) 23:04, 22 November 2023 (UTC)

I support this template being subst only, where the specific scores can be shown via templates. The template currently prevents layperson editors from editing the prose that presents the scores and perpetuates one kind of wording. This wording presumes specialist knowledge of how review aggregators work and obscures the simplistic workings of Rotten Tomatoes. I've had to convert some templates, and it is not easy and a bit tedious, just to be able to reword the sentence. Again, I support templates for the scores as straightforward numbers to update, but having a template display only one way of wording, instead of having freeform text to change, is in violation of the spirit of Wikipedia. Erik (talk | contrib) ^{(ping me)} 18:36, 22 November 2023 (UTC)

What are the situations where you've had to change the wording please? The text can normally be the same so curious where it needs to be different. Thanks, Indagate (talk) 19:03, 22 November 2023 (UTC)

What Indagate said. From your initial comment, it seems that you have an objection to the specific wording used here, rather than a need to customize the wording to a specific article. If that is the case, then what you should do is propose changes to the wording at this template, rather than substing it out. The ability to discuss such optimizations centrally and then push them out at scale if they have consensus is a benefit of this template (which is lost if substed out). {{u|Sdkb}} ^talk 19:54, 22 November 2023 (UTC)

There are many ways that editors can present this information, including by editors who add this without this template. They should have the ability to freely edit the prose supplied by this template on article after it has been subst, without having to remove the template transclusion to make a desired change. This isn't a text we need to be "locking in" for editors. Good for a starting point if anyone wants it, not one to stay as such if a change has to be made. - Favre1fan93 (talk) 23:04, 22 November 2023 (UTC)

I agree with Favre1fan93. While standardizing text across hundreds of articles, if not thousands, sounds beneficial on paper, there's no reason to enforce specific phrasing in locked-down fashion. There are multiple, acceptable ways to write the same statement, and it has yet to be shown that it was a real problem before the template's existence. On the contrary, the problem now becomes the proliferation of the template across Wikipedia, which even the smallest adjustment to its phrasing, only requiring a small consensus among a handful of editors, could impact thousands of articles that were never edited by the editors involved in that discussion. Instead of asking why we don't need embedded text in the template, we should be asking and gaining consensus for why we do need it. For many years, WP:FILM could never agree on standardized phrasing for Rotten Tomatoes, Metacritic, and the like, yet those behind this template's existence believe this template somehow found the elusive magic bullet. --GoneIn60 (talk) 23:30, 22 November 2023 (UTC)

I have been away for a few days, and there hasn't seemed to be much more involvement. I think this is an important issue to settle, and will plan to create an RfC on the matter to hopefully generate wider community input if more voices don't chime in and create a clearer consensus. - Favre1fan93 (talk) 16:05, 27 November 2023 (UTC)

Sounds good. Where do you want to hold the RfC? Here? I assume it will include all of the templates with similar wording, correct? ―Justin (koavf)❤T☮C☺M☯ 22:26, 27 November 2023 (UTC)

Here I think would be the best location. Yes, it would apply to this template and the two Metacritc ones (and any others I'm not aware of that are similar). I will give this regular discussion until the end of the week before starting any RfC. - Favre1fan93 (talk) 22:36, 27 November 2023 (UTC)

[thumbs up emoji]. I also don't know of any other templates that work like this, but if I bump into any, I'll post them here, so we don't have to reinvent the wheel. (If I had a dollar for every time that I had to argue about adding accessibility features to every single table here on Wikipedia, I'd be rich.) ―Justin (koavf)❤T☮C☺M☯ 22:43, 27 November 2023 (UTC)

RfC: Should this and similar templates be substonly?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Should this prose template, along with the similar {{Metacritic film prose}} and {{Metacritic album prose}}, be made substonly templates? - Favre1fan93 (talk) 19:54, 1 December 2023 (UTC)

Background

Past discussions regarding this include this TfD WP:Templates for discussion/Log/2022 March 31#Review aggregator prose templates, and the discussion above #This needs to be listed as a substonly template. The talk pages of {{Metacritic film prose}} and {{Metacritic album prose}}, along with WikiProjects/relevant MOSs WP:FILM, MOS:FILM, WP:WPMUSIC, MOS:MUSIC, and WP:ALBUM, and WP:ROTTEN have all been notified of this RfC. The following editors who commented above are being pinged to this RfC: @Koavf, SMcCandlish, GoneIn60, Michael Bednarek, Sdkb, Erik, and Indagate: - Favre1fan93 (talk) 19:54, 1 December 2023 (UTC)

Survey

• Yes - Echoing some of my comments above, the Wikipedia:Template namespace guideline, specifically the first guideline point states the following: Templates should not normally be used to store article text, as this makes it more difficult to edit the content. They should also not be used to "collapse" or "hide" content from the reader. These templates are doing just that, storing article text, and I don't see any reasonable reason for these templates to be an exception to this guideline. Additionally, for the two film prose templates, there is currently no consensus within WP:FILM, at MOS:FILM, or on WP:ROTTEN for a standardized wording for this information. I know that was the goal some editors had with this, as not subst-ing the templates allowed for a uniform approach and ease of making mass alterations to this wording if needed, but as just stated, there is no consensus for a uniform approach, so the prose and reference formatting should not be locked behind a template. While in most cases this wording probably will be fine for an article, an editor should still have the option to easily adjust the wording and citation in article, without it then affecting the other transclusions of this template as is currently happening. Creating a boilerplate text for these aggregators for editors to subst into an article can be a useful tool to get started with this information, but that's all it should be: a tool that anyone afterwords can adjust and alter if needed. - Favre1fan93 (talk) 19:54, 1 December 2023 (UTC)

  Guidelines exist as expressions of underlying principles, not as rigid dogma. In this case, the underlying principle, helpfully articulated in the guideline itself, is that we don't want to make it more difficult to edit the content when it needs to be customized or otherwise adapted to fit the specific circumstances of an article.

  However, in the discussion above, you and the others opposed to this template were unable when challenged to name any hypothetical circumstance whatsoever that would require customization. The only issue raised was Erik's objection to the template's current wording, which is a reason to propose changes to the wording, not to delete or subst-only the template. (I would also note that, even if there is some circumstance that requires customization this template couldn't handle, the fix is pretty simple — just subst it in that individual instance.)

  Centralizing information that is presented in similar circumstances is the fundamental reason that templates exist on Wikipedia, and the centralized discussion it fosters is core to how our consensus process works. If an editor's potential desire to change the presentation of information out of personal preference (rather than something about the article that prompts a need for customization) was a reason to make templates subst-only, then every template that includes any substantive content would be subst-only. Which would be a disaster, since it'd mean disputes would play out diffusely on thousands of low-visibility pages rather than in a centralized space where they might actually be resolved.

  So foundationally, the underlying principle of the guideline does not apply to this circumstance, making an exception absolutely warranted. Keeping this information templated makes it easier to update scores by facilitating bulk updates via Wikidata, and it centralizes discussion on wording changes, which is exactly what we want in a situation where the circumstances in which information is presented is the same. {{u|Sdkb}} ^talk 20:45, 1 December 2023 (UTC)

• Weak no I see the value in standardization (obviously, as I created it) and this does correct some incorrect statements that I've seen in the wild. I generally agree that obfuscating text is not ideal, but particularly with this template, it is easy to add relevant text in the consensus portion and anyone can add text before and after the template, so I think this is a sensible exception with some benefit. ―Justin (koavf)❤T☮C☺M☯ 20:07, 1 December 2023 (UTC)
• No, absolutely not. This RfC is essentially a rehashing of the two prior TfDs hoping for a different result. My reasoning is largely unchanged, so I will copy the bulk of what I previously wrote (with minor tweaks):

  First, the existence of this template does not force any particular wording, as its use is optional, so editors are free to ignore it. Second, standardization is often good. Readers become accustomed to certain aspects of Wikipedia style over time, and when articles are similar, it makes it easier to navigate unfamiliar pages because they know what to look for. Third, templating allows for optimization. When a format is applied over hundreds of pages, it becomes worthwhile to refine small details like whether to use % or "percent" that probably would never have been considered at the level of an individual page. It's particularly advantageous for sensitive areas like critical reception, as it helps us remain neutral—when this template is at an article, it's unlikely to be changed to Film did extremely well at Rotten Tomatoes, where critics gave it a very positive 68% fresh rating. Fourth, removing the template would hamper future improvement efforts. To see what I mean here, look at the example of census data at WikiProject Cities: a long time ago, a bunch of census info was added to city pages, but because it was done via copy-and-paste, rather than templates, updating and improving it turned from a relatively straightforward task into an arduous saga. The same sort of thing could happen here. For instance, it's perfectly plausible that at some point Wikidata will be able to mass-import RT scores on a regular basis. If this template exists [non-substed], plugging those in to the transclusions will be easy. If not, it'll be basically impossible.

  Substing a template like this is an irreversible decision that would hamper future improvements to how we present this information on a mass scale. I therefore strongly oppose. {{u|Sdkb}} ^talk 20:15, 1 December 2023 (UTC)
• Yes This is quite clearly article text that should not be in a template, and thus forbidden per the applicable guidance. * Pppery * _{it has begun...} 23:12, 1 December 2023 (UTC)

  Guidelines are not policies and don't "forbid" anything. From WP:P&G: "Editors should attempt to follow guidelines, though they are best treated with common sense, and occasional exceptions may apply." See also WP:COMMONSENSE and WP:IAR (and WP:NOT#BUREAUCRACY and WP:WIKILAWYER): when following a rule (to its strict letter rather than applying it sensibly as it was actually intended) would produce worse results for the encyclopedia in a particular case, we should do the more sensible thing and not apply that rule (or that interpretation of it) in that instance.  — SMcCandlish ☏ ¢ 😼  01:12, 2 December 2023 (UTC)

• No. This is not "article content" in the usual sense but is attribution-related boilerplate being consistently used to correctly attribute something (which when left to random-editor discretion is very often written incorrectly and misleadingly). It is not any more a TMPG violation than other templates that provide boilerplate attribution strings like {{EB1911}}. If there is some overriding need in a particular instance to change the wording, the template can be substituted and the text it emits can then be edited in that particular case. That is something that should be done after a consensus discussion establishing the need. The idea that random drive-by editors needs the ability to change this carefully constructed boilerplate on a whim is simply false. Also agree with the majority of Sdkb's rationale above.  — SMcCandlish ☏ ¢ 😼  01:08, 2 December 2023 (UTC)
• No per my earlier reason, and those offered by others above. -- Michael Bednarek (talk) 01:20, 2 December 2023 (UTC)
• No. This is not article prose. It's a template with multiple parameters, closer in spirit to an external link template than a block of prose used in multiple articles. A decent test to see if something is article prose is: "If we put this text into an article and used section transclusion, would it work just fine?" This template fails that test. Also, when (looks for stick to beat dead horse) the template is finally changed to read "out of" instead of "/", per MOS, it will be a lot easier to fix all of the affected articles if the text is still applied via transclusion. – Jonesey95 (talk) 05:27, 2 December 2023 (UTC)
• No, this template and the others listed combine for several thousand transclusions. Many editors are displaying their attitude just by transcluding the templates. The previous TfD also did not decide to make the template subst-only. I'm not convinced that the averages phrased by the templates are body content in the sense that templates are prohibited from generation. Rjjⁱⁱⁱ (talk) 05:34, 2 December 2023 (UTC)
• No, for reasons mentioned above. This text doesn't need to be changed other than the numbers which can be easily done. It makes the inclusion of audience score and words like Tomatometer or rotten less likely. Any potential changes can be done on a mass-scale. Thanks, Indagate (talk) 09:29, 2 December 2023 (UTC)
• Yes - this is clearly article text that goes against the Wikipedia:Template namespace guideline, and there is also no consensus for film and TV articles that there should be standard wording for review aggregators. - adamstom97 (talk) 19:58, 2 December 2023 (UTC)

  Templates exist as a way to centralize discussion and consensus around how to word things. No one would ever argue that e.g. the city infobox should be substed because WikiProject Cities didn't explicitly endorse the decision to have certain fields in it. But that's essentially the standard you're applying.

  And in some ways, it's even worse, because there's basically no choice other than to use the city infobox for a city article, whereas here, if someone doesn't like the wording this template uses, they can just not use it (or change it). {{u|Sdkb}} ^talk 04:46, 4 December 2023 (UTC)

  Infoboxes are not article text, that's not the same situation. - adamstom97 (talk) 05:50, 4 December 2023 (UTC)

  It seems like the same in regards to your consensus point, a template does not need consensus by anyone including a WikiProject to exist and be used. Indagate (talk) 17:34, 4 December 2023 (UTC)

• Yes. Adamstom echoes my thoughts precisely. This is replacing prose, it absolutely should follow the guidelines for templates, and the arguments for not (IAR over a Rotten Tomatoes template, really?) being stuff like "it's easier for some people to replace the terrible boilerplate RT stuff they're spamming in articles" isn't compelling to me. Der Wohltemperierte Fuchs ^talk 20:15, 2 December 2023 (UTC)

  That's (at least in part) a deprecated WP:RUBBISH fallacy. If you disagree with the content of the boilerplate, then edit it. Not liking exactly what it says right this instant isn't an argument against the template existing, or against what it does, or against how it does it.  — SMcCandlish ☏ ¢ 😼  11:00, 3 December 2023 (UTC)

• Yes, and to repeat from the previous thread: I support this template being subst only, where the specific scores can be shown via templates. The template currently prevents layperson editors from editing the prose that presents the scores and perpetuates one kind of wording. This wording presumes specialist knowledge of how review aggregators work and obscures the simplistic workings of Rotten Tomatoes. I've had to convert some templates, and it is not easy and a bit tedious, just to be able to reword the sentence. Again, I support templates for the scores as straightforward numbers to update, but having a template display only one way of wording, instead of having freeform text to change, is in violation of the spirit of Wikipedia. Erik (talk | contrib) ^{(ping me)} 18:48, 4 December 2023 (UTC)

  This wording presumes specialist knowledge of how review aggregators work and obscures the simplistic workings of Rotten Tomatoes. So, as you were advised above, start a thread proposing it be changed to different wording you think is better. Making this subst-only won't fix your concern. Instead, substing out the current transclusions would in a sense freeze the current wording in place in the 1000+ transclusions of this template, preventing them from benefiting from future improvements to it unless someone goes around changing thousands of pages in bulk. {{u|Sdkb}} ^talk 19:18, 4 December 2023 (UTC)

  And on the spirit of Wikipedia, to me the spirit of Wikipedia is editing collaboratively to achieve consensus. Having this template allows for such centralized discussion, permitting a level of attention and refinement that a single sentence in an article would never normally receive outside of FAC. Blowing up that central forum, since someone as an individual might want to do something different on an individual article (not because there's anything specific to that article that warrants customization, but rather just because of one's personal preference), while simultaneously ignoring the opportunity to have a broader impact by collaborating on the text of the template — that is what seems anti-wiki to me. {{u|Sdkb}} ^talk 19:59, 4 December 2023 (UTC)

• No, for reasons mentioned above. The average reader doesn't know what Tomatometer rating means, and being able to explicitly use the definition helps to understand/utilize it better. Otherwise all articles would be full of misleading descriptors like "...has an approval rating of...". ภץאคгöร 19:31, 4 December 2023 (UTC)
• Yes – The template is a work-in-progress solution in search of a problem. Retaining the template's transclusive properties boils down to these two stated goals:

  1. Enforce standardized wording for Rotten Tomatoes (RT) and Metacritic (MC)

  2. Automate the updating of RT and MC scores

In its two plus years of existence, a convincing argument has yet to be made that standardized wording is a necessity (there are multiple ways to express the numbers from RT and MC correctly). To date, I have only read anecdotal evidence from template proponents that this was an issue in need of a fix. Also, the idea of updating automatically appears to have stalled. Great idea, but one that puts the cart before the horse in regard to transclusion – not to mention the very real possibility that it never happens. The tradeoff in the meantime is added complexity for novice editors that don't see the citation or article text when they click edit on the page. We only want that tradeoff when the benefits outweigh the disadvantages, but that's not currently the case.

Exceptions to guidelines do occasionally happen. The justification here is lacking, however. --GoneIn60 (talk) 21:37, 4 December 2023 (UTC)

Automating the updating of scores is done by Template:RT data, these templates can be connected by a prose parameter in RT data, but that's the extent of their connection. Benefits of the standardised wording include consistency across articles, able to change wording on many articles with consensus, avoids describing scores as "rotten" or "fresh", avoids potentially confusing "approval rating", including wikilinks like 100% or 0% (talk section), and weighted average for Metacritic, etc, ensuring wikilinks aren't next to each other, able to update many articles like when they update website (talk section). Indagate (talk) 22:15, 4 December 2023 (UTC)

You have described some potential issues in the absence of consistency, but were these actual issues you can speak to? In my long editing tenure, rarely did I come across a film or TV article that used such terms or had such problems. Do you agree that there is more than one acceptable way to write the statements in prose? If so, why settle on only one form that hides text from novice users? This is the "tradeoff" that IMO fails justification unless it can be shown we had a real problem. The injection of this template on top of perfectly fine existing text, by the way, opens another can of worms reminiscent of MOS:VAR. --GoneIn60 (talk) 22:33, 4 December 2023 (UTC)

The use of this template is completely optional; nothing is being "enforced". But many editors like to use it because it's convenient, and because they know that, since templates like this are higher-visibility than lines in articles, care has been put into it and will continue to be put into it. To answer you directly, yes, there are absolutely multiple ways to write out the information. Anyone who wants to not use this template or to subst it out can do so. But those of us who trust other Wikipedians to maintain and improve this template over time (a trust I believe is wisely placed) should also be able to choose not to subst it.

Regarding novices, as a Teahouse host and primary maintainer of the introductory tutorial series, making things easier for them is one of my top focuses. But do I trust a novice editor who lacks the expertise to make their way to a template page to come up with better wording than a collective of editors who have refined this template over time? No, and nor should you. The wording of this template is not the only possible wording, but it's also perfectly fine wording, so the worst-case-scenario is that we stick with perfectly fine wording. No one is going to quit editing because they can't make an arbitrary change to a line about Rotten Tomatoes.

Lastly, to expand on the idea of future changes/improvements to this template, I'll copy a comment from the prior discussion this one is rehashing:

[Several editors] in the keep-but-make-subst-only camp have asked what benefit there could be to keeping transclusions of this, so allow me to present a plausible example. Currently, the Rotten Tomatoes template includes the average critics rating out of 10, a meaningful but distinct number from the Tomatometer score (which is the percentage of reviews which are positive). However, Rotten Tomatoes itself hides the average critic rating, requiring an extra click to get to it. Let's say that they decide in the future to stop reporting it entirely. And let's say that the community decides that given this, we don't want to include it in articles. What happens then? If there's no template, it becomes an arduous slog through every film article on Wikipedia to remove the information. But if some articles have it in template form, it's as easy as making a single edit to the template to stop displaying it. If you dislike that example, you can consider any other possible future change, but the overall principle is the same: having a template allows for refinement and optimization. And it's better to have that in a centralized forum, where it can be given more scrutiny through the wisdom of the crowd, than to have it dispersed over hundreds of individual pages.

{{u|Sdkb}} ^talk 23:28, 4 December 2023 (UTC)

The Marvels, and other MCU have similar, has potentially confusing "approval rating" and wikilinks next to each other (which goes against MOS:SEAOFBLUE. The issue are only potential but appear common, and the template is only optional. The difference between transclusion and subst is the ability to make mass changes in the future, like when they update their website (talk section). Indagate (talk) 08:21, 5 December 2023 (UTC)

One hand says the template is optional while the other hand says propagate to as many articles as possible for that mass change, "just in case" scenario (propagation is the only way a mass change would be successful). The hands seem to be sending different messages.

Another point from WP:TMPG: "Templates...that contain text which is not likely to ever be changed should be invoked with substitution." A very small chance that the wording needs to change years or decades from now is no reason to avoid subst-only. Also leaving future updates in the hands of a centralized forum, a handful of editors, isn't always the right prescription to produce the best results. Creative solutions can also come from relative newcomers who are not set in our ways; a process that can become stymied when we force them to jump through hoops (i.e. the template namespace and Wikidata) or seek consensus for every new idea at a centralized discussion. --GoneIn60 (talk) 12:23, 5 December 2023

The "just in case" scenario doesn't need every article to have the template for it to be beneficial and save time and effort. The Metacritic website redesign I mentioned above was only few months ago, and text could be changed with consensus at any time if anyone proposes a change, so don't think it's fair to say the text is "not likely to ever be changed". Newcomers are much more likely to make mistakes in phrasing, include the audience score, etc, than create a new creative way of phrasing boilerplate text that would have consensus. They don't need to know anything about Wikidata to use this, just RT data but that can be separate, similar templates like Template: Metacritic film prose have no Wikidata integration. Indagate (talk) 13:04, 5 December 2023 (UTC)

Just a quick clarification that "relative newcomers" may also include editors who have been here for some time but are simply new to the film/TV realm on Wikipedia. Since there are so few exceptions of templates like this one in running article text, even editors with significant experience may be thrown off. Nice to see a use-case example of a change implemented by the MC template, but an already prevalent method is to include archived URLs in citations, especially for websites that catalog information in database-like fashion that are subject to change. Since Wikipedia is not a catalog or database, it doesn't need to be up-to-the-minute in sync, and archived URLs already fill that specific kind of need. --GoneIn60 (talk) 14:00, 5 December 2023 (UTC)

• Yes - This template is not only unnecessary, but also against the Wikipedia:Template namespace guideline. LancedSoul (talk) 11:19, 5 December 2023 (UTC)
• No The arguments opposed convinced me this is unnecessary. Thanks! Nemov (talk) 14:10, 21 December 2023 (UTC)

Discussion

Please notify participants from the 2021 TFD to avoid the appearance of canvassing. – Jonesey95 (talk) 21:29, 1 December 2023 (UTC)

Since the last commenter was 14 days prior and I do not see any meaningful additions to the RfC in the next 10-15 days happening, I have submitted a closure request to have someone close the RfC. - Favre1fan93 (talk) 00:03, 19 December 2023 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Broken uses

@Indagate and MikeAllen: It's now your responsibility to fix all ~100 articles with script errors. * Pppery * _{it has begun...} 03:18, 8 December 2023 (UTC)

I mean, okay. I could probably get that done tomorrow, if a bot can't be commissioned. Mike Allen 03:23, 8 December 2023 (UTC)

that link's empty as looks reverted now, i tested with the bottom entry in Template:Rotten Tomatoes prose/testcases, the 9 was being converted to nine by the edit. Made edit after noticing an article like that, Assumed the template would ignore words? Indagate (talk) 10:06, 8 December 2023 (UTC)