Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataset metadata validation – problem with linking to both WFS and Atom #1136

Open
VeronikaKusova opened this issue Nov 12, 2024 · 1 comment
Assignees
Labels
user-to-fix Problem is present on user side

Comments

@VeronikaKusova
Copy link

Hi,
I am validating dataset metadata. We provide WFS and Atom services (both) for most of our datasets. When I validate the metadata of the data, which contains WFS and Atom service in the distributionInfo, the test is passed with manual check for CC 8: INSPIRE data sets and data set series linked service metadata (see the picture below and the attached report). The descriptive message in the test does not make sense neither: “Please review that the Resource locator URL points to the response of the Get View Service Metadata request of the related Network Service.” Because it mentions view service in the part dedicated to download service linking.
Test report: Test_report_WFS_Atom_both.zip

image
image

But when there is only WFS or Atom mentioned in the metadata distributionInfo (just one of them), the CC 8 is passed without the need for manual control (see the picture below).
Test report: Test_report_WFS_only.zip

image

Metadata file: CZ-CUZK-TN_AIR_test.zip

Best regards.
Veronika

@fabiovinci
Copy link
Collaborator

Dear @VeronikaKusova,

regarding the error message, there is a typo, since it should refer to the Download Service. We will fix it.

It seems that the validator is not able to proper detect the declaration od the Download service because you used only one "<gmd:transferOptions>/<gmd:MD_DigitalTransferOptions>" for all services.

According to the related requirement (TG Requirement 1.8) you should use separate elements.

Please have a look at the metadata example for the right encoding.

Could you please encode all the resource locators properly and validate the metadata again?

@fabiovinci fabiovinci added the user-to-fix Problem is present on user side label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user-to-fix Problem is present on user side
Projects
None yet
Development

No branches or pull requests

2 participants