Have recently gotten a request from my internal team on our asset files in Squidex. Today all asset files are stored on the file system. Each app has a separate folder by GUID, and each asset in that app is in that folder under its own GUID. As well, resized assets get created and stored here.
The complaint I am hearing is that they feel there are too many files in one directory, and it is difficult to know what each file is since its just a GUID. Note, this is an individual who doesn’t want to use the Squidex interface directly.
Looking to see if there is any possibility to…
-
Limit the number of assets being all in one directly. While the file system does support many more assets than we currently have, the larger number of assets stored in a single folder does impact overall performance in visually viewing the folder. We are launching a new piece soon that will have 80k+ assets that will also be responsively sized, so we expect the total assets to increase quite a bit.
-
They would prefer the ability to have some naming structure on the files.
In terms of #1, it would be nice if the folder structure under an app could mimic the folder structure of assets in Squidex. That would give some control to the app creator to limit the size of # of assets in each network directory as well as keep similar organization as the app itself.
In terms of #2, general file name that was uploaded would work best, but since Squidex focuses on GUID, it already allows same file name more than once, and so this may not be possible. Another option might be something like General file name + Guid to keep each file unique, but this could run into issues for files already at max length with the name uploaded.
Anyways, I let the person in-house know I would look into both requests for them, so passing this feature request along to see if possible.