Open main menu

Changes

1,830 bytes added ,  17:12, 14 May 2020
no edit summary
{{Feature
|image=Namespace MediaWiki.svg
|imgdesc=Namespaces
|title=
}}
{{#set:feature description = Using the namespaces feature of MediaWiki, you can setup areas that segregate content. Although MediaWiki is not a CMS designed for roles and access permissions, it nevertheless can be useful to segregate content in a wiki that should be 'nearby', but not in the same space. }}
{{#set:feature notes = }}
{{#set:feature tests = }}
{{#set:feature examples = setup a 'private' namespace which is access restricted so that only a certain class of user can access that space. Because MediaWiki is not a CMS, pages in the private namespace would still show up in a search. However, the content would only be accessible to the group you set it to. So, you wouldn't use this feature to setup a space reserved for the 'human resources' group, and then draft a 'layoff' announcement because although nobody outside the HR group could read the announcement, it's existence would be knowable. On the other hand, 'status-update' wouldn't give too much of a clue about what the contents were. }}
There is a short list of namespaces that are built into this wiki
[[Special:PrefixIndex]]is a friendly interface to the namespaces. This [{{SERVER}}{{SCRIPTPATH}}/api.php?action=query&meta=siteinfo&siprop=namespaces&formatversion=2 api query] is the machine method for looking at this wiki's namespaces.
You can find out more about them in the [[w:Wikipedia:Namespace]] page.
E.g.
<nowiki>[[Category:Development]]</nowiki> will link to the page 'Development' inside the Category namespace. Built-in namespaces are also tied to built-in functionality so for example an 'Image' link inserts that image into the page. And the 'Category' namespace is tied to the functionality of tagging an article as belonging to the category. So, to actually '''link''' to the category (or image) you would place a ''':''' (colon) before the prefix. e.g. <nowiki>[[:Category:Development]]</nowiki>
== Interwiki Links Usage ==The [http[MW:BlueSpice|BlueSpice]] distribution uses the [[MW://meta.wikimedia.org/wiki/HelpExtension:Interwiki_linking Interwiki LinksNSFileRepo]] are another use of CURIEs to make it very easy extension to link semi-protect files according to other important/useful websites without so much effortnamespace.
E.g.<nowiki>[[google:foo]]</nowiki> will produce a link to the Google results page In QualityBox, we're interested in creating an extension called Level10 that would allow for a search editing content in 10 separate namespaces for 'foo' like this [[google:foo]] (Note that the Interwiki prefix is not case sensitive, so Google works as well as gOOgle10 separate levels of focus. Lowercase The idea is preferred. Note too that roughly the following:# concept - term only - defined in one sentence# marketing - in words most people can understand# user - in order words relevant to suppress wiki usage# design / layout / interface - how the display of the namespace concept is manifest, or manipulated in the link, you'll want to use UI# developer - how the pipe syntax concept is related to format code or implemented in code# test - how the link text:concept can be tested across updates or new feature implementations<nowiki>[[google:foo|search for 'foo' on Google]]</nowiki> results # demo - where can the concept be seen in this: [[google:foo|search for 'foo' on Google]]action# admin - how the concept can be manipulated by a sysop in the UI, or consoleThere # system - how the concept is a long list of convenient Interwiki Links available to you (displayed by implemented at the Interwiki extension): [[Special:Interwiki]]system component level - dependencies or alternatesIf you run your own mediawiki installation, get # architecture - how the concept fits with the Interwiki extension. It makes it so simple overall system architectureViewing content in any level would automatically include links to add more short-cuts like 'w' for wikipediathe other levels.
== Alternatives ==
An alternative to namespaces is to setup a "wiki farm" where each group or product, or purpose has it's own individual wiki, all running on a single software instance to reduce administrative overhead.
Directly in the database, you can look at the 'interwiki' table:== See Also ==<source lang="mysql">SELECT iw_prefix, iw_url FROM interwiki </source>[[Interwiki links]]
[[Category:Wiki]]