Story #13494

[Workbench2] View/copy/expunge previous versions of a collection

Added by Tom Clegg 7 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

See Collection version history

When viewing a collection in Workbench, a tab/button should show the history of prior changes. For each prior update, it should be possible to
  • view/star/bookmark the selected version of the collection (name, description, files, etc. as they appeared after the update)
  • preview/download the files as they appeared in the selected version (if the data blocks still exist)
  • copy the selected version into a new collection (if the data blocks still exist)
  • release the storage consumed by the data blocks (if the site is configured to allow this)

When searching collections, the user should have an option to include non-current versions in the results.

The site admin should be able to control
  • whether collection version history is retained at all
  • if so, whether the data blocks for the old version are retained
  • if so, whether users are allowed to drop the retained data blocks for old versions of a collection

Related issues

Related to Arvados - Story #14086: [keep-web] Serve previous collection versionsResolved2018-10-15

Blocked by Arvados - Feature #13561: [API] Store, and add APIs to retrieve, previous versions of collection objectsResolved2018-10-04

History

#1 Updated by Tom Clegg 7 months ago

#2 Updated by Tom Morris 7 months ago

  • Target version set to To Be Groomed

#3 Updated by Tom Morris 7 months ago

When searching collections, the user should have an option to include non-current versions in the results -- at least when searching by PDH.

Including old versions should always be an available search option (off by default). I'm not sure why it's restricted to searches by PDH.

"Data blocks" is an implementation detail. From the user's point of view, there's just data and metadata.

It feels like we may want a version number which users can easily use to reference a particular version of a collection, rather than forcing them to rely on dates or logical UUID chains.

#4 Updated by Tom Clegg 6 months ago

  • Description updated (diff)

#5 Updated by Tom Clegg 6 months ago

  • Description updated (diff)

#6 Updated by Tom Morris 6 months ago

  • Blocked by Feature #13561: [API] Store, and add APIs to retrieve, previous versions of collection objects added

#7 Updated by Tom Clegg 5 months ago

  • Description updated (diff)

#8 Updated by Lucas Di Pentima 4 months ago

Some thoughts

  • Update the collection view to show version list (using a dropdown widget?) and allowing the user to select another version of the collection
  • URL for previous versions: workbench.abcde.arvadosapi.com/collections/UUID/VERSION
  • On previous versions, the “Copy to project…” button may be replaced by “Copy as new version…”. The “Move collection…” shouldn’t appear
  • On previous versions, the “Upload” tab shouldn’t exist & file list should be read-only. The lock button isn’t necessary.
  • On previous versions, name & description can’t be edited. Should “Sharing and permissions” pane appear?

#9 Updated by Tom Clegg 4 months ago

  • Related to Story #14086: [keep-web] Serve previous collection versions added

#10 Updated by Tom Morris about 2 months ago

#11 Updated by Tom Morris about 2 months ago

  • Subject changed from [Workbench] View/copy/expunge previous versions of a collection to [Workbench2] View/copy/expunge previous versions of a collection

We'll do this in the context of Workbench2 only.

Also available in: Atom PDF