Developmental Timeline

Timeline and Milestones as January 23, 2023

This is an update of the notes on how the JThermodynamicsCloud will be developed over the next half year as of January. This basically is an informal list of priorities and goals with very approximate times when the tasks are expected to be completed. This can also be used to see what type of developments are in the works and their priorities.

This is a document that should be updated continuously.

Currently, important goals are priorities.

The first is to get a 'working' version where some sort of calculations can be made to be out as soon as possible. This version will be available to partners interested in using and developing the database to give them some insight of what is to be expected (Look and Feel). This aspect has been delayed, mainly for the further development of reading in the database and, most importantly having a clear user login and managment procedure.

The second is to have an initial version of user management. This is important step in leading to the user having their own databases to update. An important aspect of this is the interaction with the 'Standard' database made available. The management of users will develop over the next few months, increasing in security, what the user can do and the interaction with dataset collections used for calculations.

The third is to get a version ready, again for partners, so that they can start actually inputting their own data and building their own database. This version will undoubtedly be buggy, but the initial aim is to be that if the input is 100% correct and the use of software is 100% as was intended, then a valid database can be built up. Together with the partners, it is hoped that later stages of the interface will be more user friendly.


Initial Goals and Priorities

  • Middle of February: A demonstration version of JThermodynamicsCloud will be available on the cloud. This version should demonstrate the look and feel of the website. Calculations using the 'standard' database should be possible.

  • End of February: A demonstration version, particularly for partners, where users can produce and use their own database. This is a typical beta-version, if it the site is used 'properly' and the data read in is absolutely correct format, the system should function okay. Error detection and recovering from errors at this point is not guaranteed (may require administrator intervention). Each user would have their own account.

  • End of February: Organization of 'standard' data file as a basis of a complete database (also to be used as patterns for new data).

  • Feburary-April: The robustness of the website experience should improve (again with cooperation with partners).

  • March: Improvement of the visualization of individual pieces of fundamental data. This includes the visualization of 'related' and 'traceable' data. This would also include outputing files containing the database element

  • March: Before this point, data input is largely done by reading in of blocks of data in input files. During this development time, updating (and maybe even creating) individual pieces of fundamental

  • March: The ability to transfer fundamental data from one dataset to another (this includes making a clone of an existing database)

  • March and beyond: Incorporation of new data introduced by partners.

For the most part, until Summer 2023,