I think SeaDrive should be changed so that shared libraries are structured within a better folder hierarchy, rather than placed in a flat list below the “Shared with ___/” folders.
I’m evaluating Seafile for use within a company setting and we’re running into some odd/frustrating issues that seem easily solvable via some smart design changes.
For example, if 2 groups (or Departments) have libraries of the same name, SeaDrive places both libraries in the same Shared with groups folder, causing a naming conflict. It’s ugly and there’s no way to tell which share belongs to which group or department:
- Department A / Documents:
SeaDrive/Shared with groups/Documents - Department B / Documents:
SeaDrive/Shared with groups/Documents (1)
It would be signficantly better if they were stored in a hierarchy like so:
- Department A / Documents:
SeaDrive/Shared with groups/Department A/Documents - Department B / Documents:
SeaDrive/Shared with groups/Department B/Documents
This reminds me of another related issue which is that the web UI shows the sub-departments as a top-level department to users:
The ‘Financial’ department is a sub-department of ‘Sound Yarn and Fibre’, so I would expect to see it structured as such in the UI.
Edit to add: The issue gets even deeper in the web UI when you try to move files between libraries and can’t tell which library to move things to, because you can’t see which group or department the library is in…
Seafile & SeaDrive as so close to a perfect solution, and yet so far in such odd ways. I really hope this suggestion is recognized as worthwhile 