The best news, perhaps of the semester, is that my ibiblio.org contact got Web Curator Tool (WCT) up and running for me. I've been testing different parts of the program, and there are some bugs (I haven't been able to actually run a harvest) but I've gotten a feel for the procedure the software imposes (harvest authorisation -> target creation -> harvest approval -> target instance -> harvest). The interface is definitely more approachable compared with NetarchiveSuite and HTTrack, down to the colorful grains of wheat next to the "Harvester Configuration" box.
It can still feel a little complex, clicking back and forth between harvest authorisation and target, but I think this is due to (1) my lack of experience with the program (2) some lingering bugs and (3) the fact that setting up the authorisations and targets would require more time investment in the beginning than after your staple harvests were configured.One point about WCT that vexes me is the difficult install. If I was presented with these three tools, without any prior experience, and told to evaluate them based on interface alone, I'd choose WCT above the others in a heartbeat. But ease-of-use balanced against installation tribulations is a harder decision to make. Not being the installer doesn't really alleviate that tension for me, either.
Also, the harvest authorisation feature of WCT would not be an especially useful aspect of the program for archiving UNC sites. This can be done without gaining the creator's permission based on public records law. The HA feature then becomes a superfluous extra step. On the other side of that coin, in the future, if UARMS or another department wishes to expand the scope of their web site archive to other sites for which permission is needed, this feature would become very useful, because it helps keep the temptation to crawl on the sly at bay.
Another feature of WCT that could work to slow or facilitate the workflow is the harvest approval. If you're a lone harvester, getting approval from yourself is just an extra step. But if multiple people are wrangling and suggesting different harvests, this helps portion out the resources.
I can't comment on the harvesting feature, but will do so if we can make it work in the next few days. Testing it has held up the opinion I gave at the end of my poster: right now, HTTrack is a good option for UARMS, but WCT would be a very nice alternative in the (technologically-supported and web-site-archiving-program-developed) future.