Saving project as local .mdzip will trigger MD migration. The tag values will be replaced with local element ids (except for document).
Adding it to server, will triger replacement again. Tags will get server element ids.
So the challenge will be documentId and siblingId
So, to recap:
In containment tree, under the model, you should have package which has the same name as collaborator document.
It should have <<CollaboratorDocument>> stereotype applied.
Open specification window of that element -> Tags
<<CollaboratorDocument>> -> id
Value should be changed to document.id#document.branch.id – this is how document knows where to store its elements (comments/paragraphs)
<<CollaboratorDocument>> will have elements package – inside will be comment elements with <<CollaboratorParagraph>> stereotype
Open specification those comments -> Tags
<<CollaboratorParagraph>> ->
documentId = should be changed with the new one
siblingId – this id says the order of paragraph in section. It will require manual adjustment.