metadatacenter / cedar-project

Build project for all CEDAR Java repositories
https://github.com/metadatacenter/cedar-docs/wiki
Other
12 stars 1 forks source link

Mechanism for capturing 'field type' #526

Open martinjoconnor opened 7 years ago

martinjoconnor commented 7 years ago

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?

graybeal commented 7 years ago

I'm convinced we'll need something like this to achieve search interoperability across templates.

martinjoconnor commented 7 years ago

Also see ideas in https://github.com/metadatacenter/cedar-template-editor/issues/501

graybeal commented 7 years ago

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.)

martinjoconnor commented 7 years ago

See also https://github.com/metadatacenter/cedar-project/issues/545

graybeal commented 5 years ago

Interested parties:

graybeal commented 1 year ago

Saw today that LinkML has this very feature, to specify the subject (not property) that described the field.

martinjoconnor commented 1 year ago

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.)