Create a database model to store meetings, groups and users about jitsi-magnify HOT 8 CLOSED

Proposal for the database modeling

from jitsi-magnify.

@sampaccoud. Would it be possible to review this database model ?

from jitsi-magnify.

The graph would be easier to read if you liste the foreign keys and many to many links? Not sure if it's possible.

For Meeting:
Use DateTimeField instead of DateField. You don't need the boolean fields for days of the week as you can do start.day... In our https://github.com/openfun/marsha project from which you can reuse a lot of code as it is based on Grommet and the same Ux design as yours... we have chosen to define start and estimated_duration instead of end... and we derive the end by calculating start + estimated_duration. See in this app for example : https://github.com/openfun/marsha/blob/master/src/backend/marsha/bbb/models.py#L108

I didn't understand in groups the sentence : "for anonymous users we create a link". But indeed we need a way to define some emails (phone numbers?) as members of a group for users that don't have an account, right?

For roles on a group or a room, I think we need through models to carry the role? Maybe they can be drawn on the graph.

For Jitsi settings, will it be a json document that we save? Can we retrieve it for an on-going conf from the API? Or should we manually detail in a form all the settings that we want to allow saving?

from jitsi-magnify.

Graph
Yes, we can work on that

Meetings
A meeting has indeed a start (startTime, or better start_time) and a duration (duration, or estimated_duration). But it can be recursive: "any Monday, Thursday, Friday, at 10AM, from the June 6th to the July 8th. So the boolean allow to encode it in an easy way (and easy to retrieve too)

Reuse of marsha
If we need to reuse parts of the code of marsha, the best would be to extract it from marsha to a third lib... not an easy task to achieve... That's the kind of consideration that make me a fan of making small reusable libraries.

Groups
In the groups, we imagine 2 ways of adding user to a group:

• Either we invite users by adding their email, and so they need to connect using an account proving they possess this email (either on magnify, or on another provider)
• Or we generate a link for this group, with a token and a tokenId, and any user accessing the meeting with this token is considered as a member of this group.

Roles
This should be discussed indeed. For now we assumed a room can have a single admin (by default the creator of the room), and many groups that are members. A meeting can also have a single admin (by default the admin of the room) a groups that are invited. Do we need a mode elaborate role system ?

Settings
For now, I'm not sure of the structure of the settings. If it's a simple key-value, we can keep it in the pg database. It would be better if we can save it from a meeting indeed.

from jitsi-magnify.

Here is an update on the database model, with improved naming and relation displayed.

from jitsi-magnify.

Jitsi settings : in Django the name settings is already used for something else... so maybe call it JitsiConfiguration.
Since you already have a group Membership class, I would add a field "role" to it and avoid the "admin" foreignkey to duplicate the membership...
For the room admin : ok to start with only one admin in the Ux but it's not much more expensive to materialize the foreignkey via a relation as well in db knowing that you want several admin users soon? The hard part that will delay the feature is the frontend I think.

from jitsi-magnify.

Note that AbstractUser does not really exist in db. It is only Python code inheritance but there is only 1 User db table.

from jitsi-magnify.

Updated version

from jitsi-magnify.