Does DH provide a way of storing attributes of a row/object but never displaying them?

[turbomam]

@pkalita-lbl an example case would be associating NMDC minted ids with entries in the Submission Portal, but not showing them

[pkalita-lbl]

No, or at least not in a particularly clean way. That use case was called out in this proposal: #359 but that hasn't really gotten much traction yet.

[ddooley]

DH should have this, but a question is whether this could be coded in the LinkML spec directly? So generically, not specific to DH user interface? This gets back to question of how we should provide a mechanism for generically (i.e. DH or any other app) hiding classes from a user interface menu choice and slots from DH interface columns (from a given schema).

What if we had a class and slot slot called "ui_behaviour" and we start with a basic "hide" value?

[ddooley]

Or maybe "ui_behaviour" is placed in a class or slot annotation that DH pays attention to?