How does Phoenix ELN relate to legacy Espresso ELN?

[abrechts]

Although Phoenix ELN shares many concepts of its predecessor Espresso ELN, it is a different application, rewritten from scratch and gradually growing in functionality. Some functionalities are similar, but not the same. The overall goal is to reduce previously often unused complexity by concentrating on simple and efficient functionality, often achieving the same goal. Thus:

• Periodic save is replaced by auto-save: Instead of saving the ELN contents every 10 min, the contents now are continuously saved after every relevant change (indicated by the green dot appearing in the tip right corner).

• Project folders now simply organize experiments into folders. No more and no less. In Espresso ELN, at all times complex calculations took place to create reaction sequence relationships across all experiments contained in an individual project folder. And there are no more project categories.

• The materials database now is a collection of last used materials and their properties - no more a manually maintained static list. Its items are added and updated just by adding a material to the protocol, and can be removed via the delete button "x" in their individual materials dialog dropdown menu item. Moreover, the database now also contains about 200 commonly used and so-called preset materials, whose molecular weight and density data were cross-checked and therefore are read-only for protection against unintended changes.

• The Phoenix ELN server database is different from the Espresso ELN one. You will need to set it up as a separate database if planning to optionally utilize the server. The server installer package is available here.

• Due to the complexity of the Espresso ELN protocol structure, a data migration to the Phoenix ELN format will not be possible. Phoenix ELN, on the other hand, will provide a more feasible path for future data migrations.

[Demydoff]

Are you planning to expand the functionality of the program to work with multiple products? For example, separating R/S isomers? Currently, calculating the yields of such reactions in the program is very inconvenient.

[abrechts]

You can do that already. Draw your side product as an additional product in the reaction sketch. In the protocol area, add a product item via the Addition toolbar at the bottom. Then click the "Side Prod (B)" radio button in the header area of the Add Product dialog and you are done.