Skip to content

Problem with multiple grouping of concepts

Nicola Stoira requested to merge sphnc-541 into main

Problem is raised due to the following conditions:

  • Under sphn:Measurement/sphn:hasResult we group together target concepts into two main sets. The problem is that for one group we define a restriction on ucum:deg on the property sphn:hasQuantity/sphn:hasUnit/sphn:hasCode/sphn:iri while on the other group we do not have any restrictions.
  • When creating the database table, the name of the column will be the same sphn_hasResult__sphn_hasQuantity__sphn_hasUnit__sphn_hasCode__iri but in one case we do not have a type assigned to it while in the other we should have.
  • We cannot create two columns with the same name so we need to define an approach here.
  • I think the best is probably when checking the columns already defined, in case a type is defined, then in the case the column already exists but do not have a type defined, then we do not define any type. Similarly the other way around, if we find a column that has a type assigned, if the same column is processed again and has no type defined, then we should remove the creation of the type

Merge request reports

Loading