User Tools

Site Tools


wiki:abbi_dokuwiki
LDAP: couldn't connect to LDAP server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
wiki:abbi_dokuwiki [2014/11/10 23:27]
gabriel created
wiki:abbi_dokuwiki [2014/11/13 17:47] (current)
gabriel
Line 14: Line 14:
   * **N**: No right (permission denied)   * **N**: No right (permission denied)
   * **R**: Only read access   * **R**: Only read access
-  * **E**: Editing +  * **E**: Editing ​existing pages 
-  * **C**: Creating new pages+  * **C**: Creating new namespaces, creating and deleting ​pages
   * **U**: Uploading media (e.g., pictures, document) ​   * **U**: Uploading media (e.g., pictures, document) ​
-  * **D**: Delete+  * **D**: Delete ​pages, namespaces and media
  
 Access rights are ordered (**N**<​**R**<​**E**<​**C**<​**U**<​**D**) such as higher rights include lower rights. Access rights are ordered (**N**<​**R**<​**E**<​**C**<​**U**<​**D**) such as higher rights include lower rights.
  
-Access ​right management is based on user groups and namespaces:+In ABBI DokuWiki, access ​right management is based on user groups and namespaces:
  
-^ Namespace ​  ​^ @ALL ^ @abbi_ext ^ @abbi_int ^ @abbi_master ^  +^ Namespace ​    ^              User Groups ​                ​^^^^ 
-^ public ​     |  R   ​| ​ E        |  E        |  D           | +^ :::           ^ @ALL ^ @abbi_ext ^ @abbi_int ^ @abbi_master ^  
-^ private ​    ​| ​ N   ​| ​ E        |  E        |  D           | +:public     ​| ​ R   ​| ​ E        |  E        |  D           | 
-^ private_iit |  N   ​| ​ N        |  E        |  D           | +:private    |  N   ​| ​ E        |  E        |  D           | 
-^ wiki        |  N   ​| ​ R        |  R        |  E           |+:private_iit|  N   ​| ​ N        |  E        |  D           | 
 +:wiki       ​| ​ N   ​| ​ R        |  R        |  E           |
  
 where the groups are where the groups are
Line 34: Line 35:
   * **@abbi_ext**:​ registered non-IIT ABBI staff   * **@abbi_ext**:​ registered non-IIT ABBI staff
   * **@abbi_int**:​ registered IIT ABBI staff    * **@abbi_int**:​ registered IIT ABBI staff 
-  * **@abbi_master**:​ a selected few who understand what access control ​is about :-). +  * **@abbi_master**:​ a selected few who understand what namespaces and access control ​are about :-). 
  
-There is also a **@abbi_admin** group who can do additional things like moving a page or a namespace, installing a plugin, etc.  ​The namespace **wiki** is reserved for this section of ABBI DokuWiki.+There is also a **@abbi_admin** group who can do additional things like moving a page or a namespace, installing a plugin, etc.  ​
  
