Received the following email from Ron Tiller at HDW:
--quote:
"A horse named "Man of Chrome" with 2 spaces before Chrome has been in the Jockey Club Registry and the Equibase data since being registered. This was an error. It should have had 1 space. "Man of Chrome" with 1 space is the correct name and the name currently in the Equibase (and hence HDW) database and Jockey Club registry. Somehow that horse has existed in the official jockey club registry with 2 spaces for as long as the horse has been registered. It was changed to "Man of Chrome" with 1 space on July 13th, after the final data file had gone out from Equibase for the race on July 15th.
Thus, "Man of Chrome" with 2 spaces was in the racefile for July 15th. From that point forward, "Man of Chrome" with 1 space is the official name and will appear that way in all future data files should the horse run again.
I spoke with somebody at Equibase and this is the first time either she or I can remember something weird like this happening - i.e. 2 spaces errantly entered into the horse name instead of 1. Because I assume customers storing the PPs are using the horse name as part of the primary key, this is really tantamount to a name change.
I just thought I would give you a heads up in case you are accumulating horse PPs in a permanent database.
Ron"
--end quote
If you are using JCapper with either HDW or Brisnet data -- I doubt this will impact you.
The next time the horse runs (provided the horse races again) I fully expect the horse's previous running lines to be in your data file -- and everything to run smoothly.
BUT --
If you are maintaining your own outside of JCapper data project:
I recommend you read the above email from Ron carefully -- and make your own determination how this might impact your data project.