This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 85 | ← | Archive 87 | Archive 88 | Archive 89 | Archive 90 | Archive 91 | → | Archive 94 |
I've just cleaned up a few articles where the author field ended with "(View posts)" ( sample diff) -- John of Reading ( talk) 09:26, 13 July 2023 (UTC)
Since there is a parameter for "translated title", and there is a parameter for "quote", I suggest a parameter for "translated quote". Currently I tend to write a translation of the quote in brackets after the quote, but this is probably not optimal, since the source itself is not the source of the translation (just as we usually cannot attribute a "translated title" to the source). Thiagovscoelho ( talk) 12:26, 13 July 2023 (UTC)
|trans-quote=
.|quote=
to give a fuller version of a quotation from the article itself, and sometimes it was to make clear how a source supported a claim, since it was a large webpage source and I can't give page numbers.
Thiagovscoelho (
talk) 13:30, 13 July 2023 (UTC)Hello. I frankly have no idea if this is the appropriate venue for this.
Istro-Romanian is one of the Balkan Romance languages. The others are Romanian, Aromanian and Megleno-Romanian. Adding a parameter |language=ro/rup/ruq
in a citation template will produce (in Romanian/Aromanian/Megleno-Romanian)
, but |language=ruo
does not produce (in Istro-Romanian)
. An example is reference 50 at
Istro-Romanians. I fixed it manually with |version=
but I don't see why Istro-Romanian should be excluded from Wikipedia's technical code, or whatever the root of this is. Note that there is already
Template:Lang-ruo so it's not a problem of "ruo" or of the language not being integrated anywhere within Wikipedia's code.
Can this be fixed? Super Dromaeosaurus ( talk) 20:17, 16 July 2023 (UTC)
Can "staff" be added to generic author names? There are 63 articles citing "Staff, Ars". 93.72.49.123 ( talk) 06:39, 20 July 2023 (UTC)
If I put this in the 'issue' field, it renders as "No. Spring 2022" which doesn't really seem correct. But it doesn't really seem like it should be in the date field like that either. – jacobolus (t) 15:49, 20 July 2023 (UTC)
I'm wondering whether it would make sense to show an error when a date of 1 January 1970 (the Unix epoch) is supplied. Of course there would be false positives, but from a quick search most articles appear to be using this date in error. 93.72.49.123 ( talk) 06:46, 20 July 2023 (UTC)
I fix a lot of script-generated citations, and about once every twenty or thirty, I'll end up duplicating a parameter that was actually already included but I didn't notice, causing the page to be added to
Category:Articles using duplicate arguments in template calls and creating additional work as other editors
User:Davemck and
User:Ira Leviton clean up after me.
Is there a way for this to generate a warning message / for me to enable display of a warning message that is already generated? I am sometimes able to notice the category being added to the page on preview, but this typically only displays if I'm editing the full page rather than just a section, which accounts for maybe 5% of my edits. Folly Mox ( talk) 13:14, 21 July 2023 (UTC)
{{cite book |title=Title1 |title=Title2}}
Is this the expected behavior? Rjjiii ( talk) 00:43, 12 July 2023 (UTC)
{{
cite web}}
: Check date values in: |access-date=
(
help){{
cite web}}
: Check date values in: |access-date=
(
help){{
cite web}}
: Check date values in: |access-date=
(
help)After adding references to Grand Sanhedrin, I noticed that Template:Cite journal creates somewhat obscure and (in my opinino) inaccessible output:
> Niles, H. (12 June 1830). "The Jews". Niles' Weekly Register. 38: 296.
The number 38 represents the "Volume" and "296" presentes the page number. In other citation templates, we state the page number after "pp.", such as when using Template:Cite book. I think applying this to journal citations would make it significantly easier for readers to find the facts in the source, and thus to help them read the surrounding information. This especially because the URLs tend to go to a place for the work as a whole, which places a heavy burden on understanding that 1) the page number is in fact given, and 2) which number is what.
Perhaps less importantly than the page numer is the volume. This because each volume tends to be its own work and thus its own ISBN and/or online entry page. This means the volume number isn't required for navigation within the work. Having said that, I wouldn't mind spelling that out as "Volume 38".
Would these changes be welcomed? What other ways might there be to address the usability issue? Or perhaps there exists documentation we expect people to find that explains this?
Krinkle ( talk) 23:37, 12 July 2023 (UTC)
With the move, the error messages and maint notices still point to cite techreport. Chandrasekhar Boyapati, William Beebee, Jr., Martin Rinard. A (Technical report).{{
cite tech report}}
: CS1 maint: multiple names: authors list (
link) (Technical report). {{
cite tech report}}
: Missing or empty |title=
(
help)
AManWithNoPlan (
talk) 16:26, 25 July 2023 (UTC)
{{cite tech report/new | title=A |author1=Chandrasekhar Boyapati, William Beebee, Jr., Martin Rinard }}
{{
cite tech report}}
: CS1 maint: multiple names: authors list (
link){{cite tech report/new | title=}}
{{
cite tech report}}
: Missing or empty |title=
(
help){{
Cite arXiv}}
, {{
Cite bioRxiv}}
, {{
Cite CiteSeerX}}
, and {{
Cite medRxiv}}
.For {{cite news}} or {{cite web}}, what parameter should be used to add a translation link to the original article (written in a foreign language) when both the URL and archive-URL have already been utilized? I don't see a translation-url or anything similar. Thank you.-- TerryAlex ( talk) 17:59, 25 July 2023 (UTC)
|translation-url=
parameter.|url=
to link to it if it is available online. You might include |type=Translation
. If you are citing the original-language source, cite that and use |url=
to link to it if it is available online. In either case, you can always add an external wikilink to the 'other' (translated or original-language source) after the closing braces of the {{cite <whatever>}}
template.{{cite news|url=www.abc.com/newsarticle.html|archive-url=web.archive.org/20230724091214/www.abc.com/newsarticle.html|title=News Article|work=ABC|date=March 23, 2021|archive-date=July 24, 2023|access-date=July 24, 2023|language=foreign|url-status=live}}
. Thanks.--
TerryAlex (
talk) 20:32, 25 July 2023 (UTC)
|at=
parameter and format it like this {{cite news|url=https://www.abc.com/newsarticle.html|archive-url=https://web.archive.org/20230724091214/www.abc.com/newsarticle.html|title=News Article|work=ABC|date=March 23, 2021|archive-date=July 24, 2023|access-date=July 24, 2023|language=foreign|url-status=live|at=https://web.archive.org/20230725112323/www.translation.com/translationpage.html English Translation]}}
It yields no error and the citation shows up looking properly. Is this a good way to do it or does it violate the citation format in any ways? Thanks.--
TerryAlex (
talk) 00:05, 26 July 2023 (UTC)
|at=
will corrupt the citation's metadata. What I meant in my first post was something like this:
<ref>{{cite news |url=https://www.abc.com/newsarticle.html |title=News Article |work=ABC |date=March 23, 2021 |access-date=July 24, 2023 |language=und}} https://www.translation.com/translationpage.html English Translation]</ref>
I want to reference a single video but different timestamps, ideally using SFN style where that uses page numbers, is there a way of doing this for time stamps? Darkwarriorblake ( talk) 16:03, 26 July 2023 (UTC)
{{
sfn}}
parameter |loc=
not do what you want?How about [1] this [2] or this? [3] – Jonesey95 ( talk) 01:09, 27 July 2023 (UTC)
References
{{cite book|last1=Hiriart-Urruty|first1=Jean-Baptiste|last2=Lemaréchal|first2=Claude|author-link2=Claude Lemaréchal|year=1993|chapter=XII Abstract duality for practitioners|title=Convex analysis and minimization algorithms, Volume II: Advanced theory and bundle methods|series=Grundlehren der Mathematischen Wissenschaften |trans-series=Fundamental Principles of Mathematical Sciences|volume=306|publisher=Springer-Verlag |location=Berlin |pages=136–193 (and bibliographical comments on pp. 334–335)|isbn=3-540-56852-2 |mr=1295240}}
{{
cite book}}
: Unknown parameter |trans-series=
ignored (
help)Headbomb { t · c · p · b} 15:05, 2 July 2023 (UTC)
For consistency with the other format categories (Bibcode, MR, PMC). Headbomb { t · c · p · b} 04:04, 7 July 2023 (UTC)
|mr=MR1234567
or |pmc=PMC12345
when they should have written |mr=1234567
or |pmc=12345
.
Category:CS1 maint: Zbl exists to catch cases where the specified identifier is temporary so that editors can come back later and provide the permanent identifier.maint_bibcode
isn't defined in the
Module:Citation/CS1/Configuration error_conditions
table — that's why the category page is showing "Pages with this condition are automatically placed in unknown error_conditions key: maint_bibcode." instead of its own name.
FeRDNYC (
talk) 17:28, 13 July 2023 (UTC)
This morning, I tried repeatedly without success, first to archive on the WayBack Machine, then secondly to cite the two relevant webpages of the meeting on 19 July 2023 of the House of Commons Business and Trade Select Committee (1,2). The WayBack Machine failed to archive the two relevant Committee webpage. Using the easy citation tool in Wikipedias's Visual Editor, I was unable to cite either webpage of the Committee. Hence, I now need to cite the two webpages using the Wikipedia generic default of {WebCite}. I'm not sure what citation protocol best to follow. I've tried without success to look up the APA guidelines for citing committee meetings and committee reports. In my view, it would be helpful to have wikipedia citation templates specifically for citing committee meetings and citing committee reports.
[2] https://committees.parliament.uk/event/19035/formal-meeting-oral-evidence-session/
Humanity Dick ( talk) 11:59, 24 July 2023 (UTC)
{{cite web |author=((Business and Trade Committee)) |date=19 July 2023 |title=Food and fuel price inflation: will prices come down this year? |website=UK Parliament |url=https://committees.parliament.uk/work/7774/food-and-fuel-price-inflation-will-prices-come-down-this-year}}
{{cite web |author=((Business and Trade Committee)) |date=19 July 2023 |title=Food and fuel price inflation: will prices come down this year? - Oral evidence |website=UK Parliament |url=https://committees.parliament.uk/event/19035/formal-meeting-oral-evidence-session/}}
{{
cbignore}}
otherwise IABot will remove it (c.f.
T321146)--
Green
C 14:21, 24 July 2023 (UTC)
This gives an overview of various citation tools out there. I figured many of you would get something out of this. Headbomb { t · c · p · b} 05:52, 1 August 2023 (UTC)
URLs get embedded in various places of the template which makes link rot repair difficult to manage for bots and scripts. Typically they are skipped. For example
Help_talk:Citation_Style_1#Documentation_needed_for_linking_multiple_urls_within_the_'pages'_parameter shows the free-form nature of how we do it. Another way is more systematically like we do for |author=
+ |author-link=
separating the metadata from the link.
It would be |page1=
("page=42") + |page1-url=
with perhaps support for up to 5 or 10 pages. Note |page=
would be an alias for |page1=
.
For page ranges use |pages1=42-44
(display: "pages=42-44") + |pages1a-url=
+ |pages1b-url=
where "a" is for 42 and "b" for 44. More page ranges can be added for example |pages2=47-50
(display: "pages=42-44, 47-50") + |pages2a-url=
+ |pages2b-url=
. This way one can have a mix of single page and page ranges, all with their own URLs, contained in parameters. --
Green
C 16:03, 10 July 2023 (UTC)
|page*=
parameters, but I definitely recognize that there are times when only linking to a single location risks leaving the user fumbling around to figure out how they can reach the rest of the content being cited.|page=
, alongside a more generic |url=
linking to the source as a whole. ...I was also under the impression that was incorrect: the |url=
parameter should simply hold the link from |page=
, shouldn't it?|title-link=
. When that is done, and there is no named |contribution=
within the book to cite, the only way to provide a convenience link for specific content within the book (and the way that has been repeatedly recommended) is to put the link into the page or pages parameter. —
David Eppstein (
talk) 20:26, 13 July 2023 (UTC)
|section-url=
will do what you need. Normally I use both links unless the relevant text is on the first page of the section. --
Shmuel (Seymour J.) Metz Username:Chatul (
talk) 21:17, 13 July 2023 (UTC)|title-link=
and |url=
interact with each other. (Or more to the point, that they don't, and result in a CS1 error when used in the same citation.)|pageN-url=
scheme like
GreenC is proposing.
FeRDNYC (
talk) 02:45, 15 July 2023 (UTC)
Markup |
|
---|---|
Renders as | Bloggs, Joe; Smith, John; Smythe, Jim. 1000 Acres (2nd ed.). |
|title-link=
instead of piping? I'll
be bold and fix it (plus any others), if we agree |title-link=
is always preferable now. I feel like the documentation should demonstrate best current practices, not outdated ones. (And we wonder how editors pick up / retain bad habits?)
FeRDNYC (
talk) 05:06, 15 July 2023 (UTC)
|title=
to |title-link=
could go a long way. And/or, a feature request to Citation bot (if it doesn't already have). --
Green
C 01:33, 17 July 2023 (UTC)
|title-link=
and |url=
should not be used together.
FeRDNYC (
talk) 11:11, 22 July 2023 (UTC)
|page1-url=
and |page1-archive-url=
and |page1-archive-date=
fields for every individual page?
Mr.choppers |
✎ 16:35, 2 August 2023 (UTC)
I'm trying to {{ Cite news}} an article that is republished from another work and the original work is attributed in the article. The original article is paywalled so I want to cite the freely available copy.
Kelly Smith, Star Tribune staff writer. Republished same day with no changes to Inforum. Should I say via=Inforum? And for work say Star Tribune? Or work=Inforum and agency=Star Tribune? Pingnova ( talk) 18:29, 2 August 2023 (UTC)
'^[^1-5]%d%d%d%d$', -- 5 digits without subcode (0xxxx, 60000+); accepts: 10000–59999 needs to now be 1-6 instead of 1-5 since doi: 10.60082/2817-5069.2017 exists. AManWithNoPlan ( talk) 00:39, 27 July 2023 (UTC)
Wikitext | {{cite journal
|
---|---|
Live | "Title". Journal. doi: 10.60082/2817-5069.2017. |
Sandbox | "Title". Journal. doi: 10.60082/2817-5069.2017. |
Shouldn't {{
Cite report}} wrap the output of |title=
in quotes? Its
TemplateData says it should, at least. –
MJL
‐Talk‐
☖ 17:32, 3 August 2023 (UTC)
|journal=
parameter. For example:example
|
---|
{{cite report |last1=Baumer |first1=Matt |last2=Kephart |first2=Curtis |title=Aggregate dynamics in a large virtual economy: Prices and real activity in Team Fortress 2 |id={{hdl|10419/125549}} |publisher=University of California, Economics Department |location=Santa Cruz |type=Working Paper |year=2015 |language=en}} to output: |
|id=
parameter since it's more-or-less redundant.{{cite document}}
would suite that reference:
{{cite document/new |last1=Baumer |first1=Matt |last2=Kephart |first2=Curtis |title=Aggregate dynamics in a large virtual economy: Prices and real activity in Team Fortress 2 |id={{hdl|10419/125549}} |publisher=University of California, Economics Department |location=Santa Cruz |type=Working Paper |year=2015 |language=en}}
{{cite document}}
.One of the citations on this page shows an error message when the SSRN value that the citation bot added is correct and greater than 4500000. Achmad Rachmani ( talk) 07:37, 7 August 2023 (UTC)
Wikipedia articles on illustrated books -- especially children's books -- could really use an "illustrator" parameter, to go along with (for example) "editor." Jhlechner ( talk) 15:52, 8 August 2023 (UTC)
|others=
parameter for this, |others=Illustrated by John Smith
for example. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 16:00, 8 August 2023 (UTC)Hello, can you add "Facebook" as a generic title. Currently, 859 instances. Keith D ( talk) 22:00, 9 August 2023 (UTC)
I know that ReFill works such that <ref>https://example.com/whatever</ref> gets converted into a properly formatted cite template with the correct metadata. Does there exist anything that does this for ISBNs? I just noticed that I am probably wasting a lot of time typing in book citation information when there's already a gigantic unified metadata tracking system that is based on ISBNs. jp× g 23:40, 11 August 2023 (UTC)
{{
cite book}}
: Missing or empty |title=
(
help)So, on TRAPPIST-1 we use the Template:Cite Gaia EDR3 (a wrapper for a {{ cite journal}}) and we also need to add {{ sfn whitelist}} because otherwise it throws sfn errors. Is there a way to fix the {{ Cite Gaia EDR3}} template so that we don't need to hide bogus harv errors? Jo-Jo Eumerus ( talk) 05:38, 12 August 2023 (UTC)
The current " Archived from the original on YYYY-MM-DD" phrasing at the end of many citations takes a pretty significant amount of space, especially since we now have bots indiscriminately adding these pre-emptive archive links to every citation. Is there any way we could cut that down to just " Archived YYYY-MM-DD" or the like? (If it were up to me we would entirely leave off archive links for still-living pages, as these typically have no direct benefit to readers.) – jacobolus (t) 17:57, 31 July 2023 (UTC)
from the originalwhere
url-status=live
(where else would it be archived from?). I'd also support suppressing display of |access-date=
where an |archive-date=
is present and url-status=dead
, since if the link is dead and there's an archive, there's no point. Ditto for |access-date=
for all {{
cite book}} and {{
cite journal}}, since if they've gone to print there won't be an update to the information.
Folly Mox (
talk) 20:03, 31 July 2023 (UTC)
|access-date=
parameters by bot seems disruptive and annoying. Probably easier just to suppress display in cases where it's of no use to readers, only editors tryna repair an archive.
Folly Mox (
talk) 08:46, 1 August 2023 (UTC)
|access-date=
looks like this:
<span class="reference-accessdate">. Retrieved <span class="nowrap">2023-08-01</span></span>
not all webpages are static documents. Even in the case of an archive, I'd like to know when that page was accessed.But, archives are static documents — even if the page changes over time, the archive won't. It's a snapshot of a particular moment, and the date of that snapshot "trumps" the access date... no matter when the archive was accessed, the version they got is the one archived on the date indicated. An
|archive-date=
(and |url-status=dead
) makes the access date completely irrelevant.
FeRDNYC (
talk) 02:01, 16 August 2023 (UTC)
|access-date=
if the archived page has been checked and the content matches.
Mr.choppers |
✎ 16:17, 2 August 2023 (UTC)
|access-date=
as possible, ideally.) But if someone submits an |archive-url=
with a citation (I try to do so, if I think it's likely to vanish at some point), I'd certainly expect it not to be an archive created after that point!
FeRDNYC (
talk) 02:07, 16 August 2023 (UTC)
not as thoughtful, and do not provide archives at the time of edit– personally I submit pages to be saved by the internet archive but then intentionally ("thoughtfully") do not include the archive link on the page (or sometimes even remove archive links that were added by the IA bot), because to me the proliferation of archive links for still living pages seems like a space-wasting spammy distraction. – jacobolus (t) 05:01, 16 August 2023 (UTC)
/info/en/?search=Wikipedia:ISSN includes "An ISSN is particularly helpful in the following circumstances" which include "In a citation to an article that is not available online except behind a WP:PAYWALL" and "In a citation to an article that is not available online in full text". How are they helpful in those circumstances? When I've seen paywalled articles cited I've sought/created archived versions. Should I also add ISSNs? To date I've only noticed an ISSN of one Wall Street Journal article. Mcljlm ( talk) 18:42, 12 August 2023 (UTC)
Personally, my experience is that, because ISSNs are for publications rather than for individual articles, they're much less helpful than e.g. DOIs, and they're often overused because VisualEditor's citation tool seems to like them. Basically, all you really want to have is at least one identifier in each citation. That could be a URL, or a DOI, or an OCLC, or an ISSN, but just plain text is non-preferable. And all of this only matters if you're trying to get an article's references to a featured-quality level. Hope that helps! Cheers, {{u| Sdkb}} talk 18:12, 12 August 2023 (UTC)
|language=en
for citations on the English language Wikipedia is my favourite totally unnecessary automated reference add, which I'll usually delete when cleaning up other people's work to add page numbers etc.From what I understand, the Foundation has a single contractor responsible for all of Citoid, who is currently tasked with integrating it into Wikidata for some reason instead of fixing any of its issues.
Folly Mox (
talk) 21:52, 12 August 2023 (UTC)
|language=
parameter is very valuable, but it doesn't display anything when it matches the language of the project it's being used in. Aren't people checking the references whenever they translate articles? I'd think that they'd be able to fill out the language parameter manually during that process. It's hardly a blip of effort when the overall time investment of translation is taken into account.
Folly Mox (
talk) 02:22, 13 August 2023 (UTC)
Thanks everybody, especially Sdkb for suggesting I asked here. Until reading the responses above I assumed I was missing something significant about their use. Maybe I should delete the ISSN from the WSJ citation. Mcljlm ( talk) 23:38, 12 August 2023 (UTC)
|language=en
, except for multi-lingual pages, e.g. |language=de,en,fr
. --
Michael Bednarek (
talk) 01:53, 13 August 2023 (UTC)
Coincidentally, I had just yesterday gone through every entry on Bibliography of works on Davy Crockett to tidy up references, etc. Looked great yesterday. Imagine my surprise when I opened that list today and found red messages on numerous cite book entries such as "{{ cite book}}: Cite has empty unknown parameter: |1= (help)" Etc. etc. It looked perfect yesterday. Whatever it is, also affected the drop-down cite book template - in that if you had an ISBN number, you would put it in the template and click on that little magnifying glass to the right of it, it would fill out the rest of the template. Now it just sits there and does nothing if you try that. So, I've been randomly going through other lists and it seems that only the cite book template triggers that. What happened between yesterday and today that affected the cite book template? — Maile ( talk) 01:49, 13 August 2023 (UTC)
{{
cite book}}
: Empty citation (
help): |website= ignored (help)" "22:01, August 13, 2023 Citation bot talk contribs block 3,818 bytes −24 Alter: template type, url. URLs might have been anonymized. Add: date, newspaper, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Eastmain | #UCB_webform 25/30 "
— Maile (
talk) 03:14, 14 August 2023 (UTC)I have encountered a problem in Elias Lönnrot: two references using {{ SLS Q}} yield a maintenance error message: "location missing publisher" but the Wikidata items ( Swedish Writings volume 1 (Q113396160) and Swedish Writings volume 2 (Q113396181)) have both publisher (P123) and place of publication (P291).-- Carnby ( talk) 11:56, 13 August 2023 (UTC)
|publisher=unset
, which is going to block an publisher setup on wikidata. I suggest asking the creator of the template about it. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 12:17, 13 August 2023 (UTC)
Could we add Template: namespace? For example in European Union Referendum Act 2015 there is Template:UKEU2016Result which has the error. If it was in the tracking category my bot would find it automatically. As-is I have to manually track them down. In the first 200 articles of the category, randomly sorted, there were 3 articles with templates that required a fix (1.5%) -- Green C 00:26, 14 August 2023 (UTC)
Something in the latest update is causing a page with a reference to transclude itself. This has the downside that templates that are otherwise unused, are now hidden from reports. Is this something that can be fixed? A setting that can be set to ignore on template pages? I remember a previous change a while back that also had this issue. Gonnym ( talk) 09:23, 14 August 2023 (UTC)
error()
in the namespace test that calls title_object:getContent()
(this is what counts as self transclusion). Previewing an article with the modified code showed an error for every cs1|2 template in the article (the expected result). I then previewed {{
cite Grove}}
; no errors so the module is not calling title_object:getContent()
in template namespace. Still, as I write this, in
Special:WhatLinksHere for {{cite Grove}}
, the template appears to still be transcluding itself. Is there a WhatLinksHere lag as there is for categories?year: Year of source being referenced. The usage of this parameter is discouraged; use the more flexible |date= parameter instead unless both of the following conditions are met: Currently the Citation Bot adds years for journals, etc. Should we be using date? AManWithNoPlan ( talk) 18:30, 1 August 2023 (UTC)
|date=
is most appropriate.
|year=2023
– ok because parameter name matches parameter value|year=Winter 2023
– not ok because semantic conflict|date=2023
– ok because parameter name matches parameter value|date=Winter 2023
– ok because parameter name matches parameter value|day=
and |month=
but so long as
MOS:DATES allows YYYY-MM-DD format publication dates, |year=
will be required when CITEREF
disambiguation is needed (|date=2023-08-01
|year=2023a
...)CITEREF
disambiguation then, for ease of coding, it should probably just use |date=
.|year=
. When it's a full date/date with month, use |date=
.
Headbomb {
t ·
c ·
p ·
b} 20:49, 1 August 2023 (UTC)
|date=
for either case? I see no benefit in having two types of fields for this information.
Mr.choppers |
✎ 16:09, 2 August 2023 (UTC)
CITEREF
disambiguators may make it more difficult for readers to determine which of your 1979 sources is being cited. For example, someone reading a printed copy of an en.wiki article will not be able to mouse-over the short form citation to see which one gets highlighted. The only case where |year=
is required is the one I described above. Don't hide the CITEREF
disambiguators.|year=
parameter is not necessary, when |date=1979
and |year=1979a
appear in the same cs1|2 template,
Module:Citation/CS1 emits a maintenance message and adds the article to
Category:CS1 maint: date and year.|date=
as just the year, but set |ref=
to use 2007a, 2007b etc. Is this recommended practice?
Folly Mox (
talk) 19:50, 2 August 2023 (UTC)
|date=
, because it saves you the two seconds pondering which one you ought to be using.
Mathglot (
talk) 06:48, 3 August 2023 (UTC)
|date=
fields weren't exactly dates; glad to know that isn't the case.
Folly Mox (
talk) 13:31, 3 August 2023 (UTC)Those diffs look good.I disagree. At §Notes there are three Francillon 1979 short-form references. In §Bibliography there is no Francillon 1979 and one each of Francillon 1979a and Francillon 1979b. Which of the three Francillon 1979 short-form references goes to Francillon 1979a and which goes to Francillon 1979b?
Am I right in thinking that {{ Please check ISBN}} and Category:Articles with invalid ISBNs are obsolete? (The former places articles in the latter.)
There are currently only 10 pages in that category, and all but one of them are also in Category:CS1 maint: ignored ISBN errors (which itself contains 382 pages). In the only one that isn't, Rodney Hallworth, the template marks the text "ISBN B001ALS2EY" in a hand-written book reference. The last non-minor edit on the category's talk page is from 2015; the last and only edits on the template's talk page are from 2012.
So it looks as if these have fallen out of use and been replaced by
Category:CS1 maint: ignored ISBN errors and
Category:Pages with ISBN errors (perhaps due to the switch from
magic links for ISBNs to {{
ISBN}} and isbn=
parameters), and the template is only being used sporadically. Of the 10 current cases, 9 were already being tracked elsewhere, and the remaining exceptional one could have been handled by adding the ISBN template (which should be done anyway) and then the invalid ISBN would have shown up in
Category:Pages with ISBN errors.
So it seems that this template and category should be decommissioned? Or am I overlooking a reason for keeping them? Joriki ( talk) 20:32, 17 August 2023 (UTC)
ISBN B001ALS2EYis really an ASIN so should read: 'ASIN B001ALS2EY'.
Just stumbled on a problem that you could consider tracking. Cite template having an |author-link=
parameter but no |author=
or equivalent parameter. Probably similar situation for |editor-link=
.
Keith D (
talk) 10:36, 14 August 2023 (UTC)
language=Swiss German
?There are a handful of pages that weren't listed at
Category:CS1 maint: unrecognized language yesterday (I know because I'd gone through all the pages) but are listed there now without having been edited:
The Night Game,
Satanic panic,
List of songs recorded by Owl City (I already fixed the last one). What they have in common is that they specify "Swiss German" as a language, which is apparently no longer recognized. If this is replaced by gsw
, it now displays as "Alemannic".
{{
Citation Style documentation/language/doc}} says that the 3-character code gsw
stands for "Swiss German".
Category:CS1 maint: unrecognized language says that "For recognized ISO 639-2 languages with multiple official names, MediaWiki recognizes only one." The official names for gsw
are "Swiss German", "Alemannic" and "Alsatian".
So it seems that there's been a breaking change where gsw
is now being mapped to "Alemannic" instead of "Swiss German". I wonder how we should deal with this. "Swiss German" is more specific than "Alemannic", and also more understandable to non-linguists. Everyone in Germany knows what Swiss German is, but few people know what Alemannic is or that it contains Swiss German as a subset. So it doesn't make much sense to relabel these works as "Alemannic". But keeping "Swiss German" would leave these articles in the maintenance category indefinitely. (
List of songs recorded by Owl City was fixable because the resource is actually in Swiss High German, which has its own code.)
So ideally I think this change should be reverted, but I have no idea where to request that. If it isn't, then {{ Citation Style documentation/language/doc}} needs to be updated (and that may apply to other codes as well if this was part of a broader change). Joriki ( talk) 22:11, 18 August 2023 (UTC)
{{#language}}
magic word). Some languages and tags are overridden in cs1|2.gsw
from 'Swiss German' to another English-language form 'Alemannic'.{{cite book |title=Title |language=Alemannisch}}
→ Title (in Swiss German).gsw
, this seems to confirm that, when given tag gsw
, MediaWiki used to return the English-language form: 'Swiss German'. Because there is no override for gsw
, cs1|2 also recognized 'Swiss German' as a known language.Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
gsw
would then be preferred over "Swiss German", right?
Joriki (
talk) 00:31, 19 August 2023 (UTC)
gsw
code to Swiss German, as already justified in the commit notes. Both the Ethnologue and the Glottolog recognize that Allemanic is a parent of Swiss German, and renaming it to Swiss German excludes other Allemanic languages that do not have their own MediaWiki code, such as
Swabian. Additionally, arguments like Everyone in Germany knows what Swiss German isare irrelevant; many Allemanic languages like Alsatian are not even spoken in Germany, so it doesn't really matter what everyone in Germany thinks.
{{#language:gct|en}}
→ gct – no support for the
Colonia Tovar dialect{{#language:gsw|en}}
→ Alemannic{{#language:swg|en}}
→ swg – no support for
Swabian German{{#language:wae|en}}
→ Walser{{#language:}}
magic word are supported by cs1|2.
ISO 639-3 maps gsw
to Alemannic, Alsatian, and Swiss German.
ISO 639-2 maps the same languages in a different order: Swiss German, Alemannic, and Alsatian.gsw
in the infobox.
CLDR v37.0β maps gsw
to Swiss German (English) and Schweizerdeutsch (native). The common language name for gsw
among all three is Swiss Germanswg
) to be supported by MediaWiki, take it to Phabricator.gsw
as Swiss German and will recognize Swiss German as a known language name. Because MediaWiki uses CLDR for language name translations, it knows the local language names for its supported languages (mostly):
{{#language:gsw|es}}
→ alemán suizo|language=gsw
in a cs1|2 template copied to es.wiki will produce the correct local-language rendering without the need for editor intervention.I've noticed that {{
cite book}} has started emitting an error message where it contains |work=
instead of displaying the value held in |work=
. Are these being tracked anywhere? Most of the |work=
parameters can probably just be reparameterised as |series=
, although I found a few that weren't so easy. Seems like there should be an easy way to find these citations so whatever is held in the |work=
parameter can be caused to be displayed again instead of hidden away in the source.
Folly Mox (
talk) 17:24, 18 August 2023 (UTC)
{{cite book}}
ignores |work=
, the fix has been:
|title=
→ |chapter=
(or appropriate alias)|work=
→ |title=
|title=
→ |volume=
; |work=
→ |title=
. Hopefully they're mostly easy swaps of one kind or another. Thanks again.
Folly Mox (
talk) 18:23, 18 August 2023 (UTC)
|series=
was the right change, but most need chapter/title conversion, per Trappist. –
Jonesey95 (
talk) 20:36, 18 August 2023 (UTC)
Not all of these parameters are supported by every CS1 template.
|work=
is not listed as a supported parameter in the documentation for {{
Cite book}}. Yes, there are 46,000 pages to fix, but we have had much larger piles of pages to fix before, and happily, the fixes are typically pretty easy. As usual, the error messages are new, but the errors have been there for a long time. –
Jonesey95 (
talk) 05:05, 20 August 2023 (UTC)I just added language=kk-cyrl
(meaning "Kazakh (Cyrillic script)") to a citation in
Sadyk Abdujabbarov. That automatically added the article to the non-existent
Category:CS1 Kazakh (Cyrillic script)-language sources (kk-cyrl), which is explicitly showing up as a red-linked category in the article's category list. (
Category:CS1 Kazakh-language sources (kk) and
Category:CS1 Kazakh (Kazakhstan)-language sources (kk-kz) already exist.) (Interestingly, the new category's page says "Wikipedia does not have a category with this exact title" and yet also "This category contains only the following page".)
Am I right in thinking that I should now create
Category:CS1 Kazakh (Cyrillic script)-language sources (kk-cyrl) with the content {{
CS1 language sources}}
? And is there anything else I need to do?
Joriki (
talk) 14:53, 20 August 2023 (UTC)
{{
CS1 language sources/core}}
. There are, according to
this search about 80 categories that have an extraneous {{
CatAutoTOC}}
template. I'll hack an awb script to remove them.I propose to update cs1|2 module suite over the weekend 12–13 August 2023. Here are the changes:
|archive-date=
/ |archive-url=
timestamp mismatch;
discussion|location=
(or alias) but do not have |publisher=
;
discussion|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
;
discussion{{
cite document}}
;
discussion|medrxiv=
and {{
cite medrxiv}}
;
discussionfkv
;
discussion{{
cs1 config}}
;
discussionModule:Citation/CS1/Configuration
|archive-date=
/ |archive-url=
timestamp mismatch;|location=
(or alias) but do not have |publisher=
;|subject-first=
, |subject-last=
, and aliases and enumeration variants;
discussion|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
, |transcripturl=
;{{cite document}}
;|medrxiv=
and {{cite medrxiv}}
;|title-note=
;
discussion{{
cite tech report}}
, {{
cite arXiv}}
, {{
cite bioRxiv}}
, {{
cite CiteSeerX}}
, and {{
cite SSRN}}
;
discussion{{cs1 config}}
;|subject-first=
, |subject-last=
, and aliases and enumeration variants;|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
, |transcripturl=
;{{cite document}}
;|medrxiv=
and {{cite medrxiv}}
;|title-note=
;Module:Citation/CS1/Date validation
|archive-date=
/ |archive-url=
timestamp mismatch;Module:Citation/CS1/Identifiers
|bibcode=
;
discussion|medrxiv=
and {{cite medrxiv}}
;|class=
arXiv linkto use https;
discussion|medrxiv=
and {{cite medrxiv}}
;— Trappist the monk ( talk) 15:54, 5 August 2023 (UTC)
|publisher=London
to stop the maintenance message from appearing (which citations generated automatically from sources hosted on Internet Archive already do), and b. after reading through the linked discussion, I'm understanding that |location=
in {{
cite conference}} is not supposed to hold the location of the conference, which is wild to me. What is it for then, and what parameter is supposed to hold the location of the conference?
Folly Mox (
talk) 02:38, 6 August 2023 (UTC)
|Location=
is for the location of the publisher. Bibliographically speaking, nothing holds the location of the conference. The only place it appears is often in the title, e.g. Proceedings of the 12th Conference on Rat Extermination, Held in Phoenix, AZ, on December 6–9, 2009. Likewise, |date=
isn't the date of the conference, but rather the date the proceedings were published.
Headbomb {
t ·
c ·
p ·
b} 02:46, 6 August 2023 (UTC)
|conference=
. If using {{
cite conference}}
, it is best to provide the title of the conference proceedings in |book-title=
so that that information makes it into the citation's metadata; |conference=
is not part of the metadata.emit error when year less than 100be on citations to ancient book sources that legitimately predate 100 CE? Folly Mox ( talk) 19:59, 5 August 2023 (UTC)
0
. Here is the live module – no error message when there should be an error message:
* {{cite sign | title = Victory stele of Thutmose III | location = Sudan, Gebel Barkal | publisher = Egyptian New Kingdom | date = 1440 BC | via = Boston Museum of Fine Arts | url = https://collections.mfa.org/objects/145121}}
{{
cite sign}}
: Check date values in: |date=
(
help)|orig-date=
is suppressed when |date=
is not provided, I usually just guess at the publisher and date so I can get the |orig-date =
value to display.
Folly Mox (
talk) 02:16, 6 August 2023 (UTC)straightforward to implementdoesn't fit with that philosophy.
|series=
is one of those parameters that has different meaning for different templates; particularly {{
cite episode}}
and {{
cite serial}}
.detect, can some minor variance not throw up an error (e.g. +/- 24 hours)? If someone uses their local time as the "archive date/time" but the URL is encoded using UTC, this should not be an error or something that is "fixed". — Locke Cole • t • c 17:47, 21 August 2023 (UTC)|archive-date=
/|archive-url=
timestamp mismatch
Revert the edit that caused timestamp errors across the entire site or nah? 4theloveofallthings ( talk) 09:23, 14 August 2023 (UTC)
|archive-date=
parameters with the values present in |archive-url=
.
Folly Mox (
talk) 13:08, 14 August 2023 (UTC)
I found |url-status=bot: unknown
in
an article. Is that a valid setting? What does that mean? In this case, the archive is to
archive.today, which does not seem to be a currently functioning site. —
BarrelProof (
talk) 01:19, 18 August 2023 (UTC)
|url-status=
parameter refer to the original link rather than the archive url? It was my understanding that archive urls were presumed to be functional.
Folly Mox (
talk) 02:24, 18 August 2023 (UTC)
|url-status=
— which is ONLY valid when there are both |url=
and |archive-url=
parameters in a citation — provides the status of the original source URL, and dictates how the |archive-url=
is presented in the citation: Whether it's relegated to being a "backup" source (when |url-status=live
), whether it's given prominence over the original |url=
(when |url-status=dead
), or whether it's the only link provided, and the original |url=
is suppressed (when |url-status=usurped
).
FeRDNYC (
talk) 10:50, 20 August 2023 (UTC)It's not so much that they're presumed to be functional, more that they're recognized (unlike sourceIt was my understanding that archive urls were presumed to be functional.
|url=
s) to have no value unless they're functional. IOW, if a citation template includes an |archive-url=
that points to a dead link (the archiver shut down, they changed their access system without providing redirects from older-system URLs, etc.) the correct mitigation is to simply delete that parameter. An inaccessible archive... isn't. (An archive.)
FeRDNYC (
talk) 11:09, 20 August 2023 (UTC)
Can someone sync the templates over to there again. AManWithNoPlan ( talk) 00:38, 22 August 2023 (UTC)
{{
citation}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 2006-05-23 suggested (
help)The archive-date and archive-url are actually correct. WebCite encodes the archive date in base-62 which also serves as the capture ID eg. 6GOwnekjN. A Lua function for this is in Module:Webarchive. -- Green C 18:00, 22 August 2023 (UTC)
|archive-url=
. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 18:23, 22 August 2023 (UTC)A command-line tool for testing/checking the value of WebCite IDs:
base62.lua
|
---|
#!/usr/bin/lua --[[--------------------------------------------------- The MIT License (MIT) Copyright (c) 2016-2023 by User:GreenC (at en.wikipedia.org) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ]] -- Given a Webcite ID on arg[1], return dates in mdy|dmy|iso|ymd format -- example ID: 6H8pdR68H -- http://convertxy.com/index.php/numberbases/ -- http://www.onlineconversion.com/unix_time.htm --[[--------------------------< base62 >----------------------- Convert base-62 to base-10 Credit: https://de.wikipedia.org/wiki/Modul:Expr ]] local function base62( value ) local r = 1 if value:match( "^%w+$" ) then local n = #value local k = 1 local c r = 0 for i = n, 1, -1 do c = value:byte( i, i ) if c >= 48 and c <= 57 then c = c - 48 elseif c >= 65 and c <= 90 then c = c - 55 elseif c >= 97 and c <= 122 then c = c - 61 else -- How comes? r = 1 break -- for i end r = r + c * k k = k * 62 end -- for i end return r end local function main() -- "!" in os.date means use GMT zday = os.date("!%d", string.sub(string.format("%d", base62(arg[1])),1,10) ) day = zday:match("0*(%d+)") -- remove leading zero zmonth = os.date("!%m", string.sub(string.format("%d", base62(arg[1])),1,10) ) month = zmonth:match("0*(%d+)") nmonth = os.date("!%B", string.sub(string.format("%d", base62(arg[1])),1,10) ) year = os.date("!%Y", string.sub(string.format("%d", base62(arg[1])),1,10) ) mdy = nmonth .. " " .. day .. ", " .. year dmy = day .. " " .. nmonth .. " " .. year iso = year .. "-" .. zmonth .. "-" .. zday ymd = year .. " " .. nmonth .. " " .. day year = tonumber(year) month = tonumber(month) day = tonumber(day) if year < 1970 or year > 2020 then print "error" elseif day < 1 or day > 31 then print "error" elseif month < 1 or month > 12 then print "error" else print(mdy .. "|" .. dmy .. "|" .. iso .. "|" .. ymd) end end main() |
20060523220016
from which it extracts the date 2006-05-23
. That date does not match |archive-date=2013-05-06
. The correct fix here, it seems to me, is to write: |archive-url=
https://web.archive.org/web/20060523220016/http://www.alwatan.ma/html/Publication_Fondation/Publication_2006/Publication/Ouvrage.pdf
(http
changed to https
)
http://web.archive.org
doesn't work for me so that probably should be fixed else someone will try to re-add the archive-snapshot-of-an-archive-snapshot WebCite url.
This search found two other archive-snapshot-of-an-archive-snapshot WebCite urls which should probably be fixed. I don't see a need to fix the module to support archive-snapshot-of-an-archive-snapshot urls.I was going to fix the articles in Category:CS1 maint: date format, but then I thought that replacing hyphens by dashes in parameters that the template is already automatically identifying sounds like something a bot should be doing; hence my questions:
Joriki ( talk) 11:06, 22 August 2023 (UTC)
Just a heads-up on some changes I envision to
Module:CS1 translator to add support for
fr:Template:Chapitre. After expansion, typical French usage is very similar to an en-wiki {{
cite book}} template that contains a |chapter=
param, so my approach has been to take advantage of the existing _cite_fr function, as we don't have a separate, {{
cite chapter}} template, and we won't need a new function in the module to handle it because it's so close to cite book.
This is a very common citation template on fr-wiki and my current activity here results from a real-world problem based on my intention to translate fr:Manifestations de ménagères, in which about half of the items in the "Bibliographie" section use the "Chapitre" template. I've put that translation aside for the moment, while looking at this module.
I'm still in the middle of it, but here is roughly the current status (tl;dr: working. except for one bug not yet looked at, but more test cases needed):
This is my first attempt at Lua coding, so it's a bit slow, and I may be making dumb mistakes, or coding inefficiently, or not aligning properly with existing data structures or the original design for which I beg pardon and ask for indulgence, but I am making progress. I believe I have a working version for dealing with the unknown param |pages totales=
that passes my current test cases (but more are needed), and almost everything in the Chapitre template is being translated correctly. There is one notable exception that I have not looked at yet, which is that it flags "Unknown parameter |titre chapitre= ignored". Thanks,
Mathglot (
talk) 11:38, 24 August 2023 (UTC)
{{
cite chapter/French/sandbox}}
) includes {{
Subst only|auto=yes}}
, substing is handled by AnomieBOT usually within the hour. To prevent AnomieBOT from substing, you can add a {{
nobots}}
template to the ~/testcases page. That done, test cases are written like this:
{{Cite chapter/French/sandbox |auteur=Jean-François Condette |titre chapitre=Les manifestations de ménagères dans le département du Nord de 1940 à 1944 : Révolte frumentaire ou résistance ? |auteurs ouvrage=Robert Vandenbussche (dir.) |titre ouvrage=Femmes et Résistance en Belgique et en zone interdite |lieu=Lille |éditeur=Publications de l’Institut de recherches historiques du Septentrion |collection=Histoire et littérature du Septentrion (IRHiS) |numéro dans collection=38 |année=2007 |pages totales=247 |isbn=978-2-490296-12-5 |lire en ligne=http://books.openedition.org/irhis/2189 |consulté le=2023-07-13 |passage=125–164}}
{{cite book/subst |access-date=2023-07-13 |author=Jean-François Condette |chapter=Les manifestations de ménagères dans le département du Nord de 1940 à 1944 : Révolte frumentaire ou résistance ? |date=2007 |isbn=978-2-490296-12-5 |location=Lille |page=125–164 <!--pages totales=247--> |publisher=Publications de l’Institut de recherches historiques du Septentrion |series=38 |series=Histoire et littérature du Septentrion (IRHiS) |title=Femmes et Résistance en Belgique et en zone interdite |url=http://books.openedition.org/irhis/2189 |veditors=((Robert Vandenbussche (dir.)))}}
{{
Bots}}
template to prevent the above from being subst'd.|veditors=
as a translation of |auteurs ouvrage=
. That may violate
WP:CITEVAR for templates that use |nom=
, |postnom=
, |prenom=
, |prénom=
because those |last=
/ |first=
parameters will render in Vancouver Style when they should not.|series=38
and |series=Histoire et littérature du Septentrion (IRHiS)
which does not get flagged by MediaWiki and is not caught by
Module:CS1 translator when rendering the citation. I suspect that this is because at
line 609 we don't look for out_t[param]
already present in out_t
. That should be fixed. Still, in your translation, you should probably concatenate |collection=
and |numéro dans collection=
in some way before assigning the result to |series=
.|pages=12–14
and |pages totales=355
into |pages=12–14 <!--pages totales=355-->
lives hard-coded in function _cite_fr and was kind of proof-of-concept to see if I could do it; but the intention all along, was to generalize it into a new function that would examine a predefined table of param pairs relating one French/foreign param with no cs1|2 equivalent (like |pages totales=
) as k, to a 'nearest cs1|2 target' (if there is one) as v, and concatenate the former to the latter as hidden text; the table probably to live as an extension to /data which would define these relationships as k-v pairs relating the foreign-param to en-param (and multiple k's pointing to the same v would not be a problem). Anyway, the point being that I agree, but I don't know if I'll get to it in my first version, this being already at the limit of my Lua ability, but I think users are used to occasionally imperfect translations that might miss one thing here or there while still generating an essentially correct citation and are hugely useful timesavers, and I think that users can deal with the series/collection problem for now, and will be well-served by something that can translate {{
Chapitre}} 95% perfectly, rather than not handle it at all and have to slog through it the long way, the way they do now. Maybe what I can do for now, is combine |series=
and |collection=
with the "brute force" method I used for |pages totales=
, and the obvious parallelism between the two cases will point the way to a better, more generalized solution next iteration. Thanks very much for the feedback!
Mathglot (
talk) 20:09, 24 August 2023 (UTC)
|editor=
still exists (although not |editors=
, which would've been ideal here). In any case, this works: |editor=((Robert Vandenbussche (dir.), John Smith, Mary Doe))
, so I'll make this change to the sandbox. Probably not ideal, but still one click better than |veditors=
.
Mathglot (
talk) 20:50, 24 August 2023 (UTC)
|pages totales=
pass through so that the editor knows that it's there and can decide what to do with that information. Hiding the parameter in html comment markup makes it likely that the editor won't know that its there especially those editors who use that abomination that is ve. Similarly, don't mask the maintenance message that will occur with a comma separated list of editor names. Most editors won't see that because maint messaging is hidden by default but masking with accept-as-written markup hides the issue from gnome editors who would otherwise separate the list into individual parameters as should be done.|trans-title=
right after the |title=
, so I remember to fill it in later. I like url last, or almost last, others like it closer to the front, and so on.I understand this was just rolled out in the recent update, but can this somehow be downgraded to a maintenance message from error status? It honestly doesn't seem like such a big problem that it requires red error text. For archives that support generating this mismatch, couldn't the template be coded to display the archive date by parsing
Folly Mox (
talk) 09:32, 13 August 2023 (UTC) Secondary suggestion struck 16:22, 13 August 2023 (UTC)
|archive-url=
, instead of forcing editors to fill in the parameter manually, risking typos?
{{use xxx dates}}
template. That template is not visible when section editing so the 'suggested date would necessarily be in YYYY-MM-DD format. This same might be applied to templates with |archive-url=
but missing |archive-date=
but only for those archive urls that include a YYYYMMDDhhmmss timestamp (currently archive.org and archive.today).I'd like the module to do the work for me of adding the date.Templates/modules cannot modify wikitext so adding
|archive-date=
and its value is on you.We could add a suggested date in the article-preferred format only when the module can see the {{use xxx dates}}
template.
I was thinking also of |df=
.Frankly, I don't thinkWe should go the extra mile. It's probably not too much work once you have the date in the message.
I don't know what you meanA bit literalist of an interpretation on your part. You know I'm quite aware of what templates and modules can do. :) Izno ( talk) 15:47, 26 August 2023 (UTC)
it is not possible for the module to do the work for youIs there a reason it can't detect an archive.org/archive.today link, parse the date and output/override the
|archive-date=
if there is a mismatch (I'd actually think we should deprecate/make optional |archive-date=
for these two archive sources)? No need to change wikitext or emit an error, just add it to a maintenance category so it can be cleaned up with other more serious issues by bot. —
Locke Cole •
t •
c 20:38, 27 August 2023 (UTC)
|archive-date=
value in error message. Suggested date is formatted according to |df=
or {{use xxx dates}}
or YYYY-MM-DD in that order.
{{cite book/new |title=Title |url=//example.com |archive-url=https://web.archive.org/20230827081416/https://example.com |archive-date=August 26, 2023|df=dmy-all}}
{{
cite book}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 27 August 2023 suggested (
help){{cite book/new |title=Title |url=//example.com |archive-url=https://web.archive.org/20230827081416/https://example.com |archive-date=August 26, 2023|df=dmy}}
{{
cite book}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 2023-08-27 suggested (
help)|df=
or {{use xxx dates}}
or YYYY-MM-DD, the module extracts the format used in |archive-date=
and uses that format in the absence of |df=
or {{use xxx dates}}
.|df=dmy
. That parameter value tells the date-reformatter to leave |access-date=
and |archive-date=
formats as they are. The suggested date for the error message is YYYY-MM-DD before the format specified in |df=
is applied. Because |df=dmy
instructs the module to ignore |archive-date=
(which this date is) the message renders as YYYY-MM-DD. I suspect that this is generally acceptable because YYYY-MM-DD is the common and usual format when |access-date=
and |archive-date=
have a different format from the publication dates.Is there any script that allows one to reorder CS1 reference parameters on a page into some sort of standardized order? {{u| Sdkb}} talk 04:23, 14 August 2023 (UTC)
paramOrder
(kudos @
Stjn and @
AntiCompositeNumber for reminding me). So the cat is already out of the bag in that sense. {{u|
Sdkb}}
talk 15:22, 17 August 2023 (UTC)
{{cite work |parameter1=value1 |parameter2=value2}}
as the most readable for the predominant (inline) use case.
Izno (
talk) 19:49, 26 August 2023 (UTC)( ←) I also prefer parameters to be in the order of display. This ultimately supports the bibliography comment above. If there's a script that reorders things this way, so long as it's in the context of a major edit, I see no issue. Izno ( talk) 19:49, 26 August 2023 (UTC)
Why does this produce an error? Found in Typhoon Nanmadol (2022), there are probably others.
-- Green C 18:36, 24 August 2023 (UTC)
|archive-date=
. The template uses whatever is in |date=
to populate |access-date=
and |archive-date=
. The latter appears to not be reliant on |archive-url=
existing to be populated. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 19:02, 24 August 2023 (UTC)
|archive-url=
is required if |date=
is provided. I have added that requirement to the documentation. –
Jonesey95 (
talk) 19:07, 24 August 2023 (UTC)
{{
Cite PAGASA}}
which can have a |date=
and no |archive-url=
. It looks like an unintentional feature maybe added by accident:
|archive-date=
to each one, I'd be OK with fixing the template so that |date=
is used as it should be and not "triple-counted". I recommend that this whole discussion be moved from here to the template's talk page. –
Jonesey95 (
talk) 22:38, 24 August 2023 (UTC)
|archive-url=
field to store non-
web archive URLs which of course have no archive date since they are not archive URLs. This was a problem because CS1|2 was throwing a red error when there is an |archive-url=
but missing |archive-date=
. So they generated a default "dummy date" to stop the errors (based on the value of the |date=
field). Then recently we added this new tracking category that caught the mismatch of the dates and so on. Then it all became clear. I removed the default |archive-date=
from the template, and am currently processing all instances of this template, moving the |archive-url=
to outside the template (when not a valid archive URL) .. it's really a second citation. --
Green
C 16:43, 28 August 2023 (UTC)
I've started putting subtitles for multi-volume books in the volume field rather than in the more traditional title field because I think it's easier for the reader to understand exactly that exact volume covers. Forex title=German Warships 1815–1945: U-boats and Mine Warfare Vessels|vol=Two versus title=German Warships 1815–1945|vol=Two: U-boats and Mine Warfare Vessels. The first example could easily be understood as the second volume of a book devoted to U-boats and Mine Warfare Vessels within a larger work covering German warships while the second example makes it much clearer that volume 2 of German Warships covers only U-boats and Mine Warfare Vessels, IMO.
Currently the documentation for the volume field only covers numbers, not actual text. I would like to make adding a subtitle in addition to the number a valid option. This may raise the hackles of professional catalogers, but I believe that the extra clarity is worth making this change, especially since we're not strictly bound by MARC standards. Thoughts, comments? Sturmvogel 66 ( talk) 15:08, 25 August 2023 (UTC)
|volume=
parameter is lost to those readers.
{{cite book |title=Title |volume=Some sort of subtitle}}
'"`UNIQ--templatestyles-0000009A-QINU`"'<cite class="citation book cs1 cs1-prop-long-vol">''Title''. Vol. Some sort of subtitle.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Title&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1%2FArchive+89" class="Z3988"></span>
&rft.volume=Some sort of subtitle
.{{cite book}}
template has any of these parameters:
|type=
|series=
|language=
|title=
and |volume=
which visually disconnects the subtitle from the title.
{{cite book |title=Title |type=Type |series=Series |language=nv |volume=Some sort of subtitle}}
|volume-title=
in the deeper archives, but I vaguely recall a more recent thought on it.
Izno (
talk) 22:08, 25 August 2023 (UTC)
|volume-title=
makes sense, but only if we are not supposed to place the title in |volume=
(which seems easier). Thanks,
Mr.choppers |
✎ 14:38, 26 August 2023 (UTC)
I propose three parameters be added to this template.
The purpose of this parameter would be as follows: Wikipedia has reasonably significant issues regarding the verifiability and reliability of information on this site. The 'verified' field provides two things; (1) it gives readers a degree of confidence in a citation without having to click through, (2) it gives editors the ability to identify citations that are worth checking.
Adding these parameters would allow Wikipedians to trawl through the citations on this site and verify them.
Wikipedians already engage in the verification of citations, however it is often unclear whether a citation has already been checked by another editor or not. Adding this parameter would make it easier for editors to focus on citations / claims that haven't yet been checked, substantially increasing the productivity of site editors.
What do my fellow editors think of this proposal?
Kind regards Jack4576 ( talk) 10:08, 26 August 2023 (UTC)
Ultimately editors who are concerned about the referencing ... should verify the details themselvesAgree Folly Mox ( talk) 19:20, 26 August 2023 (UTC)
|name=
parameter of <ref>
.
Kanguole 17:08, 26 August 2023 (UTC)
In addition, many Wikipedia editors are not very rigorous about what they use citationsRight. See: Fire basket, currently linked from the main page. This would presumably have "verified" citations in those boolean yes/no parameter slots, which without additional context would be misleading, Rjjiii ( talk) 06:24, 27 August 2023 (UTC)
The beacon atop the Altenburg castle in Bamberg served to communication with the neighboring Giechburg castle.Rjjiii ( talk) 03:22, 28 August 2023 (UTC)
I agree that that anything we can do to improve the integrity of our sourcing is a good thing, but it's a mug's game when any editor can alter the text without changing the sourcing accordingly and only those who have that article on their watchlist are likely to notice or even care. And that doesn't even take into account the scale of the issue with FA-quality articles often having over a hundred cites. Admittedly, the quantity of cites sharply declines in most of the rest of the articles on Wiki, but stretched over 7-odd million articles that's still a number that no volunteer group like ours can handle. I applaud anyone who actually enjoys verifying cites, but I much prefer generating them from the books and journals spread out in front of me and on my monitors.-- Sturmvogel 66 ( talk) 15:55, 28 August 2023 (UTC)
I ran into a false positive for the "multiple names: authors list" error for the name "Fernando Alfonso III". My understanding (supported by this archived topic) was we put the Jr./Sr./III/etc. into |first= in the cite templates, like "|first1=Fernando, III last1=Alfonso". The reference to MOS:JR on Template:Cite web/doc is confusing, though, because that seems to apply specifically to body text and not reference parameters.
{{
cite news}}
: CS1 maint: multiple names: authors list (
link)My suggestions:
Thanks.- Ich ( talk) 11:20, 29 August 2023 (UTC)
When the surname is shown first, the suffix follows the given name. It then goes on to say
Do not place a comma before a Roman numeral name suffix. Jr, Sr, III are suffixes all explicitly mentioned as suffixes in MOSJR.
Kennedy, John F. Jr.of how Jr and Sr should be used in a listing, but the example
Otis D. Wright IIdoesn't make clear how the name should look in a listing with a Roman numeral suffix. I've seen many "Wright II, Otis D." examples in articles, so something isn't clear enough. -- LCU ActivelyDisinterested ∆ transmissions∆ ° co-ords° 14:58, 29 August 2023 (UTC)
|first1=Fernando III
(without the comma) the correct format. If you believe that the cs1|2 documentation can be improved, please do so. If you believe that
MOS:JR should be constrained to body-text only, discuss at
WT:MOSBIO.This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 85 | ← | Archive 87 | Archive 88 | Archive 89 | Archive 90 | Archive 91 | → | Archive 94 |
I've just cleaned up a few articles where the author field ended with "(View posts)" ( sample diff) -- John of Reading ( talk) 09:26, 13 July 2023 (UTC)
Since there is a parameter for "translated title", and there is a parameter for "quote", I suggest a parameter for "translated quote". Currently I tend to write a translation of the quote in brackets after the quote, but this is probably not optimal, since the source itself is not the source of the translation (just as we usually cannot attribute a "translated title" to the source). Thiagovscoelho ( talk) 12:26, 13 July 2023 (UTC)
|trans-quote=
.|quote=
to give a fuller version of a quotation from the article itself, and sometimes it was to make clear how a source supported a claim, since it was a large webpage source and I can't give page numbers.
Thiagovscoelho (
talk) 13:30, 13 July 2023 (UTC)Hello. I frankly have no idea if this is the appropriate venue for this.
Istro-Romanian is one of the Balkan Romance languages. The others are Romanian, Aromanian and Megleno-Romanian. Adding a parameter |language=ro/rup/ruq
in a citation template will produce (in Romanian/Aromanian/Megleno-Romanian)
, but |language=ruo
does not produce (in Istro-Romanian)
. An example is reference 50 at
Istro-Romanians. I fixed it manually with |version=
but I don't see why Istro-Romanian should be excluded from Wikipedia's technical code, or whatever the root of this is. Note that there is already
Template:Lang-ruo so it's not a problem of "ruo" or of the language not being integrated anywhere within Wikipedia's code.
Can this be fixed? Super Dromaeosaurus ( talk) 20:17, 16 July 2023 (UTC)
Can "staff" be added to generic author names? There are 63 articles citing "Staff, Ars". 93.72.49.123 ( talk) 06:39, 20 July 2023 (UTC)
If I put this in the 'issue' field, it renders as "No. Spring 2022" which doesn't really seem correct. But it doesn't really seem like it should be in the date field like that either. – jacobolus (t) 15:49, 20 July 2023 (UTC)
I'm wondering whether it would make sense to show an error when a date of 1 January 1970 (the Unix epoch) is supplied. Of course there would be false positives, but from a quick search most articles appear to be using this date in error. 93.72.49.123 ( talk) 06:46, 20 July 2023 (UTC)
I fix a lot of script-generated citations, and about once every twenty or thirty, I'll end up duplicating a parameter that was actually already included but I didn't notice, causing the page to be added to
Category:Articles using duplicate arguments in template calls and creating additional work as other editors
User:Davemck and
User:Ira Leviton clean up after me.
Is there a way for this to generate a warning message / for me to enable display of a warning message that is already generated? I am sometimes able to notice the category being added to the page on preview, but this typically only displays if I'm editing the full page rather than just a section, which accounts for maybe 5% of my edits. Folly Mox ( talk) 13:14, 21 July 2023 (UTC)
{{cite book |title=Title1 |title=Title2}}
Is this the expected behavior? Rjjiii ( talk) 00:43, 12 July 2023 (UTC)
{{
cite web}}
: Check date values in: |access-date=
(
help){{
cite web}}
: Check date values in: |access-date=
(
help){{
cite web}}
: Check date values in: |access-date=
(
help)After adding references to Grand Sanhedrin, I noticed that Template:Cite journal creates somewhat obscure and (in my opinino) inaccessible output:
> Niles, H. (12 June 1830). "The Jews". Niles' Weekly Register. 38: 296.
The number 38 represents the "Volume" and "296" presentes the page number. In other citation templates, we state the page number after "pp.", such as when using Template:Cite book. I think applying this to journal citations would make it significantly easier for readers to find the facts in the source, and thus to help them read the surrounding information. This especially because the URLs tend to go to a place for the work as a whole, which places a heavy burden on understanding that 1) the page number is in fact given, and 2) which number is what.
Perhaps less importantly than the page numer is the volume. This because each volume tends to be its own work and thus its own ISBN and/or online entry page. This means the volume number isn't required for navigation within the work. Having said that, I wouldn't mind spelling that out as "Volume 38".
Would these changes be welcomed? What other ways might there be to address the usability issue? Or perhaps there exists documentation we expect people to find that explains this?
Krinkle ( talk) 23:37, 12 July 2023 (UTC)
With the move, the error messages and maint notices still point to cite techreport. Chandrasekhar Boyapati, William Beebee, Jr., Martin Rinard. A (Technical report).{{
cite tech report}}
: CS1 maint: multiple names: authors list (
link) (Technical report). {{
cite tech report}}
: Missing or empty |title=
(
help)
AManWithNoPlan (
talk) 16:26, 25 July 2023 (UTC)
{{cite tech report/new | title=A |author1=Chandrasekhar Boyapati, William Beebee, Jr., Martin Rinard }}
{{
cite tech report}}
: CS1 maint: multiple names: authors list (
link){{cite tech report/new | title=}}
{{
cite tech report}}
: Missing or empty |title=
(
help){{
Cite arXiv}}
, {{
Cite bioRxiv}}
, {{
Cite CiteSeerX}}
, and {{
Cite medRxiv}}
.For {{cite news}} or {{cite web}}, what parameter should be used to add a translation link to the original article (written in a foreign language) when both the URL and archive-URL have already been utilized? I don't see a translation-url or anything similar. Thank you.-- TerryAlex ( talk) 17:59, 25 July 2023 (UTC)
|translation-url=
parameter.|url=
to link to it if it is available online. You might include |type=Translation
. If you are citing the original-language source, cite that and use |url=
to link to it if it is available online. In either case, you can always add an external wikilink to the 'other' (translated or original-language source) after the closing braces of the {{cite <whatever>}}
template.{{cite news|url=www.abc.com/newsarticle.html|archive-url=web.archive.org/20230724091214/www.abc.com/newsarticle.html|title=News Article|work=ABC|date=March 23, 2021|archive-date=July 24, 2023|access-date=July 24, 2023|language=foreign|url-status=live}}
. Thanks.--
TerryAlex (
talk) 20:32, 25 July 2023 (UTC)
|at=
parameter and format it like this {{cite news|url=https://www.abc.com/newsarticle.html|archive-url=https://web.archive.org/20230724091214/www.abc.com/newsarticle.html|title=News Article|work=ABC|date=March 23, 2021|archive-date=July 24, 2023|access-date=July 24, 2023|language=foreign|url-status=live|at=https://web.archive.org/20230725112323/www.translation.com/translationpage.html English Translation]}}
It yields no error and the citation shows up looking properly. Is this a good way to do it or does it violate the citation format in any ways? Thanks.--
TerryAlex (
talk) 00:05, 26 July 2023 (UTC)
|at=
will corrupt the citation's metadata. What I meant in my first post was something like this:
<ref>{{cite news |url=https://www.abc.com/newsarticle.html |title=News Article |work=ABC |date=March 23, 2021 |access-date=July 24, 2023 |language=und}} https://www.translation.com/translationpage.html English Translation]</ref>
I want to reference a single video but different timestamps, ideally using SFN style where that uses page numbers, is there a way of doing this for time stamps? Darkwarriorblake ( talk) 16:03, 26 July 2023 (UTC)
{{
sfn}}
parameter |loc=
not do what you want?How about [1] this [2] or this? [3] – Jonesey95 ( talk) 01:09, 27 July 2023 (UTC)
References
{{cite book|last1=Hiriart-Urruty|first1=Jean-Baptiste|last2=Lemaréchal|first2=Claude|author-link2=Claude Lemaréchal|year=1993|chapter=XII Abstract duality for practitioners|title=Convex analysis and minimization algorithms, Volume II: Advanced theory and bundle methods|series=Grundlehren der Mathematischen Wissenschaften |trans-series=Fundamental Principles of Mathematical Sciences|volume=306|publisher=Springer-Verlag |location=Berlin |pages=136–193 (and bibliographical comments on pp. 334–335)|isbn=3-540-56852-2 |mr=1295240}}
{{
cite book}}
: Unknown parameter |trans-series=
ignored (
help)Headbomb { t · c · p · b} 15:05, 2 July 2023 (UTC)
For consistency with the other format categories (Bibcode, MR, PMC). Headbomb { t · c · p · b} 04:04, 7 July 2023 (UTC)
|mr=MR1234567
or |pmc=PMC12345
when they should have written |mr=1234567
or |pmc=12345
.
Category:CS1 maint: Zbl exists to catch cases where the specified identifier is temporary so that editors can come back later and provide the permanent identifier.maint_bibcode
isn't defined in the
Module:Citation/CS1/Configuration error_conditions
table — that's why the category page is showing "Pages with this condition are automatically placed in unknown error_conditions key: maint_bibcode." instead of its own name.
FeRDNYC (
talk) 17:28, 13 July 2023 (UTC)
This morning, I tried repeatedly without success, first to archive on the WayBack Machine, then secondly to cite the two relevant webpages of the meeting on 19 July 2023 of the House of Commons Business and Trade Select Committee (1,2). The WayBack Machine failed to archive the two relevant Committee webpage. Using the easy citation tool in Wikipedias's Visual Editor, I was unable to cite either webpage of the Committee. Hence, I now need to cite the two webpages using the Wikipedia generic default of {WebCite}. I'm not sure what citation protocol best to follow. I've tried without success to look up the APA guidelines for citing committee meetings and committee reports. In my view, it would be helpful to have wikipedia citation templates specifically for citing committee meetings and citing committee reports.
[2] https://committees.parliament.uk/event/19035/formal-meeting-oral-evidence-session/
Humanity Dick ( talk) 11:59, 24 July 2023 (UTC)
{{cite web |author=((Business and Trade Committee)) |date=19 July 2023 |title=Food and fuel price inflation: will prices come down this year? |website=UK Parliament |url=https://committees.parliament.uk/work/7774/food-and-fuel-price-inflation-will-prices-come-down-this-year}}
{{cite web |author=((Business and Trade Committee)) |date=19 July 2023 |title=Food and fuel price inflation: will prices come down this year? - Oral evidence |website=UK Parliament |url=https://committees.parliament.uk/event/19035/formal-meeting-oral-evidence-session/}}
{{
cbignore}}
otherwise IABot will remove it (c.f.
T321146)--
Green
C 14:21, 24 July 2023 (UTC)
This gives an overview of various citation tools out there. I figured many of you would get something out of this. Headbomb { t · c · p · b} 05:52, 1 August 2023 (UTC)
URLs get embedded in various places of the template which makes link rot repair difficult to manage for bots and scripts. Typically they are skipped. For example
Help_talk:Citation_Style_1#Documentation_needed_for_linking_multiple_urls_within_the_'pages'_parameter shows the free-form nature of how we do it. Another way is more systematically like we do for |author=
+ |author-link=
separating the metadata from the link.
It would be |page1=
("page=42") + |page1-url=
with perhaps support for up to 5 or 10 pages. Note |page=
would be an alias for |page1=
.
For page ranges use |pages1=42-44
(display: "pages=42-44") + |pages1a-url=
+ |pages1b-url=
where "a" is for 42 and "b" for 44. More page ranges can be added for example |pages2=47-50
(display: "pages=42-44, 47-50") + |pages2a-url=
+ |pages2b-url=
. This way one can have a mix of single page and page ranges, all with their own URLs, contained in parameters. --
Green
C 16:03, 10 July 2023 (UTC)
|page*=
parameters, but I definitely recognize that there are times when only linking to a single location risks leaving the user fumbling around to figure out how they can reach the rest of the content being cited.|page=
, alongside a more generic |url=
linking to the source as a whole. ...I was also under the impression that was incorrect: the |url=
parameter should simply hold the link from |page=
, shouldn't it?|title-link=
. When that is done, and there is no named |contribution=
within the book to cite, the only way to provide a convenience link for specific content within the book (and the way that has been repeatedly recommended) is to put the link into the page or pages parameter. —
David Eppstein (
talk) 20:26, 13 July 2023 (UTC)
|section-url=
will do what you need. Normally I use both links unless the relevant text is on the first page of the section. --
Shmuel (Seymour J.) Metz Username:Chatul (
talk) 21:17, 13 July 2023 (UTC)|title-link=
and |url=
interact with each other. (Or more to the point, that they don't, and result in a CS1 error when used in the same citation.)|pageN-url=
scheme like
GreenC is proposing.
FeRDNYC (
talk) 02:45, 15 July 2023 (UTC)
Markup |
|
---|---|
Renders as | Bloggs, Joe; Smith, John; Smythe, Jim. 1000 Acres (2nd ed.). |
|title-link=
instead of piping? I'll
be bold and fix it (plus any others), if we agree |title-link=
is always preferable now. I feel like the documentation should demonstrate best current practices, not outdated ones. (And we wonder how editors pick up / retain bad habits?)
FeRDNYC (
talk) 05:06, 15 July 2023 (UTC)
|title=
to |title-link=
could go a long way. And/or, a feature request to Citation bot (if it doesn't already have). --
Green
C 01:33, 17 July 2023 (UTC)
|title-link=
and |url=
should not be used together.
FeRDNYC (
talk) 11:11, 22 July 2023 (UTC)
|page1-url=
and |page1-archive-url=
and |page1-archive-date=
fields for every individual page?
Mr.choppers |
✎ 16:35, 2 August 2023 (UTC)
I'm trying to {{ Cite news}} an article that is republished from another work and the original work is attributed in the article. The original article is paywalled so I want to cite the freely available copy.
Kelly Smith, Star Tribune staff writer. Republished same day with no changes to Inforum. Should I say via=Inforum? And for work say Star Tribune? Or work=Inforum and agency=Star Tribune? Pingnova ( talk) 18:29, 2 August 2023 (UTC)
'^[^1-5]%d%d%d%d$', -- 5 digits without subcode (0xxxx, 60000+); accepts: 10000–59999 needs to now be 1-6 instead of 1-5 since doi: 10.60082/2817-5069.2017 exists. AManWithNoPlan ( talk) 00:39, 27 July 2023 (UTC)
Wikitext | {{cite journal
|
---|---|
Live | "Title". Journal. doi: 10.60082/2817-5069.2017. |
Sandbox | "Title". Journal. doi: 10.60082/2817-5069.2017. |
Shouldn't {{
Cite report}} wrap the output of |title=
in quotes? Its
TemplateData says it should, at least. –
MJL
‐Talk‐
☖ 17:32, 3 August 2023 (UTC)
|journal=
parameter. For example:example
|
---|
{{cite report |last1=Baumer |first1=Matt |last2=Kephart |first2=Curtis |title=Aggregate dynamics in a large virtual economy: Prices and real activity in Team Fortress 2 |id={{hdl|10419/125549}} |publisher=University of California, Economics Department |location=Santa Cruz |type=Working Paper |year=2015 |language=en}} to output: |
|id=
parameter since it's more-or-less redundant.{{cite document}}
would suite that reference:
{{cite document/new |last1=Baumer |first1=Matt |last2=Kephart |first2=Curtis |title=Aggregate dynamics in a large virtual economy: Prices and real activity in Team Fortress 2 |id={{hdl|10419/125549}} |publisher=University of California, Economics Department |location=Santa Cruz |type=Working Paper |year=2015 |language=en}}
{{cite document}}
.One of the citations on this page shows an error message when the SSRN value that the citation bot added is correct and greater than 4500000. Achmad Rachmani ( talk) 07:37, 7 August 2023 (UTC)
Wikipedia articles on illustrated books -- especially children's books -- could really use an "illustrator" parameter, to go along with (for example) "editor." Jhlechner ( talk) 15:52, 8 August 2023 (UTC)
|others=
parameter for this, |others=Illustrated by John Smith
for example. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 16:00, 8 August 2023 (UTC)Hello, can you add "Facebook" as a generic title. Currently, 859 instances. Keith D ( talk) 22:00, 9 August 2023 (UTC)
I know that ReFill works such that <ref>https://example.com/whatever</ref> gets converted into a properly formatted cite template with the correct metadata. Does there exist anything that does this for ISBNs? I just noticed that I am probably wasting a lot of time typing in book citation information when there's already a gigantic unified metadata tracking system that is based on ISBNs. jp× g 23:40, 11 August 2023 (UTC)
{{
cite book}}
: Missing or empty |title=
(
help)So, on TRAPPIST-1 we use the Template:Cite Gaia EDR3 (a wrapper for a {{ cite journal}}) and we also need to add {{ sfn whitelist}} because otherwise it throws sfn errors. Is there a way to fix the {{ Cite Gaia EDR3}} template so that we don't need to hide bogus harv errors? Jo-Jo Eumerus ( talk) 05:38, 12 August 2023 (UTC)
The current " Archived from the original on YYYY-MM-DD" phrasing at the end of many citations takes a pretty significant amount of space, especially since we now have bots indiscriminately adding these pre-emptive archive links to every citation. Is there any way we could cut that down to just " Archived YYYY-MM-DD" or the like? (If it were up to me we would entirely leave off archive links for still-living pages, as these typically have no direct benefit to readers.) – jacobolus (t) 17:57, 31 July 2023 (UTC)
from the originalwhere
url-status=live
(where else would it be archived from?). I'd also support suppressing display of |access-date=
where an |archive-date=
is present and url-status=dead
, since if the link is dead and there's an archive, there's no point. Ditto for |access-date=
for all {{
cite book}} and {{
cite journal}}, since if they've gone to print there won't be an update to the information.
Folly Mox (
talk) 20:03, 31 July 2023 (UTC)
|access-date=
parameters by bot seems disruptive and annoying. Probably easier just to suppress display in cases where it's of no use to readers, only editors tryna repair an archive.
Folly Mox (
talk) 08:46, 1 August 2023 (UTC)
|access-date=
looks like this:
<span class="reference-accessdate">. Retrieved <span class="nowrap">2023-08-01</span></span>
not all webpages are static documents. Even in the case of an archive, I'd like to know when that page was accessed.But, archives are static documents — even if the page changes over time, the archive won't. It's a snapshot of a particular moment, and the date of that snapshot "trumps" the access date... no matter when the archive was accessed, the version they got is the one archived on the date indicated. An
|archive-date=
(and |url-status=dead
) makes the access date completely irrelevant.
FeRDNYC (
talk) 02:01, 16 August 2023 (UTC)
|access-date=
if the archived page has been checked and the content matches.
Mr.choppers |
✎ 16:17, 2 August 2023 (UTC)
|access-date=
as possible, ideally.) But if someone submits an |archive-url=
with a citation (I try to do so, if I think it's likely to vanish at some point), I'd certainly expect it not to be an archive created after that point!
FeRDNYC (
talk) 02:07, 16 August 2023 (UTC)
not as thoughtful, and do not provide archives at the time of edit– personally I submit pages to be saved by the internet archive but then intentionally ("thoughtfully") do not include the archive link on the page (or sometimes even remove archive links that were added by the IA bot), because to me the proliferation of archive links for still living pages seems like a space-wasting spammy distraction. – jacobolus (t) 05:01, 16 August 2023 (UTC)
/info/en/?search=Wikipedia:ISSN includes "An ISSN is particularly helpful in the following circumstances" which include "In a citation to an article that is not available online except behind a WP:PAYWALL" and "In a citation to an article that is not available online in full text". How are they helpful in those circumstances? When I've seen paywalled articles cited I've sought/created archived versions. Should I also add ISSNs? To date I've only noticed an ISSN of one Wall Street Journal article. Mcljlm ( talk) 18:42, 12 August 2023 (UTC)
Personally, my experience is that, because ISSNs are for publications rather than for individual articles, they're much less helpful than e.g. DOIs, and they're often overused because VisualEditor's citation tool seems to like them. Basically, all you really want to have is at least one identifier in each citation. That could be a URL, or a DOI, or an OCLC, or an ISSN, but just plain text is non-preferable. And all of this only matters if you're trying to get an article's references to a featured-quality level. Hope that helps! Cheers, {{u| Sdkb}} talk 18:12, 12 August 2023 (UTC)
|language=en
for citations on the English language Wikipedia is my favourite totally unnecessary automated reference add, which I'll usually delete when cleaning up other people's work to add page numbers etc.From what I understand, the Foundation has a single contractor responsible for all of Citoid, who is currently tasked with integrating it into Wikidata for some reason instead of fixing any of its issues.
Folly Mox (
talk) 21:52, 12 August 2023 (UTC)
|language=
parameter is very valuable, but it doesn't display anything when it matches the language of the project it's being used in. Aren't people checking the references whenever they translate articles? I'd think that they'd be able to fill out the language parameter manually during that process. It's hardly a blip of effort when the overall time investment of translation is taken into account.
Folly Mox (
talk) 02:22, 13 August 2023 (UTC)
Thanks everybody, especially Sdkb for suggesting I asked here. Until reading the responses above I assumed I was missing something significant about their use. Maybe I should delete the ISSN from the WSJ citation. Mcljlm ( talk) 23:38, 12 August 2023 (UTC)
|language=en
, except for multi-lingual pages, e.g. |language=de,en,fr
. --
Michael Bednarek (
talk) 01:53, 13 August 2023 (UTC)
Coincidentally, I had just yesterday gone through every entry on Bibliography of works on Davy Crockett to tidy up references, etc. Looked great yesterday. Imagine my surprise when I opened that list today and found red messages on numerous cite book entries such as "{{ cite book}}: Cite has empty unknown parameter: |1= (help)" Etc. etc. It looked perfect yesterday. Whatever it is, also affected the drop-down cite book template - in that if you had an ISBN number, you would put it in the template and click on that little magnifying glass to the right of it, it would fill out the rest of the template. Now it just sits there and does nothing if you try that. So, I've been randomly going through other lists and it seems that only the cite book template triggers that. What happened between yesterday and today that affected the cite book template? — Maile ( talk) 01:49, 13 August 2023 (UTC)
{{
cite book}}
: Empty citation (
help): |website= ignored (help)" "22:01, August 13, 2023 Citation bot talk contribs block 3,818 bytes −24 Alter: template type, url. URLs might have been anonymized. Add: date, newspaper, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Eastmain | #UCB_webform 25/30 "
— Maile (
talk) 03:14, 14 August 2023 (UTC)I have encountered a problem in Elias Lönnrot: two references using {{ SLS Q}} yield a maintenance error message: "location missing publisher" but the Wikidata items ( Swedish Writings volume 1 (Q113396160) and Swedish Writings volume 2 (Q113396181)) have both publisher (P123) and place of publication (P291).-- Carnby ( talk) 11:56, 13 August 2023 (UTC)
|publisher=unset
, which is going to block an publisher setup on wikidata. I suggest asking the creator of the template about it. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 12:17, 13 August 2023 (UTC)
Could we add Template: namespace? For example in European Union Referendum Act 2015 there is Template:UKEU2016Result which has the error. If it was in the tracking category my bot would find it automatically. As-is I have to manually track them down. In the first 200 articles of the category, randomly sorted, there were 3 articles with templates that required a fix (1.5%) -- Green C 00:26, 14 August 2023 (UTC)
Something in the latest update is causing a page with a reference to transclude itself. This has the downside that templates that are otherwise unused, are now hidden from reports. Is this something that can be fixed? A setting that can be set to ignore on template pages? I remember a previous change a while back that also had this issue. Gonnym ( talk) 09:23, 14 August 2023 (UTC)
error()
in the namespace test that calls title_object:getContent()
(this is what counts as self transclusion). Previewing an article with the modified code showed an error for every cs1|2 template in the article (the expected result). I then previewed {{
cite Grove}}
; no errors so the module is not calling title_object:getContent()
in template namespace. Still, as I write this, in
Special:WhatLinksHere for {{cite Grove}}
, the template appears to still be transcluding itself. Is there a WhatLinksHere lag as there is for categories?year: Year of source being referenced. The usage of this parameter is discouraged; use the more flexible |date= parameter instead unless both of the following conditions are met: Currently the Citation Bot adds years for journals, etc. Should we be using date? AManWithNoPlan ( talk) 18:30, 1 August 2023 (UTC)
|date=
is most appropriate.
|year=2023
– ok because parameter name matches parameter value|year=Winter 2023
– not ok because semantic conflict|date=2023
– ok because parameter name matches parameter value|date=Winter 2023
– ok because parameter name matches parameter value|day=
and |month=
but so long as
MOS:DATES allows YYYY-MM-DD format publication dates, |year=
will be required when CITEREF
disambiguation is needed (|date=2023-08-01
|year=2023a
...)CITEREF
disambiguation then, for ease of coding, it should probably just use |date=
.|year=
. When it's a full date/date with month, use |date=
.
Headbomb {
t ·
c ·
p ·
b} 20:49, 1 August 2023 (UTC)
|date=
for either case? I see no benefit in having two types of fields for this information.
Mr.choppers |
✎ 16:09, 2 August 2023 (UTC)
CITEREF
disambiguators may make it more difficult for readers to determine which of your 1979 sources is being cited. For example, someone reading a printed copy of an en.wiki article will not be able to mouse-over the short form citation to see which one gets highlighted. The only case where |year=
is required is the one I described above. Don't hide the CITEREF
disambiguators.|year=
parameter is not necessary, when |date=1979
and |year=1979a
appear in the same cs1|2 template,
Module:Citation/CS1 emits a maintenance message and adds the article to
Category:CS1 maint: date and year.|date=
as just the year, but set |ref=
to use 2007a, 2007b etc. Is this recommended practice?
Folly Mox (
talk) 19:50, 2 August 2023 (UTC)
|date=
, because it saves you the two seconds pondering which one you ought to be using.
Mathglot (
talk) 06:48, 3 August 2023 (UTC)
|date=
fields weren't exactly dates; glad to know that isn't the case.
Folly Mox (
talk) 13:31, 3 August 2023 (UTC)Those diffs look good.I disagree. At §Notes there are three Francillon 1979 short-form references. In §Bibliography there is no Francillon 1979 and one each of Francillon 1979a and Francillon 1979b. Which of the three Francillon 1979 short-form references goes to Francillon 1979a and which goes to Francillon 1979b?
Am I right in thinking that {{ Please check ISBN}} and Category:Articles with invalid ISBNs are obsolete? (The former places articles in the latter.)
There are currently only 10 pages in that category, and all but one of them are also in Category:CS1 maint: ignored ISBN errors (which itself contains 382 pages). In the only one that isn't, Rodney Hallworth, the template marks the text "ISBN B001ALS2EY" in a hand-written book reference. The last non-minor edit on the category's talk page is from 2015; the last and only edits on the template's talk page are from 2012.
So it looks as if these have fallen out of use and been replaced by
Category:CS1 maint: ignored ISBN errors and
Category:Pages with ISBN errors (perhaps due to the switch from
magic links for ISBNs to {{
ISBN}} and isbn=
parameters), and the template is only being used sporadically. Of the 10 current cases, 9 were already being tracked elsewhere, and the remaining exceptional one could have been handled by adding the ISBN template (which should be done anyway) and then the invalid ISBN would have shown up in
Category:Pages with ISBN errors.
So it seems that this template and category should be decommissioned? Or am I overlooking a reason for keeping them? Joriki ( talk) 20:32, 17 August 2023 (UTC)
ISBN B001ALS2EYis really an ASIN so should read: 'ASIN B001ALS2EY'.
Just stumbled on a problem that you could consider tracking. Cite template having an |author-link=
parameter but no |author=
or equivalent parameter. Probably similar situation for |editor-link=
.
Keith D (
talk) 10:36, 14 August 2023 (UTC)
language=Swiss German
?There are a handful of pages that weren't listed at
Category:CS1 maint: unrecognized language yesterday (I know because I'd gone through all the pages) but are listed there now without having been edited:
The Night Game,
Satanic panic,
List of songs recorded by Owl City (I already fixed the last one). What they have in common is that they specify "Swiss German" as a language, which is apparently no longer recognized. If this is replaced by gsw
, it now displays as "Alemannic".
{{
Citation Style documentation/language/doc}} says that the 3-character code gsw
stands for "Swiss German".
Category:CS1 maint: unrecognized language says that "For recognized ISO 639-2 languages with multiple official names, MediaWiki recognizes only one." The official names for gsw
are "Swiss German", "Alemannic" and "Alsatian".
So it seems that there's been a breaking change where gsw
is now being mapped to "Alemannic" instead of "Swiss German". I wonder how we should deal with this. "Swiss German" is more specific than "Alemannic", and also more understandable to non-linguists. Everyone in Germany knows what Swiss German is, but few people know what Alemannic is or that it contains Swiss German as a subset. So it doesn't make much sense to relabel these works as "Alemannic". But keeping "Swiss German" would leave these articles in the maintenance category indefinitely. (
List of songs recorded by Owl City was fixable because the resource is actually in Swiss High German, which has its own code.)
So ideally I think this change should be reverted, but I have no idea where to request that. If it isn't, then {{ Citation Style documentation/language/doc}} needs to be updated (and that may apply to other codes as well if this was part of a broader change). Joriki ( talk) 22:11, 18 August 2023 (UTC)
{{#language}}
magic word). Some languages and tags are overridden in cs1|2.gsw
from 'Swiss German' to another English-language form 'Alemannic'.{{cite book |title=Title |language=Alemannisch}}
→ Title (in Swiss German).gsw
, this seems to confirm that, when given tag gsw
, MediaWiki used to return the English-language form: 'Swiss German'. Because there is no override for gsw
, cs1|2 also recognized 'Swiss German' as a known language.Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
Wikitext | {{cite book
|
---|---|
Live | Title (in Swiss German). |
Sandbox | Title (in Swiss German). |
gsw
would then be preferred over "Swiss German", right?
Joriki (
talk) 00:31, 19 August 2023 (UTC)
gsw
code to Swiss German, as already justified in the commit notes. Both the Ethnologue and the Glottolog recognize that Allemanic is a parent of Swiss German, and renaming it to Swiss German excludes other Allemanic languages that do not have their own MediaWiki code, such as
Swabian. Additionally, arguments like Everyone in Germany knows what Swiss German isare irrelevant; many Allemanic languages like Alsatian are not even spoken in Germany, so it doesn't really matter what everyone in Germany thinks.
{{#language:gct|en}}
→ gct – no support for the
Colonia Tovar dialect{{#language:gsw|en}}
→ Alemannic{{#language:swg|en}}
→ swg – no support for
Swabian German{{#language:wae|en}}
→ Walser{{#language:}}
magic word are supported by cs1|2.
ISO 639-3 maps gsw
to Alemannic, Alsatian, and Swiss German.
ISO 639-2 maps the same languages in a different order: Swiss German, Alemannic, and Alsatian.gsw
in the infobox.
CLDR v37.0β maps gsw
to Swiss German (English) and Schweizerdeutsch (native). The common language name for gsw
among all three is Swiss Germanswg
) to be supported by MediaWiki, take it to Phabricator.gsw
as Swiss German and will recognize Swiss German as a known language name. Because MediaWiki uses CLDR for language name translations, it knows the local language names for its supported languages (mostly):
{{#language:gsw|es}}
→ alemán suizo|language=gsw
in a cs1|2 template copied to es.wiki will produce the correct local-language rendering without the need for editor intervention.I've noticed that {{
cite book}} has started emitting an error message where it contains |work=
instead of displaying the value held in |work=
. Are these being tracked anywhere? Most of the |work=
parameters can probably just be reparameterised as |series=
, although I found a few that weren't so easy. Seems like there should be an easy way to find these citations so whatever is held in the |work=
parameter can be caused to be displayed again instead of hidden away in the source.
Folly Mox (
talk) 17:24, 18 August 2023 (UTC)
{{cite book}}
ignores |work=
, the fix has been:
|title=
→ |chapter=
(or appropriate alias)|work=
→ |title=
|title=
→ |volume=
; |work=
→ |title=
. Hopefully they're mostly easy swaps of one kind or another. Thanks again.
Folly Mox (
talk) 18:23, 18 August 2023 (UTC)
|series=
was the right change, but most need chapter/title conversion, per Trappist. –
Jonesey95 (
talk) 20:36, 18 August 2023 (UTC)
Not all of these parameters are supported by every CS1 template.
|work=
is not listed as a supported parameter in the documentation for {{
Cite book}}. Yes, there are 46,000 pages to fix, but we have had much larger piles of pages to fix before, and happily, the fixes are typically pretty easy. As usual, the error messages are new, but the errors have been there for a long time. –
Jonesey95 (
talk) 05:05, 20 August 2023 (UTC)I just added language=kk-cyrl
(meaning "Kazakh (Cyrillic script)") to a citation in
Sadyk Abdujabbarov. That automatically added the article to the non-existent
Category:CS1 Kazakh (Cyrillic script)-language sources (kk-cyrl), which is explicitly showing up as a red-linked category in the article's category list. (
Category:CS1 Kazakh-language sources (kk) and
Category:CS1 Kazakh (Kazakhstan)-language sources (kk-kz) already exist.) (Interestingly, the new category's page says "Wikipedia does not have a category with this exact title" and yet also "This category contains only the following page".)
Am I right in thinking that I should now create
Category:CS1 Kazakh (Cyrillic script)-language sources (kk-cyrl) with the content {{
CS1 language sources}}
? And is there anything else I need to do?
Joriki (
talk) 14:53, 20 August 2023 (UTC)
{{
CS1 language sources/core}}
. There are, according to
this search about 80 categories that have an extraneous {{
CatAutoTOC}}
template. I'll hack an awb script to remove them.I propose to update cs1|2 module suite over the weekend 12–13 August 2023. Here are the changes:
|archive-date=
/ |archive-url=
timestamp mismatch;
discussion|location=
(or alias) but do not have |publisher=
;
discussion|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
;
discussion{{
cite document}}
;
discussion|medrxiv=
and {{
cite medrxiv}}
;
discussionfkv
;
discussion{{
cs1 config}}
;
discussionModule:Citation/CS1/Configuration
|archive-date=
/ |archive-url=
timestamp mismatch;|location=
(or alias) but do not have |publisher=
;|subject-first=
, |subject-last=
, and aliases and enumeration variants;
discussion|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
, |transcripturl=
;{{cite document}}
;|medrxiv=
and {{cite medrxiv}}
;|title-note=
;
discussion{{
cite tech report}}
, {{
cite arXiv}}
, {{
cite bioRxiv}}
, {{
cite CiteSeerX}}
, and {{
cite SSRN}}
;
discussion{{cs1 config}}
;|subject-first=
, |subject-last=
, and aliases and enumeration variants;|lay-date=
, |lay-format=
, |lay-source=
, |lay-url=
, |transcripturl=
;{{cite document}}
;|medrxiv=
and {{cite medrxiv}}
;|title-note=
;Module:Citation/CS1/Date validation
|archive-date=
/ |archive-url=
timestamp mismatch;Module:Citation/CS1/Identifiers
|bibcode=
;
discussion|medrxiv=
and {{cite medrxiv}}
;|class=
arXiv linkto use https;
discussion|medrxiv=
and {{cite medrxiv}}
;— Trappist the monk ( talk) 15:54, 5 August 2023 (UTC)
|publisher=London
to stop the maintenance message from appearing (which citations generated automatically from sources hosted on Internet Archive already do), and b. after reading through the linked discussion, I'm understanding that |location=
in {{
cite conference}} is not supposed to hold the location of the conference, which is wild to me. What is it for then, and what parameter is supposed to hold the location of the conference?
Folly Mox (
talk) 02:38, 6 August 2023 (UTC)
|Location=
is for the location of the publisher. Bibliographically speaking, nothing holds the location of the conference. The only place it appears is often in the title, e.g. Proceedings of the 12th Conference on Rat Extermination, Held in Phoenix, AZ, on December 6–9, 2009. Likewise, |date=
isn't the date of the conference, but rather the date the proceedings were published.
Headbomb {
t ·
c ·
p ·
b} 02:46, 6 August 2023 (UTC)
|conference=
. If using {{
cite conference}}
, it is best to provide the title of the conference proceedings in |book-title=
so that that information makes it into the citation's metadata; |conference=
is not part of the metadata.emit error when year less than 100be on citations to ancient book sources that legitimately predate 100 CE? Folly Mox ( talk) 19:59, 5 August 2023 (UTC)
0
. Here is the live module – no error message when there should be an error message:
* {{cite sign | title = Victory stele of Thutmose III | location = Sudan, Gebel Barkal | publisher = Egyptian New Kingdom | date = 1440 BC | via = Boston Museum of Fine Arts | url = https://collections.mfa.org/objects/145121}}
{{
cite sign}}
: Check date values in: |date=
(
help)|orig-date=
is suppressed when |date=
is not provided, I usually just guess at the publisher and date so I can get the |orig-date =
value to display.
Folly Mox (
talk) 02:16, 6 August 2023 (UTC)straightforward to implementdoesn't fit with that philosophy.
|series=
is one of those parameters that has different meaning for different templates; particularly {{
cite episode}}
and {{
cite serial}}
.detect, can some minor variance not throw up an error (e.g. +/- 24 hours)? If someone uses their local time as the "archive date/time" but the URL is encoded using UTC, this should not be an error or something that is "fixed". — Locke Cole • t • c 17:47, 21 August 2023 (UTC)|archive-date=
/|archive-url=
timestamp mismatch
Revert the edit that caused timestamp errors across the entire site or nah? 4theloveofallthings ( talk) 09:23, 14 August 2023 (UTC)
|archive-date=
parameters with the values present in |archive-url=
.
Folly Mox (
talk) 13:08, 14 August 2023 (UTC)
I found |url-status=bot: unknown
in
an article. Is that a valid setting? What does that mean? In this case, the archive is to
archive.today, which does not seem to be a currently functioning site. —
BarrelProof (
talk) 01:19, 18 August 2023 (UTC)
|url-status=
parameter refer to the original link rather than the archive url? It was my understanding that archive urls were presumed to be functional.
Folly Mox (
talk) 02:24, 18 August 2023 (UTC)
|url-status=
— which is ONLY valid when there are both |url=
and |archive-url=
parameters in a citation — provides the status of the original source URL, and dictates how the |archive-url=
is presented in the citation: Whether it's relegated to being a "backup" source (when |url-status=live
), whether it's given prominence over the original |url=
(when |url-status=dead
), or whether it's the only link provided, and the original |url=
is suppressed (when |url-status=usurped
).
FeRDNYC (
talk) 10:50, 20 August 2023 (UTC)It's not so much that they're presumed to be functional, more that they're recognized (unlike sourceIt was my understanding that archive urls were presumed to be functional.
|url=
s) to have no value unless they're functional. IOW, if a citation template includes an |archive-url=
that points to a dead link (the archiver shut down, they changed their access system without providing redirects from older-system URLs, etc.) the correct mitigation is to simply delete that parameter. An inaccessible archive... isn't. (An archive.)
FeRDNYC (
talk) 11:09, 20 August 2023 (UTC)
Can someone sync the templates over to there again. AManWithNoPlan ( talk) 00:38, 22 August 2023 (UTC)
{{
citation}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 2006-05-23 suggested (
help)The archive-date and archive-url are actually correct. WebCite encodes the archive date in base-62 which also serves as the capture ID eg. 6GOwnekjN. A Lua function for this is in Module:Webarchive. -- Green C 18:00, 22 August 2023 (UTC)
|archive-url=
. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 18:23, 22 August 2023 (UTC)A command-line tool for testing/checking the value of WebCite IDs:
base62.lua
|
---|
#!/usr/bin/lua --[[--------------------------------------------------- The MIT License (MIT) Copyright (c) 2016-2023 by User:GreenC (at en.wikipedia.org) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ]] -- Given a Webcite ID on arg[1], return dates in mdy|dmy|iso|ymd format -- example ID: 6H8pdR68H -- http://convertxy.com/index.php/numberbases/ -- http://www.onlineconversion.com/unix_time.htm --[[--------------------------< base62 >----------------------- Convert base-62 to base-10 Credit: https://de.wikipedia.org/wiki/Modul:Expr ]] local function base62( value ) local r = 1 if value:match( "^%w+$" ) then local n = #value local k = 1 local c r = 0 for i = n, 1, -1 do c = value:byte( i, i ) if c >= 48 and c <= 57 then c = c - 48 elseif c >= 65 and c <= 90 then c = c - 55 elseif c >= 97 and c <= 122 then c = c - 61 else -- How comes? r = 1 break -- for i end r = r + c * k k = k * 62 end -- for i end return r end local function main() -- "!" in os.date means use GMT zday = os.date("!%d", string.sub(string.format("%d", base62(arg[1])),1,10) ) day = zday:match("0*(%d+)") -- remove leading zero zmonth = os.date("!%m", string.sub(string.format("%d", base62(arg[1])),1,10) ) month = zmonth:match("0*(%d+)") nmonth = os.date("!%B", string.sub(string.format("%d", base62(arg[1])),1,10) ) year = os.date("!%Y", string.sub(string.format("%d", base62(arg[1])),1,10) ) mdy = nmonth .. " " .. day .. ", " .. year dmy = day .. " " .. nmonth .. " " .. year iso = year .. "-" .. zmonth .. "-" .. zday ymd = year .. " " .. nmonth .. " " .. day year = tonumber(year) month = tonumber(month) day = tonumber(day) if year < 1970 or year > 2020 then print "error" elseif day < 1 or day > 31 then print "error" elseif month < 1 or month > 12 then print "error" else print(mdy .. "|" .. dmy .. "|" .. iso .. "|" .. ymd) end end main() |
20060523220016
from which it extracts the date 2006-05-23
. That date does not match |archive-date=2013-05-06
. The correct fix here, it seems to me, is to write: |archive-url=
https://web.archive.org/web/20060523220016/http://www.alwatan.ma/html/Publication_Fondation/Publication_2006/Publication/Ouvrage.pdf
(http
changed to https
)
http://web.archive.org
doesn't work for me so that probably should be fixed else someone will try to re-add the archive-snapshot-of-an-archive-snapshot WebCite url.
This search found two other archive-snapshot-of-an-archive-snapshot WebCite urls which should probably be fixed. I don't see a need to fix the module to support archive-snapshot-of-an-archive-snapshot urls.I was going to fix the articles in Category:CS1 maint: date format, but then I thought that replacing hyphens by dashes in parameters that the template is already automatically identifying sounds like something a bot should be doing; hence my questions:
Joriki ( talk) 11:06, 22 August 2023 (UTC)
Just a heads-up on some changes I envision to
Module:CS1 translator to add support for
fr:Template:Chapitre. After expansion, typical French usage is very similar to an en-wiki {{
cite book}} template that contains a |chapter=
param, so my approach has been to take advantage of the existing _cite_fr function, as we don't have a separate, {{
cite chapter}} template, and we won't need a new function in the module to handle it because it's so close to cite book.
This is a very common citation template on fr-wiki and my current activity here results from a real-world problem based on my intention to translate fr:Manifestations de ménagères, in which about half of the items in the "Bibliographie" section use the "Chapitre" template. I've put that translation aside for the moment, while looking at this module.
I'm still in the middle of it, but here is roughly the current status (tl;dr: working. except for one bug not yet looked at, but more test cases needed):
This is my first attempt at Lua coding, so it's a bit slow, and I may be making dumb mistakes, or coding inefficiently, or not aligning properly with existing data structures or the original design for which I beg pardon and ask for indulgence, but I am making progress. I believe I have a working version for dealing with the unknown param |pages totales=
that passes my current test cases (but more are needed), and almost everything in the Chapitre template is being translated correctly. There is one notable exception that I have not looked at yet, which is that it flags "Unknown parameter |titre chapitre= ignored". Thanks,
Mathglot (
talk) 11:38, 24 August 2023 (UTC)
{{
cite chapter/French/sandbox}}
) includes {{
Subst only|auto=yes}}
, substing is handled by AnomieBOT usually within the hour. To prevent AnomieBOT from substing, you can add a {{
nobots}}
template to the ~/testcases page. That done, test cases are written like this:
{{Cite chapter/French/sandbox |auteur=Jean-François Condette |titre chapitre=Les manifestations de ménagères dans le département du Nord de 1940 à 1944 : Révolte frumentaire ou résistance ? |auteurs ouvrage=Robert Vandenbussche (dir.) |titre ouvrage=Femmes et Résistance en Belgique et en zone interdite |lieu=Lille |éditeur=Publications de l’Institut de recherches historiques du Septentrion |collection=Histoire et littérature du Septentrion (IRHiS) |numéro dans collection=38 |année=2007 |pages totales=247 |isbn=978-2-490296-12-5 |lire en ligne=http://books.openedition.org/irhis/2189 |consulté le=2023-07-13 |passage=125–164}}
{{cite book/subst |access-date=2023-07-13 |author=Jean-François Condette |chapter=Les manifestations de ménagères dans le département du Nord de 1940 à 1944 : Révolte frumentaire ou résistance ? |date=2007 |isbn=978-2-490296-12-5 |location=Lille |page=125–164 <!--pages totales=247--> |publisher=Publications de l’Institut de recherches historiques du Septentrion |series=38 |series=Histoire et littérature du Septentrion (IRHiS) |title=Femmes et Résistance en Belgique et en zone interdite |url=http://books.openedition.org/irhis/2189 |veditors=((Robert Vandenbussche (dir.)))}}
{{
Bots}}
template to prevent the above from being subst'd.|veditors=
as a translation of |auteurs ouvrage=
. That may violate
WP:CITEVAR for templates that use |nom=
, |postnom=
, |prenom=
, |prénom=
because those |last=
/ |first=
parameters will render in Vancouver Style when they should not.|series=38
and |series=Histoire et littérature du Septentrion (IRHiS)
which does not get flagged by MediaWiki and is not caught by
Module:CS1 translator when rendering the citation. I suspect that this is because at
line 609 we don't look for out_t[param]
already present in out_t
. That should be fixed. Still, in your translation, you should probably concatenate |collection=
and |numéro dans collection=
in some way before assigning the result to |series=
.|pages=12–14
and |pages totales=355
into |pages=12–14 <!--pages totales=355-->
lives hard-coded in function _cite_fr and was kind of proof-of-concept to see if I could do it; but the intention all along, was to generalize it into a new function that would examine a predefined table of param pairs relating one French/foreign param with no cs1|2 equivalent (like |pages totales=
) as k, to a 'nearest cs1|2 target' (if there is one) as v, and concatenate the former to the latter as hidden text; the table probably to live as an extension to /data which would define these relationships as k-v pairs relating the foreign-param to en-param (and multiple k's pointing to the same v would not be a problem). Anyway, the point being that I agree, but I don't know if I'll get to it in my first version, this being already at the limit of my Lua ability, but I think users are used to occasionally imperfect translations that might miss one thing here or there while still generating an essentially correct citation and are hugely useful timesavers, and I think that users can deal with the series/collection problem for now, and will be well-served by something that can translate {{
Chapitre}} 95% perfectly, rather than not handle it at all and have to slog through it the long way, the way they do now. Maybe what I can do for now, is combine |series=
and |collection=
with the "brute force" method I used for |pages totales=
, and the obvious parallelism between the two cases will point the way to a better, more generalized solution next iteration. Thanks very much for the feedback!
Mathglot (
talk) 20:09, 24 August 2023 (UTC)
|editor=
still exists (although not |editors=
, which would've been ideal here). In any case, this works: |editor=((Robert Vandenbussche (dir.), John Smith, Mary Doe))
, so I'll make this change to the sandbox. Probably not ideal, but still one click better than |veditors=
.
Mathglot (
talk) 20:50, 24 August 2023 (UTC)
|pages totales=
pass through so that the editor knows that it's there and can decide what to do with that information. Hiding the parameter in html comment markup makes it likely that the editor won't know that its there especially those editors who use that abomination that is ve. Similarly, don't mask the maintenance message that will occur with a comma separated list of editor names. Most editors won't see that because maint messaging is hidden by default but masking with accept-as-written markup hides the issue from gnome editors who would otherwise separate the list into individual parameters as should be done.|trans-title=
right after the |title=
, so I remember to fill it in later. I like url last, or almost last, others like it closer to the front, and so on.I understand this was just rolled out in the recent update, but can this somehow be downgraded to a maintenance message from error status? It honestly doesn't seem like such a big problem that it requires red error text. For archives that support generating this mismatch, couldn't the template be coded to display the archive date by parsing
Folly Mox (
talk) 09:32, 13 August 2023 (UTC) Secondary suggestion struck 16:22, 13 August 2023 (UTC)
|archive-url=
, instead of forcing editors to fill in the parameter manually, risking typos?
{{use xxx dates}}
template. That template is not visible when section editing so the 'suggested date would necessarily be in YYYY-MM-DD format. This same might be applied to templates with |archive-url=
but missing |archive-date=
but only for those archive urls that include a YYYYMMDDhhmmss timestamp (currently archive.org and archive.today).I'd like the module to do the work for me of adding the date.Templates/modules cannot modify wikitext so adding
|archive-date=
and its value is on you.We could add a suggested date in the article-preferred format only when the module can see the {{use xxx dates}}
template.
I was thinking also of |df=
.Frankly, I don't thinkWe should go the extra mile. It's probably not too much work once you have the date in the message.
I don't know what you meanA bit literalist of an interpretation on your part. You know I'm quite aware of what templates and modules can do. :) Izno ( talk) 15:47, 26 August 2023 (UTC)
it is not possible for the module to do the work for youIs there a reason it can't detect an archive.org/archive.today link, parse the date and output/override the
|archive-date=
if there is a mismatch (I'd actually think we should deprecate/make optional |archive-date=
for these two archive sources)? No need to change wikitext or emit an error, just add it to a maintenance category so it can be cleaned up with other more serious issues by bot. —
Locke Cole •
t •
c 20:38, 27 August 2023 (UTC)
|archive-date=
value in error message. Suggested date is formatted according to |df=
or {{use xxx dates}}
or YYYY-MM-DD in that order.
{{cite book/new |title=Title |url=//example.com |archive-url=https://web.archive.org/20230827081416/https://example.com |archive-date=August 26, 2023|df=dmy-all}}
{{
cite book}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 27 August 2023 suggested (
help){{cite book/new |title=Title |url=//example.com |archive-url=https://web.archive.org/20230827081416/https://example.com |archive-date=August 26, 2023|df=dmy}}
{{
cite book}}
: |archive-date=
/ |archive-url=
timestamp mismatch; 2023-08-27 suggested (
help)|df=
or {{use xxx dates}}
or YYYY-MM-DD, the module extracts the format used in |archive-date=
and uses that format in the absence of |df=
or {{use xxx dates}}
.|df=dmy
. That parameter value tells the date-reformatter to leave |access-date=
and |archive-date=
formats as they are. The suggested date for the error message is YYYY-MM-DD before the format specified in |df=
is applied. Because |df=dmy
instructs the module to ignore |archive-date=
(which this date is) the message renders as YYYY-MM-DD. I suspect that this is generally acceptable because YYYY-MM-DD is the common and usual format when |access-date=
and |archive-date=
have a different format from the publication dates.Is there any script that allows one to reorder CS1 reference parameters on a page into some sort of standardized order? {{u| Sdkb}} talk 04:23, 14 August 2023 (UTC)
paramOrder
(kudos @
Stjn and @
AntiCompositeNumber for reminding me). So the cat is already out of the bag in that sense. {{u|
Sdkb}}
talk 15:22, 17 August 2023 (UTC)
{{cite work |parameter1=value1 |parameter2=value2}}
as the most readable for the predominant (inline) use case.
Izno (
talk) 19:49, 26 August 2023 (UTC)( ←) I also prefer parameters to be in the order of display. This ultimately supports the bibliography comment above. If there's a script that reorders things this way, so long as it's in the context of a major edit, I see no issue. Izno ( talk) 19:49, 26 August 2023 (UTC)
Why does this produce an error? Found in Typhoon Nanmadol (2022), there are probably others.
-- Green C 18:36, 24 August 2023 (UTC)
|archive-date=
. The template uses whatever is in |date=
to populate |access-date=
and |archive-date=
. The latter appears to not be reliant on |archive-url=
existing to be populated. -- LCU
ActivelyDisinterested ∆
transmissions∆ °
co-ords° 19:02, 24 August 2023 (UTC)
|archive-url=
is required if |date=
is provided. I have added that requirement to the documentation. –
Jonesey95 (
talk) 19:07, 24 August 2023 (UTC)
{{
Cite PAGASA}}
which can have a |date=
and no |archive-url=
. It looks like an unintentional feature maybe added by accident:
|archive-date=
to each one, I'd be OK with fixing the template so that |date=
is used as it should be and not "triple-counted". I recommend that this whole discussion be moved from here to the template's talk page. –
Jonesey95 (
talk) 22:38, 24 August 2023 (UTC)
|archive-url=
field to store non-
web archive URLs which of course have no archive date since they are not archive URLs. This was a problem because CS1|2 was throwing a red error when there is an |archive-url=
but missing |archive-date=
. So they generated a default "dummy date" to stop the errors (based on the value of the |date=
field). Then recently we added this new tracking category that caught the mismatch of the dates and so on. Then it all became clear. I removed the default |archive-date=
from the template, and am currently processing all instances of this template, moving the |archive-url=
to outside the template (when not a valid archive URL) .. it's really a second citation. --
Green
C 16:43, 28 August 2023 (UTC)
I've started putting subtitles for multi-volume books in the volume field rather than in the more traditional title field because I think it's easier for the reader to understand exactly that exact volume covers. Forex title=German Warships 1815–1945: U-boats and Mine Warfare Vessels|vol=Two versus title=German Warships 1815–1945|vol=Two: U-boats and Mine Warfare Vessels. The first example could easily be understood as the second volume of a book devoted to U-boats and Mine Warfare Vessels within a larger work covering German warships while the second example makes it much clearer that volume 2 of German Warships covers only U-boats and Mine Warfare Vessels, IMO.
Currently the documentation for the volume field only covers numbers, not actual text. I would like to make adding a subtitle in addition to the number a valid option. This may raise the hackles of professional catalogers, but I believe that the extra clarity is worth making this change, especially since we're not strictly bound by MARC standards. Thoughts, comments? Sturmvogel 66 ( talk) 15:08, 25 August 2023 (UTC)
|volume=
parameter is lost to those readers.
{{cite book |title=Title |volume=Some sort of subtitle}}
'"`UNIQ--templatestyles-0000009A-QINU`"'<cite class="citation book cs1 cs1-prop-long-vol">''Title''. Vol. Some sort of subtitle.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Title&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1%2FArchive+89" class="Z3988"></span>
&rft.volume=Some sort of subtitle
.{{cite book}}
template has any of these parameters:
|type=
|series=
|language=
|title=
and |volume=
which visually disconnects the subtitle from the title.
{{cite book |title=Title |type=Type |series=Series |language=nv |volume=Some sort of subtitle}}
|volume-title=
in the deeper archives, but I vaguely recall a more recent thought on it.
Izno (
talk) 22:08, 25 August 2023 (UTC)
|volume-title=
makes sense, but only if we are not supposed to place the title in |volume=
(which seems easier). Thanks,
Mr.choppers |
✎ 14:38, 26 August 2023 (UTC)
I propose three parameters be added to this template.
The purpose of this parameter would be as follows: Wikipedia has reasonably significant issues regarding the verifiability and reliability of information on this site. The 'verified' field provides two things; (1) it gives readers a degree of confidence in a citation without having to click through, (2) it gives editors the ability to identify citations that are worth checking.
Adding these parameters would allow Wikipedians to trawl through the citations on this site and verify them.
Wikipedians already engage in the verification of citations, however it is often unclear whether a citation has already been checked by another editor or not. Adding this parameter would make it easier for editors to focus on citations / claims that haven't yet been checked, substantially increasing the productivity of site editors.
What do my fellow editors think of this proposal?
Kind regards Jack4576 ( talk) 10:08, 26 August 2023 (UTC)
Ultimately editors who are concerned about the referencing ... should verify the details themselvesAgree Folly Mox ( talk) 19:20, 26 August 2023 (UTC)
|name=
parameter of <ref>
.
Kanguole 17:08, 26 August 2023 (UTC)
In addition, many Wikipedia editors are not very rigorous about what they use citationsRight. See: Fire basket, currently linked from the main page. This would presumably have "verified" citations in those boolean yes/no parameter slots, which without additional context would be misleading, Rjjiii ( talk) 06:24, 27 August 2023 (UTC)
The beacon atop the Altenburg castle in Bamberg served to communication with the neighboring Giechburg castle.Rjjiii ( talk) 03:22, 28 August 2023 (UTC)
I agree that that anything we can do to improve the integrity of our sourcing is a good thing, but it's a mug's game when any editor can alter the text without changing the sourcing accordingly and only those who have that article on their watchlist are likely to notice or even care. And that doesn't even take into account the scale of the issue with FA-quality articles often having over a hundred cites. Admittedly, the quantity of cites sharply declines in most of the rest of the articles on Wiki, but stretched over 7-odd million articles that's still a number that no volunteer group like ours can handle. I applaud anyone who actually enjoys verifying cites, but I much prefer generating them from the books and journals spread out in front of me and on my monitors.-- Sturmvogel 66 ( talk) 15:55, 28 August 2023 (UTC)
I ran into a false positive for the "multiple names: authors list" error for the name "Fernando Alfonso III". My understanding (supported by this archived topic) was we put the Jr./Sr./III/etc. into |first= in the cite templates, like "|first1=Fernando, III last1=Alfonso". The reference to MOS:JR on Template:Cite web/doc is confusing, though, because that seems to apply specifically to body text and not reference parameters.
{{
cite news}}
: CS1 maint: multiple names: authors list (
link)My suggestions:
Thanks.- Ich ( talk) 11:20, 29 August 2023 (UTC)
When the surname is shown first, the suffix follows the given name. It then goes on to say
Do not place a comma before a Roman numeral name suffix. Jr, Sr, III are suffixes all explicitly mentioned as suffixes in MOSJR.
Kennedy, John F. Jr.of how Jr and Sr should be used in a listing, but the example
Otis D. Wright IIdoesn't make clear how the name should look in a listing with a Roman numeral suffix. I've seen many "Wright II, Otis D." examples in articles, so something isn't clear enough. -- LCU ActivelyDisinterested ∆ transmissions∆ ° co-ords° 14:58, 29 August 2023 (UTC)
|first1=Fernando III
(without the comma) the correct format. If you believe that the cs1|2 documentation can be improved, please do so. If you believe that
MOS:JR should be constrained to body-text only, discuss at
WT:MOSBIO.