Project

General

Profile

Actions
Copy link

Feature #14258

closed

[Data operation] Collection filtering

Added by Chrystian Klingenberg about 6 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Michał Kłobukowski
Category:
-
Target version:
sprint 13 (lucky number)
Story points:
3.0
Release:
Arvados v1.4 - Q1/Q2 2019
Release relationship:
Auto

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

Download all files
collection filters.PNG (6.23 KB) collection filters.PNG Chrystian Klingenberg, 09/27/2018 10:45 AM
collection type - API.PNG (38.7 KB) collection type - API.PNG Chrystian Klingenberg, 11/14/2018 10:53 AM
collection properties edit panel.PNG (5.99 KB) collection properties edit panel.PNG Michał Kłobukowski, 11/16/2018 12:43 PM
Actions
Copy link
 #1

Updated by Chrystian Klingenberg about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Chrystian Klingenberg about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Chrystian Klingenberg about 6 years ago

Actions
Copy link
 #4

Updated by Chrystian Klingenberg about 6 years ago

  • Target version set to sprint 13 (lucky number)
Actions
Copy link
 #5

Updated by Chrystian Klingenberg about 6 years ago

  • Story points set to 3.0
Actions
Copy link
 #6

Updated by Chrystian Klingenberg about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #8

Updated by Chrystian Klingenberg about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #9

Updated by Michał Kłobukowski about 6 years ago

  • Status changed from New to In Progress
  • Assigned To changed from Chrystian Klingenberg to Michał Kłobukowski
Actions
Copy link
 #10

Updated by Michał Kłobukowski about 6 years ago

  • Status changed from In Progress to New
  • Assigned To deleted (Michał Kłobukowski)
Actions
Copy link
 #11

Updated by Michał Kłobukowski about 6 years ago

Should we block edition of properties that hold collection's type and origin metadata?

Actions
Copy link
 #12

Updated by Michał Kłobukowski about 6 years ago

  • Status changed from New to In Progress
  • Assigned To set to Michał Kłobukowski
Actions
Copy link
 #13

Updated by Moritz Gilsdorf about 6 years ago

  • 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.

Actions
Copy link
 #14

Updated by Michał Kłobukowski about 6 years ago

  • Status changed from New to In Progress
  • Assigned To set to Michał Kłobukowski
Actions
Copy link
 #15

Updated by Michał Kłobukowski about 6 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #16

Updated by Peter Amstutz 8 months ago

  • Release set to 15
Actions
Copy link

Also available in: Atom PDF