Handling external resource IDs #22
Description
How we should go about external resources' IDs? We are pushing the of refusing client-generated IDs, but we still have to keep track of of the mapping between resources in the DestinationData API and in the Open Data Hub API for updates.
I suggest that we add to this implement fields that do not exist in the standard, like odhId, or something like that. Either way, I believe that for the time being all updates will come from Open Data Hub API to the DestinationData API, and not the other way around.