We've 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 currently DSpace supports only flat schemas.
We'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. Our idea to solve this problem is to add hierarchical information to both metadatafieldregistry and metadatavalue tables. Simple Adjacency List Model would be sufficient, as metadata trees won't be very high. We've noticed you used it to store communities hierarchical information (by introducing community2community table). Attached pictures illustrate our problem and proposed solution. We also consider placing hierarchical information in separate tables (e.g. metadatafield2field and metadatavalue2value), but we're not sure how it will affect solr search. We plan to make changes in following areas: 1. dspace-api 2. dspace-rest 3. dspace solr configuration There are many details lacking in our solution description, but for now, we'd like to hear your opinion: Are we going in the right direction? (We've created issue on DSpace JIRA: https://jira.duraspace.org/browse/DS-2769) -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
