There are three options for birth type: {CAPTIVE BORN}, {WILD BORN}, and {UNKNOWN}. This data field is important because, along with the <DAM> and <SIRE> fields, it can be used to help decide which specimens are likely to carry unique genetic information. The options for this data field are straightforward. If the specimen was collected from the wild its birth type should be entered as {WILD BORN}. This is also the correct entry for fertilized eggs or gametes collected from the wild. The birth event should be interpreted as physical separateness from a parent or parents. Therefore, an immature specimen collected with a parent would be {WILD BORN}, while a specimen born to a pregnant female collected from the wild would be {CAPTIVE BORN}. {CAPTIVE BORN} should be used when it is known that the specimen was born in captivity, whether the parents of the specimen are known. There is an important difference between specimens with unknown, but captive-born, parents and specimens whose parents and birth type are unknown. In the former case it is more likely that the alleles carried by the specimen are carried by other specimens in the population. In other words, captive-born specimens of unknown parentage are not considered possible founders under usual circumstances. On the other hand, specimens of unknown parentage and unknown birth type may be considered possible founders, for analysis purposes only, if it is determined that a wild- caught origin is possible or likely given information in other data fields (e.g., date of birth, location of birth). Unknown birth type should be used when the birth type is unknown, and although there are some rare exceptions, unknown birth type will usually be associated with unknown parentage, unknown birth date and unknown birth location.
Birth type is the last option in the first event field and is entered or edited by:
(1) selecting Data Entry from the Main Menu of SPARKS
(2) selecting Edit Animal Data from the Data Entry menu
(3) moving the cursor to the Events window (upper right of Data Entry menu)
(4) selecting event type as birth or wild-caught
(5) entering the mnemonic for location where the event took place
(6) entering local identification number (local ID) at the event location
(7) entering loan as {NO} (unless ownership is being tracked)
(8) entering the date of the event (and date estimate if appropriate)
77
(9) entering removal date and removal date estimate as blank
(10) entering birth type as {WILD CAUGHT}, {CAPTIVE BORN}, or {UNKNOWN}
78
Besides basic information about a specimen's life history and movements, supplementary data may be available for many specimens that will further help the studbook keeper in tracking or otherwise selecting the correct identity of a specimen. The type of information offered in this section may be specific to certain groups of taxa and but not to others. Recording this information becomes particularly important when trying to trace the movements of specimens that have been deceased for some time.
Data of this type are entered in the lower left field of the SPARKS Data Entry screen. Typical data include house names for many mammals (primates, feiids and other carnivores) or other large taxa (raptors, ratites, crocodiles, etc.), transponder lD #'s for most taxa, .tattoo numbers for many mammals, band numbers for birds, ear-tags for mammals, and various clippings for reptiles. Other identifying characteristics such as scars, melanistic features, etc., should also be entered as Special Data. This information is often not, available from old inventory records but rather, from keeper and veterinary reports, and will help to verify a specimen's identity when historical or other information is vague.
Special Data is entered into SPARKS by:
(1) selecting Data Entry from the Main Menu of SPARKS
(2) selecting Edit Animal Data from the Data Entry menu
(3) moving the cursor to the Special Data window (lower left) and pressing return
(4) selecting an existing Special Data field or creating a new Special Data field
79
The <USER DEFINED> field (UDF) allows the studbook keeper or species manager great flexibility when defining the population that is to be managed. With a UDF the user can define a specific subset of the data for analysis. Use of several UDFs simultaneously will allow a creative studbook keeper to divide the database into a wide range of subsets for analysis.
UDFs can be used to identify subspecies, color phases, hybrids, reproductive status, chromosome type, common defects, proven-breeder, in the SSP©, other management plans, etc. Once identified with a UDF, the studbook keeper can analyze, for example, just one subspecies out of the entire studbook database.
The UDF can only be used to select specimens that have been previously given a UDF. The studbook keeper cannot use the UDF to search the database or to sort the database. Also, it is not possible to select the subgroup "not the UDF." A UDF for a specimen does not exists untill it is entered for that specific individual. For example, if one-quarter of the population, is given UDFs designating them as "subspecies A," it is not possible to select the subset "not subspecies A" when analyses are to be restricted to the other three-quarters of the population. If the studbook keeper wishes to select the remaining three-quarters of the population, each of those specimens would need to have a UDF value as »subspecies B" or some other designation.
If multiple UDFs are used at the same time, it is important to be certain which subset of the database is being selected. SPARKS uses boolean logic to select the subset. Therefore, if two UDFs are connected with an "and» (e.g., hybrid and white color-phase), both UDFs must be correct for the specimen to be selected. In the »and" case, only white hybrids will be selected. Using an "or" will allow the specimen to be selected if either one or both of the UDFs are correct. In our example above, specimens selected when using an »or" would be all specimens that are either white or hybrid or both.
Some UDFs will remain constant over a specimen's entire lifespan. Subspecies would usually be such a UDF, unless the specimen was misidentified or the subspecies definition were to change. However, some UDFs may change with time (e.g., nonproven parent to proven parent). When using UDFs, it is extremely important to keep them up to date when their status changes. It is easy to forget this step in updating the studbook, because the specimen is already entered. The UDF is only as good as the studbook keeper's updating service.
80
A UDF can be created or edited by:
(1) selecting Data Entry from the Main Menu of SPARKS
(2) selecting Edit Animal Data from the Data Entry menu
(2) select Define User Fields (lower right of Data Entry screen)
(3) typing F9 to create a new UDF(or F10 to edit an existing UDF)
(4) typing a Field Name for the new UDF (a short title that describes the function of or information in the UDF)
(5) typing in a Fieid Description. This can be a more lengthy description of the UDF
(6) typing in a Field Type. SPARKS will accept three field types: character (C), numerical {N}, or logical {L}
A character field should be used if the information to be entered is letter and numbers, such as with a subspecies designation (e.g., {SUBSP A}). A numerical field should be used to enter a number. A logical field should be used if a true or false designation will identify the specimen. For example, if the UDF is a proven parent, the specimen either is a proven parent or not. Therefore, this logical UDF can be true {T} or false {F}.
(7) once a UDF is created individual specimen records can be edited (F10) to enter their specific designation
The UDF must be entered for each specimen that is intended to be selected in the future.
81