Comment 7 for bug 1739460

Elaine,

The patch as it stands only addresses the editor, not the template UI. The way the code knows what libraries to pull locations for is by looking at the set of copies that the user has chosen.

With that in mind, I'm struggling to find a clean way to choose which library or libraries to use in the template context. Certainly we don't want to simply load all locations globally. Perhaps a "Context Location" option lets the user of the template UI specify, say, the system-level org unit to gather locations for. This would gather locations from ancestor and descendent org units, of course. This would be a new feature, however.

Can you confirm that you are getting the appropriate set of locations in the editor proper, given a set of copies from different branches?

Thanks!