Extend data model support for region and layer + searchable terms

[ddelpiano]

As per ERD attached above, we will need to extend the current model to support region and layer as well as searcheable terms. Migration will have to be performed in order to remove synonyms from the AE table and point eventually KSs that are using these to the right entity to use.

Acceptance criteria:

• the rdfs label needs to be retrieved during the ingestion of the anatomical entities For instance,

  o;o_label;o_synonym
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;canalis cervicis uteri
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;caudal segment of uterus
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;cervical canal
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;cervical canal of uterus
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;cervix
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;cervix of uterus
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;cervix uteri
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;neck of uterus
  http://purl.obolibrary.org/obo/UBERON_0000002;uterine cervix;uterine cervix

  the first param is the URI, the second is the rdfs label, the third are the synonims.

• when visualising a population diagram or the chips in the path builder component we need to display always the rdfs label
• the anatomical entities will be filled with unique entities per URI
• all the synonyms per AE will be in the searchable terms table, linked to the right AE record
• we will need to be able to search by rdfs label or synonyms.

[stappan]

When selecting a term, the rdfs label will be the one displayed, even if the user searches/finds a synonym.

[ddelpiano]

When selecting a term, the rdfs label will be the one displayed, even if the user searches/finds a synonym.

that's correct @stappan