Wikipedia:Did you know/Supplementary guidelines: Difference between revisions
→Other supplementary rules for the hook: Just a thought -- probably needs a more careful explanation. I'm thinking here of phrases like /de facto/ and so on |
thanks, Mi Shebeirach |
||
Line 27: | Line 27: | ||
*C8<span id="C8"></span>: The three ellipsis points and the space before "that" do not count towards the hook length. |
*C8<span id="C8"></span>: The three ellipsis points and the space before "that" do not count towards the hook length. |
||
*C9<span id="C9"></span>: No parentheses in the hook unless absolutely unavoidable. The ''(pictured)'' (or equivalent) for the image slot is an exception. |
*C9<span id="C9"></span>: No parentheses in the hook unless absolutely unavoidable. The ''(pictured)'' (or equivalent) for the image slot is an exception. |
||
*C10<span id="C10"></span>: Unless in common English usage (in which case simply use italics), enclose non-English text in {{t|lang}} e.g. |
*C10<span id="C10"></span>: Unless in common English usage (in which case simply use italics), enclose non-English text in {{t|lang}} (or {{t|transl}} for [[transliterated]] text) e.g. |
||
::<code><nowiki>... that Luciano Berio based '''''{{lang|it|[[Quattro versioni originali della "Ritirata notturna di Madrid"]]}}''''' on Boccherini's ''{{lang|it|[[Musica notturna delle strade di Madrid]]}}''?</nowiki></code> |
::<code><nowiki>... that Luciano Berio based '''''{{lang|it|[[Quattro versioni originali della "Ritirata notturna di Madrid"]]}}''''' on Boccherini's ''{{lang|it|[[Musica notturna delle strade di Madrid]]}}''?</nowiki></code> |
||
:In the example, ''it'' is the code for Italian. Other common codes are ''fr''=French, ''de''=German, ''la''=Latin, ''es''=Spanish; see [[List of ISO 639-1 codes]]. Note also the use of <code><nowiki>''</nowiki></code> for ''italics'' and <code><nowiki>'''''</nowiki></code> for '''''bold-italics'''''. |
:In the example, ''it'' is the code for Italian. Other common codes are ''fr''=French, ''de''=German, ''la''=Latin, ''es''=Spanish; see [[List of ISO 639-1 codes]]. Note also the use of <code><nowiki>''</nowiki></code> for ''italics'' and <code><nowiki>'''''</nowiki></code> for '''''bold-italics'''''. |
Revision as of 07:53, 30 December 2022
These are the supplementary guidelines (formerly called additional rules or unwritten rules) of Did You Know; that is, they are supplementary to Wikipedia:Did you know#DYK rules and Template talk:Did you know#Instructions for nominators. These rules provide detailed explanations for commonly asked questions regarding the basic rules. It is not necessary to be thoroughly familiar with every one of these rules, but if you have a question regarding interpretation of the basic rules, you will probably find the answer here.
These rules are meant (as said in G4 below) to describe consensus that has been reached among the DYK community through previous discussions of issues that have come up repeatedly.
Supplementary article length rules
- A1: The 1500-character minimum includes letters, numbers, punctuation, and spaces.
- A2: It includes only "readable prose"; it does not include the table of contents, section headers, image captions, block quotes, auxiliary sections such as "See also" and "References", citation callouts such as "[6]", tags such as "[citation needed]", and so on.
- A3: DYK qualifying characters: To count the number of characters in a piece of text, you may need to use a JavaScript extension like User:Dr pda/prosesize.js (instructions on the talk page), a free website like this, or an external software program that has a character-counting feature. Prosesize.js is the preferred counting method, and usually carries the most weight at DYK, because it counts only the prose as defined by Did you know rules, thus avoiding mistakes and providing an impartial settlement of disputed counting. The character counts indicated on "Revision history" pages are useless for DYK purposes.
- A4: Fivefold expansion is calculated from the last version of the article before the expansion began, no matter how bad it was (copyvios are an exception), no matter whether you kept any of it and no matter if it were up for deletion. This may be a bad surprise, but we don't have enough time and volunteers to reach consensus on the quality of each previous article.
- A5: New text seven days old or less can only count toward the 1500 character minimum in one article; if it is duplicated in other nominated new articles, it is ignored for the purpose of character count. If some of the text in a nominated article was copied from another Wikipedia article, and the copied text is more than seven days old, then the copied text must be expanded fivefold as if the copied text had been a separate article.[1]
Supplementary article link rules
- B1: The hook must link to a qualifying article. "Qualifying" refers to the many rules (including these supplementary guidelines) regulating the quality of that article.
- B2: Don't capitalize your article as it appears in the hook, just because that's how it appears in the article. Capitalize it only if the word would normally be capitalized, even if you weren't linking it.
- B3: Many hooks are better when the link is piped, and show on the Main Page that way. Disambiguated article titles like Gene Green (baseball) are always piped like this:
'''[[Gene Green (baseball)|Gene Green]]'''
.
Other supplementary rules for the hook
- C1: No redlinks, external links, redirects, or links to disambiguation pages in the hook.
- C2: Don't assume everyone worldwide knows what country or sport you're talking about.
- C3: A hook introducing more than one article is an exception to the hook length rule: subtract from the overall count the bolded characters for each additional new article beyond the first. If the result is 200 or less, the hook length is probably acceptable. Otherwise the hook may still be acceptable (on a case-by-case basis) if it is reasonably compact and readable.
- C4: No space before the question mark.
- C5: [moved]
- C6: If the subject is a work of fiction or a fictional character, the hook must involve the real world in some way.
- C7: If the hook uses a possessive apostrophe after the qualifying article, use {{`}} or {{`s}} to keep the bold text and the apostrophe distinct e.g. "... that John's house (etc)?" If the article is in italics (e.g. a ship's name), use the slightly different templates {{'}} or {{'s}} e.g. "... that HMS Hood's anchor (etc)?"
- C8: The three ellipsis points and the space before "that" do not count towards the hook length.
- C9: No parentheses in the hook unless absolutely unavoidable. The (pictured) (or equivalent) for the image slot is an exception.
- C10: Unless in common English usage (in which case simply use italics), enclose non-English text in {{lang}} (or {{transl}} for transliterated text) e.g.
... that Luciano Berio based '''''{{lang|it|[[Quattro versioni originali della "Ritirata notturna di Madrid"]]}}''''' on Boccherini's ''{{lang|it|[[Musica notturna delle strade di Madrid]]}}''?
- In the example, it is the code for Italian. Other common codes are fr=French, de=German, la=Latin, es=Spanish; see List of ISO 639-1 codes. Note also the use of
''
for italics and'''''
for bold-italics.
Other supplementary rules for the article
- D1: [deleted]
- D2: The article in general should use inline, cited sources. A rule of thumb is one inline citation per paragraph, excluding the lead, plot summaries, and paragraphs which summarize other cited content.
- D3: Sources should be properly labelled; that is, not under an "External links" header. References in the article must not be bare URLs (e.g., http://example.com or [1]), but can be automatically completed with the Reflinks tool or the reFill tool.
- D4: Wikipedia, including Wikipedia in other languages, is not considered a reliable source.
- D5: Articles nominated for deletion must go on hold until they have survived the deletion process.
- D6: The article is likely to be rejected for unresolved edit-warring or the presence of dispute tags. (Removing the tags without consensus does not count.) A list can be found at WP:DISPUTETAG. An orphan tag is not a dispute tag.
- D7: There is a reasonable expectation that an article—even a short one—that is to appear on the front page should appear to be complete and not some sort of work in progress. Therefore, articles which include unexpanded headers are likely to be rejected. Articles that fail to deal adequately with the topic are also likely to be rejected. For example, an article about a book that fails to summarize the book's contents, but contains only a bio of the author and some critics' views, is likely to be rejected as insufficiently comprehensive.
- D8: "Seven days old" means seven days old in article space. You may spend as long as you want writing/expanding an article on a user subpage; the seven days start when you move it into article space. Such moves are often overlooked when enforcing the seven-day rule, so we may need a reminder. But if you merge the edit history when you move, we might not see that you moved it.
- D9: The "seven days old" limit can be extended for a day or two upon request. If the nominator is new to DYK, a seven-day extension may be allowed.
- D10: If an article contradicts an existing article, the contradiction should be resolved one way or the other before the article is approved.
- D11: If an article otherwise qualifies for DYK, it is not a stub, and any stub tag should be removed before promotion.
- D12: Multiple sources are generally preferred, though more leeway may be given for more obscure topics.
- D13: To some extent, DYK approval is a subjective process. No amount of studying rules, almost-rules, and precedents will guarantee approval; nor will violating any rule guarantee disapproval. Just because an unfamiliar criterion is not listed does not mean a nomination cannot be disqualified. The subjective decision might depend on an attempt to circumvent the details of the rules, especially if the attempt does not address the underlying purpose of improving the hook and article.
"Rules" sometimes invoked but lacking a consensus
- E1: Does the first word always have to be "that"?
- E2: Can there be multiple sentences in a hook?
- E3: [deleted]
- E4: Occasionally someone objects to linking an unfamiliar word to Wiktionary on the front page, but such objections have always been overruled.
- E5: Do the 11 characters in " (pictured)" or the 27 characters in " (specific object pictured)" (i.e. including an introductory space) count towards the 200 character limit?
Rules listed elsewhere but often overlooked
- F1: There must be a space after the ellipsis.
- F2: The link to your article should be in bold (e.g.,
'''[[Manx cat]]'''
). - F3: The hook should end with a question mark.
- F4: For a hook with an accompanying picture, the string (pictured) is all in italics, including the parentheses.
- F5: For titles or words with dashes see WP:DASH.
- F6: For hooks containing numbers see MOS:NUM#Numbers as figures or words.
- F7: Make sure your article title conforms with Wikipedia:Manual of Style (titles)
- F8: A 'new' article is no more than seven days old. This does not include articles split from older articles, although an article sufficiently expanded from a section of an older article can be a fivefold expansion. The word "fork" is sometimes used to mean Wikipedia:Splitting.
- F9: Fix redirects in hooks – see MOS:DYKPIPE.
- F10: WP:NOTADVERTISING
Other recurring issues
- G1: [deleted]
- G2: To calculate fivefold expansion:
- Count the characters in the prose-only portion of the current version.
- On the history screen, access the pre-expansion version of the article. You can find it by clicking on the timestamp directly before the first expanding edit.
- Divide the prosesize of the current revision by the prosesize of the historical revision. The resulting number should exceed five in a qualifying article.
- G3: [deleted]
- G4: These supplementary guidelines are intended to describe the consensus, not to prescribe it.
Rules for evaluating other people's hooks and articles
- H1: You don't have to be an administrator or a DYK regular to comment on a hook, to use a symbol such as or , or even to edit one of the preparation areas. However, the judgments of regulars are less likely to be challenged.
- H2: You're not allowed to approve your own hook or article, nor may you review an article if it's a recently listed Good Article that you either nominated or reviewed for GA (though you can still nominate it for DYK). DYK novices are strongly discouraged from confirming articles that are subject to active arbitration remedies, as are editors active in those areas. Use common sense here, and avoid even the appearance of conflict of interest. A valid DYK nomination will readily be confirmed by a neutral editor.
- H3: If the article is sourced entirely to offline or foreign-language sources in such a way that you cannot verify that the subject of the article actually exists or that contentious material is accurate, don't verify the article; instead, leave a note explaining your difficulty below the hook. This will alert other users to the fact that the article lacks basic verifiability and a discussion can then be had as to whether or not to promote it.
- H4: Where a nomination offers more than one new or expanded article, an article-for-article quid pro quo (QPQ) is required for each nominated article. The consensus is that hook-for-hook reviewing is not acceptable in case of multiple nominations. As soon as a new nominator's hook includes articles beyond their fifth nomination of an article for DYK, each of those requires a separate QPQ review.
Rules of thumb for preparing updates
Users are encouraged to help out by preparing updates in the seven prep areas. Promoting your own articles is generally discouraged, and promoting your own articles before they have been independently verified is not allowed. Updates should be filled from the approved nominations page, including those being held for specific dates in the Special occasion holding area at the top of the page.
Here are a few rules of thumb for preparing updates:
- J1: Users are encouraged to help out by preparing updates in the seven prep areas; you don't have to be an administrator. However, it's a no-no to promote a hook you wrote, or a hook for an article you created, nominated, or reviewed. (Ask for assistance at WT:DYK if one of "your" hooks has been waiting a long time for promotion.)
- J2: Choose approved hooks ( or ). These will be on the approved nominations page, including the special occasions holding area at the top of that page.
- J3: The accepted length of an update is a fixed number that changes on occasion, usually six, seven or eight hooks (currently nine). This is not an absolute rule but it is the currently accepted standard length for an update, depending on page balance, so the items selected fit with whatever else is on the Main Page at that time. Check by using the links on the prep page you're working on. For example, for Prep 1: "See how this template appears on both today's Main Page and tomorrow's Main Page." to see if the DYK template balances the rest of the main page layout.
- J4: Make sure to choose a varied selection – don't choose half a dozen people hooks, for example, or a bunch of hooks about one particular country or topic. Variety is the spice of life. (However, see the following clause for an important qualification).
- J5: Because of the disproportionate number of US-related hooks and biography hooks, it is usually appropriate to have roughly 50% of hooks in a given update on both US and biography topics, but no more than half. That is to say, in an eight-hook update you should have roughly four hooks per update on US topics, and four on biography. These are not mutually exclusive, for example if you have two US bio hooks that would count as both two US hooks and two bio hooks. Note that "roughly 50%" means just that – this is not an absolute; you can have less of either if there are not many currently available such hooks to choose from on the Suggestions page. Note however that as a general rule you should almost never have more than 50% of hooks on US, biography or any other topic.
- J6: Also, mix your hooks up. Try to avoid having two hooks of the same general type next to one another in the update (for example, two US hooks or two bio hooks together). Putting several US hooks in a row looks US-centric, so intersperse US hooks with non-US ones. In the same spirit, try to avoid putting two bio hooks together, or two cooking hooks, two railroad hooks, whatever.
- J7: Avoid awkward juxtapositions. For example, don't put a sad hook next to a funny one; it looks incongruous and jerks the reader uncomfortably from one emotion to another.
- J8: Hooks on the approved nominations page that include images often get verified first. Users sometimes then just go and grab a bunch of the nearest verified hooks for the preparation areas, which can often include several of these verified picture hooks. Not every submitted picture can be featured in the picture slot of course, but since only one picture can be featured per update, try to leave the good picture hooks behind for another update if you possibly can.
- J9: A funny or quirky hook in the last (bottom) slot rounds out an update nicely.
- J10: Don't be afraid to ruthlessly trim hooks of extraneous information and clauses. A lot of people who submit hooks tend to overestimate the amount of information that is required, but the end result is a hook that has too much information and is difficult to process. In general, the shorter and punchier the hook, the more impact it has. As it says on the Suggestions page, the 200-character limit is an outside limit not a recommended length—the ideal length is probably no more than about 150–160 chars. Note however that some hooks cannot be reduced in length without losing essential information, so don't assume that every hook that is 200 characters long requires trimming.
- J11: [moved]
- J12: Make sure to include the article name, date, nominator, and creator under the "Credits" section to allow others to return it if a dispute arises.
- J13: It is the promoter's responsibility to make sure all review issues have been resolved, that the hook is verified by sourcing within the article. The promoter acts as a secondary verification that the nomination was reviewed properly. The article should not have any problem templates on it at the time of promotion.
- J14: When verifying the sourcing for a hook, there are some common pitfalls to avoid:
- Check that when viewing the source for a fact (not a quote), the source states this fact in their own voice. If they're attributing to someone else, that might mean they're not willing to say it in their own voice. Make sure you know who or what this fact is ultimately sourced to, and judge whether or not it is trustworthy.
- Make sure that quotes used in the hook have in-line attribution in the article. If there isn't attribution, the hook would fall afoul of MOS:WEASEL.
- Opinion pieces are not reliable for facts, even when published by reputable organizations.
Notes
- ^ For discussion removing the 2X BLP criteria, please see Archive: Feb 26, 2018 - Remove the 2x BLP criterion