Private WIKIs

From Redazione
Jump to navigation Jump to search
(Created page with "Besides the two main components composing this platform (the back-end part represented by this wiki, and the front-end for the navigation among contents within the scope of a...")
 
Line 1: Line 1:
−
Besides the two main components composing this platform (the back-end part represented by this wiki, and the front-end for the navigation among contents within the scope of a single-page-application) a third component which would complete its design, is represented by an arbitrary number of private WIKIs where to store all reserved information and to make them conditionally available on the front-end, for instance to students accessing their own data or digital representation of their classes, to readers accessing some content for paying, and so on: through the combination of a streamlined interface (based on Node.js, Vue.js and Quasar Framework, as well as Pouchdb for offline navigation), a collaborative wiki for contents intended to the public domain, and an arbitrary number of private wikis managed by the respective owners or by a data controller, every requirement conceivable within the frame of IT, information technology, could be potentially met.
+
Besides the two main components composing this platform (the back-end part represented by this wiki, and the front-end for the navigation among contents within the scope of a single-page-application) a third component which would complete its design, is represented by an arbitrary number of private WIKIs where to store all reserved information and to make them ''conditionally'' available on the front-end, for instance to students accessing their own data or the digital representation of their classes, to readers accessing some paid content, and so on: through the combination of a streamlined interface (based on Node.js, Vue.js and Quasar Framework, as well as Pouchdb for offline navigation), a collaborative wiki for contents intended to the public domain, and an arbitrary number of private wikis managed by the respective owners or by a data controller, every requirement conceivable within the frame of IT, information technology, may be potentially met.
  
 
The overall structure of this platform therefore is expected to be composed by a public wiki at this address (1)
 
The overall structure of this platform therefore is expected to be composed by a public wiki at this address (1)
Line 13: Line 13:
 
</pre>
 
</pre>
  
−
then by a generate private wiki managed by a specific data controller, at this address (3)
+
then by a general private wiki managed by a specific data controller, at this address (3)
  
 
<pre class="language-xxxx">
 
<pre class="language-xxxx">
Line 20: Line 20:
  
  
−
and then by an arbitrary number of private wiki at an address like (4)
+
and then by an arbitrary number of private wikis at an address like (4)
  
 
<pre class="language-xxxx">
 
<pre class="language-xxxx">
Line 27: Line 27:
  
  
−
To be noted that '[organization username]' in the (2) corresponds to a wiki page, while '[organization username]' in the (4) corresponds to a username used by the webserver to query a specific database (while in the 2 the database is the same for all the organizations).
+
To be noted that '[organization username]' in the (2) corresponds to a wiki page of a shared wiki, while '[organization username]' in the (4) corresponds to a username used by the webserver to query a specific database (while in the 2 the database is the same for all the organizations) so that any associated page will reside in a dedicated wiki.
  
 
This is an optimal solution in the view of data security, because while [https://www.mediawiki.org/wiki/Category:Page_specific_user_rights_extensions a number of Mediawiki extensions] allow to restrict access to data based on some privileges, they are not intrinsically secure as long as the database is shared.
 
This is an optimal solution in the view of data security, because while [https://www.mediawiki.org/wiki/Category:Page_specific_user_rights_extensions a number of Mediawiki extensions] allow to restrict access to data based on some privileges, they are not intrinsically secure as long as the database is shared.
  
−
On the other side,  
+
On the other side, <html><span style="font-size: 32px;line-height: 1em;padding-right: 6px" class="BroadcastMatter">Cultura italiana</span></html> offers a model in which a subject requiring the maximum level of confidentiality (taken for granted the value of the information) virtually can manage his own wiki, within his own server, which will be conditionally accessed using specific precautions by a "bot" ensuring interoperability with the components aimed at processing and conditionally disseminating such data: to the extent of the will of rights holder.
−
 
 
−
 
 
−
 
 
−
Optionally, we can provide you with a private wiki hosted at an address like
 
−
 
 
−
<pre class="language-xxxx">
 
−
https://culturaitaliana.org/private-wiki/[organization username]
 
−
</pre>
 
−
 
 
−
which differs from the public wiki in that it is not a shared environment,
 
−
while it remains managed as its codebase, modules, templates, available
 
−
forms and so on.
 
−
 
 
−
A private wiki allows you to store any private information (without using specific
 
−
extension in the public wiki which would make some of your pages private, posing
 
−
nonetheless security risks) with the maximum level of security (inasmuch as the wiki
 
−
itself can be accessed only by authorized users) complementing the information you
 
−
have on your public wiki.
 
−
 
 
−
For instance we allow the creation of pages representing language courses in the  
 
−
public wiki, and the creation of pages representing classes and students (registered
 
−
together with their personal information) in the private wiki. This way, we can offer
 
−
an additional platform, named 'classes', which combines the public as well private
 
−
information of your courses, and provides a reserved area for your students where to  
 
−
retrieve their teaching material and even to interact with their class. [... to be continued]
 

Revision as of 20:16, 18 July 2020

Besides the two main components composing this platform (the back-end part represented by this wiki, and the front-end for the navigation among contents within the scope of a single-page-application) a third component which would complete its design, is represented by an arbitrary number of private WIKIs where to store all reserved information and to make them conditionally available on the front-end, for instance to students accessing their own data or the digital representation of their classes, to readers accessing some paid content, and so on: through the combination of a streamlined interface (based on Node.js, Vue.js and Quasar Framework, as well as Pouchdb for offline navigation), a collaborative wiki for contents intended to the public domain, and an arbitrary number of private wikis managed by the respective owners or by a data controller, every requirement conceivable within the frame of IT, information technology, may be potentially met.

The overall structure of this platform therefore is expected to be composed by a public wiki at this address (1) 

https://culturaitaliana.org/wiki

which as mentioned will contain in a shared environment an arbitrary number of organizations at an address like (2) 

https://culturaitaliana.org/wiki/[organization username]

then by a general private wiki managed by a specific data controller, at this address (3) 

https://culturaitaliana.org/private-wiki/culturaitaliana


and then by an arbitrary number of private wikis at an address like (4) 

https://culturaitaliana.org/private-wiki/[organization username]


To be noted that '[organization username]' in the (2) corresponds to a wiki page of a shared wiki, while '[organization username]' in the (4) corresponds to a username used by the webserver to query a specific database (while in the 2 the database is the same for all the organizations) so that any associated page will reside in a dedicated wiki.

This is an optimal solution in the view of data security, because while a number of Mediawiki extensions allow to restrict access to data based on some privileges, they are not intrinsically secure as long as the database is shared.

On the other side, Cultura italiana offers a model in which a subject requiring the maximum level of confidentiality (taken for granted the value of the information) virtually can manage his own wiki, within his own server, which will be conditionally accessed using specific precautions by a "bot" ensuring interoperability with the components aimed at processing and conditionally disseminating such data: to the extent of the will of rights holder.

Retrieved from "https://culturaitaliana.org/w/index.php?title=How_it_works/Private_WIKIs&oldid=5606"