[Enh] Make field paths in databases generated from odML files more intuitive

[hlmore]

When using odML files as a source of metadata, the Document, section, and properties designations are included in the path of each field in the resulting database. For example, a path could look like "Document.sections.FirstSectionName.sections.SubSection.properties.PropertyName.value" instead of the more intuitive "FirstSectionName.SubSection.PropertyName.value". Removing parts of the field paths that aren't intuitive, in particular sections and properties, would make it easier for users to generate paths themselves instead of relying on a third-party tool such as Robo3T.