Run batch SoilWise profile metadata validation of new harvested repositories

[DajanaSnopkova]

• [ ] CORDIS
• [ ] BonaRes
• [ ] INSPIRE Geoportal

Links to Prepare ETS config for SoilWise profile metadata validation

DoD:

• records are validated against SoilWise metadata profile
• tag "EUSO compliant" is displayed in the Catalogue for records that are compliant with this metadata profile
• log from the validation is available in Hale admin console

[BerkvensNick]

@pvgenuchten, @DajanaSnopkova and @thorsten-reitz , this issue is not clear, can we discuss this further in the sprint refinement meeting 15/08?

[pvgenuchten]

My suggestion is that for all metadata which is marked as inspire, we will run ets validation. For other metadata we will first harmonize the metadata to a common profile and then run a validation (based on euso profile), later we can run a similar validation after metadata augmentation.

Inspire metadata can be detected by:

• is iso19139 type and
• Has inspire theme keyword

inspire self conformity declaration can be detected by evaluating the quality report section.

Problematic records are those which self declare as conformant, but are not