Open martinjoconnor opened 7 years ago
I'm convinced we'll need something like this to achieve search interoperability across templates.
Also see ideas in https://github.com/metadatacenter/cedar-template-editor/issues/501
A suggestion is to manage this as metadata about the field (which is what it is, rather than about the values), so it would go into the template metadata area in the model, rather than into the core data area. (And I think would not persist into the instances; even though it has some contextual value for interpreting those answers, it can be accessed by looking up the corresponding template.)
Interested parties:
Saw today that LinkML has this very feature, to specify the subject (not property) that described the field.
Which construct? I investigated LINK-ML last year and it seemed very similar to CEDAR in they way it specifies fields. (Though has modeling constructs beyond what CEDAR offers.)
We previously had a 'field type' tab for fields but is was poorly thought out.
Can we still capture the essence of this concept.
Perhaps using SHACL in the template specification?