Add statistics page for absences #266
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Alsijil#266
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Due to the frequent need of aggregated absence data per student/per group/per course, statistic components on the person and group pages should be introduced. It should be possible to filter the data that is aggregated by school term.
https://design.edugit.org/#/workspace/4cb67ad2-841a-81b6-8003-4809953226e4/d4872814-7693-809c-8003-df116cce0642?page-id=d4872814-7693-809c-8003-df116cce0643
Aggregations on student page (component 1)
Query per person and school term
count_as_absentAggregations on groups page (component 2)
Query per group and school term with a list of persons and annotated statistics
for each student
count_as_absentPossibly connected in some way to #124 #120
Our idea: no separate page, but a widget with fullscreen capabilities, displayed on the person overview page in the core (and possibly later as well on the dashboard).
How would this work technically: Each app can declare inside the index.js which collection the respective app defines, and which components it provides for specific collections. Vite/the bundler will somehow merge thes values and provide at a singular place (via the aleksis mixin maybe?).
Example: the core would define the collections "core-dashboard", "core-person-overview" and "core-group-overview", and alsijil would supply components for personal statistics (and at a later point one for group statistics as well)
this would solve/require https://edugit.org/AlekSIS/official/AlekSIS-Core/-/issues/122
@hansegucker please think very hard about this as well
I like this idea. But we also have to consider additional pages for statistic overviews for whole groups.
We have consider different ways of aggregating information (e.g. summing up missed days vs summing up missed lessons) – in Berlin, for example, school certificates need to state the count of missed days.
ignore the "Kursbuchstatistik" card, this idea has been verworfen
assigned to @yuha
new mockups presented in devmeeting, @hansegucker will now present them to the Katharineum
mentioned in issue #253
changed the description
changed the description
created branch
266-add-statistics-page-for-absencesto address this issuementioned in merge request !751
A draft of the UI for a person in compact form for the person overview page and maximized form:
StatisticsForPersonPage should have two lists:
https://edugit.org/AlekSIS/official/AlekSIS-App-Alsijil/-/issues/255#note_91635
One has PeronalNotes et al
and the other has absences & actions (change status)
assigned to @permcu and unassigned @yuha
assigned to @ZugBahnHof and unassigned @permcu
mentioned in commit
43588ac578added 1 design
added 1 design
added 1 design
added 1 design