Saturday 25 May 2013

[cobirds] Re: COUNTIES PLEASE

Joe, I had a problem with sending in a message to Cobirds last year. Ira
Sanders called me from, I believe, Chico Basin, with several good birds. He
asked that I send them in to Cobirds. I did this, using my daughter's
iPhone. And I used my name and home base of Centennial in my message.
However, they were never printed and I was never contacted for more
information.
I appreciate your informative post. But we have problems already with
reports from afield.

Karl Stecher
Centennial

Joe Roller writes:

> Yes, when reporting a sighting it is wise to include the county name in the
> subject line. Very helpful.
>
> And I also agree with Steve Stachowiak The implication of a quick phoned-in
> note is, "Stay tuned for more details, I am busy
> collecting a DNA sample."
>
> We can help each other by reading such a post from somewhere out in the
> Boondocks, recognizing where the call is coming from and perhaps sending a
> quick note to Cobirds
> explaining more details about how to get there.
>
> An example:
> "Congrats to Big Bob Birder and his cousin, Marybelle, for finding Barred
> Owls at "Maggie's Farm!"
> For those of you unfamiliar with Maggies's Farm, that freeholding is in
> Cheyenne County. Detailed directions to Maggie's Farm (where no one works
> no more) are copied here from the CFO County Birding website:
>
> *<<Picturesque Maggie's Farm has been a Cheyenne County birding hot spot
> for over six months now. It has been *
> *good for eastern passerines and the habitat looks great for Tufted
> Titmouse and who knows, even Barred Owl is possible.*
> *Directions:*
> *Drive 5.22 miles east of Cheyenne Wells on Highway 40, past the airfield,
> then watch for 44 Road. Maggie's Farm *
> *(fee area) is on the southeast corner of Highway 40 and 44 Road.*
> *DeLorme page 103.*
> *>>*
>
> Please do not play a Barred Owl tape or handle the nestlings.
>
> Good birding,
> Full name, city, and state, here.
>>>
>
>
>
> submitted by:
> RIchard Joseph Roller,
> Denver, Colorado.
>
>
>
>
>
>
>
> On Wed, May 22, 2013 at 12:30 AM, Steve Stachowiak & Melody Egge <
> waxwing2@q.com> wrote:
>
>> I would hope that there is still some leniency granted for those posts
>> that may be lacking in correct protocol that are made on the fly from a
>> cell phone in a remote location with bad coverage in order to get the word
>> out on a good bird, even if those pesky four letter banding codes are used.
>> ****
>>
>> ** **
>>
>> Good Birding,****
>>
>> Steve Stachowiak****
>>
>> Highlands Ranch, CO****
>>
>> *From:* cobirds@googlegroups.com [mailto:cobirds@googlegroups.com] *On
>> Behalf Of *Mark Peterson
>> *Sent:* Tuesday, May 21, 2013 11:59 AM
>> *To:* cobirds@googlegroups.com
>> *Subject:* [cobirds] Re: COUNTIES PLEASE****
>>
>> ** **
>>
>> I would also add, there are a number of volunteers who try and extract
>> information from COBirds for CFO's quarterly journal and for ABA's North
>> American Birds. These volunteers are regional and have specific counties
>> they cover. It makes it much easier on them if they can search COBirds by
>> the county as searching by a city name is really not feasible. You
>> may occasionally have reports for multiple counties, if you at least list
>> all the counties in the body of the email they will get found by a search.
>> ****
>>
>> ** **
>>
>> ** **
>>
>> Mark Peterson****
>>
>> Colorado Springs
>>
>> On Tuesday, May 21, 2013 11:26:51 AM UTC-6, Todd Deininger wrote:****
>>
>> Make sure when posting a sighting that you include the county of the
>> sighting in the subject line.****
>>
>> ****
>>
>> There are 64 counties in Colorado and county listing is popular among
>> COBirders. Others are only interested in their local patch, so a quick
>> scan of the subject line in all that is needed.****
>>
>> ****
>>
>> Thanks all and keep the posts coming. And remember all emails need a
>> complete signature. ( Full name, City, and State)
>>
>> --
>> Todd Deininger****
>>
>> List Manager
>> Longmont, CO****
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Colorado Birds" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to cobirds+unsubscribe@googlegroups.com.
>> To post to this group, send email to cobirds@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/cobirds/82078fd0-4f0a-4594-9cc5-7ca23293febb%40googlegroups.com?hl=en-US
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>> ****
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Colorado Birds" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to cobirds+unsubscribe@googlegroups.com.
>> To post to this group, send email to cobirds@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/cobirds/000501ce56b5%24c9986480%245cc92d80%24%40q.com?hl=en-US
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups "Colorado Birds" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cobirds+unsubscribe@googlegroups.com.
> To post to this group, send email to cobirds@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/cobirds/CAJpZcUDqRiseZdKB2S%2Bp5rmG1L9OyhxpsH7WNGn8DvZQfanQDg%40mail.gmail.com?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


--
You received this message because you are subscribed to the Google Groups "Colorado Birds" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cobirds+unsubscribe@googlegroups.com.
To post to this group, send email to cobirds@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cobirds/20130526025022.3062678018B%40mailhost.idcomm.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment