Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[files-module] Better metadata and organisation of files #4760

Closed
fryiee opened this issue Mar 29, 2018 · 11 comments
Closed

[files-module] Better metadata and organisation of files #4760

fryiee opened this issue Mar 29, 2018 · 11 comments

Comments

@fryiee
Copy link
Contributor

fryiee commented Mar 29, 2018

As title. The files module should support nested folder structures.

@dwainscheeren
Copy link

I really would like to have this!

@Pixney-William
Copy link
Contributor

I really would like to have this !

@RyanThompson
Copy link
Member

There will need to be some cleverness with the filesystem cause not all adapters support this. BUT.. we could use uniqueness to have virtual nested folders..

@dwainscheeren
Copy link

Thats a good idea.

@fryiee
Copy link
Contributor Author

fryiee commented May 22, 2018

I think this is an important one to have, as it's a significant issue both in terms of infrastructure and useability on the admin UI.

@Pixney-William
Copy link
Contributor

Agreed. And so does my cat application!

@RyanThompson
Copy link
Member

This comes with a lot of consequences I don't think are worth the hefty payment for them.

FTs basically do this for us. Any nested or automatic functionality should be handled as a field type or extension.

@fryiee
Copy link
Contributor Author

fryiee commented Jan 17, 2019

@RyanThompson can you please direct me to the issue related to the underlying problem that this card is intended to solve (if there is one)? If there isn't, I think this should be kept open and modified to represent the core issue, which is files module organisation. I fail to see how FTs and or an extension solve this core issue. Whether this is solved through nested folders or through another method, I think this is a legitimate business requirement that should be discussed. One of our projects has hundreds of files across multiple folders and the files module UI is unwieldy for that.

@dwainscheeren
Copy link

What about creating all folders in root, but in the admin make them nested only for GUI?

@fryiee fryiee changed the title [files-module] Nested folders [files-module] Better metadata and organisation of files Jan 17, 2019
@fryiee
Copy link
Contributor Author

fryiee commented Jan 17, 2019

I have modified the title to better represent the intention of this issue, which is to solve the underlying organisation issue with the files module (and all files within Pyro). If you could please re-open it @RyanThompson so we could continue discussing potential options for solving this it would be greatly appreciated.

@fryiee
Copy link
Contributor Author

fryiee commented Jan 17, 2019

With that in mind, I would suggest at a minimum, the following things which would go a long way to improving useability:

  • Categories for files (additional to folder location)
  • Tagging for files
  • Filters for: MIME Type, size, categories, tags and any other data dimension that could make file delineation easier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants