Resource schema issues from migrated assets

For some migrated resources, the client side schema validation fails, preventing users to push a new version of the resource.

One example for this is the event:
`evnt_36jNJGwJYeS2eplQkZruLSLV`

Resulting issue with two fields:
```
{
"date_published": {
"message": "Invalid datetime",
"type": "invalid_string"
},
"note": [
{
"message": "Expected string, received object",
"type": "invalid_type"
}
]
}
```

Neither of the fields can be edited in the editor, should I remove these from the data model, or should we debug why they don't fulfil the validation.

These are all assets on the production server, so I can't really test this unless a change is deployed.

@joaquinvanschoren