Advanced sharing

[jennydaman]

Background

Currently, feeds can be shared from user to user.

A feature we are working on a feature where feeds can be marked "global" meaning all users, including when user is not logged in, can see it (read-only).

What are some other ideas of how we can improve collaboration, reproducibility, and open science using ChRIS?

[jennydaman]

Copying feeds can be done using pipelines

[jennydaman]

Feed Shallow Copies

Let's say a feed has been shared with you read-only. You want to add a plugin instance to it, but you cannot because you do not own the feed.

There should be a feature in ChRIS where feeds shared with you can be copied to a new feed which you own with read-write permissions.

Deep Copy

A feed (deep) copy would be very inefficient because all of its plugin instances would need to rerun. This can be optimized on various levels

Copy metadata, not data

Plugin instance copies can use the same files as the source, but its metadata (id, owner, title) are different. When a copied plugin instance is deleted, its files are not deleted. When a plugin instance which owns its files are deleted, then its files are deleted.

Stretch feature: copied plugin instances know who their source is.

Plugin instances belonging to multiple feeds

As title says. Currently, plugin instances belong to 1 feed. In the proposed change, plugin instances belong to [1, n) feeds. When a plugin instance is deleted, it is merely hidden from that feed, rather being truly deleted, unless the number of feeds which have it drops to 0 (like a UNIX filesystem hard link created by the ln command)

Inspirations

In Github's model, you could create a fork of the repository and work on your own fork. Datalad is built on Git so this data management workflow is possible with Datalad as well.

Copy-on-write e.g. BtrFS