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

[epic] Evolution of Metadata Schemas #35

Open
rufuspollock opened this issue Jul 16, 2020 · 0 comments
Open

[epic] Evolution of Metadata Schemas #35

rufuspollock opened this issue Jul 16, 2020 · 0 comments
Assignees
@rufuspollock
Labels
question Further information is requested

Comments

@rufuspollock
Copy link
Member

How are we going to handle the evolution of Metadata Schemas? This is, over time, new revisions contains new metadata fields that didn't exist in previous revisions. We should have some custom logic when updating the CKAN dictionary to address this situation.

How are we gonna address this in the UI level? There may be cases where the UI requires data that didn't exist in the past.

How are we gonna address this with the promote feature? If we want to set as current an older revision that doesn't contain any new metadata field this will cause issues.
@rufuspollock rufuspollock added the question Further information is requested label Jul 16, 2020
@rufuspollock rufuspollock self-assigned this Jul 16, 2020
@pdelboca pdelboca mentioned this issue Jul 16, 2020
Closed
@pdelboca pdelboca changed the title Evolution of Metadata Schemas [epic] Evolution of Metadata Schemas Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rufuspollock rufuspollock

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rufuspollock