Perhaps if under media types as well as the common types such as video file etc. You could have container types for directories. Giving a way for Linuxmce to understand what directories are.
You could have container types such as folders containing films, and folders containing parts of one film; that way if you have Part A and Part B Mce will play both subquestionally if you defined that folder as a container of parts of films rather than just a selection of films. You could also have containers defined as seasons or tv show's which might help the structuring of TV shows in combination to the media indentifier tool i suggested in another post (if linuxmce already knew the shows season it would make searching on an online database much easier). Another useful container would be for audio albums. That way you could create playlists by album etc. Currently acording to another user you have to enter the album folder and click play-all. Finally a photo container, you could define a container of photos as wedding pics. Then in the screensaver plugin you could tell it to just use the wedding pictures photo container for X orbiter and the childrens holiday photos container on another orbiter. Uploading new media into a pictures container would automatically put them into the screensaver if its container was in use for a oribter's screensaver.
Once MCE understands folders you could also then set attributes to them which pass on traits to files below them. So setting a film container as an attribute of video files will set the files below it as video files. For tv shows this could be useful to automatically pass on director traits, show names etc.
By having container support it should allow a user to have any type of hirachy they wish (and mce still being able to understand it) and for those who just use media identification to still be able to browse easily whilst provinding a backbone for some features of linuxmce to work better.
Whats peoples views on this?