-Non-IIT staff must register on the [[https://rbcscms.humanoids.iit.it/​login ​| RBCS portal]]. Contact ​%%gabriel.baud-bovy@iit.it%% if you want to change your access rights.+Non-IIT staff must register on the [[https://accounts.rbcs.iit.it | RBCS portal]]. Contact ​<gabriel.baud-bovy@iit.itif you want to change your access rights.
  
-==== Creating pages ====+==== ABBI namespace structure ​====
  
-When creating ​page in this wikithe link should include a namespace ​to manage its +A namespace is similar to directory or folderwhile pagenames are similar ​to files. In DokuWiki you can use [[https://​www.dokuwiki.org/​namespaces | namespaces]] to categorize your [[https://​www.dokuwiki.org/​pagename | pages ]].  
-access rights+  
 +A partial representation of ABBI namespace structure is
  
-<code+<file  
-   [[<​access_namespace>:<​page_name>​]] +   root namespace (always present) 
-</​code>​+     │ 
 +     ​└── '​public'​ namespace 
 +     ​│ ​      ​└── '​media'​ namespace 
 +     │ 
 +     ​└── '​private'​ namespace 
 +     ​│ ​      ​└── '​media'​ namespace 
 +     ​│ ​      │ 
 +     ​│ ​      ​└── '​ble'​ namespace 
 +     ​│ ​      ​│ ​    ​└── '​media'​ namespace 
 +     ​│ ​      │ 
 +     ​│ ​      ​└── '​fw'​ namespace 
 +     ​│ ​      ​│ ​    ​└── '​media'​ namespace 
 +     ​│ ​      │ 
 +     ​│ ​      ​└── '​hw'​ namespace 
 +     ​│ ​      ​│ ​    ​└── '​media'​ namespace 
 +     ​│ ​      │ 
 +     ​│ ​      ​└── '​app'​ namespace 
 +     ​│ ​            ​└── '​media'​ namespace 
 +     │ 
 +     ​└── '​wiki'​namespace ​                        
 +     │ 
 +     ​└── '​software'​namespace ​                       ​
  
-where access is one of the of namespace defined above. For example, to create a page  +<​\file>​
-visible by all, the link should be %%[[:​public:​page]]%%.+
  
-By convention in this wiki, page names are in lower cases and underscores are +By convention, namespaces and pagenames ​in this wiki are in //lower cases// and //underscores// are be used to separate words.  ​
-be used to separate words.  ​Note that the whole string is the actual +
-name of the page. Therefore, %%public:​page%% is a different page than %%public:​page%%. ​+
  
-By default, child pages inherit access rights from their parent ​pageCreating a ling %%[[new_page]]%% in page %%private:page%% actually creates page %%[[private:​new_page]]%%+The root namespaces ''​public''​ and ''​private''​ are used to define access rights. ​By default, child namespaces ​inherit access rights from their parent ​namepage and pages inherit access rights from their namepagesTherefore, all pages under the ''​private''​ namespace will have a restricted access as defined previously, etc.
  
-==== Uploading ​media ====+The ''​media''​ namespace is used to store media (e.g. pictures, videos, documents) that are linked from pages in the corresponding namespace. ​ For example, the picture file ''​pic.jpg''​ inserted in page '':​private:​fw:​overview''​ should be placed in namespace '':​private:​fw:​media''​. ​
  
-Media should be loaded ​with a double ​namespace ​classification scheme:+New pages and namespaces are created by creating a link and editing the page. Exactly where the page is created depends on the syntax of the link: 
 + 
 +  * Absolute paths in links start with a colon '':''​ or with the namespace 
 +  * Relative paths start with a colon ''​.''​ 
 + 
 +For example, let's assume that one creates the following links in the page ''​:private:​development''​ 
 + 
 +  - ''​%%[[new_page]]%%''​  
 +  - ''​%%[[:​private:​new_page]]%%''​ 
 +  - ''​%%[[.ff:​new_page]]%%''​ 
 +  - ''​%%[[:​private:​ff:​new_page]]%%''​ 
 +  - ''​%%[[ff:​new_page]]%%''​ 
 +  - ''​%%[[:​ff:​new_page]]%%''​ 
 + 
 +  * 1. is relative to the current namespace and will therefore create the page '':​private:​new_page''​ like 2. 
 +  * 3. starts with a colon is is therefore relative to the current namespace and create the page '':​private:​ff:​new_page''​ like 4.  In addition, it will create the namespace ''​ff''​ beneath ''​private''​ if it does not exist. ​  
 +  * Somewhat counter-intuitively,​ the syntax of 5. refers to an absolute path. It will therefore create page '':​ff:​new_page''​ like 6. In addition, it will create '​ff'​ in the root directory if it does not exist.  
 + 
 +[[https://​svn.rbcs.iit.it/​abbi | ABBI SVN]] should normally be used to manage the development of software within the project. However, it might occasionally be useful to upload in the wiki some software to be distributed (e.g. as a zipfile). Software should be placed in the ''​software''​ namespace. Access right will be managed on a case-by-case basis. ​
  
-  [[:<​access_namespace>:<​type_namespace>:<​filename>​]] 
  
-where access names space are one of the namespace define above and 
-type namespace can be 
  
-  * **doc**: documents (e.g. pdf, docx) 
-  * **pic**: pictures 
-  * **vid**: videos 
  
  
wiki/abbi_dokuwiki.1415658471.txt.gz · Last modified: 2014/11/10 23:27 (external edit)