There are various minor tasks, that should be improved/fixed:
Team sharing
On the overview the correct amount of shared data is visible. However, the little icon, indicating whether an entry is shared or not, seems to be glowing only if the entry is shared directly with the user. Should glow on any shared way.
Team leave
A user should be able to leave a team by himself. Currently there is no such button on the team management hub
QR codes clickable
QR codes are handy if scanned, which creates its full potential only if printed. If it's still digital, e.g. on the page, it should be clickable as well.
Recorded entry editing
Normally the final ETS users should unshare the entry with all users who are not supposed to have further access on the data entry. However, it's likely that some will forget about it. Furthermore it would then still be possible for a shared user to edit the recorded entry again, which results in an automatic unrecording.
We want to give the users as much freedom as possible, but should still support lightly in proper situations. Therefore: If an entry is recorded, all direct-shared-users not having ETS group privileges should be removed automatically. In most cases this will remove the initial creator of the entry, which is the first direct-shared-user by default. Team sharing will not be affected by this.
Edit->unrecord log comment
If an entry will be unrecorded due to an edit activity, there should be a comment on the unrecord log, stating that this was an automatic unrecording due to a previous edit action.
Extend output for updateallparcels
The command is very quiet, there is no progress visible. Since updating geometries may take a while, depending on size and number, it would be good to see how many geometries already have been processed
Geometry admin
Show some interesting info about a geometry on it's admin view
Show the geometry_id on all major data entries (intervention, compensation, ema, ecoaccount)
Default rpp on overview
Increase from 5 to 10 for better UX
# Status quo
There are various minor tasks, that should be improved/fixed:
1. ~~Team sharing~~
1. On the overview the correct amount of shared data is visible. However, the little icon, indicating whether an entry is shared or not, seems to be glowing only if the entry is shared directly with the user. Should glow on any shared way.
1. ~~Team leave~~
1. A user should be able to leave a team by himself. Currently there is no such button on the team management hub
1. ~~QR codes clickable~~
1. QR codes are handy if scanned, which creates its full potential only if printed. If it's still digital, e.g. on the page, it should be clickable as well.
1. ~~Recorded entry editing~~
1. Normally the final ETS users should unshare the entry with all users who are not supposed to have further access on the data entry. However, it's likely that some will forget about it. Furthermore it would then still be possible for a shared user to edit the recorded entry again, which results in an automatic unrecording.
1. We want to give the users as much freedom as possible, but should still support lightly in proper situations. Therefore: If an entry is recorded, all direct-shared-users not having ETS group privileges should be removed automatically. In most cases this will remove the initial creator of the entry, which is the first direct-shared-user by default. Team sharing will not be affected by this.
1. Edit->unrecord log comment
1. If an entry will be unrecorded due to an edit activity, there should be a comment on the unrecord log, stating that this was an automatic unrecording due to a previous edit action.
1. ~~Extend output for updateallparcels~~
1. The command is very quiet, there is no progress visible. Since updating geometries may take a while, depending on size and number, it would be good to see how many geometries already have been processed
1. ~~Geometry admin~~
1. Show some interesting info about a geometry on it's admin view
1. Show the geometry_id on all major data entries (intervention, compensation, ema, ecoaccount)
1. ~~Default rpp on overview~~
1. Increase from 5 to 10 for better UX
Whilst working on this task, I was wondering why should we even allow any editing on a recorded entry?
Wouldn't it be more predictable for a user, if instead of a (maybe unwanted) automatic unrecording of the data, we simply prohibit any editing whilst being recorded?
This approach could look like this: If an entry (does not matter what) is recorded and a user (does not matter which group) tries to add/edit/delete data, the proper form or modal form will not show up but instead a message, that the entry can not be edited as long as it is still recorded. This way we would force the ETS users actively to verify the unrecording, then check on the edited data and record it manually afterwards again.
If a user tries to open the general data form of an entry, we could simply redirect back to the detail page, stating that editing is not possible, whilst the data is recorded. The modal forms could render the same message as well instead of the regular modal form content.
This should be thought through carefully and result in a new issue.
## 5. Edit->unrecord log comment
Whilst working on this task, I was wondering why should we even allow any editing on a recorded entry?
Wouldn't it be more predictable for a user, if instead of a (maybe unwanted) automatic unrecording of the data, we simply prohibit any editing whilst being recorded?
This approach could look like this: If an entry (does not matter what) is recorded and a user (does not matter which group) tries to add/edit/delete data, the proper form or modal form will not show up but instead a message, that the entry can not be edited as long as it is still recorded. This way we would force the ETS users actively to verify the unrecording, then check on the edited data and record it manually afterwards again.
If a user tries to open the general data form of an entry, we could simply redirect back to the detail page, stating that editing is not possible, whilst the data is recorded. The modal forms could render the same message as well instead of the regular modal form content.
This should be thought through carefully and result in a new issue.
Status quo
There are various minor tasks, that should be improved/fixed:
Team sharingTeam leaveQR codes clickableRecorded entry editingExtend output for updateallparcelsGeometry adminDefault rpp on overview5. Edit->unrecord log comment
Whilst working on this task, I was wondering why should we even allow any editing on a recorded entry?
Wouldn't it be more predictable for a user, if instead of a (maybe unwanted) automatic unrecording of the data, we simply prohibit any editing whilst being recorded?
This approach could look like this: If an entry (does not matter what) is recorded and a user (does not matter which group) tries to add/edit/delete data, the proper form or modal form will not show up but instead a message, that the entry can not be edited as long as it is still recorded. This way we would force the ETS users actively to verify the unrecording, then check on the edited data and record it manually afterwards again.
If a user tries to open the general data form of an entry, we could simply redirect back to the detail page, stating that editing is not possible, whilst the data is recorded. The modal forms could render the same message as well instead of the regular modal form content.
This should be thought through carefully and result in a new issue.
Merged in #150