Attributes used to create Dog Entity
|
Value
|
authority
|
The authority who registers the Litter.
|
earbrand
|
Taken from the Litter attributes for each individual Litter Dog.
|
color
|
sex
|
microchip no
|
whelping date
|
Taken from Litter attributes.
|
lifestate
|
Set to ”unnamed”.
|
stud sire flag
|
Set to “false”.
|
This implies that a State authority should never need to create Dog entities directly in the NDR. The NDR will automatically create a Dog Entity for each registered pup.
4.1.3.Meeting Entity
Figure - Meeting Entity
The Meeting Entity, shown in Figure , defines the attributes of a Meeting.
A Meeting is identified in the NDR by its Track Code, Date and Time Slot.
A Meeting consists of a number of Races. Each Race has some static data, such as Title, Grade and Distance, which can be entered prior to the day of the race. The list of “Dogs in Race” is known once the field is graded. “Result” and “Dog Race Result” are known after the race has concluded.
Note:
The “track code” field of Meeting is set when the Meeting Entity is created in the NDR. The “track held” field of Meeting is used to record the code of the track where the meeting was actually held. “track held” will only differ from “track code” when there was a last minute change in the location of the meeting.
the “name”, “owner name” and “trainer name” fields of Dogs in Race are used to preserve the snapshot of information that was current at the time of the race.
In order to maintain the internal consistency of the NDR, when updating the results of a Meeting, the NDR will automatically update the corresponding Races information maintained within the linked Dog Entity. Note that this update will occur even if the Owning Authority of the Meeting is not the Owning Authority of the Dog.
Dostları ilə paylaş: 
