We have also been learning from the global software community when you really do need to 'Kill it with Fire': what are the characteristics of code and of organisations that mean that it is a good idea to give up, and if so how to -manage the rewrite. The answers are "almost never" and "don't": as explained in this summary of the book 'Kill it with Fire'. +manage the rewrite. The answers are "almost never" and "don't": as explained in this summary of the book 'Kill it with +Fire'. + +
Replacing old systems, and changing their architecture, while keeping them operating continuously, is now +a well-understood +software engineering process comprising a dozen separate techniques. With troggle, we can probably fairly easily replace the cross-referencing +between different types of things (e.g. logbook entries, survex files, persons, expedition days) but we will find it tricky to replace the +sychronisation and concurrency that SQL databases give us 'for free'. We are waiting to see if Django comes up with something cunning as it steadily +converts to a more asynchronous architecture using python asyncio.
Perhaps you can program something external to troggle, in JavaScript say, using troggle data?