Occasionally the collection script stops working (T214060), and while there are now a couple of things in place to prevent that from happening randomly, it still may be the case from time to time that the script is stopped and the tool is out of date.

We should check the most recent timestamp in the database and if it's more than, say, an hour or two back from the current time, display an informational notice to users that the latest edits may not be reflected in the tool.

Obviously we'd ideally avoid this case arising at all, but this will be a nice feature to have if it ever needs to, such as if we have to load the db from a backup or stop the collection script for any significant period of time.