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.
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.