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.
My Texas checklist contains 17 unwanted species of various exotics. I've tried updating it using the official TX checklist of 664 species using the 'get latest checklist data' button from the copy buffer and this sems to work. But when I create a preview of this checklist under report it still shows the 17 bad species. I suspect it may be because one or more child checklists for Texas Counties has these species in it. This happens when I use an eBird checklist to create a BD county checklist since ebird includes all these exotics. Do I have to remove all these exotics from every county in Texas so they don't show up in the Texas Checklist? Or is there an easier way to accomplish this?
When I load the Texas checklist in Checklist editor it only shows the actual species not the exotics. What's going on here?
Hi Gary,
Thanks for posting. And for the detailed explanation. It makes assisting you much easier.
Everything in BD, except for the Checklist Editor, includes all of the descendants of the specified Location. This is why the Checklist Report includes things attached to descendant locations of Texas, but the Checklist Editor ONLY shows those Things attached to it. If the Checklist Editor didn't work that way, you wouldn't know which location you were modifying.
Do I have to remove all these exotics from every county in Texas so they don't show up in the Texas Checklist?
Yes. Although it might be easier to edit the locations for each of the 17 exotics (the right side of the Checklist Editor) than removing the exotics from 50 locations (if that is how many descendant locations have the exotics).
Or, you could mark the 664 expected species as Common in the checklist editor, leaving the 17 exotics marked as not Common. Then, in the Checklist report, check the box that says Include Only Common.
We didn't plan for such a situation in the design. But it wouldn't be hard to add a new checkbox to the report that said "Only This Location".
What is the easiest way to figure out what descendent checklist contains the exotics? I'm having trouble finding out where they came from.
Hi Gary,
Load one of the exotics into the right side of the Checklist Editor and look for the descendant location that doesn't belong.
Uncheck the one or more locations that are descendants of TX and click the Update button.
Let me know if I can assist further.
Thanks for the help.
Yes that worked perfectly. I never figured out how that worked before your explanation.
