As you have probably seen, when you xog documents in/out of Clarity, they are copied into Clarity's document file store from some location, and exported out of Clarity's document file store to some other location visible to the server.
Your request however is referencing an existing part of the document store and re-importing it to the same place.. I would not recommend this.
Instead, you need to export your document attachments somewhere, arrange them with the appropriate files/folders as you wish them to exist in the application, and then issue the import specifying the location you want to bring them in.
That way if you have this structure at the documentLocation specified:
folder123
|_______expenses.xlsx
|_______deliverables.docx
folderabc
|_______folderxyz
| |_______meeting_minutes_template.docx
|_______meeting_minutes_january.docx
|_______meeting_minutes_february.docx
Then just by specifying the folder containing this structure, you would bring in those files/folders under the collaboration tab of your project without extra content needed in your XOG document import file, and they would retain that same structure:
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_document.xsd">
<Header action="write" externalSource="OS" objectType="document" version="13.3.0.286"/>
<Documents>
<Parent documentLocation="/correct/path/to/folder" parentObjectId="3456789" parentObjectType="Projects">
</Parent>
</Documents>
</NikuDataBus>
If your location is an existing part of the filestore, then you're going to import a lot of oddly named files/folders that are part of the internal storage structure used by Clarity, and could bring in files from quite a span or range of Clarity records (almost randomly) and you wouldn't want that. It should (always) be a separate and unrelated file/folder path that doesn't already belong to your Clarity installation.