On Friday, March 23, 2018 at 9:04:39 AM UTC-4, Claudia Jürgen wrote: > > I've tried it ages ago on a 3 or 4 instance and it did not work, thus > came up with the entity solution. > >
That's useful to know. A small adjustment to the parser configuration (to enable namespace support) might be required. There was a question about external tools. I was able to get 'xmllint --xinclude' to process a host document which refers to two XIncluded documents, and it merged them as desired. mwood@mhw ~ $ cat host.xml <?xml version='1.0'?> <whole xmlns:xi='http://www.w3.org/2001/XInclude'> <xi:include href='part1.xml'/> <xi:include href='part2.xml'/> </whole> mwood@mhw ~ $ cat part1.xml <?xml version='1.0'?> <part1 thing='thing'/> mwood@mhw ~ $ cat part2.xml <?xml version='1.0'?> <part2> <stuff> <nonsense/> </stuff> </part2> mwood@mhw ~ $ xmllint --xinclude host.xml <?xml version="1.0"?> <whole xmlns:xi="http://www.w3.org/2001/XInclude";> <part1 thing="thing"/> <part2> <stuff> <nonsense/> </stuff> </part2> </whole> So, one could do the merging manually, outside of DSpace, whenever one of the documents has changed. -- 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.
