Damion Dooley
Damion Dooley
Or maybe "ui_behaviour" is placed in a class or slot annotation that DH pays attention to?
First, possibly we could use LinkML's facility for default values for fields. One issue is whether people are allowed to keep a field empty, which would clash with adding a...
I'm sure that could be arranged. I recall HandsonTable allows for this; our frozen first column is done through it, but we had to add some css as I recall....
Just a note that Handsontable has an easily configurable parameter for freezing n columns to left. It could be a user configurable option per tab.
Source shouldn't be a problem any more. However, I will make an effort to document any "magic" field names now, and we can consider adding a prefix to make collisions...
I think this could be enforced by a two fold validation: 1: validating that the "project" slot was a curie or URI, and syntactically met that; and then by insisting...
Possibly we implement only for newly created rows while in the DataHarmonizer interface. That avoids tampering with existing empty fields.
Yes, I think any one-to-many relation could get a key title and bulleted values if say more than one item, in terms of the display? Or if just one item...
This is now done insofar as a simple markup interpreter is rendering the column header help and sidebar help content.
More info on this, or close it?