Feature #14258
closed
[Data operation] Collection filtering
Added by Chrystian Klingenberg about 6 years ago.
Updated about 6 years ago.
Description
As a user I would like to have possibility to filter collection
so that the view will be less cluttered with outputs, logs and created collections
Acceptance criteria:
- checkbox with log might be expanded
- expanded collection checkbox contains checkboxes: outputs, logs and general
- for object without type, we will sign them as "General"
Type is available inside Advanced tab -> API response -> type
Mockup: https://3czrf1.axshare.com/#g=1&p=1__projects&c=1
Files
- Description updated (diff)
- Description updated (diff)
- Target version set to sprint 13 (lucky number)
- Description updated (diff)
- Description updated (diff)
- Status changed from New to In Progress
- Assigned To changed from Chrystian Klingenberg to Michał Kłobukowski
- Status changed from In Progress to New
- Assigned To deleted (
Michał Kłobukowski)
Should we block edition of properties that hold collection's type and origin metadata?
- Status changed from New to In Progress
- Assigned To set to Michał Kłobukowski
- Status changed from In Progress to New
- Assigned To deleted (
Michał Kłobukowski)
Michał Kłobukowski wrote:
Should we block edition of properties that hold collection's type and origin metadata?
In theory these are properties like any other and if a user has permissions to alter properties of a collection he may want to to that also for the origin and type properties of a collection. But I would find it nevertheless useful if the workbench would not allow changing these values as they contain at the moment the provenance information which we don't want to lose (not even accidentially).
So my proposal would be that the workbench doesn't allow changing these props.
- Status changed from New to In Progress
- Assigned To set to Michał Kłobukowski
- Status changed from In Progress to Resolved
Also available in: Atom
PDF