The DataResource organization is meant to be hierarchical like a
filesystem to keep things simple.
If you want complex organization, use the Content and related entities.
They are kept separate to facilitate reuse of DataResource records
with multiple sets of Content records referring to t
Why the Dataresource and DataCategory do not follow the Product and
ProductCategory features such as DataCategoryRollup, DataCategoryMember ?
This would allow more flexibility in dataresource organization and the use
of DataCategory as a tagging system.
Is such an improvement in Ofbiz goal ?