MK-1201: Criterion combobox shows the Boolean terms twice

[ymarcon]

Jira issue originally created by user @kazoompa:

• Go to an entity config page

• add the following to the schema:

  "obsMatching": {
  "type": "boolean",
  "title": "t(study_taxonomy.vocabulary.methods-obsMatching.title)"
  }

• Add this to the definition:

  {
  "key": "obsMatching",
  "type": "radios-inline",
  "titleMap": [
  {
    "value": true,
    "name": "Yep"
  },
  {
    "value": false,
    "name": "Nope"
  }
  ]
  }

• Create taxonomies for this field and use string type with 'false' and 'true' as possible values

Everything works including the search, the problem is in the criterion combobox where there are '0', '1' (the actual agg keys) and 'yes', 'no' which do not match the keys.

A Boolean field get mapped to LongTerms aggregation and if one can use the associated BooleanFormatter on the server-side, the client can receive the proper key names 'false', 'true' and the UI would look correct.

[ymarcon]

Comment created by @kazoompa:

After some digging we discovered that the cause of the bug is the way an aggregation is searched in a taxonomy. In Mica 1.5.x the aggregation name used to match the name of a vocabulary whereas now the name can be anything. Solution is when searching for an aggregation, match the alias_ attribute with the input aggregation and if there were no _alias attribute fall back to the old lookup, namely, match the vocabulary name.

[ymarcon]

Comment created by @meek0:

Created pull request https://github.com/obiba/mica2/pull/1377.

[ymarcon]

Issue was closed with resolution "Done"