Open manuelmeister opened 2 months ago
Variante 1 | Variante 2 | Variante 3 |
---|---|---|
![]() |
![]() |
![]() |
>> Variante 3 <<
[ContentNode]
[ColumnLayout|data]
[ChecklistNode;#selectedChecklist]
[Checklist|Name;Organisation;Language]
[ChecklistItem|Text]
[ContentNode]^[ChecklistNode]
[ContentNode]^[ColumnLayout]
[Camp]<>-*>[Checklist]
[Checklist]<>-*>[ChecklistItem]
[ChecklistItem]<*children-<>[ChecklistItem]
[Camp]<>-*>[Activity]
[Activity]rootContentNode-1>[ColumnLayout]
[ContentNode]<* children-<>[ContentNode]
[ColumnLayout]<> des-*>[ContentNode]
[Checklist]-.-option[ChecklistNode]
[ChecklistNode]<*-*>[ChecklistItem]
We choose Variant 3.
Relation Checklist
-> Camp
can be nullable.
In the future we can still elevate the n:m relation to its own entity and a theoretical future camp checklist will just be a TodoList
.
I'm afraid we'll have to discuss the naming again.
For the first implementation we need to name three entities:
My suggestion (see UML 'Variante 3') As identical as possible to material lists:
FYI: I started to work on the backend: https://github.com/pmattmann/ecamp3/tree/feature/checklist
...
We go with the version 3:
In the future we may want to rename our contentnodes to reflect that they are Node
s or Layout
s. This should be first sketched in a issue before renaming all the things.
Kursziele/Kursanforderungen
Strukturierte Anforderungen/Ziele/Kompetenzen von einer Instanz (Schule, Verband, Bundesamt & eigenen Erwartungen) welche man Aktivitäten zuordnen kann. Die Use Cases sind:
A) Administration
B) Activity Ebene
Category
) hinzufügen.C) Reporting