This dual collection membership makes me a bit nervous.  While `collection` is multivalued we currently don't have production objects that belongs to multiple collections (nor do we plan to on the horizon AFAIK).

![dual-collection](https://cloud.githubusercontent.com/assets/96776/3183977/875907d4-ec7b-11e3-9812-17f5298c1655.png)

When I created the `In collection` panel I allowed it to support multiple collections mainly just to support the data model.  I'm not sure if this is **actually** what we'll want in the long run for objects that exist in multiple collections (although maybe it's GoodEnough&trade; as is).