Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Help talk:Citation Style 1

Discussion page of Help:Citation Style 1

Template:BotsTemplate:Skip to bottomTemplate:Talk header Template:Central Template:WikiProject banner shell User:ClueBot III/ArchiveThis Template:FAQ

doi-access

The only allowable value for doi-access is "free" so when doi-access is not free, the practice is to leave the doi-access card out. However, the Citation bot then comes along and adds a bogus |doi-broken-date= tag that generates an erroneous Template:Green error. Hawkeye7 (discuss) 19:39, 30 March 2026 (UTC)

This sound alike something that should be reported at User talk:Citation bot. It's had issue with technical support recently, this looks like another bug. There's no reason for it to ever add blank fields. -- LCU ActivelyDisinterested «@» °∆t° 19:45, 30 March 2026 (UTC)
Template:Tq? What is card?
This is about Kitty Oppenheimer and Template:Doi? That doi appears to me to be functional and links to this page at Brill which clearly shows that the cited source is behind a paywall so |doi-access=free is not appropriate. Setting |doi-access= to any other value (were other values permitted) would not change effects of |doi-broken-date= were that parameter in use in the template.
I do not know why Citation bot thinks or thought that the doi is/was inactive but, as mentioned above, the correct venue for Citation bot issues is at User talk:Citation bot.
Trappist the monk (talk) 20:01, 30 March 2026 (UTC)
Moved discussion to User talk:Citation bot, with misgivings. "Card" is an old-fashioned term for a parameter. Hawkeye7 (discuss) 23:00, 14 April 2026 (UTC)

Is there a "proper" way to cite NOAA events?

I'm asking because I've found two or three instances in dust devil, e.g. this and this one.-- Carnby (talk) 15:22, 14 April 2026 (UTC)

{{cite web}} should work fine. – Jonesey95 (talk) 21:40, 15 April 2026 (UTC)

Protected edit request on 23 April 2026

Template:Edit fully-protected Please make URL access level work with "chapter-url" parameter, or create new "chapter-url access" parameter. Thank you. Peter G Werner (talk) 16:46, 23 April 2026 (UTC)

Already exists:
<syntaxhighlight lang="wikitext" inline="1">"Chapter". Title.</syntaxhighlight>
"Chapter". Title.
Trappist the monk (talk) 17:12, 23 April 2026 (UTC)

Cite SSRN Identifiers

Template:Mdf

I propose that the following CS1 identifiers be permitted on {{Cite SSRN}}: |doi=, |s2cid=, |id=. Daask (talk) 15:30, 25 April 2026 (UTC)

Template talk:Cite SSRN has eight watchers. I have moved the above post from there to here because there are more watchers here. Also redirected Template talk:Cite SSRN to this talk page.
Trappist the monk (talk) 16:06, 25 April 2026 (UTC)
The doi of a SSRN is the same as the SSRN number, but with a doi prefix, and leads to the same place. Is there a need for duplication? -- LCU ActivelyDisinterested «@» °∆t° 16:29, 25 April 2026 (UTC)
Just a quick example taken from the first random paper I could find, Template:SSRN is the same as Template:Doi. The only real difference is that the SSRN links directly to the page, while the doi redirects to the page via doi.org -- LCU ActivelyDisinterested «@» °∆t° 16:35, 25 April 2026 (UTC)
Template:Re I think you're probably right, and the ideal scenario is to switch to {{citation|mode=cs1}}, keep the DOI and remove the SSRN. Of course, first you need to check either that the page style isn't set with {{CS1 config|mode=cs2}} or use {{citation|mode=Template:Module}}. Yeesh! I guess I was mostly trying to reduce editor headache when surprised that one of the CS1 templates lacks typical parameters. Daask (talk) 21:35, 25 April 2026 (UTC)
No don't do that. Use {{cite ssrn}} proper. Headbomb {t · c · p · b} 21:57, 25 April 2026 (UTC)
Thats seems a lot more confusing and unnecessary than just using cite SSRN. -- LCU ActivelyDisinterested «@» °∆t° 22:38, 25 April 2026 (UTC)
Template:Re I'm not willing to remove a DOI from a citation just because it duplicates the SSRN identifier or because a template doesn't support it. Other citation styles, eg. APA are explicit "Template:Tqi". It's so widely used that it is very useful as an identifier, quite apart from being linked to a resolver. If {{cite SSRN}} won't support |doi= or |id=, then I won't use it for citations with a DOI. Daask (talk) 18:06, 29 April 2026 (UTC)
We aren't bound by external standards. Every arxiv preprints has a corresponding DOI, that doesn't mean we suddently need to cite those DOIs when there are better ways to cite arxiv preprints. 18:34, 29 April 2026 (UTC) Headbomb {t · c · p · b} 18:34, 29 April 2026 (UTC)
Template:Re I know we aren't bound by them, but I do think we should be guided by them, because they are the thoughtful work of professionals who are largely dealing with the same goals and issues that we are when deciding citation format. The only difference is that our output is overwhelmingly consumed as a webpage with clickable links, whereas most citation style guidelines assume print as the primary medium. I don't mean to minimize that difference, but that has no bearing here. Identifiers that are more widely used are much more useful than smaller schemes like SSRN. I know our citations aren't APA, but if our citation lacks all the information needed to create an APA citation, then the editors of APA style regard it as incomplete, and I think we should too. Daask (talk) 19:02, 29 April 2026 (UTC)

