Site:Access Rights - Revision history

Kirsch: KOmma bei This is, ...

2020-10-02T12:33:40Z

KOmma bei This is, ...

← Older revision		Revision as of 14:33, 2 October 2020
Line 45:		Line 45:
	In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.		In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.
	==Research data with restricted access==		==Research data with restricted access==
	One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2 which requires to be logged in. That is being logged in is a necessary condition to exercise the access rights of user type 2. Likewise being logged out is sufficient to (temporarily) not having these privileges.		One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2 which requires to be logged in. That is, being logged in is a necessary condition to exercise the access rights of user type 2. Likewise being logged out is sufficient to (temporarily) not having these privileges.

	People might be willing to share project data with a limited number of trusted people but are hesitant to make it available to the whole world without restriction. For this reason restricted access has been implemented here.		People might be willing to share project data with a limited number of trusted people but are hesitant to make it available to the whole world without restriction. For this reason restricted access has been implemented here.
Line 71:		Line 71:
	At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.		At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.

	== Namespaces without read access ==		==Namespaces without read access==
	There are namespaces which serve internal purposes like the the namespace [[Projekt]] which is used for project management. Typically users of type 0 are not allowed to read such pages. However, it applies what has stated above in the context of research data with restricted access: '''access restrictions only restrict access to content but not knowledge about content.'''		There are namespaces which serve internal purposes like the the namespace [[Projekt]] which is used for project management. Typically users of type 0 are not allowed to read such pages. However, it applies what has stated above in the context of research data with restricted access: '''access restrictions only restrict access to content but not knowledge about content.'''

	For instance, a user of type 0 might type "access rights" into the search bar. By that he or she will learn about the '''existence''' of the page [[Projekt:Access_Rights]] (this very page) located in the [[Projekt]] namespace. However, he or she '''cannot access''' its content as users of type 0 don't have access to the namespace [[Projekt]].		For instance, a user of type 0 might type "access rights" into the search bar. By that he or she will learn about the '''existence''' of the page [[Projekt:Access_Rights]] (this very page) located in the [[Projekt]] namespace. However, he or she '''cannot access''' its content as users of type 0 don't have access to the namespace [[Projekt]].

Riegler at 05:30, 23 September 2020

2020-09-23T05:30:42Z

← Older revision		Revision as of 07:30, 23 September 2020
Line 71:		Line 71:
	At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.		At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.

	~~<br />~~		== Namespaces without read access ==
			There are namespaces which serve internal purposes like the the namespace [[Projekt]] which is used for project management. Typically users of type 0 are not allowed to read such pages. However, it applies what has stated above in the context of research data with restricted access: '''access restrictions only restrict access to content but not knowledge about content.'''

			For instance, a user of type 0 might type "access rights" into the search bar. By that he or she will learn about the '''existence''' of the page [[Projekt:Access_Rights]] (this very page) located in the [[Projekt]] namespace. However, he or she '''cannot access''' its content as users of type 0 don't have access to the namespace [[Projekt]].

Riegler at 05:03, 23 September 2020

2020-09-23T05:03:56Z

← Older revision		Revision as of 07:03, 23 September 2020
Line 1:		Line 1:
	==Access rights model==		==Access rights model==
	~~{\| class="wikitable"~~
	\|+
	We intend to have a lean model of access rights. Major dimensions are whether a user		We intend to have a lean model of access rights. Major dimensions are whether a user

	*is allowed to author pages on the wiki (this leads to the differentiation between user types 0 and 1)		*is allowed to author pages on the wiki (this leads to the differentiation between user types 0 and 1)
	*is allowed to access research data (this leads to the differentiation between user types 1 and 2).		*is allowed to access research data (this leads to the differentiation between user types 1 and 2).


			{\| class="wikitable"
			\|+
	!user type		!user type
	!description		!description

Riegler at 05:02, 23 September 2020

2020-09-23T05:02:54Z

← Older revision		Revision as of 07:02, 23 September 2020
Line 15:		Line 15:
	\|0		\|0
	\|any internet user		\|any internet user
	\|only those in the namespaces (Main), User, File, Category, unless restricted		\|only those in the namespaces (Main), DecodingWork, PublishedWork, User, File, Category, unless restricted
	\|none		\|none
	\|no		\|no

Riegler at 15:11, 22 September 2020

2020-09-22T15:11:24Z

← Older revision		Revision as of 17:11, 22 September 2020
Line 43:		Line 43:
	In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.		In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.
	==Research data with restricted access==		==Research data with restricted access==
	One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2.		One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2 which requires to be logged in. That is being logged in is a necessary condition to exercise the access rights of user type 2. Likewise being logged out is sufficient to (temporarily) not having these privileges.

	People might be willing to share project data with a limited number of trusted people but are hesitant to make it available to the whole world without restriction. For this reason restricted access has been implemented here.		People might be willing to share project data with a limited number of trusted people but are hesitant to make it available to the whole world without restriction. For this reason restricted access has been implemented here.
Line 51:		Line 51:
	Note that access restriction is by group not by person. Access is restricted to user type 2 (or "higher"). It is not possible that Cecil restricts access to Dagmar only. (As a matter of fact, aiming at a lean access rights model restriction by person is not intended.)		Note that access restriction is by group not by person. Access is restricted to user type 2 (or "higher"). It is not possible that Cecil restricts access to Dagmar only. (As a matter of fact, aiming at a lean access rights model restriction by person is not intended.)

	Also note, that access restriction only restricts access to content but not knowledge about content. That is Amy and Bertram might learn from a content page that a restricted resource exists.For a real example visit [[Group activities in interactive teaching]] and [[Limits]] and go the ~~the section~~ "Available resources".		Also note, that access restriction only restricts access to content but not knowledge about content. That is Amy and Bertram might learn from a content page that a restricted resource exists.

			For a real example visit both [[Group activities in interactive teaching]] and [[Limits]] and go the respective sections "Available resources."

	*In the case of [[Group activities in interactive teaching]] you will have unrestricted access to the resources offered.		*In the case of [[Group activities in interactive teaching]] you will have unrestricted access to the resources offered.
	*In the case of [[Limits]] you won't have access to the resources offered (unless you have access rights of user type 2). Following the link will result in an permission error.		*In the case of [[Limits]] you won't have access to the resources offered (unless you have access rights of user type 2 which requires to be logged in - so log out in order to check the discussed feature). Following the link will result in an permission error.

	Technically access to content is restricted by adding		Technically access to content is restricted by adding

Riegler at 15:06, 22 September 2020

2020-09-22T15:06:45Z

← Older revision		Revision as of 17:06, 22 September 2020
Line 15:		Line 15:
	\|0		\|0
	\|any internet user		\|any internet user
	\|only those in the namespaces (Main), User, File, Category unless restricted		\|only those in the namespaces (Main), User, File, Category, unless restricted
	\|none		\|none
	\|no		\|no

Riegler at 15:05, 22 September 2020

2020-09-22T15:05:58Z

← Older revision		Revision as of 17:05, 22 September 2020
Line 15:		Line 15:
	\|0		\|0
	\|any internet user		\|any internet user
	\|only those in the namespaces (Main), User, File, Category		\|only those in the namespaces (Main), User, File, Category unless restricted
	\|none		\|none
	\|no		\|no
Line 22:		Line 22:
	\|1		\|1
	\|registered wiki user		\|registered wiki user
	\|in any namespace		\|in any namespace unless restricted
	\|in any namespace		\|in any namespace
	\|yes		\|yes
Line 60:		Line 60:
	<code><nowiki><bs:pageaccess groups="sysop,researcher" /></nowiki></code>		<code><nowiki><bs:pageaccess groups="sysop,researcher" /></nowiki></code>

	to the content page. To do so using the source code editor, just insert this line (any place will be fine). Using the visual editor select Insert>Magic word>pageaccess. Restricting access rights is not a regular feature of [https://www.wikimedia.org Wikimedia] and one of the reasons why the [https://www.bluespice.com BlueSpice] extension has been chosen as a platform for this project.		to the content page. To do so using the source code editor, just insert this line (any place will be fine). Using the visual editor select <code>Insert>Magic word>pageaccess</code>. Restricting access rights is not a regular feature of [https://www.wikimedia.org Wikimedia] and one of the reasons why the [https://www.bluespice.com BlueSpice] extension has been chosen as a platform for this project.

	==Getting access to privileges of user type 2 ("researcher")==		==Getting access to privileges of user type 2 ("researcher")==

Riegler: /* Getting access to privileges of user type 2 ("researcher") */

2020-09-22T15:02:52Z

Getting access to privileges of user type 2 ("researcher")

← Older revision		Revision as of 17:02, 22 September 2020
Line 63:		Line 63:

	==Getting access to privileges of user type 2 ("researcher")==		==Getting access to privileges of user type 2 ("researcher")==
	~~<br />~~There isn't an automated process to get access rights of user type 2. And there is no plan that there will be one. Instead access rights need to be granted manually by an administrator. Only users of type 1 can apply for access rights of user type 2. In order to do so they need to send an email to an administrator. It is the administrator's responsibility to check and decide whether applicants can trustfully granted the privileges of user type 2.		There isn't an automated process to get access rights of user type 2. And there is no plan that there will be one. Instead access rights need to be granted manually by an administrator. Only users of type 1 can apply for access rights of user type 2. In order to do so they need to send an email to an administrator. It is the administrator's responsibility to check and decide whether applicants can trustfully granted the privileges of user type 2.

	At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.		At a certain point there will be a dedicated email address for access rights applications. For the time being, requests for access rights of user type 2 need to be send to p.riegler@ostfalia.de.

	<br />		<br />

Riegler at 14:57, 22 September 2020

2020-09-22T14:57:46Z

← Older revision		Revision as of 16:57, 22 September 2020
Line 1:		Line 1:
	== Access rights model ==		==Access rights model==
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 10:		Line 10:
	!reading content		!reading content
	!authoring content		!authoring content
	!needs ~~account~~		!needs login
	!~~can access~~ research data stored in wiki		!accessing research data stored in wiki
	!
	!
	\|-		\|-
	\|0		\|0
	\|any internet user		\|any internet user
	\|only those in the namespaces ~~...~~		\|only those in the namespaces (Main), User, File, Category
	\|none		\|none
	\|no		\|no
	\|only those without restricted access		\|only those without restricted access
	\|
	\|
	\|-		\|-
	\|1		\|1
	\|~~register~~ wiki user		\|registered wiki user
	\|in any namespace		\|in any namespace
	\|in any namespace		\|in any namespace
	\|yes		\|yes
	\|only those without restricted access		\|only those without restricted access
	\|
	\|
	\|-		\|-
	\|2		\|2
Line 39:		Line 33:
	\|yes		\|yes
	\|those with and without restricted access		\|those with and without restricted access
	\|
	\|
	\|-		\|-
	\|∞		\|∞
Line 48:		Line 40:
	\|yes		\|yes
	\|those with and without restricted access		\|those with and without restricted access
	\|
	\|
	\|}		\|}
	In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.		In wiki jargon a namespace refers to a certain category of content. See the [[mediawikiwiki:Manual:Namespace\|Wikimedia manual]] for details.


	~~asdflkjfsd~~

	==Research data with restricted access==		==Research data with restricted access==
	One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2.		One of the major purposes of this wiki is to make available research data such as e.g. interview recordings, transcripts, assessment items, or assessment data. Access to such data can be either unrestricted or restricted. Research data with restricted access is only accessible to users of type 2.

			People might be willing to share project data with a limited number of trusted people but are hesitant to make it available to the whole world without restriction. For this reason restricted access has been implemented here.

	To explain access rights by virtue of an example let's imagine users Amy One (of type 1), Bertram Two (of type 2), Cecil, Dagmar, and Elly Three (of type 3). Dagmar and Elly restrict access to (some of) their resources. That means that only Cecil, Dagmar and Elly to have access to these resources. Amy and Bertram don't.		To explain access rights by virtue of an example let's imagine users Amy One (of type 1), Bertram Two (of type 2), Cecil, Dagmar, and Elly Three (of type 3). Dagmar and Elly restrict access to (some of) their resources. That means that only Cecil, Dagmar and Elly to have access to these resources. Amy and Bertram don't.

Riegler at 14:50, 22 September 2020

2020-09-22T14:50:31Z

← Older revision		Revision as of 16:50, 22 September 2020
Line 1:		Line 1:
	~~<nowiki>~~== Access rights model ==~~</nowiki>~~		== Access rights model ==
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+