| 92 | Supervisor: Joeri van der Velde, Joris Lops, Morris Swertz |
| 93 | |
| 94 | Outline: |
| 95 | |
| 96 | MOLGENIS makes use of datamodels in XML format. Any change made to these datamodel files requires the entire codebase of the application to be regenerated. This can be make smarter, by finding the differences between the old and the new model, and only regenerating the code that will be changed. |
| 97 | |
| 98 | Additionally, changes in a MOLGENIS datamodel requires a new instance of a database. (typically MySQL) It would be great to have a tool that enables the transition of SQL structure so data can be maintained. This tool would be smart enough to inform users of changed which involve remapping or adding values etc to make the migration work. (....) |
| 99 | |
| 100 | Duration: ~ 3-6 Months |
| 101 | |
| 102 | === Graphical MOLGENIS modelling === |
| 103 | |
| 104 | Supervisor: Joeri van der Velde, Danny Arends, Morris Swertz |
| 105 | |
| 106 | Outline: |
| 107 | |
| 108 | The database structures are modelled in MOLGENIS XML by using text (XML) editors. This can instead be done graphically, making it much easier to maintain overview of larger models. Additionally, it would enable to model applications at runtime, press test and save to configure your application. |
| 109 | |
| 110 | Duration: ~ 3 Months |