Reimplement "School" entity, list and details view

[sleidig]

Reimplement the School module of the existing prototype for the HELGO project.

• School Entity
• School List Component
• School Details Component

[codingfabi]

what exactly should the school details feature look like? just a list of childs visiting this school? or more details of the school itself?

[sleidig]

School entities should have some general details about the school (this is what is currently in use):

• Medium [select] (i.e. the primary language in which classes are taught)
• Board [select] (i.e. which government organisation is accrediting the school)
• Private School [checkbox]
• Address [text]
• Website
• School Timing [text]
• Working Days [text]

Also, a list of the students studying in that school queried from the database would be good

[TheSlimvReal]

I figured out a design for the connection between schools and children:

• every school has an array of ID's from children visiting this school
• every child has the ID of the school the child is visiting
• when creating/editing a child, a school can be selected from the already created schools in the database
• Routing is possible between:
• SchoolList to SchoolDetails
• SchoolDetails to ChildDetails and vice versa

[sleidig]

Sounds good. For the displaying and navigation between Child and School you can use the ChildBlockComponent and SchoolBlockComponent.

But if you are saving the link on school as well as child side, isn't that redundant and in danger of becoming inconsistent when an edit is not properly implemented (or simply disturbed by connectivity problems)?

In the long run I would like a history of schools a child has attended (i.e. 2015: class 9 at School X; 2016: class 10 at School X; 2017: class 11 at School Y). But for now let's keep it simple for the first implementation.

[TheSlimvReal]

I was also thinking about implementing it on just one side. But ist'nt it a kind of slow when you always have to look through every child in every school object to find the school a child is visting, when you just save the child ID's in the school object.

[sleidig]

Yeah, might be slow, especially with many child records in the db. But saving redundant information is a big anti-pattern. To improve performance we could set up an index in pouchdb if necessary (Although the search, which is doing that, seems really slow as well on the pilot site).
relational-pouch (see #108) would probably do this internally.

Maybe we should go for the desired endresult right away:

• new Entity type "SchoolEnrollment" with child, school, dateFrom, dateUntil, grade
• Child is considered in the School, whose dateFrom-dateUntil interval falls into the current date
• an index (or relational-pouch setup) give efficient access to all enrollments of a child or a school

[sleidig]

Any work happening on this?

Let's keep the student link/lookup as it is, for the time being. Once we look further into modeling school enrollment, this can be refined. I would like to release a proper UI for SchoolDetails, including some basic fields (see #42 (comment))

[sleidig]

PR #204 will close this issue. Further work regarding the school-child-relationship is still happening in #152 and discussed there. In case of further issues related to the relationship, let's open a separate issue.