Feature: Provide study-events per proband endpoints

[motey]

Hey @JTaeger and @lamuc i am just looking at the API design and trying to find a better solution that represents our goal ( of having the proband at the root which does have an interview at a specific event) better then the current solution. While thinking i actually dont see a problem with the current design :)

A study has a fixed list of Events which we can manage with the event chapter of the API:

A patient now can have a interview in any of these events:

So what is wrong with the api/data-model? It is just a matter of presentation in the GUI! The user need to select the event while starting a new interview with a proband. Prove me wrong! :)

[motey]

As discussed in a meeting, we need an endpoint that returns all events on a proband level. We need to know if a proband has allready one or more interviews in a event. Also we need events to rankable.

[motey]

All mandatory backend changes are implemented in https://github.com/DZD-eV-Diabetes-Research/DZDMedLog/tree/rewrite/feat-events-by-probant (Luckily without the need of a major refactor 😅)

New backend/API features:

• Interview
  • interview_number becomes interviewer_user_id and is now a foreign key to user table (attribute fill in, will be handled by backend)
• Event
  • Event has new attr order_position which is the default order_by attr
  • New endpoint /study/{study_id}/proband/{proband_id}/event which
  • Lists all event but additionally includes the proband_id and the number of interviews for given proband under each event proband_interview_count.
  • Events with zero interviews can be excluded with exlude_empty_events in the query params
  • New endpoint /study/{study_id}/event/order.
  • Provide a list of event obj or event IDs and the backend will apply a new order_position in sequence of the given list.

[motey]

@JTaeger this is yours now. Lets discuss/test/merge that when you are back in town.

Update: Merged it allready in python/rewrite for the sake of https://github.com/DZD-eV-Diabetes-Research/DZDMedLog/issues/26