The pyQuARC tool reads and evaluates metadata records with a focus on the consistency and robustness of the metadata. pyQuARC flags opportunities to improve or add to contextual metadata information in order to help the user connect to relevant data products. pyQuARC also ensures that information common to both the data product and the file-level metadata are consistent and compatible. pyQuARC frees up human evaluators to make more sophisticated assessments such as whether an abstract accurately describes the data and provides the correct contextual information. The base pyQuARC package assesses descriptive metadata used to catalog Earth observation data products and files. As open source software, pyQuARC can be adapted and customized by data providers to allow for quality checks that evolve with their needs, including checking metadata not covered in base package.
Describe the bug
DIF10 allows date fields to provide ISO Dates (e.g. 2006-06-02) or ISO Date-times (e.g. 2006-06-02T01:23:59Z). Currently, only ISO Date-times are allowed.
To Reproduce
Steps to reproduce the behavior:
Run the following command: python3 main.py --format dif10 --concept_ids C1236350906-GES_DISC
See error in date fields. Example: "Error: 2006-06-02 does not adhere to the ISO 1601 standard" for Temporal_Coverage/Range_DateTime/Beginning_Date_Time.
Expected behavior
The provided input is allowed for DIF10 records, so no error is expected.
Additional context
The datetime_format_check needs to be reformatted for dif10 so that it allows either an ISO Date or ISO Date-time for all DIF10 date fields. This may mean creating a new check similar to the datetime_format_check since this is specific to the dif10 schema
Describe the bug DIF10 allows date fields to provide ISO Dates (e.g. 2006-06-02) or ISO Date-times (e.g. 2006-06-02T01:23:59Z). Currently, only ISO Date-times are allowed.
To Reproduce Steps to reproduce the behavior:
2006-06-02
does not adhere to the ISO 1601 standard" for Temporal_Coverage/Range_DateTime/Beginning_Date_Time.Expected behavior The provided input is allowed for DIF10 records, so no error is expected.
Additional context The datetime_format_check needs to be reformatted for dif10 so that it allows either an ISO Date or ISO Date-time for all DIF10 date fields. This may mean creating a new check similar to the datetime_format_check since this is specific to the dif10 schema