I've added a sub-groups feature to the groups widget.
If a group contains sub-group(s), they will displayed in the same way that individuals are currently displayed - comma, separated list in their own section. I decided not to just dump the sub-group members in to the list of individuals in the parent group because the sub-groups are frequently (or at least sometimes) included in the parent group as a group (e.g. 'sons of Thestius' are mentioned as a group when included in the Calydonian Boar Hunt).
Clicking on a sub-group name will display information about the sub-group.
Sysadmin fixed the ACLs (there were two sets of entries, apparently, which confused the process for a while), and now the machine is up and running with Jenkins on port 8080. I tried moving it to port 80, but was prevented by the Ubuntu rule which won't allow a service not running as root to run on a port below 1024 (and we definitely don't want Jinks running as root). So I may end up running Apache just so I can proxy it to port 80. Seems like overkill, but there doesn't seem to be an alternative solution.
I'm going to run the two machines side by side until I come back from vacation, so we can make sure the new one is stable before we switch to it and bring down the old one.
I'm now working on a second transform to be applied to the result of the first. This one already detects sale-to-self situations (although it doesn't find any -- waiting for some known data from JS-R to see why) and possible family sales. I'm now working on building the transaction chains, but I'm not sure whether this can actually be done with XSLT or not, because you need to keep a tally of which items have already been processed, and I can't yet figure out a way to do that.
As well as building a new Jenkins machine today (blogged in Maint), I've been working on the proposal for dereferencing of private URIs, and looking through and commenting on some other tickets assigned to me.
In between other things, I've made a good start on the next stage (based on the notes here). I've coded a transform which does the following (so far):
- Expands each owner to include full ethnicity information inside the owner element.
- Expands each title to include a full property element inside it, as well as a list of expanded owners, and a list of preceding titles.
This is already a long way towards creating the sort of big flat file that will make it easy to trace transaction-chains back in time.
The new VM was set up today, so Greg built it with Ubuntu 12.04, and I ran my Jinks-builder script on it. Everything seemed to go perfectly, and presumably it's building away behind the scenes, but because the ACL prevents any access to it except on port 22, I can't get in to finish the setup yet. We'll get there eventually...