archive.today detection false positive

Via this citation, it turns out that there used to be a http://archive.today.uci.edu website (UCI is University of California, Irvine), which is totally unrelated to the archive.today archiving service but is incorrectly being flagged. Legoktm (talk) 02:50, 26 April 2026 (UTC)

fixed in the sandbox:
<syntaxhighlight lang="wikitext" inline="1">Template:Cite book/new</syntaxhighlight>
Template:Cite book/new – not detected as a deprecated archival service
And to show that I didn't break anything:
<syntaxhighlight lang="wikitext" inline="1">Template:Cite book/new</syntaxhighlight>
Template:Cite book/new
Trappist the monk (talk) 14:29, 26 April 2026 (UTC)

Increment SSRN

Template:SSRN is valid and used on Skin disinfection. Thanks! Snowman304|talk 14:37, 26 April 2026 (UTC)

Spaced comma in issue number

See these refs:

  • Comfort, Andy (11 June 2025). "A railway with "people at its heart"". Rail Magazine. No. 1, 037. Peterborough: Bauer Media. p. 56. ISSN 0953-4563.
  • North, John (2 November 1973). "Chipping away at a fine piece of rail history". The Northern Echo. No. 32, 245. p. 10. ISSN 2043-0442.
  • "Giant railway map jigsaw". Evening Despatch. No. 18, 628. 12 February 1973. p. 21. OCLC 751646866.
  • Comfort, Andy (11 June 2025). "A railway with "people at its heart"". Rail Magazine. No. 1, 037. Peterborough: Bauer Media. p. 57. ISSN 0953-4563.
  • Bickerdyke, Paul, ed. (October 2021). "Tile map installed at Hunmanby". The Railway Magazine. Vol. 167, no. 1, 447. Horncastle: Mortons Media. p. 88. ISSN 0033-8923.
  • "Map shows the way - 1900 style". The Northern Echo. No. 30, 924. 31 July 1969. p. 3. OCLC 6685296.

These are all taken verbatim from North Eastern Railway tile maps#Locations, and in every one of them, the issue number has an unspaced comma; but on display, a space is added after the comma which is not present in the original. Why is this, when did it start happening, and please can it be reverted. Thanks. --Redrose64 🌹 (talk) 21:16, 26 April 2026 (UTC)

29 September 2018; an artefact of Template:Slink. The code presumes that comma and semicolon separators indicate that the separated values assigned to |page=, |pages=, |issue=, |volume= are lists of enumerators. There are two fixes: remove the separator or wrap the value in accept-as-written markup:
<syntaxhighlight lang="wikitext" inline="1">"Title". Magazine. No. 1234.</syntaxhighlight>
"Title". Magazine. No. 1234.
<syntaxhighlight lang="wikitext" inline="1">"Title". Magazine. No. 1,234.</syntaxhighlight>
"Title". Magazine. No. 1,234.
Trappist the monk (talk) 22:23, 26 April 2026 (UTC)
I get that |pages= can (should?) support lists of enumerators but I'm not seeing the use case for the other parameters except as an edge cases. A reference to a single issue or volume is, imo, far more common than a reference to multiple issues or volumes. Therefore we should consider changing the default behaviour for those parameters rather than forcing the alternatives suggested above for a majority of cases. Nthep (talk) 07:53, 28 April 2026 (UTC)

deprecated archival service: closed XfD

within this category i found a closed AfD from a few years back. i think i should just ignore it, as it's basically an archive, but i was thinking maybe someone could set up a thing to exclude (prefferably only closed, if possible) XfD-related things from the category. User "Oreocooke" (speak of the sun and it shines) 04:42, 29 April 2026 (UTC)

if it matters all 3 instances have the normal page as currently live ([1] [2] [3]) User "Oreocooke" (speak of the sun and it shines) 04:45, 29 April 2026 (UTC)
Basically i see nobody touches old archives,see this category. I also don't see any reason to replace archive url with another archive url or remove that completely because the afd had served it's purpose, We have bigger fish to fry.––KEmel49(📝,📋) 17:44, 29 April 2026 (UTC)

Can we just allow linefeeds in citation style 1 templates?

when I paste in a multi-line quote parameter, I am tired of getting

{{cite book}}: line feed character in |quote= at position 29 (help)

This doesn't seem useful. Dingolover6969 (talk) 07:17, 29 April 2026 (UTC)

