Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Use the Community Sharing forum for sharing Photos, Trips, Stories, etc.
Setup your Forum photo and profile here.
I was refining location data for some old trip reports just now and had a strange notice show up. Here's the background. I was looking at an old trip report for an outing from some years back and the location for this trip was Jalisco. Since this report was a conflation of a couple of days birding in and around Barra de Navidad I thought I would update the location info. Both Jalisco and Barra de Navidad were already in BD. So, I opened the view/edit sitings screen, entered the date for the sightings entries, selected all, and changed the location name for the entries. Up popped a notification saying that this was the first world sighting of the 'Flammulated Flycatcher'. See attached snip.
So, my life list count did not change, nor should it have, so I am not concerned about errors being introduced.
But it is curious Jeff that something like a location name change would trigger this response. Any thoughts?
BTW I have a backup of my database from before I made this change, if you should need it.
Hi Brian,
Thanks for posting and providing all the details you did. It makes diagnosis much easier.
This is actually working as designed. After the changes are made to each sighting, it checks each to see if it qualifies for World, Annual, or Location lifer; and then pops up this notification if any change qualifies. In this case, this sighting of a Flammulated Flycatcher is the first ever for observer "L & B". It may have already been the first FLFL seen by this observer, so the popup is redundant; but it is correct.
fyi
