Open aaclan-ebi opened 5 years ago
This would mean that analysis would have to populate it too then. -@rolando-ebi
We are postponing pending further agreement on where this validation should happen. If we generate an error because of a validation failure this might end up being reported to a user who can do nothing about it.
In the current code, it's possible to export invalid json to DS because provenance fields are being populated during exporting and validation has already happened by then.
These fields should be populated prior to submission to the ingest-api so that they can be validated
This DSS file json has extra fields in the provenance property but the project schema for this json still contains old provenance fields in the schema
https://dss.integration.data.humancellatlas.org/v1/files/922bd46e-281f-4dc4-b7b2-08f8195b8224/?replica=aws