Upcoming releases and plans
Solutions to solve current issues
Kristian Gray
Internal database - problems
- PostgreSQL is currently not supported within EMBL-EBI
- Current schema limitations makes development difficult
- Parts of the schema no longer reflect the biological data
- Database schema is not truly relational
Internal database - solutions
- Use MySQL which is supported and is the same database as our front end
- Redesign the schema to better reflect the data and fully normalise
- This will allow us to add more sources of data and allow us to query the database easier for reports and development
Internal applications
- New database = new applications
- Rewrite application using modern and widely used frameworks and layouts (AngularJS with bootstrap CSS)
Gene families - Current problems
- Data split between our database and the drupal content
- Curators have to manually create the new drupal page
- No template as such for a family page
- Families have a hierarchical structure which the current pages poorly represent
- Large families are slow to load
Current gene families
New gene families (dev)
- All the data now resides within the database
- Pages are dynamically created using the data with the database
- More information on the families added to the pages
- Easier to find and download gene families of interest
- Will have a Solr search for the families which will lead to an expansion of our REST service
New Gene Families in action