Jump to content

Help talk:Citation Style 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

    'Reformat dates' function

    [edit]

    Hi! I'm trying to figure out the date reformatting function: Module:Citation/CS1/Date validation#L-841. I see that the module can convert dates to {{#time:n F Y|2024-10-10}} -> 10 October 2024, is it possible to convert in {{#time:n xg Y|2024-10-10}} (month in genitive form) -> 10 October 2024?

    But I need to save {{#time:F Y|2024-10-10}} -> October 2024 option. Iniquity (talk) 20:35, 20 November 2024 (UTC)[reply]

    It is not really clear to me what it is that you are asking. cs1|2 doesn't use the #time parser function to do date conversions.
    The #time parser is not used because we can't write something like:
    {{#time:Y-m-d|10 octobre 2024}}
    on the French Wikipedia; doing so results in Erreur : durée invalide. This despite the #time parser's ability to render this at en.wiki:
    {{#time:n F Y|2024-10-10|fr}} → 10 octobre 2024
    You would think that, for an 'international' project, accepting dates with local-language month names as input would go hand-in-hand with rendering local-language month names.
    Trappist the monk (talk) 22:47, 20 November 2024 (UTC)[reply]
    Thanks for the answer! I mean that now the 'long' array from 'date_names' in Module:Citation/CS1/Configuration is used to form the date. There the months are in the nominative case, but for the Russian language the genitive case is needed for 'dmy' form and nominative case for 'my' form. Is it possible to add an additional array with genitive case? Iniquity (talk) 05:09, 21 November 2024 (UTC)[reply]
    Just for clarity, you want:
    10 октября 2024 ← {{#time:n xg Y|2024-10-10|ru}} – genitive for all 'dmy' dates; including ranges? what about mdy?
    октябрь 2024 ← {{#time:F Y|2024-10-10|ru}} – nominative for 'my' dates only; including ranges?
    #time parser function alludes to other languages that have nominative/genitive date forms. Do they follow the same rules as the Russian dates?
    I have some ideas for resolution of this issue. I'll think more on it. My time is occupied elsewhere so I won't be able to get to this until later this week or next week. In the meantime, here is your assignment:
    1. MediaWiki supports about 350 editions of Wikipedia. Assemble a list of those Wikipedia-edition languages that have nominative/genitive date forms.
    2. determine which date formats from the above assembled list need nominative month names and which formats need genitive names.
    Trappist the monk (talk) 15:36, 21 November 2024 (UTC)[reply]
    10 октября 2024 ← {{#time:n xg Y|2024-10-10|ru}}
    My mistake, must be j not n - {{#time:j xg Y|2024-10-10|ru}}
    genitive for all 'dmy' dates; including ranges?
    Yes.
    what about mdy?
    We dont use this format, we can leave the nominative case, but I found something, I'll write it below.
    октябрь 2024 ← {{#time:F Y|2024-10-10|ru}} – nominative for 'my' dates only; including ranges?
    Yes, but the first letter of the first month must be capitalized.
    #time parser function alludes to other languages that have nominative/genitive date forms. Do they follow the same rules as the Russian dates?
    This is a relatively complex issue, I found such a list of formats for each language. And now it seems to me that the genitive case is not the only problem of internalization:
    https://codesearch.wmcloud.org/core/?q=dmy+date&files=languages%2Fmessages&excludeFiles=&repos= Iniquity (talk) 18:42, 21 November 2024 (UTC)[reply]
    That can't be the whole list can it? Why is ru.wiki not on that list?
    Trappist the monk (talk) 22:41, 21 November 2024 (UTC)[reply]
    This is a complete list, you just need to load the remaining lines, messageRU.php there.
    Iniquity (talk) 06:38, 22 November 2024 (UTC)[reply]
    I think it is possible to use lang:formatDate for catch necessary formats. Iniquity (talk) 18:55, 21 November 2024 (UTC)[reply]
    lang:formatDate() is the Scributo version of the #time parser function. Try this in a module debug console at ru.wiki:
    =mw.language.getContentLanguage():formatDate ('j F Y') → 21 ноябрь 2024
    I used that to get the month name. Then, I turned it round and attempted to get a YYYY-MM-DD date from the Russian DMY:
    =mw.language.getContentLanguage():formatDate ('Y-m-d', '21 ноябрь 2024') → Ошибка Lua: bad argument #2 to 'formatDate': invalid timestamp '21 ноябрь 2024' ... and some other error message stuff
    To prove that the call was structured correctly, I changed 'ноябрь' to 'November':
    =mw.language.getContentLanguage():formatDate ('Y-m-d', '21 November 2024') → 2024-11-21
    mw.language:formatDate() will not work for date format conversion in Module:Citation/CS1/Date validation.
    Trappist the monk (talk) 22:41, 21 November 2024 (UTC)[reply]
    Yes, I know :( It doesn't work well with anything that isn't ISO. But it converts ISO to the required format well. Iniquity (talk) 06:39, 22 November 2024 (UTC)[reply]
    I would like to separately tell you that we have adopted a local rule that all service dates must be machine-readable (to simplify the transfer of information from wiki to wiki) and we convert them into ISO using a bot.
    I tried to globalize it (meta:Requests for comment/Technical agreement on dates and times) somehow, but I didn't succeed very well. Iniquity (talk) 10:39, 24 November 2024 (UTC)[reply]
    I was curious to see how your list of 70 matches direct testing of the time parser returns for each of the language names taken from Module:Citation/CS1/Configuration (the inter_wiki_map table). So I wrote Module:Sandbox/trappist the monk/genitive. You can see the results by adding one of these to a sandbox page:
    {{#invoke:Sandbox/trappist the monk/genitive|main|a-m}}
    {{#invoke:Sandbox/trappist the monk/genitive|main|n-z}}
    where a-m and n-z match the first letter of a language tag. These are lua set patterns: lang:match ('^[a-m]') etc.
    Alas, you can't do a-z, nor can you have a-m and n-z on the same page at the same time, because the time parser chokes and emits the confusing error message: Error: Total length of format strings for #time exceeds 6000 bytes. For an explanation, see Phab:T299909 and the linked discussion.
    When the test is run for each range, they find 143 languages where at least one month name returned by {{#time:F|2024-mm-01}} (mm is month number 1–12) differs from the month name returned by {{#time:xg|2024-mm-01}}.
    Do all of these languages use nominative/genitive dating? I don't know.
    Trappist the monk (talk) 18:34, 25 November 2024 (UTC)[reply]
    Wow! Thanks for this research. I think there are more differences because the time functions use the standard language fallback scheme from MediaWiki: https://codesearch.wmcloud.org/core/?q=fallback&files=languages%2Fmessages&excludeFiles=&repos= Iniquity (talk) 18:52, 25 November 2024 (UTC)[reply]
    mw.language:formatDate() won't work for this application because it does not accept (so far as I can tell from
    the documentation) a language parameter;

    You can use mw.language.new( code ):formatDate( format, timestamp, local ) Iniquity (talk) 19:25, 25 November 2024 (UTC)[reply]
    Nope. From the documentation: "There is a limit of 200 on the number of distinct language codes that may be used on a page. Exceeding this limit will result in errors."
    Trappist the monk (talk) 19:38, 25 November 2024 (UTC)[reply]
    I'm talking about the language parameter :) Iniquity (talk) 05:13, 26 November 2024 (UTC)[reply]
    diff
    {{#invoke:Sandbox/Iniquity|main|a-l}}{{#invoke:Sandbox/Iniquity|main|m-z}} Iniquity (talk) 16:58, 26 November 2024 (UTC)[reply]
    As idea: make a setting that will allow you to switch on the formatDate conversion function. Only ISO dates are passed to this function, and CS1 module only converts incoming dates to ISO format. Iniquity (talk) 17:35, 2 December 2024 (UTC)[reply]

    Usage of the quote parameter

    [edit]

    I'm adding/updating {{cite web}} entries on articles of towns and cities in Poland. The citation is to an official Polish website. Unfortunately, but not surprisingly, the website is almost entirely in Polish. I wish to add instructions to the citation that show how to perform the relevant search. At the moment, it seems as if the only way I can do this is to use the "quote" parameter. See, for example, this edit. I realise that this is not the intended use of this parameter, but it seems the best fit for what I'm trying to achieve. Is there another more appropriate way of doing what I'm trying here? Does there need to be a new parameter, for example? Regards, Kiwipete (talk) 03:36, 24 November 2024 (UTC)[reply]

    Don't abuse cs1|2 template parameters. Put that extra stuff inside the <ref>...</ref> tags after the template's closing }}.
    Trappist the monk (talk) 03:49, 24 November 2024 (UTC)[reply]
    @Trappist the monk - like this? [1]. Kiwipete (talk) 07:20, 25 November 2024 (UTC)[reply]

    As with my previous edit request to the Configuration subpage, I have amended the local variable script_lang_codes to support an additional language being tagged in citation titles and chapter titles (this time Cherokee chr). As with last time, I have also amended the whole variable definition to balance the line-wrapping better, so please take the whole variable definition (lines 1177–1183).

    Again, this is in no way urgent; the existing code correctly adds the IETF language tag to the text, this edit will merely suppress the error message reading Invalid |script-title=: unknown language code that appears when an unrecognised ISO 639 code is used and the resulting categorisation into Category:CS1 errors: script parameters. — OwenBlacker (he/him; Talk) 19:43, 25 November 2024 (UTC)[reply]

    And as before, there is no need for hurry.
    Trappist the monk (talk) 20:02, 25 November 2024 (UTC)[reply]
    I agree, but I don't see why you've set |answered=yes on {{Requested edit}}; won't that mean that it is more likely to get overlooked? OwenBlacker (he/him; Talk) 20:38, 25 November 2024 (UTC)[reply]
    The live module suite is updated from the sandboxen. Your change is in Module:Citation/CS1/Configuration/sandbox so won't be overlooked when next we do an update.
    Trappist the monk (talk) 21:04, 25 November 2024 (UTC)[reply]
    Oh, do those happen regularly? — OwenBlacker (he/him; Talk) 23:33, 25 November 2024 (UTC)[reply]
    No. Headbomb {t · c · p · b} 00:34, 26 November 2024 (UTC)[reply]
    Then surely {{Requested edit}} should keep |answered=no until the change is rolled out? — OwenBlacker (he/him; Talk) 16:43, 26 November 2024 (UTC)[reply]
    No, that just clutters Category:Wikipedia fully protected edit requests. The change is noted and queued for the next cs1|2 Module-suite update.
    Trappist the monk (talk) 19:30, 26 November 2024 (UTC)[reply]

    Semi-protected edit request on 26 November 2024

    [edit]

    Additional Reference with my permission as author: https://la84.s3.amazonaws.com/assets/LA84WaterPolo_2021.pdfCite error: There are <ref> tags on this page without content in them (see the help page). 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:33, 26 November 2024 (UTC)[reply]

    Peter L. Snyder, Ph.D. permission for submitting book to wikkipedia 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:35, 26 November 2024 (UTC)[reply]

     Not done: This is definitely not the right page to make whatever request this is you are making. PianoDan (talk) 18:00, 26 November 2024 (UTC)[reply]

    This page (Help talk:Citation Style 1) is for discussion on how CS1 templates format citations, not about which books can be used to cite what. Discussion about citing this book would belong at Talk:Water polo. Discussion about the book's reliability in general would be at Wikipedia:Reliable sources/Noticeboard. Good luck, Rjjiii (talk) 23:34, 26 November 2024 (UTC)[reply]

    Semi-protected edit request on 26 November 2024 (2)

    [edit]

    Author permission to publish book: https://la84.s3.amazonaws.com/assets/LA84WaterPolo_2021.pdf through the website LA84Foundation.com 2600:8802:5700:5ED:E90D:5669:A932:53C (talk) 17:52, 26 November 2024 (UTC)[reply]

     Not done: Duplicate invalid request. PianoDan (talk) 18:00, 26 November 2024 (UTC)[reply]

    [edit]

    There are a number of links to books which have since lost their accessibility to the general public on Internet Archive (e.g., [2] and [3] of the same book). These are now "[books] available [only] to patrons with print disabilities."

    Should the links like these which are not accessible to users without print disabilities be removed, or would it be possible to add another |url-access parameter to signify this? Tule-hog (talk) 20:48, 28 November 2024 (UTC)[reply]

    Alternatively (as with {{Hopcroft and Ullman 1979}}) should the link be appended to a reference a note? Tule-hog (talk) 01:33, 29 November 2024 (UTC)[reply]
    @Tule-hog: I don't think any of the values in the current current scheme accurately represent the access status you have described. I'd be inclined to leave |url-access= blank and create a new template to indicate this information after the citation template, similar to many of the templates in Category:External link note templates. Daask (talk) 17:06, 16 December 2024 (UTC)[reply]
    I went with {{Internet Archive patrons}} as a temporary solution, which allows for tracking pages (and ref-templates) that use it (which should make future modifications more streamline-able). Tule-hog (talk) 17:14, 16 December 2024 (UTC)[reply]

    DOI prefix limits should be bumped.

    [edit]

    We have DOI prefixes in the 10.70000s now. The limit should be bumped to 10.80000s Headbomb {t · c · p · b} 04:05, 1 December 2024 (UTC)[reply]

    Protected edit request on 1 December 2024

    [edit]

    Can someone please add the parameters {{{quote-p}}} and {{{quote-pp}}} as aliases of {{{quote-page}}} and {{{quote-pages}}} respectively to all citation templates, excluding {{cite episode}}, {{cite podcast}}, {{cite AV media}}, {{cite mailing list}}, {{cite newsgroup}}, {{cite serial}}, {{cite sign}} and {{cite speech}}, because they're shorter forms of those parameters, and because the parameters {{{p}}} and {{{pp}}} are already aliases of {{{page}}} and {{{pages}}} respectively on all citation templates excluding those aformentioned ones? PK2 (talk; contributions) 06:42, 1 December 2024 (UTC)[reply]

    This is something that needs further discussion and later will get synced through the periodic release process if wanted, not something an admin watching the edit requests queue should do immoderately, so deactivating the edit request template. * Pppery * it has begun... 17:31, 1 December 2024 (UTC)[reply]

    Another generic title

    [edit]

    Hello, another generic title that we should be tracking is |title=x.com. There are about 600 of these at the moment. Keith D (talk) 21:23, 1 December 2024 (UTC)[reply]

    spurious errors when fetching identifier limit data from commons

    [edit]

    cs1|2 stores identifier limit values in tabular data on commons: c:Data:CS1/Identifier limits.tab. This little file allows us to keep identifier limits for all wikis using a recent version of the cs1|2 module suite up to date. Alas, there is some sort of spurious 'something' that sometimes causes the data fetch to fail. Currently, when a failure occurs, all cs1|2 templates on a page render a shrieking-red error message: Lua error in Module:Citation/CS1/Configuration at line 2083: attempt to index a boolean value and complaints at various help and village pump pages. The fix is a null edit.

    I have tweaked the sandbox so that it traps the boolean return, sets the identifier limits to 99,999,999,999 which will cause all limit checks to pass, and adds the page to Category:CS1 maint: ID limit load fail. Articles collected in the category can be null edited to clear the category. Unlike all other maintenance categories, this category does not have an accompanying maintenance message because it would be repeated by every cs1|2 template.

    I tested this new code by disabling the category namespace limit so that a cs1|2 template in my sandbox would emit the error category when I forced a boolean false return from the data fetch.

    Trappist the monk (talk) 01:15, 2 December 2024 (UTC)[reply]

    This seems like a functional workaround. Is it worth reporting a bug to Phabricator to get at the root cause, which may be affecting other processes on MediaWiki sites? A developer may be able to poke through logs to find out why this failure is occurring. – Jonesey95 (talk) 21:38, 2 December 2024 (UTC)[reply]
    There is Phab:T229742 which may be related.
    Trappist the monk (talk) 22:32, 2 December 2024 (UTC)[reply]

    Update s2cid max limit

    [edit]

    I'm getting the "Check |s2cid= value" error when I tried to add reference for the paper https://api.semanticscholar.org/CorpusID:274306220, which has ID of 274306220, larger than the currently configured limit of 274000000. Slovborg (talk) 02:17, 2 December 2024 (UTC)[reply]

    cite episode id parameter silently ignored

    [edit]

    {{cite episode}} currently silently ignores |id=. I have been using it to add IMDb identifiers to some items, eg. Special:Diff/1261220079 using {{IMDb ID}}. I propose that we display the |id= parameter just like most other CS1 templates. A more elaborate discussion of IMDb in particular as an identifier is at Wikipedia talk:IMDb link templates § IMDB as an identifier in citations. Daask (talk) 22:44, 4 December 2024 (UTC)[reply]

    |id= was:
    Because it was the goal of the wikitext-to-module conversion to be transparent, it was necessary to overwrite whatever might be assigned to |id=. I do not recall any discussion here suggesting that we should change that.
    I am not enthusiastic about making a change just to support an identifier for a source that editors at WP:RS/P have determined to be generally unreliable.
    Trappist the monk (talk) 00:20, 5 December 2024 (UTC)[reply]
    I've commented at the other discussion, there's general agreement that IMDb should not appear in references. I don't see how a courtesy link to an unreliable source can help with verification. -- LCU ActivelyDisinterested «@» °∆t° 01:16, 5 December 2024 (UTC)[reply]

    Request to edit note at top of Category:CS1 maint: unflagged free DOI

    [edit]

    Hi there! Could someone please update the note at the top of Category:CS1 maint: unflagged free DOI? It mentions an issue affecting 17 Wikipedia articles, but there are now less than 10 articles in the category. Thanks! GoingBatty (talk) 17:45, 8 December 2024 (UTC)[reply]

    See WP:BOLD. Also, I wonder why it dropped from 17. There hasn't been a template update in ages... I suspect someone performed bad fixes just to avoid the categorization. Headbomb {t · c · p · b} 12:15, 10 December 2024 (UTC)[reply]
    [edit]

    It is usefull to have the link to arXiv with its own identification numbers in the citation template, but

    Petr Karel (talk) 10:47, 10 December 2024 (UTC)[reply]

    Proposal: Replace "biorxiv=" by "preprint DOI=" to include other preprint archives. The link to preprint is usefull when the final version is not free to access. --Petr Karel (talk) 11:19, 10 December 2024 (UTC)[reply]

    Simply put, there's almost nothing on vixra we should want to cite. It is not a reliable source, worse than your usual repository of preprints. It's a nutjob farm. Headbomb {t · c · p · b} 12:13, 10 December 2024 (UTC)[reply]
    If you want to include a courtesy link to the free preprint, along with a citation to the print version, you can do so after the template but before the closing ref tag. As an example:
    <ref>{{cite journal |author=Author |title=Title |journal=Journal |url=https://journal.org}} [https://eartharxiv.org/ Free to access preprint]</ref>
    Gives you the following:
    Author. "Title". Journal. Free to access preprint
    -- LCU ActivelyDisinterested «@» °∆t° 14:36, 10 December 2024 (UTC)[reply]
    I realize this is not the right place to bring this up, but the Visual Editor should really offer better support for this. Rjjiii (talk) 22:34, 10 December 2024 (UTC)[reply]
    That workaround feels like a kludge. I would prefer to see preprint URL support integrated into the template as a preprint-url parameter, which for some reason, has not yet been proposed in any of the 96 archive pages of this talk page. The WP:PREPRINT guideline states, "links to such repositories can be used as open-access links for papers which have been subsequently published in acceptable literature", and it would be useful for the template to link to both the paywalled published version and the unpaywalled preprint without any extra workaround. Using a template parameter would also make the preprint URL more machine-readable, compared to using a separate link.
    For example, I recently cited the following source:
    Crowston, Kevin; Wei, Kangning; Howison, James; Wiggins, Andrea (5 March 2008). "Free/Libre open-source software development: What we know and what we do not know". ACM Computing Surveys. 44 (2). Association for Computing Machinery: 7:1–7:35. doi:10.1145/2089125.2089127. ISSN 0360-0300. Retrieved 15 December 2024.
    I wanted to also include a link to this preprint of the article hosted by the Internet Archive. It would have been nice to have a preprint-url parameter that would have allowed me to do this in the {{Cite journal}} template. — Newslinger talk 22:30, 15 December 2024 (UTC)[reply]
    I've been just putting the preprint URL in |url=, because the publisher's version is already linked from |doi=. I realize this creates some confusion about which version the person creating the reference is actually looking at. I don't usually verify that the versions are identical, but if I have significant doubt, I include citations for both the preprint and the final published version in the same <ref>...</ref> with "Republished as/from" between them, with the first citation being the one I was actually looking at. The word "republished" to me leaves open the possibility of more substantial changes than "reprinted". I am surprised that neither Wikipedia:Citing sources § Say where you read it nor Wikipedia:Citing sources § Dates and reprints discuss the issue specifically. I welcome feedback from other editors on my practices.
    The issue of multiple versions of a work is bigger than just preprints, and |preprint-url= feels to me like a partial solution to a bigger problem. In some fields (eg. economics, public policy) working papers with multiple drafts distributed over many years are normal prior to publication. Daask (talk) 16:42, 16 December 2024 (UTC)[reply]

    Cite chapter in book with no editor

    [edit]

    I read part of Help talk:Citation Style 1/Archive 61#Time to fix "In: <title>"? (and somewhat related Help talk:Citation Style 1/Archive 10#Foreword|) and I am not exactly clear on the result of that discussion.

    I would like to discuss a related use case to those above discussions which is old books where you have a collection of works in a single book with no editor. This was apparently somewhat common in miscellanies and anthologies compiled in the middle ages. Here is a pretty good example of a miscellany with no editor but with named contributors and chapters: https://mvm.dhil.lib.sfu.ca/manuscript/109. The issue with the current implementation is that the citation will look like the author of the chapter is the author of the entire book because there is no "in."

    I don't have many examples but I have seen the form "chapter" in "book name," without an attribution to any editor, in history journals, so I think this may be common practice.

    So I guess my post has multiple aspects:

    1. Do journals use the "chapter" in "book name" form even with no editor? How commonplace is this? My assumption right now is that it is somewhat common.

    2. Should we support such a feature? My thought here is that we should.

    3. How should this be supported? We can support this feature without necessarily implementing "in" for all book chapters. We could do so by using a new parameter "chapter author," which would then always use "in," without having to use it in all cases, for example. There could be multiple ways to achieve this result. I would not like a solution that leaves the

    Any thoughts or questions on the above would be appreciated. I apologize if this is already a settled point. I did my best to search for previous discussions by searching "no editor" and '"editor" "is unknown"' in the archive. Lastly, if this is already supported, I suggest it be made more clear in the documentation as I could not find it.

    (edit: Reading 'Time to fix "In: <title>"?' again, it is actually the exact same issue. I'm not sure what I thought it meant when I first read it. Somehow I thought it was about citing a chapter of a book where the entire book was written by one author.) J2UDY7r00CRjH (talk) 22:43, 12 December 2024 (UTC)[reply]

    J2UDY7r00CRjH, it sounds here like the problem statement is a citation like Author, Chapter. "Chapter title". Edited Volume gives the impression that the chapter author contributed all the chapters, but the theory of change is that Author, Chapter. "Chapter title". In Edited Volume will convey the correct impression?
    I don't have an alternative solution to propose, but I do note that the opposite problem – volume or even series editors being attributed authorship of chapters – is more common by at least an order of magnitude. Folly Mox (talk) 13:45, 13 December 2024 (UTC)[reply]
    >the theory of change is that Author, Chapter. "Chapter title". In Edited Volume will convey the correct impression?
    Yes, additionally, it seems that some styles already use this format. I first saw it in this journal article: https://www.tandfonline.com/doi/full/10.1080/09596410.2017.1401797 (paywalled) (Screenshot of the relevant citation) (link to the cited book).
    Looking further, I found that the APA Publication Manual (7th Edition) seems to follow this rule:

    Example 47. Entry in a dictionary, thesaurus, or encyclopedia, with group author
    American Psychological Association. (n.d.). Positive transference. In APA dictionary of psychology. Retrieved August 31, 2019, from https://dictionary.apa.org/positive-transference
    Merriam-Webster. (n.d.). Self-report. In Merriam-Webster.com dictionary. Retrieved July 12, 2019, from https://www.merriam-webster.com/dictionary/self-report

    This is made more explicit in other guides:
    1.
    >Chapter in a book
    >If there is no editor, include the word "In" before the book title. (link)
    2.
    >Chapters, Short Stories, Essays, or Articles From a Book (Anthology or Collection)
    >[..] Note: If there is no editor given you may leave out that part of the citation.(link). This one is a bit ambiguous about what "that part of the citation" refers to. I don't think it includes "in."
    3.
    This academia.stackexchange post
    So the second reason is to be in line with other citation styles. However, I'm not an expert on citation style and I may be missing something. I found these links above by searching 'how to cite volume with "no editor"' on Google. J2UDY7r00CRjH (talk) 18:52, 13 December 2024 (UTC)[reply]
    I think I agree that In Edited Volume is clearer. I wonder if instead of a whole new set of |chapter-authorn= parameters and their attendant -link=s, -masks etc, an easier implementation might be a specific override value for |editor=, so if it has that value then In will appear before the book title (kinda like how |author-mask= will display text exactly as formatted, except numeric values which it displays as a string of dashes). Folly Mox (talk) 21:45, 13 December 2024 (UTC)[reply]
    An override value for the editor field would also work. Is there a standard value used for such cases? I think "editor=unknown" would work here. J2UDY7r00CRjH (talk) 23:21, 14 December 2024 (UTC)[reply]

    Omitting location parameter when implied by the publisher

    [edit]

    Presently, H:CS1 says The location parameter should be omitted when it is implied by the name of the work, e.g. The Sydney Morning Herald. Does this also apply to the name of the publisher, e.g. Cambridge University Press? I've only just realized I've been conflating the two. Remsense ‥  19:29, 14 December 2024 (UTC)[reply]

    I don't think this advice is valid for publishers like CUP, OUP; they often publish in various locations. OTOH, it's probably trivial and doesn't matter. -- Michael Bednarek (talk) 08:54, 15 December 2024 (UTC)[reply]
    In my mind, omitting location would imply publication in the eponymous location. But yes, I'm thinking of how necessary the parameter even is in many situations. Remsense ‥  08:59, 15 December 2024 (UTC)[reply]

    Citeref: if no year, use year from date

    [edit]

    Citeref is an html ID that is used to connect template:harv and template:sfn to cs1.

    Problem to be solved:

    An SQL search over linter errors of citerefs with the same id gives that around 280k do not have any number, so no year. It does make sense to look if the year can be fetched from elsewhere. CS1 alone makes 1.7 million out of 3.8 million duplicate IDs, so something has to be done, the status quo is not an feasible outcome.

    Expected breakages:

    https://en.wikipedia.org/w/index.php?search=hastemplate%3A%22Cite+journal%22+hastemplate%3A%22Harvard+citation%22+insource%3A%2F%5C%7B%5C%7Bharvard+citation%5C%7C%5Ba-zA-Z%5C%7C%5D%2B%5C%7D%5C%7D%2F&title=Special:Search&profile=advanced&fulltext=1&ns0=1 shows that among the usages of cite journal and harv there is only one that does not have a number, Gordon Pask with its reference to Green, but that reference does not have an date, so it will not be affected by the change. Among the usages of cite journal and harv there are none with only page and not date, so nothing expected to break there. Overall, I do expect breakages, but that that they fix more duplicate ID's than they cause issues with harv. One could do an interim solution with both IDs showing up, causing no breakages for harv and sfn in the meantime.

    Solution:

    It does make sense to look for an year in date, when year is not given. An editor is not likely to duplicate the year when the date has already been given.

    Add the following to line 4115 of Module:Citation/CS1, keeping the line break that is there.

    		if Year == nil or "" then
    			Year = string.match(Date, "%d%d%d%d")
    		end
    

    Snævar (talk) 15:00, 15 December 2024 (UTC)[reply]

    Having the same CITEREF in articles that do not use short form references is not an error that needs solving.
    The year in |date= is already used if it is part of the cite. However the example in Gordon Peak (CITEREFGreen) has no |date= parameter only |access-date= and |archive-date= neither of which would be appropriate to include in a short form reference. -- LCU ActivelyDisinterested «@» °∆t° 16:35, 15 December 2024 (UTC)[reply]
    (edit conflict)
    No. At Module:Citation/CS1 line 4114 is this:
    local year = first_set ({Year, anchor_year}, 2); -- Year first for legacy citations and for YMD dates that require disambiguation
    Normally, Year has been set to nil before this point in the code. anchor_year comes from Module:Citation/CS1/Date validation.
    This example has |date= but does not have |year=:
    {{cite book |title=Title |last=Greene |first=EB |date=15 December 2024}}Greene, EB (15 December 2024). Title.
    '"`UNIQ--templatestyles-0000005D-QINU`"'<cite id="CITEREFGreene2024" class="citation book cs1">Greene, EB (15 December 2024). ''Title''.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Title&rft.date=2024-12-15&rft.aulast=Greene&rft.aufirst=EB&rfr_id=info%3Asid%2Fen.wikipedia.org%3AHelp+talk%3ACitation+Style+1" class="Z3988"></span>
    Note the value assigned to the id= attribute in the <cite> tag; it has the year portion from |date=.
    If you know of cs1|2 templates that do not include the year portion from a publication-date parameter (|date=, |publication-date=, |year=) in the CITEREF anchor id, I'd like to see it.
    Editors do duplicate the year when the date has already been given; Category:CS1 maint: date and year wouldn't be needed else.
    It used to be that cs1 templates did not automagically create CITEREF anchor ids. Some time back, there was discussion:
    Editors in those discussions decided that all cs1|2 templates would create CITEREF anchor ids, needed or not; the automagic CITEREF anchor id can be suppressed with |ref=none. This linter thing is an artefact of that decision.
    Trappist the monk (talk) 17:01, 15 December 2024 (UTC)[reply]

    Using 'First' and 'last' over 'author' parameter

    [edit]

    Template:Citation states that |first= and |last= are preferred over |author=. I recently edited some citations accordingly and was reverted. Is there a reason |first= and |last= are preferred, or is this indeed a non-issue? Random86 (talk) 00:42, 16 December 2024 (UTC)[reply]

    Names are not universally consistent either in publishing or the world at large—given authors are generally identified primarily by surname, one can make a clear case for explicit specification. Remsense ‥  00:47, 16 December 2024 (UTC)[reply]
    Also, separating them out is necessary if you want short footnotes ({{sfn}}) to link to the reference without a lot of extra hassle working around the lack of surnames. —David Eppstein (talk) 06:01, 16 December 2024 (UTC)[reply]
    Separate first/last names are generally better. As said above, {{sfn}} and the like work much better with last names. It also allows better web searching for a reference when the source website changes between using between "Dee Lightful", "D. Lightful" or "Lightful". However, sometimes it is hard for us English speakers to know which part of a non-English name is the family name and which is the personal name - eg, in Foo Ling Yu many Westerners don't realise that Foo is the family name (ie the last name in western terms, even though it is at the start of the name) and Ling-Yu is the personal part of her name (ie, the first name in western terms). There are also a few Western names that are hard (eg Douglas, Michael vs Michael, Douglas). Which is why the author field is allowed and does not produce errors - it is the ultimate fallback when you do not know the correct order. Which means that the reverter was quite wrong to revert you based on faulty logic.  Stepho  talk  08:01, 16 December 2024 (UTC)[reply]
    The parameters are perhaps misnamed as they really mean "given name" and "family name" regardless of name order, rather than first and last. But of course there are cultures (like say Iceland) where names don't work like that. —David Eppstein (talk) 08:25, 16 December 2024 (UTC)[reply]
    Well, what they really mean is "surname" and "not surname". Remsense ‥  08:27, 16 December 2024 (UTC)[reply]
    Difficult to generalise: Saddam Hussein al Tikriti: 2nd name father's "forename", no family name, normal (not informal) single-word name Saddam. Federico del Sagrado Corazón de Jesús García Lorca; normal Spanish surname García, but known, unusually, by mother's surname Lorca. María-José Pérez de Gómez, known sometimes as M-J Pérez, others as Sra [de] Gómez. Pol098 (talk) 11:58, 16 December 2024 (UTC)[reply]
    One can also use the aliases |given= and |surname= for these parameters. Kanguole 12:11, 16 December 2024 (UTC)[reply]