[Migration] Level System for Places and users #42

New Issue

reverend · 2021-10-18T12:15:52+02:00

reverend commented

2021-10-18 12:15:52 +02:00

Original https://git.mowoe.com/reverend/lostplaces-backend/issues/42 by @reverend from Thu, 24 Dec 2020 14:35:40 CET

Places and Users should have a level assigned to.
The place-level indicates how good the place is/how worthy it is of keeping it secret, where as the user-leve indicates how trustworthy a user is. Only trustworthy users should be able to see high level places.

The place level is assigned by users who are trustworthy enough. A user, wich level is to low, should not be able to assign a level to any places, not even to his own ones. Furthermore should the option to assign a level only be visbile to users who are eligible to do so.

A user can still see his own places, even if the place is assigned a level that is to high for the user.

The user level is assigned by admins.

The levels should range from 1-5,
Level 1 is default for users and indicates the lowest trustworthiness
Level 5 is default for places and indicates a high worth of protection.

Comment by @Commander1024 from Fri, 01 Oct 2021 20:26:57 CEST

Still needs frontend integration.

Comment by @reverend from Sat, 02 Oct 2021 00:06:41 CEST

The assigned level is now considered in the following scenarios:

Listing a bunch of places like the homepage or the list all places view
DetailView of a place, user is presented with a 403 if accesed (by manual URL)
When trying to creating a favorite or visit on a place
(This doe's not let the use access any data tho, but it's more consistent)

Whenever such request is made, the user is presented with an HTTP 403 response and an according error message.

Comment by @reverend from Sat, 02 Oct 2021 00:09:23 CEST

This also takes in consideration the superuser status of the requesting user and checks if the user is the submitter

## Original https://git.mowoe.com/reverend/lostplaces-backend/issues/42 by @reverend from Thu, 24 Dec 2020 14:35:40 CET Places and Users should have a level assigned to. The place-level indicates how good the place is/how worthy it is of keeping it secret, where as the user-leve indicates how trustworthy a user is. Only trustworthy users should be able to see high level places. The place level is assigned by users who are trustworthy enough. A user, wich level is to low, should not be able to assign a level to any places, not even to his own ones. Furthermore should the option to assign a level only be visbile to users who are eligible to do so. A user can still see his own places, even if the place is assigned a level that is to high for the user. The user level is assigned by admins. The levels should range from 1-5, Level 1 is default for users and indicates the lowest trustworthiness Level 5 is default for places and indicates a high worth of protection. ### Comment by @Commander1024 from Fri, 01 Oct 2021 20:26:57 CEST Still needs frontend integration. ### Comment by @reverend from Sat, 02 Oct 2021 00:06:41 CEST The assigned level is now considered in the following scenarios: - Listing a bunch of places like the homepage or the list all places view - DetailView of a place, user is presented with a 403 if accesed (by manual URL) - When trying to creating a favorite or visit on a place (This doe's not let the use access any data tho, but it's more consistent) Whenever such request is made, the user is presented with an HTTP 403 response and an according error message. ### Comment by @reverend from Sat, 02 Oct 2021 00:09:23 CEST This also takes in consideration the superuser status of the requesting user and checks if the user is the submitter

reverend added the

Feature

label 2021-10-18 12:15:52 +02:00

reverend added this to the Release 0.1.5 milestone 2021-10-18 12:40:51 +02:00

reverend referenced this issue from a commit

2021-12-31 00:35:27 +01:00

#42 Place Voting / Level

reverend referenced this issue from a commit

2021-12-31 00:35:27 +01:00

#42 Tests for Level-System / Homepage

reverend commented

2021-12-31 00:36:37 +01:00

This feature is almost done, there is some workl left on the frontend side. But the PlaceDetailView-Page is about to be re designed, just looks awefull.

reverend referenced this issue

2021-12-31 01:09:59 +01:00

[Frontend] Redesign Place Detail Page #57

reverend modified the milestone from Release 0.1.5 to 0.1.6

2021-12-31 01:14:23 +01:00

reverend referenced this issue from a commit

2021-12-31 18:38:00 +01:00

#42 Level for Users

reverend referenced this issue from a commit

2021-12-31 18:38:00 +01:00

#42 Levels for places

reverend referenced this issue from a commit