...
- The separate 'userprefs' application was dropped, MyTimetable is now one single deployment.
- Spring was introduced as application framework, for dependency injection and database management.
- Spring MVC is now used for the web controllers (instead of custom servlets and JSP pages).
- Spring Security is used as authentication and authorization framework (instead of custom authentication code).
- Syllabus Plus support was separated from the application core. In the future it will be possible to add other timetable providers or integrate other data sources.
- The SOAP based CalendarItemsService is now deprecated in favour of the new REST API.
- SAML authentication is now available, tested against SURFconext.
- New OAuth2 endpoints, using Spring Security OAuth, were introduced.
- Upgraded build system to Gradle 1.1 (1.2 should work too, but still has to be formally tested).
- MyTimetable now uses a Java 1.6 build. This drops support for Blackboard 8. Java 1.7 is still unsupported and untested.
- Scientia Enterprise Reporting Database 3.2 support was introduced. This support is still preliminary and production performance of the 3.2 reporting database is not yet up to par with the old reporting database format. Please contact our support department to discuss the details.
- Default session timeout is now 120 minutes.
- Virtual host filter added to force clients to a specific hostname.
Outstanding issues
- A couple of features that existed in MyTimetable v1.7 still have to be implemented in MyTimetable v2.0. The following list summarises the most important ones:
- OAuth client side
...
- Configuration reloading
...
- LDAP server failover support
...
- Internationalisation of Syllabus Plus data
...
- OpenSSO support
...
Future roadmap
...
- Blackboard integration
...
- Multiple year support in the mobile interface
Future roadmap
Eveoh does not provide a formal roadmap for MyTimetable. New features and bug fixes are primarily driven by customer demand, and the needs of our customers change continuously. However, there are several features that are high on our 'wish list'. The list below summarises and discusses these features. We are always open to feature suggestions, so please let us know your ideas! Due to the open source nature of MyTimetable, larger features usually require sponsoring from one or more of our customers.
- Better Microsoft Exchange, Office 365 and Google Calendar integration — The current iCalendar feeds can be unreliable at times. By implementing a 'push-based' link to calendaring application we will be able to provide a better and more consistent user experience.
- Notification of changes in the timetable — A user should have the option to receive a text message or email if his or her timetable changes. The new Scientia Reporting Database offers 'last changed' timestamps and using this information we hope to make some progress in this area.
- Multiple datasources and new datasources — Other datasources (ranging from other timetabling software vendors to university web site events) will be supported by MyTimetable. It will be possible to use these datasources at the same time, which will also drop the need for a manual 'database year' selection by the user.
- Better authorisation options — Using the new Spring Security framework we can provide much more granular authorisation checks.