The sole criteria for a dataset being recognised as an eo3 dataset is the inclusion of the eo3 schema in the definition. If the dataset is not considered eo3 due to a missing schema but is otherwise treated as eo3 due to the product metadata type, it can cause seemingly mysterious errors down the line, as seen on slack.
Proposed changes
When resolving a dataset in Doc2Dataset, alert users if there is a mismatch between is_doc_eo3 and the product metadata type
[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Fully documented, including docs/about/whats_new.rst for all changes
Reason for this pull request
The sole criteria for a dataset being recognised as an eo3 dataset is the inclusion of the eo3 schema in the definition. If the dataset is not considered eo3 due to a missing schema but is otherwise treated as eo3 due to the product metadata type, it can cause seemingly mysterious errors down the line, as seen on slack.
Proposed changes
When resolving a dataset in
Doc2Dataset, alert users if there is a mismatch betweenis_doc_eo3and the product metadata typedocs/about/whats_new.rstfor all changes