The panoramax CLI allows to move pictures from one instance to another but when doing so, a new UUID is generated on the receiving instance. Panoramax picture UUIDs are a great way to link other databases to Panoramax, but we should keep them stable in such a case to avoid the link to be broken. This could be adressed in conjonction with issue #302 where UUIDs could be optionnaly generated on the sending client instead of the receiving API. One additional thing to think about is how to handle this at the metacatalog level when harvesting instance in the process of moving pictures between them.