Our present system uses a set of abundance and
status code to describe the occurrence of each species on the Utah
checklist in the simplest and most accurate form it can, using these
codes. It was initially instituted in the UBRC checklist of
1998 which was printed and distributed in great numbers.
Here's a link to our
present checklist
(the one we are working on now) which uses that system..
Here's an example of
some codes from our present system:
Lesser Scaup CT,RS,UW
Ruddy Duck CP
Horned Grebe UT,RW
Eared Grebe CS,RW
Band-tailed Pigeon US
Subcommittee rationale:
It's the system we've been using since 1998, so would be easy to
update. It describes the occurrence of each species in a
simple yet fairly accurate way. Comments by
Mark:
Since there is no committee here in San Blas, nor any
existing checklists, I’ve been writing my own for many years now.
I’ve had a chance to see what works “best,” in terms of efficiently
imparting the most information possible.
My opinions on the three formats presented are as follows:
1) This system is too simple, a bit arbitrary, and doesn’t offer
enough information. It goes to far towards simplicity, in my
opinion.
2) I’m not very keen on this one, either. Although it tries to be a
simplified bar chart, I think that 3-month quarters isn’t a fine
enough resolution, and doesn’t fit the cycle of most birds very
well. We could make this better by defining “winter” as Dec-Mar,
“spring” as April-May, “summer” as June-July, and “fall” as
Aug-Nov., that would fit the annual cycles of most Utah birds
better. My other objection is that it’s not an easy layout to read,
and would have more letters than necessary for species whose
abundance doesn’t vary through the year.
3) This is my favored system, and closest to what I use, though I
also include other letters and symbols to give even more
information.
But I think one of the most important aspects of any system is how
the elements are defined. This is where you can add clarity to a
cryptic and arbitrary system.
|