Also, nbsp, same reason Dingolover6969 (talk) 08:05, 29 April 2026 (UTC)
So don't? Headbomb {t · c · p · b} 08:09, 29 April 2026 (UTC)
I'm not sure I understand the suggestion. Dingolover6969 (talk) 09:06, 29 April 2026 (UTC)
Linefeeds are permitted before and/or after each pipe and equals, but should not be used within the value of any parameter. --Redrose64 🌹 (talk) 14:14, 29 April 2026 (UTC)
Right... but I would like to use them in the value of the quote parameter. This would save me some busywork. Is there any reason we couldn't/shouldn't accommodate this in the module? Dingolover6969 (talk) 19:18, 29 April 2026 (UTC)
@Dingolover6969, Tweaking module for this purpose is not worthy at all, rather replace each linebreak with br tag. There won't be a thousand linebreak to replace, just a few for the quote parameter.––KEmel49(📝,📋) 19:22, 29 April 2026 (UTC)
In particular, nbsp is sometimes the right space character to use. However, I guess it would violate the last part of MOS:NBSP to use one directly, instead of the HTML or template version, since it is visually indistinguishable from a regular space. Although I'm not sure that means this templat, specifically, should definitely complain about it... Dingolover6969 (talk) 19:27, 29 April 2026 (UTC)
@Dingolover6969, You can use <syntaxhighlight lang="text" class="" style="" inline="1"><br/></syntaxhighlight> in line break position to prevent such error, only use in |quote=.––KEmel49(📝,📋) 17:40, 29 April 2026 (UTC)
Thanks for the suggestion! I am aware of that, and wish to avoid the process of replacing \n with <br/>, which can be inconvenient. (Or, rather, \n\n with <br/><br/>, technically, I guess, since a normal newline will just be swallowed by HTML — which is sometimes what I want to happen! That would save me the trouble of replacing \n with space manually.) Dingolover6969 (talk) 19:15, 29 April 2026 (UTC)
An easy workaround to this is just to place the quote outside of the template. Dingolover6969 (talk) 19:31, 29 April 2026 (UTC)
Adding a line-feed does in fact break the expectations of HTML, which dictate that the content of inline tags is in fact inline and without line feeds. Stop including line feeds. Izno (talk) 23:13, 2 May 2026 (UTC)
Linefeeds are space characters. The browser, on encountering a sequence of one or more of these characters (mixed any way you like), treats the whole sequence as if it were a single space. --Redrose64 🌹 (talk) 15:55, 3 May 2026 (UTC)

Is there a way for editor to (manually) indicate that an article is open access?

I'm using an journal article as a source; I've researched the article and determined that is Open Access, and the publisher provides a specific CC license (free to share, but must attribute). is there any field I can put in this Cite Journal template were I can store the fact that is open access? I want that fact preserved for posterity so I don't forget and have to do the research again. I realize I can add plain text at the end of the template, but I'm wondering if there is standard field for this ... such as the unlock icon. Noleander (talk) 14:45, 29 April 2026 (UTC)

If you have the doi, you can mark it as openly accessible with |doi-access=free. Same for bibcode, jstor, ssrn, etc. (with |bibcode-access=free, |jstor-access=free, etc...). See WP:DOIACCESS for more information. Headbomb {t · c · p · b} 14:55, 29 April 2026 (UTC)
Okay, thanks. I have the DOI, so I'll use the doi-access field. Noleander (talk) 14:59, 29 April 2026 (UTC)
If using a citation template that doesn't let you specify access, there are a number of templates to use outside a citation template; see {{Open access}} and its many alternative See alsos. Pol098 (talk) 12:31, 3 May 2026 (UTC)

generic author name in other languages

There are pages using sources from other languages where author parameter is populated by generic names in that language. Should foreign language generic name marked as generic or that only applies to english language. See example name. Here firstname জেলা (jela) means District and lastname প্রতিনিধি (protinidhi) means representative.––KEmel49(📝,📋) 17:33, 29 April 2026 (UTC)

If we are to believe these search results, there are 60ish articles that have |firstn=, |lastn=, or |authorn= parameters with Lua error in Module:Unicode_data at line 483: attempt to index field 'scripts' (a boolean value). as all or part of their assigned value. When one of |firstn= or |lastn= has Lua error in Module:Unicode_data at line 483: attempt to index field 'scripts' (a boolean value). the other parameter doesn't always have Lua error in Module:Unicode_data at line 483: attempt to index field 'scripts' (a boolean value).. Not obvious to me that there are enough instances of these two words to make it worth adding them to our list.
Trappist the monk (talk) 18:11, 29 April 2026 (UTC)
Is it possible in english wikipedia to have foreign words blacklisted as generic or each language wiki has to decide from their own language only.––KEmel49(📝,📋) 18:16, 29 April 2026 (UTC)
en.wiki could, if it were warranted, blacklist non-English words. Each wiki that uses a more-or-less current version of the cs1|2 module suite can blacklist words in their own local language.
Trappist the monk (talk) 19:25, 29 April 2026 (UTC)

Another generic title

Hello, another generic title that could be trapped |title=Request Rejected. Currently we have 75 instances of this. Keith D (talk) 11:24, 4 May 2026 (UTC)