Content Drive: Upload (EPICID-194)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Overview
Folder-level upload preferences that control whether uploads create dotAssets ("Assets") or FileAssets ("Files"). The upload button label communicates the folder's effective type — no separate indicator needed. Includes drag-and-drop, MIME-type routing for Assets mode, preference inheritance, and duplicate file handling.
Problem
Content Drive is folder-and-file oriented, but uploads currently create dotAssets by default, which breaks the mental model for customers using FileAssets (~75% of existing customers). There is no compelling product reason to force one type over the other.
Design Principle
The UI never surfaces "dotAsset" or "FileAsset." Only "Assets" and "Files."
Folder States & Upload Behavior
| Folder state | Button label | Drag-and-drop | File creation |
|---|---|---|---|
| Explicit or inherited "Assets" | Upload Assets | Direct | Routed by MIME type |
| Explicit or inherited "Files" | Upload Files | Direct | All created as FileAssets |
| No preference (default) | Upload | Triggers choice dialog | Depends on user choice |
No preference state: Drag-and-drop triggers a choice dialog. If user has edit permission, a "Remember my preference" checkbox is shown.
Preference Inheritance
Child folders inherit parent's preference unless explicitly overridden. Inherited folders behave identically to explicitly set folders.
Duplicate File Handling
Replace, Keep both (appends suffix), or Cancel — following macOS / Google Drive pattern.
Out of Scope (v1)
- Site-level or user-level upload preferences
- Predictable URL support for dotAssets
- Deprecating FileAssets
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing Content Drive upload flow and folder preference handling; this issue does not name files, tests, or a code entry point. Done means uploads support the stated Assets/Files states, inheritance, drag-and-drop behavior, MIME routing, and duplicate-file choices while respecting the listed v1 scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- content, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100