| Page Properties | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- In the Synapse web client, Alice navigates to her download list (either via her profile page or via the notifications in the header)
- Alice uses the available columns to sort the items in her list, and can "uncheck" items that she wants to omit from her package, or delete items from the list entirely.
- Alice then proceeds to create and download her package.
4a: We presume Alice has "download" access to all files included in the list.
4b: Alice has access to download some or none of the files and must request access. "Request Access" button in the list design should go to the Access Requirements page for that entity, similar to how the "Unmet Conditions" button works today, we think. Download package should only include files to which Alice has permission to download.
Use Case 5: Exporting the Download List for Programmatic Usage
...
- Limit of total number of files in a single download package: up to 100
- Limit of total package size: TBD
- Access Restrictions - how to handle?
- Too many files in the list - how to handle?
- Successful download - clear the list and/or retain the list elsewhere?
Priorities
P0: For initial release, it is critical that we support #1a, #2a, #2b, #3, and #4 above. It is acceptable to phase in these features as the team deems best, over a relatively short period of time.
...