Add an endpoint which gives the clients information about their rights an privileges.
An answer from this endpoint may look like this:

{
    "admin":false,
    "can_create_classes":true,
    "...": "..."
}

This information can be used by the app or web client to hide/show buttons for the creation of classes, students, ...

Load CSV data from file to database, so classes and their students can be imported easily.

Sample data

Realization

There should be an endpoint which receives csv-data like this and automatically creates the necessary classes as well as their students.

Maybe we could add a timetable in which the helper can see where he/she and the class has to be and when.

The server answers with a 204 No Content as if the class was deleted, but for some reason, it isn't.

Maybe supplement for #1

Spring Security also offers JWT as an authentication method.
Test and think about switching to this.

I think we can massively decrease our build time if we would make our RepositoryIntegrationTests without a "real" database.
We could instead mock these repositories and annotate the tests with @MockMvcTest.

Think about documenting API with Swagger's OpenAPI.

https://github.com/springdoc/springdoc-openapi
https://reflectoring.io/documenting-spring-data-rest-api-with-springfox/

Each student gets and paper depending on its age level and achieved points.
Our system has to categorize to winner-, honour- and participant-paper.

Implement caching for methods like

• getAValue()
• getCValue()
• getVictoryValue()
• getHonorValue()
• some how calculateScore

This will improve our performance trasticly while scaling with requests.

https://docs.spring.io/spring-data/rest/docs/3.2.3.RELEASE/reference/html/#conditional.etag

This will reduce consumption of data and battery power by not retrieving the same data over and over again.

We have already some TODOs marked in the code in the asciidoc documentation:

Please document for each endpoint the object 🙏

• StudentRepository
• ClassRepository
• SportResultRepository
• UserRepository
• UserPrivilegeRepository

Probably most important is the documentation of the different disciplines in the SportResultRepository.

I want to add a feature which returns which kind of certificate the student gets.
Do you have any suggestions where I should add it? A new controller?

• those who have gotten access to a class can see just those students and their results
• administrator can see all students and their results in order to print the papers

For each grade, the 3 best boys and girls get a special announcement. To make this easy the system has to find those.

Supplementation of #4:

Add score as well later in #7 the categorization to the student's attributes.

This may be accomplished by

@Entity
public class Student {
    
    private String firstName;
    ...

    public Integer score() {
        // method call to student controller.
    }

}

Also, it would be great to have a link to /students/{id}/score in the _links-section of a student.

So to wrap it up:

• Add categorization and score to the student's attributes directly
• Add a link to categorization and score in the _links-section of a student

This would be comfortable to work with.

The score should be calculated centralized in the API.
I recommend this to be accessible at /api/v1/students/<student>/score.

The following steps might be helpfull

• Finding the formula for the right calculation of the BJS-Score
• Implementing the calculation of the formula
• Implementing a RestController for this purpose

This might help.

Document and test the following requests:
PUT /api/v1/students/{id}/class
or
GET /api/v1/students/{id}/class

• StudentRepository
• SportResultRepository
• UserPrivileges

An endpoint which returns an Excel- or CSV-file for a specific class.
This information could be formatted like this:

This file should then be accessible from the app and the web interface