Clone wiki

jummp / roadmap

Planned developments

Please note the list below is provisional and subject to change.


  • Model sorting according to configurable criteria
  • Capture keywords for models
  • View of audit trail for a model
  • Refined notification system
  • User settings and favourite models
  • Model templates
  • Request access to a model
  • Support for model reviews
  • Secured programmatic access, retrieval and update of private models using OAuth
  • Capture link between parent models and descendants

Technical updates

  • Upgrade to Grails 3
  • Performance-related improvements
  • Server-side caching

Past milestones

  • Improved model search
  • Core infrastructure with plugins
  • High level support for multiple database engines (testing using MySQL and PostgreSQL)
  • High level support for multiple version control systems (SVN, Git)
  • High level support for multiple remote access mechanisms (JMS, DBus, Apache Camel)
  • Scalable and versioned storage infrastructure
  • Initial support for SBML
  • Batch models submission
  • Switch to Java 8
  • Model submission pipeline (with support for additional files and basic metadata)
  • Initial support for OMEX archive
  • Proper themes for UI
  • Models browsing: paginated list of all hosted models the current user has access to
  • Initial model display: overview, files and history
  • Support for PharmML
  • User management: user account creation, update and management
  • Handling of publications: attach publication to models and display their details
  • Model publication: make selected models available to all, without the need for login
  • Web services (using REST): programmatic retrieval of specific public models
  • Upgrade to Grails 2.5
  • Richer model display for models encoded in standard formats such as PharmML
  • Pre-visualisation of additional files (supporting many text file formats including CSV, images and PDF files)
  • Improved model submission and update (better handling of main and additional files)
  • Some user preferences stored (for example for model browsing)
  • Generation of audit trails for each model
  • Contextual help to allow the display of some help related to the current display/action
  • Creation/edition of user teams
  • Sharing of models with specific users and teams
  • Basic user-specific notifications via his/her homepage (and email)
  • Improved search engine (with extraction of additional information from ontological terms and controlled vocabularies)
  • Model classification supporting simple tags and facets
  • Flexible strategy for capturing high-level model metadata