Difference between revisions of "Manual:Namespace"
[unchecked revision] | [quality revision] |
(Tag: Visual edit) |
(Tag: Visual edit) |
Contents
- 1 What are namespacesis a namespace?
- 2 BlueSpice Standard Namespaces
- 3 Calling pages in the namespace
- 4 Create own namespaces 5 Organize
- Characteristics of a namespace
- 3 Reasons for using namespaces
- 4 BlueSpice standard namespaces
- 5 Accessing pages in a namespace
- 6 Creating a new namespace
- 7 Organizing content without namespaces 6 All
- 8 Viewing all pages of a namespace
What is a namespace?[edit | edit source]
Namespaces are used to divide a wiki into different areas.
Namespaces structure and organize a wiki for these purposes:
Rights management: To assign content to different rights and rolesA namespace defines an area in a wiki. You can recognize a namespace by the namespace prefix in the page title:
<namespace>:Page title
In a wiki, you will find predefined namespaces. In addition, wiki administrators can create custom namespaces as needed.
There are certain aspects of namespaces that are important to consider before creating a namespace. It is therefore important to understand the characteristics of namespaces and the reasons for using a custom namespace.
Characteristics of a namespace[edit | edit source]
- Rights management : Each namespace can contain its own user rights/roles assignments. However, we recommend flat user hierarchies for wikis.
- Search function : Search can be limited to individual namespaces.
- Design : Namespaces can be styled differently.
- Flat structure :Namespaces cannot contain other namespaces
- One namespace per page : The same page name in a different namespace creates a new page.
-
Special namespaces:
- Main (Pages) - No namespace prefix in page titles
- Special pages (Special)
- Images (File)
- Documents (Media)
- Discussions (Talk)
Reasons for using namespaces[edit | edit source]
- Rights management: To assign different user permissions to separate content. For example, a company's HR department can use its own namespace to grant only Human Resources personnel access to the pages in that namespace a major . Here, rights management is the main reason for creating namespaces. However, flat hierarchies are recommended for wikis.
- Search function: To exclude pages and files in the wiki from the search.
- Design: To format pages in different wiki areas differently.
We often take use the example of cupboards to make clear the principle of namespaces. There are shelves where and everyone can look inside at them and work on something. There are glass cupboards with a lock that you can look into, but not everyone can handle everything. There only some people have the key to change the contents. Then there are closed wooden cabinets with lock, then locks and only selected people can look inside and work on itin them. And every cupboard each of these cupboards can look different.
differently.
Note: While users cannot view the pages or files in a namespace for which they have no access rights, they will still see the pages and files listed on the wiki's special pages. They will also see the page names in the search results if the namespace has not been excluded from the search.
BlueSpice standard namespaces[edit | edit source]
Among other things, BlueSpice uses, among others, the 15 standard and the two so-called pseudo namespaces from MediaWiki:
ID | Namespace | 'Function' | |
---|---|---|---|
Media | Pseudo-namespace for uploaded images and files. Will be replaced by path of the files. | ||
special | Pseudo-namespace for special pages. | ||
0 | (pages) | These are given without a prefix. | |
1 discussion | Talk | talk page. Is created in addition to each article (also in the following namespaces) to speak about its contents. Additional tab (+). | |
2 user | User | User page. Will be created for every logged in user. | |
3 | Benutzer_Diskussion | See Discussion. User talk | Cf. talk |
4 | [Wiki-Name] | Information about the wiki or the current project. Here: BlueSpice. | |
5 | [Wiki-Name]_discussion Talk | See DiscussionCf. talk | |
6 file | Image | Description of a picture and other files. Is automatically supplemented with version information and information about the occurrence of the file | |
7 | DateiFile_Discussion Talk | See DiscussionCf. talk | |
8 | MediaWiki | system messages. A complete list can be found under Special: AllMessages. Can only be changed by registered users. | |
9 | MediaWiki_Discussion Talk | See DiscussionCf. talk | |
10 template | Template | Templates can be integrated into other pages. | |
11 | VorlageTemplate_Diskussion talk | See DiscussionCf. talk | |
12 | Help | Help pages describe how to perform actions in the wiki. No clear separation from the [wiki name] namespace. | |
13 | HilfeHelp_Discussion talk | See DiscussionCf. talk | |
14 category | Category | Pages can be assigned to categories, which are then accessible in this namespace. | |
15 | KategorieCategory_Discussion talk | See DiscussionCf. talk |
Standard namespace: A page is assigned to the (pages) "Main" namespace, as long as no other information namespace is givenspecified.
Pseudo namespaces: The two pseudo namespaces (mediumMedia, specialSpecial) are used like normal namespaces, but neither pages can be created nor existing pages changedyou cannot edit them or add pages to them.
Most pages in the namespaces are created automatically:
- Special pages are generated by the system during installation.
- Media and image pages are created by uploading a during file uplad.
- User pages are created whenever a user acts on the wiki.
- Discussion pages are also created with the respective corresponding pages.
This leaves only the
pages in the main namespace (pagesdefault namespaces (Main), [wiki name],
templateTemplate,
help and category thatHelp and Category namespaces where pages can be freely created.
The pages for the respective categories can be requested via the special page "All pages".Note: {{{Note text}}}
Note: In the default MediaWiki, the names of these areas are "hard-coded". This means that they have been set in the source code of the MediaWiki and cannot be changed by users.
Accessing pages in a namespace[edit | edit source]
To address access or create a page in a specific namespace, its name is simply placed in front of the page title and separated by a colon:
[[Setup:Installation|]]
In the example, the pipe symbol (straight line) was also added. It has the effect that the name space can not namespace won't be displayed when for the link is displayed or another text can be entered, which facilitates readabilitylabel.
If you specify provide a namespace that is not known to the wiki, the page is created in the standard namespace Main. The portion of the reference specified as the namespace is then added to the title of the item instead and is not recognized as an area a namespace label.
One namespace per page: A page can only be assigned to a single namespace. The same page name in a different namespace creates a new page.
Flat structure: Namespaces are only available on one level. H. a namespace can not have child namespaces.
Search for contents in namespaces: In the search, the scope to be included can be limited to individual namespaces.
Create own namespacesCreating a new namespace[edit | edit source]
Even creating your own namespaces is possible in MediaWiki without BlueSpice only with access to the scripts.
In BlueSpice you You can create additional namespaces using namespace management.
Organize
by using the Namespace manager under Global actions > Management > Namespace manager. The menu item "Category manager" loads the page Special:NamespaceManager
.
Organizing content without namespaces[edit | edit source]
However, one If you simply want to group pages in your wiki without the need for controlling access rights, you can use the syntax of the namespaces to help simulate an area a namespace in the namespace Main by prefixing . Simply prefix the pages of a desired area that belong to a group with a colon. The general benefits of using namespaces are preserved. So name and a colon. If no namespace with this name exists, the prefix simply becomes part of the page name.
That way, it is possible to use pages with the same name in different "rooms" the main namespace and thus let different groups work on a wikicontent "sets". Since these own "namespace" prefixes are part of the page name, you can now display all pages in a "simulated namespace " by searching for the prefix in the search field.
Since you can also organize pages across with categories and subpages, you should start by understanding planning how you would like to manage organize the content in your wiki.
You After installing your wiki, you can visualize this for example with the BlueSpice draw.io Plugin directly in BlueSpice your wiki and discuss it with your team.
All Viewing all pages of a namespace[edit | edit source]
The display of You can view all pages of in a namespace is possible:
- Go to the Special
- page "All Pages"
- Leave the input field empty
- Select
Template:Box Links S: namespace
- a namespace from the Namespace drop-down menu
-
Click "Go"
Related info
==What are namespaces?== '''Namespaces''' are used to divide a wiki into different areas. Namespaces structure and organize a wiki for these purposes: *'''Rights management:''' To assign content to different rights and roles. For example, a company's HR department can use its own namespace to grant only Human Resources personnel access to the pages in that namespace a major reason for creating namespaces. However, flat hierarchies are recommended for wikis. *'''Search function:''' To exclude pages and files in the wiki from the search. *'''Design:''' To format pages in different wiki areas differently. We often take the example of cupboards to make clear the principle of namespaces. There are shelves where everyone can look inside and work on something. There are glass cupboards with a lock that you can look into, but not everyone can handle everything. There are closed wooden cabinets with lock, then only selected people can look inside and work on it. And every cupboard can look different. ==BlueSpice Standard Namespaces== Among other things, BlueSpice uses the 15 standard and two so-called pseudo namespaces from MediaWiki: <br /> {| class="wikitable tablefullwidth" |- !ID !|'''Namespace''' ! |'' 'Function' '' |- | ||Media ||Pseudo-namespace for uploaded images and files. Will be replaced by path of the files. |- | ||special ||Pseudo-namespace for special pages. |- |0 ||(pages) ||These are given without a prefix. |- |1 ||discussion ||talk page. Is created in addition to each article (also in the following namespaces) to speak about its contents. Additional tab (+). |- |2 ||user ||User page. Will be created for every logged in user. |- |3 ||Benutzer_Diskussion ||See Discussion. |- |4 ||[Wiki Name] ||Information about the wiki or the current project. Here: BlueSpice. |- |5 ||_discussion ||See Discussion. |- |6 ||file ||Description of a picture and other files. Is automatically supplemented with version information and information about the occurrence of the file |- |7 ||Datei_Discussion ||See Discussion. |- |8 ||MediaWiki ||system messages. A complete list can be found under Special: AllMessages. Can only be changed by registered users. |- |9 ||MediaWiki_Discussion ||See Discussion. |- |10 ||template ||Templates can be integrated into other pages. |- |11 ||Vorlage_Diskussion ||See Discussion. |- |12 ||Help ||Help pages describe how to perform actions in the wiki. No clear separation from the [wiki name] namespace. |- |13 ||Hilfe_Discussion ||See Discussion. |- |14 ||category ||Pages can be assigned to categories, which are then accessible in this namespace. |- |15 ||Kategorie_Discussion ||See Discussion. |} is a namespace?== A '''namespace''' defines an area in a wiki. You can recognize a namespace by the namespace prefix in the page title: <code><namespace>:Page title</code> In a wiki, you will find predefined namespaces. In addition, wiki administrators can create custom namespaces as needed. There are certain aspects of namespaces that are important to consider before creating a namespace. It is therefore important to understand the characteristics of namespaces and the reasons for using a custom namespace. ==Characteristics of a namespace== <section begin="training" /><section begin="slide-namespace" /> *'''Rights management'''<section end="slide-namespace" /> : Each namespace can contain its own user rights/roles assignments. However, we recommend flat user hierarchies for wikis. <section begin="slide-namespace" /> *'''Search function'''<section end="slide-namespace" /> : Search can be limited to individual namespaces. <section begin="slide-namespace" /> *'''Design'''<section end="slide-namespace" /> : Namespaces can be styled differently. <section begin="slide-namespace" /> *'''Flat structure'''<section end="slide-namespace" /> :Namespaces cannot contain other namespaces <section end="training" /> *'''One namespace per page'''<section end="slide-namespace" /> : The same page name in a different namespace creates a new page. *'''Special namespaces:''' **Main (Pages) - No namespace prefix in page titles **Special pages (Special) **Images (File) **Documents (Media) **Discussions (Talk)<section end="training" /> ==Reasons for using namespaces== *'''Rights management:''' To assign different user permissions to separate content. For example, a company's HR department can use its own namespace to grant only Human Resources personnel access to the pages in that namespace. Here, rights management is the main reason for creating namespaces. However, flat hierarchies are recommended for wikis. *'''Search function:''' To exclude pages and files from the [[Manual:Extension/BlueSpiceExtendedSearch|search]]. *'''Design:''' To format pages in different wiki areas differently. We often use the example of cupboards to make clear the principle of namespaces. There are shelves and everyone can look at them and work on something. There are glass cupboards with a lock that you can look into, but only some people have the key to change the contents. Then there are closed wooden cabinets with locks and only selected people can look inside and work in them. And each of these cupboards can look differently. {{Box Note|boxtype=note|Note text=While users cannot view the pages or files in a namespace for which they have no access rights, they will still see the pages and files listed on the wiki's special pages. They will also see the page names in the search results if the namespace has not been excluded from the search.}} ==BlueSpice standard namespaces== BlueSpice uses, among others, the 15 standard and the two so-called pseudo namespaces from MediaWiki:<br /> {{:Mediawiki_namespaces}} '''Standard namespace:''' A page is assigned to the (pages)"Main" namespace, as long as no other informationnamespace is givenspecified. '''Pseudo namespaces:''' The two pseudo namespaces (medium, specialMedia, Special) are used like normal namespaces, but neither pages can be created nor existing pages changedyou cannot edit them or add pages to them. Most pages in the namespaces are created automatically: *Special pages are generated by the system during installation. *Media and image pages are created by uploading a file during file uplad. *User pages are created whenever a user acts on the wiki. *Discussion pages are also created with the respectivecorresponding pages *. This leaves only the pages in the main namespace (pages), [wiki name], template, help and category that can be freely created. The pages for the respective categories can be requested via the special page "All pages". <br /> {{Box_Note|Note Textdefault namespaces ''(Main)'', ''[wiki name]'', ''Template'', ''Help'' and ''Category'' namespaces where pages can be freely created. {{Box_Note|Note text =In the default MediaWiki, the names of these areas are "hard-coded". This means that they have been set in the source code of the MediaWiki and can not cannot be changed by the users.}} ==Calling pages in the namespace== To address|boxtype=note}} ==Accessing pages in a namespace== To access or create a page in a specific namespace, its name is simply placed in front of the page title and separated by a colon: <code><nowiki>[[Setup:Installation|]]</nowiki></code> In the example, the pipe symbol (straight line) was also added. It has the effect that the name space can not be displayed when the link is displayed or another text can be entered, which facilitates readability. If you specifynamespace won't be displayed for the link label. If you provide a namespace that is not known to the wiki, the page is created in the standard namespace Main. The portion of the reference specified as the namespace is then added to the title of the item instead and is not recognized as an areaa namespace label. <br /> '''One namespace per page:''' A page can only be assigned to a single namespace. The same page name in a different namespace creates a new page. '''Flat structure:''' Namespaces are only available on one level. H. a namespace can not have child namespaces. '''Search for contents in namespaces:''' In the search, the scope to be included can be limited to individual namespaces. ==Create own namespaces== Even creating your own namespaces is possible in MediaWiki without BlueSpice only with access to the scripts. In BlueSpice you can create additional namespaces using namespace management. ==Organize content without namespaces== However, one ==Creating a new namespace== You can create additional namespaces by using the Namespace manager under Global actions > Management > [[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]. The menu item "Category manager" loads the page <code>Special:NamespaceManager</code>. ==Organizing content without namespaces== If you simply want to group pages in your wiki without the need for controlling access rights, you can use the syntax of the namespaces to help '''simulate an areaa namespace in the namespace Main''' by prefixing. Simply prefix the pages of a desired area with a colon. The general benefits of using namespaces are preserved. So that belong to a group with a name and a colon. If no namespace with this name exists, the prefix simply becomes part of the page name. That way, it is possible to use pages with the same name in different "rooms" the main namespace and thus let different groups work on a wikicontent "sets". Since these own "namespace" prefixes are part of the page name, you can now display all pages in a "simulated namespace" by searching for the prefix in the search field. Since you can also organize pages acrosswith categories and subpages, you should start by understandingplanning how to manageyou would like to organize the content in your wiki. You can visualize this for example After installing your wiki, you can visualize this with the BlueSpice draw.io Plugin directly in BlueSpice your wiki and discuss it with your team. ==All Viewing all pages of a namespace== The display ofYou can view all pages ofin a namespace is possible: *[[Special:AllPages|Special Page "All Pages"]] *Leave input field empty *Select namespace and click "Apply"<br /> {{Box_Links | Topic1 =[[Reference: NamespaceCss|NamespaceCSS]] | Topic2 =[[Namespace Management|Namespace Management]] | Topic3 = | Topic4 = }} [[en: {{FULLPAGENAME}}]] [[S: namespace]]: #Go to the Special page "All Pages" #Leave the input field empty #Select a namespace from the Namespace drop-down menu #Click "Go"<br /> {{Box_Links-en |Topic1 =[[Manual:Extension/BlueSpiceNamespaceCSS|Namespace CSS manager]] |Topic2 =[[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]}} [[en: {{FULLPAGENAME}}]] [[de:Das_Konzept_der_Namensräume]] <br /> [[Category:Training]] [[Category:Term]] [[Category:Concept]]
(35 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | ==What | + | ==What is a namespace?== |
− | |||
− | + | A '''namespace''' defines an area in a wiki. You can recognize a namespace by the namespace prefix in the page title: | |
− | + | <code><namespace>:Page title</code> | |
− | + | ||
− | + | In a wiki, you will find predefined namespaces. In addition, wiki administrators can create custom namespaces as needed. | |
+ | |||
+ | There are certain aspects of namespaces that are important to consider before creating a namespace. It is therefore important to understand the characteristics of namespaces and the reasons for using a custom namespace. | ||
+ | ==Characteristics of a namespace== | ||
+ | <section begin="training" /><section begin="slide-namespace" /> | ||
− | + | *'''Rights management'''<section end="slide-namespace" /> : Each namespace can contain its own user rights/roles assignments. However, we recommend flat user hierarchies for wikis. | |
+ | <section begin="slide-namespace" /> | ||
− | == | + | *'''Search function'''<section end="slide-namespace" /> : Search can be limited to individual namespaces. |
− | + | <section begin="slide-namespace" /> | |
− | < | + | *'''Design'''<section end="slide-namespace" /> : Namespaces can be styled differently. |
+ | <section begin="slide-namespace" /> | ||
− | + | *'''Flat structure'''<section end="slide-namespace" /> :Namespaces cannot contain other namespaces | |
− | + | <section end="training" /> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | *'''One namespace per page'''<section end="slide-namespace" /> : The same page name in a different namespace creates a new page. | ||
+ | *'''Special namespaces:''' | ||
+ | **Main (Pages) - No namespace prefix in page titles | ||
+ | **Special pages (Special) | ||
+ | **Images (File) | ||
+ | **Documents (Media) | ||
+ | **Discussions (Talk)<section end="training" /> | ||
− | + | ==Reasons for using namespaces== | |
− | ''' | + | *'''Rights management:''' To assign different user permissions to separate content. For example, a company's HR department can use its own namespace to grant only Human Resources personnel access to the pages in that namespace. Here, rights management is the main reason for creating namespaces. However, flat hierarchies are recommended for wikis. |
+ | *'''Search function:''' To exclude pages and files from the [[Manual:Extension/BlueSpiceExtendedSearch|search]]. | ||
+ | *'''Design:''' To format pages in different wiki areas differently. | ||
− | |||
− | + | We often use the example of cupboards to make clear the principle of namespaces. There are shelves and everyone can look at them and work on something. There are glass cupboards with a lock that you can look into, but only some people have the key to change the contents. Then there are closed wooden cabinets with locks and only selected people can look inside and work in them. And each of these cupboards can look differently. | |
− | + | ||
− | + | {{Box Note|boxtype=note|Note text=While users cannot view the pages or files in a namespace for which they have no access rights, they will still see the pages and files listed on the wiki's special pages. They will also see the page names in the search results if the namespace has not been excluded from the search.}} | |
− | |||
− | |||
− | {{ | ||
− | == | + | ==BlueSpice standard namespaces== |
− | + | BlueSpice uses, among others, the 15 standard and the two so-called pseudo namespaces from MediaWiki:<br /> | |
+ | {{:Mediawiki_namespaces}} | ||
− | + | '''Standard namespace:''' A page is assigned to the "Main" namespace, as long as no other namespace is specified. | |
+ | '''Pseudo namespaces:''' The two pseudo namespaces (Media, Special) are used like normal namespaces, but you cannot edit them or add pages to them. | ||
− | + | Most pages in the namespaces are created automatically: | |
− | + | *Special pages are generated by the system during installation. | |
+ | *Media and image pages are created during file uplad. | ||
+ | *User pages are created whenever a user acts on the wiki. | ||
+ | *Discussion pages are also created with the corresponding pages. | ||
− | ''' | + | This leaves only the default namespaces ''(Main)'', ''[wiki name]'', ''Template'', ''Help'' and ''Category'' namespaces where pages can be freely created. |
+ | {{Box_Note|Note text =In the default MediaWiki, the names of these areas are "hard-coded". This means that they have been set in the source code of the MediaWiki and cannot be changed by users.|boxtype=note}} | ||
+ | ==Accessing pages in a namespace== | ||
+ | To access or create a page in a specific namespace, its name is simply placed in front of the page title and separated by a colon: | ||
− | + | <code><nowiki>[[Setup:Installation|]]</nowiki></code> | |
− | + | In the example, the pipe symbol (straight line) was also added. It has the effect that the namespace won't be displayed for the link label. | |
− | + | If you provide a namespace that is not known to the wiki, the page is created in the standard namespace Main. The portion of the reference specified as the namespace is then added to the title of the item instead and is not recognized as a namespace label. | |
− | |||
− | + | ==Creating a new namespace== | |
+ | You can create additional namespaces by using the Namespace manager under Global actions > Management > [[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]. The menu item "Category manager" loads the page <code>Special:NamespaceManager</code>. | ||
− | == | + | ==Organizing content without namespaces== |
− | + | If you simply want to group pages in your wiki without the need for controlling access rights, you can use the syntax of the namespaces to '''simulate a namespace in the namespace Main'''. Simply prefix the pages that belong to a group with a name and a colon. If no namespace with this name exists, the prefix simply becomes part of the page name. | |
− | + | That way, it is possible to use pages with the same name in the main namespace and thus let different groups work on content "sets". Since these own "namespace" prefixes are part of the page name, you can now display all pages in a simulated namespace by searching for the prefix in the search field. | |
− | Since you can organize pages | + | Since you can also organize pages with categories and subpages, you should start by planning how you would like to organize the content in your wiki. |
− | + | After installing your wiki, you can visualize this with the BlueSpice draw.io Plugin directly in your wiki and discuss it with your team. | |
− | == | + | ==Viewing all pages of a namespace== |
− | + | You can view all pages in a namespace: | |
− | + | #Go to the Special page "All Pages" | |
− | + | #Leave the input field empty | |
− | + | #Select a namespace from the Namespace drop-down menu | |
+ | #Click "Go"<br /> | ||
− | {{Box_Links | Topic1 =[[ | + | {{Box_Links-en |
+ | |Topic1 =[[Manual:Extension/BlueSpiceNamespaceCSS|Namespace CSS manager]] | ||
+ | |Topic2 =[[Manual:Extension/BlueSpiceNamespaceManager|Namespace manager]]}} | ||
[[en: {{FULLPAGENAME}}]] | [[en: {{FULLPAGENAME}}]] | ||
− | [[ | + | [[de:Das_Konzept_der_Namensräume]] |
+ | <br /> | ||
+ | [[Category:Training]] | ||
+ | [[Category:Term]] | ||
+ | [[Category:Concept]] |