anchor.diff:  Perhaps the second, compositional, editor is logically broken into an uber tree manager and a checklist editor.
   
   ==== Search
  +
  +We need to clearly define the  difference between the search on names (the APNI search) and the search requirements on
  +trees. At the moment there is confusion because some searches in the advanced search are mix tree and name concerns.
  +
  +NOTE: Greg W. put this view forward too.
   
   ===== use cases
   
  
positive.code:  these trees may have more relaxed placement rules.
   . creation of composite (uber) trees made from multiple sub trees, such as accepted taxonomic trees from multiple shards
  
  ==== Editors
  
  Based on the above use cases, and current editor usage, it looks like we need two different editing pathways for trees.
  
negative.code: 
  You can even display the synonyms without further query.
  
  NOTE: Greg W says to make the search useful we'll need to store the type of synonym as well. This could be stored
  in a jsonb field so we retain the speed of the trigram indexed synonyms search with the ability to filter on instance type.
  
  === Profile data
  
  The Profile data will be stored as a JSON object/document field in the tree_element. This allows arbitrary extension of the
  