The focus in the latest release of Globalese is on corpus lifecycle management.
Corpora in Globalese are maintained centrally, meaning you only have to upload a corpus once and then you can re-use it in as many engines as you wish, in either language direction. Needless to say, some corpora change more frequently than others, and if an engine is centred around a translation memory that gets updated every day, the engine might quickly become obsolete. The way this can be tackled is to first update the corpus, and then re-train the engine so it can reflect the changes.
Up to now, updating and re-training existing engines meant taking the following steps:
Upload the most up-to-date version a corpus.
Edit all the engines that were trained on said corpus, removing its old version and adding the new one.
Re-train all affected engines.
Delete the old, no longer used version of the corpus from Globalese.