-
Type: Epic
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 4.0.4
-
Fix Version/s: 4.1.4
-
Component/s: Remote client
-
Roadmap Milestone:DR.UC.cleanUploadUX, DR.UC.massiveUploadsCapability
-
Tags:
-
Completion Level (0 to 5):5
Upload-client : who will use it ?
DAM/video users - needs to transfer files typically 150 Gb or above to a platform to collaborate on these files
Users are ‘end’-users with desktops : clients may stop, go offline, restart… ...And they use external drives
Broader audience : transfer of big files is a pain point for most ECM : an upload client would be an occasion to show that we can scale on file transfer too.
Requirements
Heavy files capture should be faster than browser upload protocols / accelerated (typically the value proposition of Aspera, Signiant..) than classic EFSS (should saturate available bandwidth).
Bad conditions handling : high latency connections, super slow connections, or totally lost connection (think : Nuxeo Paris offices).
Restart computer or unplug external drive should not be an issue to resume right where it left off
The user flow should integrate with webUI planned asynchronous upload UX (upload batch of files -> larger than xxGB > propose to install client OR if installed, auto upload through upload-client instead of browser).
Relevant (more relevant than full sync) features includes :
Batch upload : document metadata
Keep Folders structure
Upload multiple files to a target documents