Andrew, it’s nice to hear from you, and what you have to say about the workflow in getting the data to the user is interesting, and it’s especially gratifying to know that the process has been so well optimized. This is as it should be.
My particular beef - and the reason I use the ironic term “interesting times” - is with the time-delay in presenting corrections to mistakes in the data to the user. To my mind, the user - the customer if you will - is the most important part of this particular equation and, if I were administering such a system, I would take steps to ensure that the user is served with the corrected data ASAP. Which would mean that, for such cases as this one, the workflow should include an extra step to get the data changed in the database as soon as is practicable, so that the user can have timely access to the corrected data, even though the changes may not yet have been made to the background working documents.
It would seem, however, that the current SOTA ethos is to get the documents in order first, and the customers will just have to wait until the changes have percolated through an inflexible system (it’s two days later, and we users are still waiting for the corrected data). IMHO, that should change, but the professionals in the MT might well have a different take on the matter.
Lastly, I’m not at all suggesting that the MT should be perfect - we all make mistakes; it’s par for the course, since we’re involved in creating and maintaining complex systems. Even the inexpertly-written SMP (which somehow manages to stagger its’ way into the user’s browser) has at least some degree of complexity - no doubt the planned replacement for the SMP will be written professionally from the ground up…