You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
schema_slots.tsv have 'meaning' which hold ontology URIs.
schema_enums.tsv have 'slot_URIs' which hold ontology URIs.
However, these ontology URIs do not get displayed in template anywhere. Since ontology is primary concept for data integration, it is good to display them.
The text was updated successfully, but these errors were encountered:
Thanks for this input. So we've been a bit low-key about displaying the ontology ids, but I like the idea of say in table column help (double clicking on header) that we could add a "Semantic URI" field which has term link that resolves term to where its supposed to provide resource info on the web. Does that sound satisfactory?
The schema.yaml file for each template is provided locally now in the /templates/ folder, and it has all the ontology ids in it, so that's a way to get that info from a programatic level for each column header and picklist item that has been coded.
Some of our specifications have the ontology ids in them in the label of picklist items, as per a request from clients. Ideally though this kind of info would be one click away in the interface rather than "in your face"!
schema_slots.tsv have 'meaning' which hold ontology URIs.
schema_enums.tsv have 'slot_URIs' which hold ontology URIs.
However, these ontology URIs do not get displayed in template anywhere. Since ontology is primary concept for data integration, it is good to display them.
The text was updated successfully, but these errors were encountered: