Regarding Bejewel(l)ed: the next snapshot has the 8-Apr-11 BejeweLLed->Just Saying notification deleted. There's a new notification, presumably a correction by whomever submitted the initial request given that there is a new date of 9-May-11, for BejeweLed->Just Saying.

I suppose you could avoid most ocurrences from the past by investigating cases where there are duplicate records for New Horse names. Officials wouldn't approve the name change in this instance; the duplication means that the elder record would have been superceded.

Don't know how it would've been handled successfully at the time though. I would've updated past performance records for BejeweLLed to Just Saying on 9-Apr-11 and then, none-the-wiser, updated past performance records for BejeweLed to Just Saying on 10-May-11. Just Saying would get both Bejewel(l)ed's past performances. The next time that BejeweLLed raced it would be - in my database at least - as a maiden, having had its prior performances misattributed.

R&S seemed to handle it though. Perhaps they were familiar with the horse, given its record, and noticed something awry. Surely a spelling error on a form that happens to be the name of another horse doesn't happen all too often... In which case I can probably get by

Horses switching names as they flit back and forth between countries seems more of an issue (as the Old Name It's A Dundeel, for Dundeel, seems to imply)