Comment 1 for bug 1730981

I gave this just a bit of thought today since someone asked me about it. I do think we need YAOUS set for child org units as a parent org may want to search some child shelving locations but not all. For example, a headquarters library that has a book mobile org and a tech services org as children and wants shelving locations for the bookmobile to show up. And it may need to populate up more than one parent level.

So, my thinking currently is a setting for populate parent copy location search and if null it ignores it, if given an integer value it goes that back up the tree to include it's copy locations. One concern I have though is that systems in a consortium could unwitting add their copy locations to consortial search. Thoughts?