Custom File Handling - rsync files

[djbrooke]

Certain buttons or other options may be disabled for files added to dataverse using rsync.

[pdurbin]

During the 2016-09-08 SBGrid Sprint Planning meeting ( https://docs.google.com/document/d/1wWSdKUOGA1L7UqFsgF3aOs8_9uyjnVpsPAxk7FObOOI/edit ) this issue was given an effort level of "5" but I feel like this issue is highly intertwined with #3350 with regard to "download all as zip".

This issue raises several concerns I expressed at the 2016-09-07 demo because those buttons we're talking about hiding do very important things in the system such as versioning of files and restricting files. I called this "Tradeoffs" during the talk: https://docs.google.com/presentation/d/1cOOLylj5mMNllE8--Gg65lG6HS1Ih4oGypnWLeh0h4k/edit?usp=sharing

The thing to keep in mind is that for the migration story from https://data.sbgrid.org that @bmckinney and @pameyer are working on, they're fine with hiding these buttons because their customers:

• Don't need versioning of files since the files come off an instrument and don't change.
• Don't need to restrict data since the data is CC0 licensed.
• Don't need to download all as zip because they'll use rsync instead.

The other day @mheppler said, "We're trying not to have a 100% custom experience for your users." I agree with this too, at least in the long run. In the short run, however, do we make these tradeoffs? Do we say that if you use the rsync feature, you can't version files or restrict files? Do we disable the buttons? What's in scope for this issue? I'm afraid I have more questions than answers so I'm assigning this to @djbrooke @scolapasta @bmckinney and myself to discuss further.

[pdurbin]

@bmckinney @scolapasta @djbrooke and I discussed this issue today but decided to leave it in the backlog for now. We still need to figure out what the plan is for changing the code.

[djbrooke]

Closing. Changes will be made in #3348 or in issue spawned from there.

[pdurbin]

All the non-restricting of files is part of #3776 as well.