Serpwidgets
New member
Joe's description of how it could work is very close to what I think will be done.
The point I was making about trying to make a living off of it is that in order to do so, someone would have to put up a lot of money and effort up front, and that might be all for naught. If they only get a handful of participants, their entire effort and investment is lost. I don't see that "risk" as part of this project for me. The only risk I see is that it would be so well received that we wouldn't be able to keep up with all of the demand. That's a pretty cool problem to have. :crazy02:
Hurley and I decided that we were going to do this for our own collection so that we can offer pedigrees and allow our customers to view the family trees of our own corns. That part was going to be done even if we are the only ones who ever have any "registered" corns. The point is not to assign cultivar classifications, standards, or values to any animals. The point is to allow an owner of a snake, whose ancestors are registered, to use the database to find any available information about those ancestors.
It is only a small step from that to make this available to other breeders. We just need to formalize a few things. I suspect that the vast majority of people who participate will be hobbyists, but if larger-scale breeders want to join in, that can be done, too.
The advantage is that this data doesn't become "fuzzy" over time like our memories do, nor does it require a special effort by the breeder to go look it up and then email or call the customer and relay only what snippets of data they thought the customer wanted.
At the start, we will just be compiling data. There will be check boxes, as shown in the screenshots we posted, for items that we think are useful. This does not "officiate" the validity of anything, it only makes it more easily accessible. There is an "other" field in these areas, along with a catch-all "special notes" field. For example, if someone wants to put "crimson" or "silver queen" or "Naples line" in the "special notes" field, that's not a problem at all. If one wants to register their breeder male as a "green Okeetee" color morph with "plaid" pattern and white eyes, and say in the special notes that it has wings and legs and add "John: 3-16" they can do exactly that.
As long as it is not rated R, I don't see why we would not allow it in there.
We will not be going through policing the data and/or telling people "you can't call that an Okeetee" or, "we don't like the term snow bloodred so you can't put that in the notes." Nobody will be able to make a case that their animals are devalued by us not "recognizing" their naming conventions, unless their naming conventions involve use of the "F" word.
The data on a particular animal will only be as reliable as the people who registered it. That is true of any database. As they say, "garbage in, garbage out." They (whomever "they" are) also say, "consider the source." Since every registration shows the person who registered it, users can judge for themselves what that data is worth to them. The same is true of all registries.
If people see a registry entry that says the snake has feathers and eats aluminum foil, or that a snake--whose father is a cal king--says "pure corn" they can use common sense to interpret the data. (Although the "hybrid" checkbox can be set for any animal whose ancestry in the registry has any hybrids, and a "search for hybrid ancestors" feature will be included.) If some people are putting in stupid or useless data, it doesn't detract from the value of the data put in by anyone else. Putting useless or false data into a database doesn't make it true, but what it does do is provide a paper trail back to the person telling those lies.
Since corn morphology and genetics are constantly changing/growing, it is being built with the intention of being able to add or alter fields in the future with very little effort. This is why we came up with specifications and I wrote the software myself. If certain cultivars such as silver queen or anything else are mentioned often enough in the special notes, it will be easy enough for us to adjust the forms and database to allow a checkbox for it, and for me to write a quick algorithm to convert those items from "special notes" over to the new checkbox in the latest update of the database. It would benefit us to do so, because it saves space and makes the important data more accessible to those searching for it, which is the whole point of having a family tree.
Hurley and I decided that we were going to do this for our own collection so that we can offer pedigrees and allow our customers to view the family trees of our own corns. That part was going to be done even if we are the only ones who ever have any "registered" corns. The point is not to assign cultivar classifications, standards, or values to any animals. The point is to allow an owner of a snake, whose ancestors are registered, to use the database to find any available information about those ancestors.
It is only a small step from that to make this available to other breeders. We just need to formalize a few things. I suspect that the vast majority of people who participate will be hobbyists, but if larger-scale breeders want to join in, that can be done, too.
The advantage is that this data doesn't become "fuzzy" over time like our memories do, nor does it require a special effort by the breeder to go look it up and then email or call the customer and relay only what snippets of data they thought the customer wanted.
At the start, we will just be compiling data. There will be check boxes, as shown in the screenshots we posted, for items that we think are useful. This does not "officiate" the validity of anything, it only makes it more easily accessible. There is an "other" field in these areas, along with a catch-all "special notes" field. For example, if someone wants to put "crimson" or "silver queen" or "Naples line" in the "special notes" field, that's not a problem at all. If one wants to register their breeder male as a "green Okeetee" color morph with "plaid" pattern and white eyes, and say in the special notes that it has wings and legs and add "John: 3-16" they can do exactly that.
We will not be going through policing the data and/or telling people "you can't call that an Okeetee" or, "we don't like the term snow bloodred so you can't put that in the notes." Nobody will be able to make a case that their animals are devalued by us not "recognizing" their naming conventions, unless their naming conventions involve use of the "F" word.
The data on a particular animal will only be as reliable as the people who registered it. That is true of any database. As they say, "garbage in, garbage out." They (whomever "they" are) also say, "consider the source." Since every registration shows the person who registered it, users can judge for themselves what that data is worth to them. The same is true of all registries.
If people see a registry entry that says the snake has feathers and eats aluminum foil, or that a snake--whose father is a cal king--says "pure corn" they can use common sense to interpret the data. (Although the "hybrid" checkbox can be set for any animal whose ancestry in the registry has any hybrids, and a "search for hybrid ancestors" feature will be included.) If some people are putting in stupid or useless data, it doesn't detract from the value of the data put in by anyone else. Putting useless or false data into a database doesn't make it true, but what it does do is provide a paper trail back to the person telling those lies.
Since corn morphology and genetics are constantly changing/growing, it is being built with the intention of being able to add or alter fields in the future with very little effort. This is why we came up with specifications and I wrote the software myself. If certain cultivars such as silver queen or anything else are mentioned often enough in the special notes, it will be easy enough for us to adjust the forms and database to allow a checkbox for it, and for me to write a quick algorithm to convert those items from "special notes" over to the new checkbox in the latest update of the database. It would benefit us to do so, because it saves space and makes the important data more accessible to those searching for it, which is the whole point of having a family tree.