The ability to have multiple, separate, user-named watch-lists is now active.
As a part of this, all existing watches have been preserved, and are now placed in a list named "Watched" (actually, all watches were always on the "Watched" list, but it was not exposed previously).
This should make it a lot easier to manage a large set of watched content, as you can divide series up by your own interest or other categorization scheme.
Series pages can how have a link to the relevant website for the series.
Additionally, the item updating system has been extended to allow it to update the series entries, so that I can now automatically fill-out the description of a lot of the autogenerated series entries, something that was sorely lacking in the past (particularly for the OEL content).
There were a few seconds of downtime during the update process when I had to restart the server processes in order to free any database locks and allow the modification of the DB schema.
Ok, the migration wound up taking about 14 hours before I had the feeder system active.
Everything should be functioning normally again now.
The update system is currently down as I am in the process of migrating the host computer to a new disk array.
The downside is I have to copy a whole bunch of data across, and that takes a non-trivial amount of time. I should be able to selectively prioritize bringing across the scripts and tooling needed to restart the update feeder system before the entire backup is copied, which is fortunate as it will probably take 5+ days to complete the entire data migration.
The upside is: 36TB of space! Whooo!
The whole site was partially broken for a while this afternoon, because of a space issue on the server.
A background task I was running accidentally got out of hand, and wound up actually filling the entire disk, at which point the server started having issues because it couldn't insert data into the DB any more. This broke a bunch of functionality, including a lot of the normal views, since some of the statistics monitoring inserts/updates a row on each render.
Anyways, things should be back to normal now, hopefully.