Home › Forums › Developers › General developer's discussion ›

Concept for Breeds

Submitted by Ben_Charlton on Fri, 30/05/2014 - 13:40
in

veNOm breeds present a problem which I think is also an issue for any practice that deals in legal paperwork for dogs.

Often owners walk in and declare the dog a Labradoodle and when i explain that isnt a breed they get quite upset (because they paid exorbitant amounts of money for a crossbreed) 

However as we often are involved in exporting we are required to declare the dog as it stands

a Labrador x Poodle.

veNOM has no provision for this with the exception of Crossbred.  This is not adequete legally as many airlines and countries want the primary breed declared...which i know many argue is often impossible to determine. 

So hence I would argue that the breed field should actually be called Primary Breed, with the possibility of adding a Secondary breed being added. the secondary breed field could hold 1 of three things 

1. Purebreed

2. generic crossbred

3. specific secondary breed - veNOM coded.

This gets around the most common data entry problem I see in practice data the presence of 50 variations of 

Terrier x Lab

Terrier x Labrador

Terrier x Labrador Retriever 

etc etc etc

 

‹ Nesting Constraints in a query veNOM codes ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Concept for Breeds

Submitted by tanderson on Fri, 30/05/2014 - 14:26.

VeNom does have codes for Labradoodles:

  • Labradoodle - Miniature
  • Labradoodle - Standard
  • Labradoodle (unspecified)

Where VeNom doesn't have a breed, this can be supported by allowing lookup.speciesVeNom to link to either lookup.breedVeNom or lookup.breed. This enables practices to create lookup.breed codes as required, whilst still using VeNom species codes.

To add support for secondary (sub?) breeds by:

  • creating a lookup.secondaryBreed lookup
  • creating a relationship lookupRelationship.secondaryBreed that can have lookup.breed as the source, and either lookup.secondaryBreed or lookup.breedVeNom as the target

If you were going down this path, you wouldn't use VeNom species codes as this would make all of the VeNom breeds available for the Breed field. Instead, you would:

1. define your primary breeds as lookup.breed

2. define secondary breeds as lookup.secondaryBreed where there is no corresponding lookup.breedVeNom

3. add relationships between lookup.breed and lookup.secondaryBreed or lookup.breedVeNom where required

 

 

Syndicate content