Wow! I love that you guys are posting these neat ways of using BD! Thanks so much.
Kathryn, your idea for how to use Checklist data, along with Locations and Lifer Bars is really unique and something I have never seen before.
Thanks Jim for posting the concept of multiple parents for locations (something you will NOT find in any other tool) and something that has been part of BD since v3.0.
But Jim, I don't see how your multiple-parent solution is going to solve Kathryn's problem. She wants her sightings to automatically be included for location "Code 1", but only for those birds tied to that location in the Checklist editor. The lifer bar code functionality will could all birds seen at the specified location, and all descendant locations, regardless of whether they are tied to that checklist location or not.
The right side of that lifer bar - the background gray bar - comes from the total species linked to that location in the checklist area; while the green and blue bars come from actual sightings rolled-up from that location and all descendants.
So, if she makes it a parent of "ABA Area" then she automatically gets all sightings in the ABA Area, but that will include species not tied to that location in the checklist editor.
If she makes it a child of the "ABA Area", then she will not get any sightings.
Kathryn, if you make it a child of the "ABA Area", you can use the "Clone Sightings" feature in View/Edit to Clone sightings of Code 1 birds to that location. But this seems kind of clunky to me, as you will have to remember to assign all future sightings of any such birds to both the location you saw it at, and the Code # location it applies to (e.g. 1, 2, 3, 4, 5).
The one way I would do this, that doesn't include Lifer Bars (sorry), is to create a UDF (user-defined Field) of type List. The list of course will contain values such as "Code 1", "Code 2", etc. Then as you add sightings, set this value. Now you can quickly get sightings reports for all Code1 and/or Code 2 and/or etc birds seen for any particular location hierarchy. But this won't work for Lifer Bars. Which has limited functionality of Observer, Location, Taxonomy.
Unfortunately, Life List reports don't contain UDF functionality at this time, Trying to get that into V4.0. [Ok - 4 hour time span in between writing this and going and adding UDF support to LifeList reports!!!!!! - available in V4.0!]
So, back to how we might get this to work with Lifer Bars and Checklist Locations. The only thing I can think of is to create the UDF mentioned above and tag your Band 1, etc birds in that UDF field. Until v4.0, you can generate a Sightings report for UDF.Code = # and get a count of species you have seen with that code.
That is all I can think of right now as my brain is much after getting UDFs to work in Life List reports.
Let me know if this sparks any questions or further ideas.