Help:Processing errors

From Linux Web Expert

Processing errors are stored with a special property starting in Semantic MediaWiki 2.4.0Released on an unknown date unknown versions of MediaWiki.1

The rationale for providing information on processing errors via special property "Processing error"Holds a "container" with further information about a problem and allows to explore and rectify it is to make issues more visible and to provide better assistance for rectifying mistakes made. It gets automatically filled with a label for the "container" holding further information about the respective problem, i.e. the description of the error and if applicable further information like improper values or failed queries or the error type. Click on the search icon search icon right next to the label for the processing error "container" to access it.

Special page "ProcessingErrorList"No description was provided. provides an easily accessible overview on processing errors and should be checked in regular intervals.

Example

See special page "Processing error list" on this very wiki to see a list of processing errors.

To query for processing errors, you can use the following syntax (in this example querying for processing errors in the property Telephone number):

{{#ask: [[Processing error.Has improper value for::Property:Telephone number]] 
 |?Processing error.Has improper value for
 |?Processing error.Processing error message
}}

Which result in:

 Has improper value for"Has improper value for" is a predefined property that tracks input errors for irregular value annotations and is provided by Semantic MediaWiki.Processing error message"Processing error message" is a predefined property containing a textual description of an error and is provided by Semantic MediaWiki.
$smwgInlineErrorsHas description
Telephone number
Property "Has description" (as page type) with input value "Sets whether warnings should be shown right after problematic [[Help:Annotation|annotations" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
URIs of the form "info@example.org" are not allowed.

See also

References

  1. ^ gh:smw:1293