The sheer length of that path makes evident the need for an optimization in the folder structure.
I disagree, The point of a folder hierarchy is 1) to provide a logical representation of the data held within that allows someone who understands the structure to find what they are looking for without confusion and 2) to divide up the data in such a hierarchical fashion that any risks of data being misinterpreted, misrepresented or misunderstood are reduced (and in the environments I’m used to 3) convince customer and regulator QA of all of the above). Any ‘simplification’ or ‘optimization’ of the folder structure would result in files from different products or suppliers being held together, creating rather than preventing confusion. The structure in the given path starts with the data folder (everything prior is just addressing), drops down into a supplier specific folder (daz3d), a product specific folder (genesis), sub-product (base) and then the specific component within the product (morphs). If you look in morphs then you’ll start to see the complexity that the folder structure is simplifying out, with a sub-folder per supplier (15 there already in my runtime, with 1700 files), and within those a sub-folder per individual morph product (DAZ3D alone has 22 sub-folders, and almost 1300 files). When it comes to sorting through that many files for the one I want - and I have edited files at this level just this week - I for one want them as split up as the folder structure allows. Having been a configuration management engineer in a CMM level 4 organisation, I give the Studio folder design my thumbs up.
Unfortunately not all PAs do a good job of following DAZ’s example - some even seem to have trouble spelling their name the same twice running! so we get a lot of parallel entries outside of DAZ folders, but outside of data you can pretty much re-organise files to suit yourself (the sole caveats there being the geometries and textures folders under the runtime hierarchy inherited from Poser, but if you know what you’re doing and are willing to edit files you can even reformat those).
And I’d have all such elements keeps in the Applications folder, not the Documents folder.
A general principle of good software engineering design is not to mix executables and data. Things in your content are data, things in the application folder are the executables. The later versions of Windows now have issues with data in the applications folder, so good principle got turned into necessary move.
I’m personally not a fan of the My Documents folder, but I’ve had my runtime separate from my DAZ installation pretty much from the word go back in version 2 (maybe even v1), and many people have multiple runtimes, often spread over different hard-drives.
IN a way, their Smart Content system makes things more confusing.
If you organise your content folders to suit yourself you don’t actually need smart content, and it’s easy enough to turn off and set Studio to display your actual file hierarchy.