Sufia's product owner has blessed the following assumption already and has been talking about it (howsoever vaguely) for a while now: 

• Sufia is on a path away from its identity as only a self-deposit IR toward a more configurable application that can accommodate other use cases such as mediated-deposit IR with others to be identified.

Note: this is just a stub! None of the things on this list have undergone a vote or anything!

1. We will simplify user interaction at each step. Sometimes this will mean there are more steps.
2. We will guide users through each workflow.
3. We will find consensus among a number of different Sufia implementations, such that more code can live in Sufia proper and less UI/workflow customization – which is difficult to maintain and privatizes benefit -- needs to be done at the application level.
4. We will support the simplest case of a single user uploading a single file.
5. We will support the most complex case of a 'power user' batch uploading 100s of files, which may or may not belong to a single work.
6. We will maintain the existing Sufia 6.x workflow and functionality on which current production Sufia applications are dependent.

Existing Sufia 6.x functionality

Batch Upload

• support uploads via...
  
  • upload files from My Computer (select files through a dialog or drag-n-drop, also supports upload from folder in some browsers)
  • upload files from Cloud Providers
  • upload files from Network/Server Location
• best if modifications are compatible with current upload mechanism...  https://blueimp.github.io/jQuery-File-Upload/
• upload to collections
• agree to terms and services agreement
• specify permissions (looking like both works and filesets will have permissions - not solidified and subject to change)