GreenButtonAlliance
Entity id in self/related link of XML
While exporting data from Datacustodian, self or related link is formed using entity id in generate XML irrespective of what value is used in import XML. So link value differ in import xml and export xml.
The Data Custodian needs to insure that it maintains locally unique entity id's - we chose to use a locally unique identifier for this purpose. That means that imported entity ids (that are only going to be locally unique to the externally generating DataCustodian) are not used at the entity id of the imported resources.
On the otherhand, the UUIDs of the resources are respected (i.e. I believe we insure that if the UUID of an imported resource is found to equal the UUID of a locally maintained resource, then the local resource is used.)
Is there a particular reason/requirement that leads you to have assumed that the imported entity id's might be maintained??
Where do we stand with this? in this enhancement, where the DataCustodian export service must re-produce the externally generated URLs), we have the (negative) potential of impacting all of the code that generates the export of URLs.