In the init_relationships method, the migration can create tiles that violate cardinality rules for cardinality 1 cards such as part_of_scheme and classification_status. The migration should be adjusted to only insert one tile per resource for each of these cards.
Upon reflection, these nodegroups should accept multiple values: relation_status, match_status, classification_status, part_of_scheme, and top_concept_of
"A concept can participate in multiple schemes" - part_of_scheme
"A concept can participate in multiple schemes, and be the top concept of those schemes" - top_concept_of
"A concept can have multiple parent concepts" - classification_status
"A concept can be related to multiple other concepts" - relation_status
"A concept can be related to multiple other concepts" - match_status
In theinit_relationshipsmethod, the migration can create tiles that violate cardinality rules for cardinality 1 cards such aspart_of_schemeandclassification_status. The migration should be adjusted to only insert one tile per resource for each of these cards.Upon reflection, these nodegroups should accept multiple values: relation_status, match_status, classification_status, part_of_scheme, and top_concept_of
"A concept can participate in multiple schemes" - part_of_scheme "A concept can participate in multiple schemes, and be the top concept of those schemes" - top_concept_of "A concept can have multiple parent concepts" - classification_status "A concept can be related to multiple other concepts" - relation_status "A concept can be related to multiple other concepts" - match_status