Add tree metadata fields to curation UI (Tree > Properties popup)

[jimallman]

As we're gathering per-tree metadata, we'll want to add (or choose) properties in Nexson to hold them. These will need to be included in the curation UI, possibly as controlled vocabularies.

[jimallman]

Related to #552.

[jar398]

Discussed on Feb 20th software call. Decision was to have field of checkboxes for inference methods and tree types ('check all that apply') together with (not as alternative to) a free form text input field for detailed and/or additional description.

[jimallman]

All this implies a few changes to Nexson structure:

• remove ot:curatedType field probably (too vague)
• add ot:inferenceMethods (allows multiple values)
• add ot:treeType (just one value? or multiple?)
• add ot:treeDescription (or maybe just description?)

How should we migrate existing studies in phylesystem? We might sweep all the studies in phylesystem and...

• create any missing fields
• move existing ot:curatedType value based on value
  • if it matches one of our preferred inference-method options, move it to ot:inferenceMethods
  • if it matches one of our preferred tree-type options, move it to ot:treeType
  • any other text moves to ot:treeDescription
  • watch for near misses (e.g. "genes tree") and alert when they're found, for a closer look?

Of course, we'll also need to sweep the codebase for any references to ot:curatedType and change it to handle the new schema. Thoughts?

[jimallman]

See related discussion in #552.