Wrong view and download links in newly added metadata

[antjacques]

Dear helpdesk,

We were successfully harvested today (#252) but we noticed some issues in the newly added metadata records.

1. Wrong view options: in the LPIS 2025, we see that the view options aren't the right ones.
   First one is the WMS getcapabilities but not displayed as our others metadata records, besides the preview isn't working properly. The 3 other links are related to our OGC API (link to the collection + 2 links to the documentation) but shouldn't be appearing there.

2. Wrong download link: the download link used here is the one pointing to the ATOM feed while it should be pointing to our open data repository data.public.lu. Same behaviour is observed for other new metadata such as this one. However, for the latest the view options are correct.

Did you change something in your harvesting and publishing process? It seems that download and view information aren't fetched in the same ISO metadata node as it used to...

We also noticed another error in older metadata, still concerning LPIS, not sure if it's linked or not. For LPIS from 2020 to 2024, the view options list all those years in a single metadata and there are also some duplicates.

Do we have to adapt something on our side or is something wrong with your workflow?

Many thanks for you time !

[antjacques]

Dear helpdesk, did you get the opportunity to look into our issue?

[jrc-inspire]

Dear @antjacques ,
we made some changes in the code in order to manage some new structure of data. Could you please verify if the issue is still present?

[antjacques]

Dear @jrc-inspire,

Thanks for the update!

Here is the list of the issue I spotted in my first message and the status:

1. Wrong view options for LPIS 2025 --> not resolved
2. Wrong download link (ATOM instead of download URL) --> not resolved
3. View options has several years within (example LPIS 2024) --> not resolved
4. Duplicate view options (example LPIS 2024) --> OK

[jrc-inspire]

Dear @antjacques ,
thanks for your answer. We will analyze the problem.

[antjacques]

Dear @jrc-inspire, we investigated a bit on our side and we might have found why WMS layers for LPIS 2020, 2021, 2022, 2023 and 2024 are displayed in the same geoportal fiche. Can you harvest Luxembourg national endpoint to check whether it is solved or not?

Unfortunately, we don't think that it will fix the issue with the view and download links of LPIS 2025.

Best regards

[jrc-inspire]

Dear @antjacques ,
we harvested your national endpoint as you requested.

[antjacques]

Dear @jrc-inspire

Thanks for the harvest. Are the fiches on the INSPIRE geoportal immediately updated?

I explain: we noticed that some of our fiches shared the same resource identifier, which would lead to confusion in the display of the view service (among others). We updated the resource identifiers in our national catalog to fix the issue and we expected that a new harvest would solve it on the INSPIRE geoportal.

However, the resource identifiers haven't been updated in our LPIS fiches, it is still the same as before so the problem we are facing remains:

This particular field isn't updated through a new harvest?

[jescriu]

Dear @antjacques,
I am checking with the IT team if the new harvesting results were duly updated in the Geoportal frontend.
They will answer you as soon as this is clarified.

[jrc-inspire]

Dear @antjacques ,
the new harvesting results are correctly updated in the Geoportal frontend.

[antjacques]

Dear @jrc-inspire,

Unfortunately I don't see any change in the fiche, it still displays the same resource identifier while it is different in our national catalog, details below:

Year	INSPIRE geoportal	Luxembourg catalog
2023	900cff51-74b1-4f4b-8b8d-05a7f8ed98a9	c2845068-121e-4dcf-8ed5-2c32d5f6fbd9
2024	900cff51-74b1-4f4b-8b8d-05a7f8ed98a9	9be5ce4f-5a1a-404e-b6cc-bff2c54fea77

I also verified another dataset that has been updated on our side in the past weeks and the changes aren't displayed in the geoportal frontend either.
So I'd say that the issue still remains.

[antjacques]

Dear @jescriu @jrc-inspire

Did you get the opportunity to check this issue? Why the newest information from the harvest aren't published on Geoportal? Are we the only one impacted?

Thanks for your time! As the monitoring gets closer, we want to make sure that all the fixes and improvements that we performed on our side are correctly replicated in the European portal.

[jescriu]

Dear @antjacques - Our IT team is analysing it. We will come back to you as soon as we progress on the analysis.