Just a backlog ticket to possibly look at in future, many of the CKAN API calls have frustrating interconnectivity that doesn't seem helpful and can get in the way. One example case is where we are updating a resource via an API call and while the resource is validating when it is duplicated into the package it is failing to validate there. It would be nice in future if it were possible to make these types of updates independently and not duplicate data
Just a backlog ticket to possibly look at in future, many of the CKAN API calls have frustrating interconnectivity that doesn't seem helpful and can get in the way. One example case is where we are updating a resource via an API call and while the resource is validating when it is duplicated into the package it is failing to validate there. It would be nice in future if it were possible to make these types of updates independently and not duplicate data