You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a user updates a single resource, all existing resources are validated (this is a core CKAN functionality). If any resource is invalid, then it's impossible to update another.
Many resources (especially geographic datasets) are not validating because mandatory fields are not set to any value. We need to set these mandatory fields properly to allow for proper validation.
To fix this we will need to:
set reasonable default values; and
update the migration script to support this
NB - If we extend the new schema to add additional mandatory fields, we will have to use this workflow again to ensure proper validation (and thus proper updating).
@jachurchill to also create a script that will allow us to extend the new schema with additional mandatory fields.
The text was updated successfully, but these errors were encountered:
Currently, when a user updates a single resource, all existing resources are validated (this is a core CKAN functionality). If any resource is invalid, then it's impossible to update another.
Many resources (especially geographic datasets) are not validating because mandatory fields are not set to any value. We need to set these mandatory fields properly to allow for proper validation.
To fix this we will need to:
NB - If we extend the new schema to add additional mandatory fields, we will have to use this workflow again to ensure proper validation (and thus proper updating).
@jachurchill to also create a script that will allow us to extend the new schema with additional mandatory fields.
The text was updated successfully, but these errors were encountered: