Move timesheet and worklogs to employee-specific graph #4
Conversation
add a group `public-all-employees` so kimai-service kan keep access to all the graphs. only persons part of the `employee` group have their own graph. The assumption is made that other users have no timesheet/worklog data.
|
Looking at this from a distance, I think this will work as long as we don't have too many users (sadly, I don't know the number where it will fail). Some naming improvements may help a first read. As the amount of graphs grows, we'll select from more of them which makes the triplestore slow. Further, having too many mu-auth-allowed-groups could make the header too long. An ideal solution would collect the data from the users and populate a graph for Kimai to consume. We should be prepared to quickly use sudo-queries instead when the problem would appear. Looking at the sync service that should be feasible on late notice so that's ok for me at this point. I was a bit confused by the name of the new group, so I may rename that so it's easier to read. There's also some spurious spaces in the query which don't hurt. |
No logical change to the migration so it's safe to update it without changing the filename.
A group
public-all-employeesis used so kimai-service can keep access to all the graphs.