Date: 3/25/25 10:15 pm
From: Marla Mitchell <marla.mitchell...>
Subject: Re: [GABO-L] ADMIN - Using Banding/Bird Codes in Georgia Birders Online (GABO-L) Posts
Thank you Mark. I was wracking my brain on that one lol!

On Mon, Mar 24, 2025, 4:08 AM Mark McShane <mcshanebirder...> wrote:

> Hi All/Marla,
>
> PUFI is the code for Purple Finch!
>
> - - -
>
> Regarding using banding/bird codes in Georgia Birders Online (GABO-L)
> posts, here is what the official posting guidelines have to say:
>
> the FULL NAME of a reported bird should be used, at least in the first
> reference to that bird within a message. Abbreviations and non-standard
> names should be avoided; they are of little use in a database search.
>
> - - -
>
> Common best practice in most bird/birder forums and bird messaging groups
> is that the first time a bird is referenced in a post or message in which
> the initiator of the message wishes to use a banding/bird code to refer to
> a bird, the writer of the post should FIRST list the COMMON NAME of the
> bird, followed by the CORRECT CAPITALIZED banding/bird code IN PARENTHESES.
>
> For the first use in such a post of Purple Finch the example would then be
> formatted as:
>
> Purple Finch (PUFI)
>
> Any subsequent referral to the bird in the same post could then be made by
> using the already listed, and linked, banding/bird code as desired instead
> of the full common name, Purple Finch example:
>
> PUFI
>
> A sample post excerpt showing proper usage of a banding/bird code in a
> post would be:
>
> I saw my first Purple Finch (PUFI) at my bird feeder a few days ago, it
> was so amazing! I discovered that two PUFI were seen two days ago at my
> neighbor's bird feeder. My neighbor and I are now both trying to research
> and provide the correct and best food items in our bird feeders in order to
> attract as many PUFI to our yards and feeders this season as possible.
> Today my neighbor told me that because PUFI are such beautiful birds they
> are going to put up maybe ten more bird feeders hoping to attract a whole
> flock of PUFI before the end of the season and try to train the birds to
> come back next and every year!
>
> A small s could be added to the end of the capitalized banding/bird code
> to denote multiple birds instead of just one, as in PUFIs... or not.
>
> - - -
>
> One big problem of using codes is that many birders, even very experienced
> ones, use incorrect codes in some cases.
>
> The codes officially originated are not always what one would think they
> should naturally be because of conflicts with another bird name/code in the
> initial generating of the code, so different than obvious codes have to be
> generated.
>
> There are also different sets of codes in use in the world by different
> organizations. Each different coding system uses methodology to resolve
> potential code name conflicts to come up with their codes, and there are
> many conflicts, and so many unexpected codes.
>
> - - -
>
> Folks who do not know about the codes, or how to look them up, or who
> don't want to look them up (not that they should), get confused, some
> people use incorrect codes, there are different codes from different
> systems, and time and energy is wasted thinking about these codes. Every
> year one usually gets involved in, or hears, a discussion about
> banding/bird codes somewhere along the way, usually it's a debate
> concerning if the correct code is being used and why.
>
> However, following the best practices detailed above basically solves the
> whole in-writing problem, even if an incorrect or different code is used at
> least the reader knows what bird the writer is talking about, instead of
> the writer just talking about a code. The reader can follow the bird
> referenced with the code in the post or article and be clear through to the
> end. Using the code shortcut method may not be the best writing solution
> but it can make it easier to refer to a certain species over and over again
> (especially a bird with a long and/or multipart and/or hyphenated name for
> example) in a post or write-up.
>
> In GABO-L posts it's ok to use codes following the above best practices,
> but maybe best not to.
>
> The GABO-L posting guidelines live here:
> https://www.gos.org/georgia-birders-online
>
> - - -
>
> Good Birding All,
>
> Mark
>
> Mark McShane
> Georgia Birders Online (GABO-L) co-admin
> Lawrenceville, Gwinnett County, Georgia
>
> You must be a subscriber to post to GABO-L.
> Instructions for subscribing (and the guidelines) are found here:
> http://www.gos.org/georgia-birders-online Please read the guidelines
> before posting.
>
> Send regular postings to <gabo-l...>
>
> To search GABO-L archives or manage your subscription, go to
> https://listserv.uga.edu/cgi-bin/wa?A0=GABO-L
>
> To contact a listowner, send message to <GABO-L-request...>
>

You must be a subscriber to post to GABO-L.
Instructions for subscribing (and the guidelines) are found here:
http://www.gos.org/georgia-birders-online Please read the guidelines before posting.

Send regular postings to <gabo-l...>

To search GABO-L archives or manage your subscription, go to
https://listserv.uga.edu/cgi-bin/wa?A0=GABO-L

To contact a listowner, send message to <GABO-L-request...>

 
Join us on Facebook!