Tɛmplet:Failed verification

Diyila Dagbani Wikipedia

[failed verification]

Template documentation[view] [edit] [history] [purge]

The {{Failed verification}} tag is used when an editor tried to verify the information in an article with its sources, but failed to do so. The tag will categorise articles into Category:All articles with failed verification. This template is a self-reference and thus is part of the Wikipedia project rather than the encyclopedic content.

When to use[mali mi di yibu sheena n-niŋ]

Use this tag only if:

  • an inline citation to a source is given,
  • you have checked the source,
  • the source does not support what is contained in the article, and
  • despite the source not supporting the article, the source still contains useful information on the topic.

For example, if the article says that 26% of statistics are made up, and the source says that statistics are made up without giving a percentage, then that information has failed verification. If you are unable to fix the error, then you should tag the information as not matching the named source. If the discrepancy between the source and the article isn't obvious, then please explain the situation in detail on the talk page.

If the source given is an unreachable website, keep the source and mark it with {{Dead link}} instead. See Wikipedia:Link rot and WP:DEADREF for more information.

If no source is given, and you believe that an inline citation is necessary for that information, then use {{Citation needed}}.

If the source has absolutely no relevance to any part of the article, delete the reference and replace with {{Citation needed}}.

How to use[mali mi di yibu sheena n-niŋ]

Placement[mali mi di yibu sheena n-niŋ]

The template should be placed outside the reference (<ref> ... </ref>), within the article's text:

... 26% of statistics are made up.<ref>some alleged source for this</ref>{{Failed verification|date=Silimin gɔli May 2024}} Next sentence in the article.

Common form (with current date)[mali mi di yibu sheena n-niŋ]

{{Failed verification|date=Silimin gɔli May 2024}}

Optional parameters[mali mi di yibu sheena n-niŋ]

Link to the relevant section on the current page's talk page with:

|talk=Section title

or to a discussion elsewhere with:

|talkpage=Talk:Page name

or:

|talkpage=Talk:Page name#Section title

Add a brief note on the nature of the verification failure with:

|reason=A sentence here.

This is displayed as a mouse-over tooltip, and may be of use to later editors trying to resolve the verification issue. It must not contain any markup, like italics, links, etc., and any use of the double-quote character (") must be escaped, e.g. as &quot; – otherwise the tooltip will break. This is a limitation of HTML, not of the template.

Template data[mali mi di yibu sheena n-niŋ]

What is template data?[mali mi di yibu sheena n-niŋ]

Template data is the standardized description of a template, used by the default VisualEditor, the optional 2017 wikitext editor and other tools to improve the template-editing experience for the user. Both VisualEditor and the 2017 wikitext editor include a wizard to edit templates, but for the wizard to be most useful, it needs to present specific information to the user about each template, such as a short description of the template's purpose and its parameters. This information is codified formally (by any wiki editor) using template data.

Editing without template data[mali mi di yibu sheena n-niŋ]

Without template data, each parameter needs to be added manually when inserting a new template.

No information is provided about what the value of the parameter should be.

Editing with template data[mali mi di yibu sheena n-niŋ]

With template data, a list of supported parameters (and their description) is provided for the template.

Template data provides context for each parameter, and makes it much easier for users to modify templates.

Adding template data[mali mi di yibu sheena n-niŋ]

Anyone can help by adding template data to templates (particularly high-profile ones, such as infoboxes) so that they are easier to edit in VisualEditor. The following is a minimal example, placed on a template's documentation page:

<templatedata>{
  "description": "insert description here",
  "params": {
    "first parameter": {
      "label": "x",
      "description": "x",
      "type": "string",
      "suggested": true,
      "autovalue": "derived automatic value",
      "default": "default value",
      "required": false
    }
  }
}</templatedata>

You can also add or edit template data using a GUI, by pressing the following button which appears at the top of the edit page: Edit template data

The template data tutorial explains in detail how to add template data information to a template.

Adding suggested values for parameters[mali mi di yibu sheena n-niŋ]

The parameter property suggestedvalues lets you define a list of parameter values to be shown to VisualEditor users in a dropdown for easy selection. This can be done either directly in JSON or using the TemplateData editor with no coding required. Both methods are explained in detail below.

Once the values have been added to template data, the VisualEditor will display them in a combo box (a dropdown into which users can also enter a custom value). The user selects the desired value by clicking on it. If the list of values is long - for example, a list of a country’s states - the user can begin typing in the field, whereupon the list will be filtered to show only values containing the typed text. To change an entered value, the user must simply clear the field, and the full dropdown list will appear again. If the user needs a value not included in the list (for example, "message in a bottle") they can type it in manually.

For suggested values to be displayed in the VisualEditor, the parameter’s type must be set to one of the following options:

  • content
  • line
  • string
  • number
  • unknown
  • unbalanced wikitext.

Other types (file, page, template, user, date, boolean, URL) are not currently supported because they have special functionalities in the VisualEditor already (such as autocomplete) which would interfere with the dropdown menu for suggested values in the VisualEditor.

Adding suggested values for parameters in wikitext[mali mi di yibu sheena n-niŋ]

To add suggested values to any parameter type, add the new property “suggestedvalues” to the parameter in JSON. The “suggestedvalues” attribute must be a list of strings.

An example might look like this:

"media_type": {
	"label": "Type of media",
	"example": "Newspaper",
	"type": "string",
	"description": "In what medium was the article published?",
	"suggestedvalues": [
    	"Journal",
    	"Book",
    	"Newspaper",
    	"Magazine"
	]
}

Adding suggested values for parameters with the template data editor[mali mi di yibu sheena n-niŋ]

For the parameter types listed above, you can add suggested values using the template data editor.

Step 1. Click on "Manage TemplateData".
Step 2. Click on the name of the parameter you want to add suggested values to.
Step 3. If it’s not already, set the type of the parameter to one of the following: content, line, string, number, unknown or unbalanced wikitext. A new input field "Suggested values" will appear. If the parameter is already set to one of these types, the input field should already be visible.
Step 4. Type in the suggested value(s), including any spaces and special characters, and press enter to add it to the list.

Here you can see an example of how to add suggested values in the TemplateData editor.

Used templates[mali mi di yibu sheena n-niŋ]

See also[mali mi di yibu sheena n-niŋ]

The template will categorize articles into [[:Category:All articles with failed verification]].

Template parameters

ParameterDescriptionTypeStatus
Month and yeardate

Provides the month and year (e.g. 'January 2013', but not 'jan13').

Auto value
{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}
Stringsuggested
Current page's relevant talk sectiontalk

Title of the appropriate section of the current page's talk page, for further discussion of the verification failure (e.g. 'Section title').

Stringoptional
Another page's relevant talk sectiontalkpage

Title of the appropriate section of another page's talk page, for further discussion of the verification failure (e.g. 'Talk:Page name#Section title').

Stringoptional
Reasonreason

A brief note, displayed as a mouse-over tooltip. May be of use to later editors.

Stringoptional

Redirects[mali mi di yibu sheena n-niŋ]

See also[mali mi di yibu sheena n-niŋ]