design example src.xml.xmlIntroduction

I decided to use DSpace in Young Digital Planet to store assets we use in our educational materials. Neither DC nor DC Terms is suitable for our metadata. We have to use LOM and deal with its hierarchical structure as I see currently DSpace supports only flat schemas. I've noticed "Hierarchical Metadata Support" is on your road map as "Candidate Features for DSpace 7.0 - Priority 2". As it's very important use case for us, we'd like to work on this feature now.

...

1. Do I mention all areas of change?
2. Should I create separate schema for each category of LOM (general, technical, etc like dc and dcterms) or one big LOM schema?
3. In what areas I can come across difficulties?
4. Is there any other option to use LOM in DSpace without touching database structure?
5. Do we need column "qualifier" in table "metadatafieldregistry" in this approach?
6. We want to deploy DSpace on production in our company in March 2016. What version of DSpace you recommend to use? 5.x or 6?

Attachments

design example src.xml.xml - editable file for https://www.draw.io/