I have one situation in which I am utilizing document DLS versioning feature in the application. So, there is demand of document updated before publishing a new version of the document (the reason behind is, it require verification from the third party before publish). Below is the example for more clear idea,
/test/2c5faaaf-1f5f-4679-9918-0e8117a0ad7b.xml
/test/2c5faaaf-1f5f-4679-9918-0e8117a0ad7b_xml_versions/1-2c5faaaf-1f5f-4679-9918-0e8117a0ad7b.xml
/test/2c5faaaf-1f5f-4679-9918-0e8117a0ad7b_xml_versions/2-2c5faaaf-1f5f-4679-9918-0e8117a0ad7b.xml
In this example, I want to update some nodes in /test/2c5faaaf-1f5f-4679-9918-0e8117a0ad7b.xml (which is on the most recent version) and after the verification process, would like to create a new version (ie 3) with changes made.
It works fine in MarkLogic 7 with the help of xdmp:document-insert without losing the managed document from DLS collection and not working in MarkLogic 10
I am trying to achieve this situation because it is the demand for existing designed application which communicates with MarkLogic.