Template talk:Citation Style documentation/author

list of params from 1 to 9
As it is now, we have:
 * Aliases: authorlink, authorlink1, author-link, author1-link; authorlink2, author2-link; ... authorlink9, author9-link.

Would it be clearer with one more in the series:


 * Aliases: authorlink, authorlink1, author-link, author1-link; authorlink2, author2-link; authorlink3, author3-link; ... authorlink9, author9-link?

What about a different format, like this:


 * Aliases: authorlink, authorlink1, author-link, author1-link; authorlink[n], author[n]-link (where [n] is 1 through 9)?

What about trying this vertically:


 * Aliases:
 * authorlink, authorlink1, author-link, author1-link;
 * authorlink2, author2-link;
 * authorlink2, author2-link;
 * authorlink9, author9-link
 * authorlink9, author9-link

Any other ideas? Coastside (talk) 20:13, 15 July 2012 (UTC)


 * Help talk:Citation Style 1. ---— Gadget850 (Ed)  talk 21:46, 15 July 2012 (UTC)


 * I understand that discussion, but I don't see why you are linking to it here. The question is how to handle aliasing of authorlink paramaters in this sub template. Are you saying that discussion answers the question?  If so, I'm confused, because it shows the way this was done when I originally added the authorlink parameters to this sub template on July 14 (they weren't documented prior to that).  So it seems we've come round in a circle.Coastside (talk) 23:13, 15 July 2012 (UTC)

Thought you might want to participate in that discussion.

This part does not make sense to me:

authorlink2, author2-link; ... authorlink9, author9-link

The semicolon separates a series, the ellipsis indicates an omission. I am going to make one more stab at this, then I have other things to do. ---— Gadget850 (Ed)  talk 12:21, 17 July 2012 (UTC)
 * The semicolon doesn't separate a series. It separates elements in a series. Everything within a set of semicolons is an alias of the same thing. In the above, authorlink2 and author2-link are aliases, which is why they are not separated by semicolons.  The semicolon sets off the next group of aliases.  The ellipses does represent an omission. The sequence [2] throuh [8] is omitted for brevity.Coastside (talk) 21:09, 17 July 2012 (UTC)
 * See WP:ELLIPSIS. You are using it to indicate a range; if these were pure numbers, then we would use an en dash per WP:DASH. They aren't numbers, thus is more appropriate. The semicolon is now moot. ---—  Gadget850 (Ed)  talk 22:16, 17 July 2012 (UTC)
 * I think this approach works well. Nice job.  Still one more problem, though.  In the line that describes usage for last, you list aliases:  last, author, authors, last1, author1.  In the line that describes usage for first, there is no list of aliases.  Shouldn't this include something that says aliases: first, first1? Coastside (talk) 00:02, 18 July 2012 (UTC)
 * Done. ---— Gadget850 (Ed)  talk 00:35, 18 July 2012 (UTC)
 * I'm happy with the result. Very clear.Coastside (talk) 09:35, 18 July 2012 (UTC)

Honorifics and suffixes
I was taught that citations should follow the form of the person's name, only inverted, with a comma, followed by a space, going where the space between the first and last names fell. Thus "Rev. Martin Luther King, Jr.", would become "King, Jr., Rev. Martin Luther"; however, the style manuals I've perused specifically state not to use honorifics unless they're needed to identify the person, so this would become "King, Jr., Martin Luther". In the case of Bill Graham, the rock promoter, versus Billy Graham, the minister, it might be appropriate to cite the latter as "Graham, Rev. Billy", but even that is not strictly necessary because of the difference in the first names they used.

What I'm proposing is that the usage documentation be modified to instruct editors to include any necessary suffixes (Jr., Sr., etc.) in the last field, and any necessary honorifics, such as "Rev.", in the first field; but titles such as "Dr." and other honorifics should be omitted. If it is important, for reasons of distinguishing an author, to include a title, it should be done in the formal style: "Welby, M.D., Marcus", rather than "Welby, Dr. Marcus", and certainly "Hill, Robert, Ph.D.", rather than "Dr. Robert Hill". Additionally, omitting unnecessary prefixes and suffixes surely must help when COinS metadata is extracted?

Also, do we need to include the case of an author that is known by a titled position, rather than a name, e.g., "Queen Elizabeth II"?

I apologize if this has been discussed before; I was away from Wikipedia for some time and missed a lot of conversations about stuff like this. Thanks!&mdash; D'Ranged 1  VTalk  01:11, 25 May 2014 (UTC)
 * Where it is impractical to rearrange a name into a last/first pair, the author parameter (and its numbered siblings) may be used. -- Red rose64 (talk) 07:59, 25 May 2014 (UTC)
 * I was perhaps too verbose; I object to instructing editors to put unnecessary titles in any field at all. If required, I think the documentation should instruct editors to put courtesy titles such as "Rev." in first and suffixes in last. Your comment didn't address the issues I was trying to raise; however, your comment would make an excellent addition to the documentation, just as you have written it. Thanks.&mdash; D'Ranged 1  VTalk  00:46, 26 May 2014 (UTC)
 * What is an example of "Where it is impractical to rearrange a name into a last/first pair"? And how can we encapsulate such examples into an exception or otherwise specific instruction? When it comes to things like "Jr[.]" and "III", these go at the end of first since they are not part of the surname and putting them in last will both pollute the surname data and mess with by-surname sorting. There is nothing complicated or confusing about ChenJaime C. Jr. We're doing this thousands and thousands of times (though, yes, there still mangled instances like Chen Jr.Jaime C. or Chen, Jr., Jaime C. or Chen, Jaime C., Jr. to still clean up).  — SMcCandlish ☏ ¢ 😼  04:14, 25 October 2023 (UTC)
 * And (to better address the OP) Wikipedia doesn't use "Dr.", "PhD", etc. – in running prose or in citations. Doing so in citations would be insanely cumbersome (not to mention it isn't expected in any major citation style), since for many topics in academia and the sciences virtually every author would have one or more such glommed-on titles before and/or after their names. It would probably also lead to a bunch of confusion and WP:OR, with people doing their own research to try to figure out what kind of degree someone has and whatnot, then whether it applied at the time of the work's publication, and so forth. What a mess. Nor do we use ecclesiastical honorifics like "Rev.", or role-based ones like "Rt. Hon." or "Esq.", or nobility ones like "B[ar]t." and "Duchess". We have no reason to do "King James I" instead of just "James I". For guideline material, see MOS:PEOPLETITLES and its subsections on professional, honorific, and other titles, both prefixed and postfixed. There seems to be something vaguely approaching a consensus that "Sir/Dame [Firstname]" is okay, but it is still usually omitted in citations, and I've seen disputes arise when it comes to sticking such a title onto a name when the publication pre-dated the honour, so it's just best avoided. It simply doesn't help the reader identify the source in any way, and that is the purpose of all the data in the citation to begin with. If you have the book title The Tartans of the Clans and Families of Scotland, the edition information "7th" and/or publication date "1964", and author name "Thomas Innes of Learney" (which should be coded Innes of LearneyThomas since "of Learney" is properly part of the surname in such a case, and should just be omitted in cases where it is not), then you have no use at all for "Sir" stuck onto "Thomas" in tracking this source down, and he was not in fact Sir Thomas when the book was first published in 1938, so that would just be ripe for unproductive dispute.  — SMcCandlish ☏ ¢ 😼  04:35, 25 October 2023 (UTC)