This page serves to provide an insight in the design of the core microservice.
As of right now I am unsure whether to put this here (GENERAL) or on the core confluence (OMSCORE), for the time being I put it here to have everything in one place, and there is not much else anyway right now.
Database
Current
The current, and considered old, database diagram. This is a direct database export using auto lay outing. Considering this is only here for historical purposes not much effort was put into this.
Due too automated generation the links between tables might be incorrect.
Diagram 1. Old database schema
.png?version=1&modificationDate=1493298264536&cacheVersion=1&api=v2 "OMS-CORE database old")
Stripped new version
Old database stripped from some tables which should no longer be used (or are removed because they will be added again in the future (in their own microservice)
Diagram 2. Auto generated stripped database schema.png?version=1&modificationDate=1493299048505&cacheVersion=1&api=v2 "OMS-CORE database stripped")
Some thoughts/proposals on this:
- Rename users to members
- There is too much overlap in fields between users and recruited users
- It is questionable what linking organization roles to bodies directly adds.
- The module concept is probably outdated considering the new architectural design in which the core is less monolithic
- What is the difference between module pages and menu items?
I have not yet taken a detailed look at the fields inside the tables.
Diagram 3. Edited stripped database schema
.png?version=1&modificationDate=1493300236384&cacheVersion=1&api=v2)