For me also I never contemplated storing the actual content files in a database, but just pointers to the content files, where they come from, which other files they call and where to find relevant help info.

For consistency it would be good to protect the storage folder from direct user intervention.

The database preferably would support compatibility info on a system level. Conforming potential, of course, but also say for a texture file: uv_layouttype: 'V4' and 'body', for a geomentry file: uv_layouttype: 'LaFemme'. For poses with interface to props a pointer to the related prop, say the chair to sit on.