Timur: Views should support manipulating table data

[coleshaw]

Use case is for AIP1, score model. It would be nice to be able to define the order or appearance of clinical table data, most likely by supporting:

• Selection of attribute values, within a specific attribute name (i.e. category)
• Negative selection of attribute values, within a specific attribute name

The current use case is a score model with the following attributes:

• type
• category
• category_value

We would like to configure a view such that, in a separate tab:

• Specific category values matching a regex would be listed at the top (i.e. clasi_score)
• All other related category variables would be listed below (i.e. clasi_* but !clasi_score)

[graft]

Hmm, we could perhaps achieve the same desired result by allowing column-wise sorting and filtering features?

[coleshaw]

That would be a question for @bsamad , but I think she wants to pin a specific row to the top, not exactly let users sort arbitrarily...