refactor with_taxonomy_scope to optimize SQL
per Marek's comment on PR 1105
so we find all records within specific location, the find the same for specific organization and then combine these ids which we use in third query? sounds like work for SQL instead of ruby? I understand it's not that easy using ancestry but this does not feel right to me, what do others think?