Okay, I will update this question by myself: it seems possible to configure SWORD to deliver communities instead of collections:
swordv2-server.expose-communities = true [local.cfg] Then, I am able to retrieve a list of service documents for their collections. This way it should be possible to build a community-collection hierarchy. It just remains unclear what will happen for repositories that make use of sub-communities and have a deeper hierarchy level e.g. bibliography-community-subcommunity-collection. Could anyone please elaborate on that? Would be amazing if I could cover all functionality with SWORD-only! Regards Stefan On 10/24/18 2:20 PM, Stefan Kombrink wrote: > Dear community, > > after the latest success in our SWORD-related DSpace Quests :D there > remains one last challenge: > > Obtaining a community/subcommunity/collection hierarchy within the > service document. > > To us this seems impossible. Actually the only thing missing is a > definable unique path for each collection of the service document since > names are often similar, e.g. "Research Data", "Publications", ... > > Currently we retrieve this hierarchy using REST but some institutions > seem reluctant enabling it. Is there a way to bootleg this data through > the service document? > > Any suggestions / ideas? > > Thanks in advance & appreciation > Stefan > -- Stefan Kombrink Universität Ulm Kommunikations- und Informationszentrum (kiz) Abteilung Informationsmedien +49-731-50-31482 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
