Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handling external resource IDs #22

Open
claudenirmf opened this issue Sep 22, 2021 · 0 comments
Open

Handling external resource IDs #22

claudenirmf opened this issue Sep 22, 2021 · 0 comments

Comments

@claudenirmf
Copy link
Collaborator

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@claudenirmf