@ahmdthr the PR still is marked as draft .. if this is intended, though, please ignore my comment

@ahmdthr this one would have to be aligned to the latest changes of linked resources

Thanks @ahmdthr

@giohappy the PR is now ready for review on your side

@ridoo @ahmdthr we're taking a look right now

@ahmdthr Kindly resolve the conflicts and align the code changes with the latest changes in master. Thanks!

@giohappy Sorry @ahmdthr was busy with other tasks and we need some additional days to sort out our ressources. Are we to late for lending a helping hand? @dsuren1 already did some changes and requested a review.

I've tested the PR locally. The idea is good and it's really useful, but I have a few concerns:

• every time a layer is selected in the TOC a new API request is sent to obtain the required information to enable (or not) the info button for the layer
• the information that has been retrieved is not saved, so the same request is sent again every time a layer is selected

I think this could be improved if the following is implemented:

• The response can be stored, somehow, inside the state of the component. This avoids making the same request for the same layer multiple times
• But, the real point is: are these calls really needed? We already query both the map and the datasets endpoint when the map is loaded. Much information about datasets is retrieved at that time. Isn't this enough? If more attributes are required we can add them to the response of those requests, instead of making additional calls.

@gannebamm @ahmdthr if you agree I would consider these improvements before merging it. In that case the PR should be marked as Draft for the time being.

I've tested the PR locally. The idea is good and it's really useful, but I have a few concerns:

• every time a layer is selected in the TOC a new API request is sent to obtain the required information to enable (or not) the info button for the layer
• the information that has been retrieved is not saved, so the same request is sent again every time a layer is selected

I think this could be improved if the following is implemented:

• The response can be stored, somehow, inside the state of the component. This avoids making the same request for the same layer multiple times
• But, the real point is: are these calls really needed? We already query both the map and the datasets endpoint when the map is loaded. Much information about datasets is retrieved at that time. Isn't this enough? If more attributes are required we can add them to the response of those requests, instead of making additional calls.

@gannebamm @ahmdthr if you agree I would consider these improvements before merging it. In that case the PR should be marked as Draft for the time being.

@giohappy Thank you very much for your comments. The only reason a new request was being made was because the linked resources were not included in the batch request. Now with recent changes, it is no longer necessary to sent a request to fetch linked resources. I am currently working on it and expect the final version of the PR shortly.

The info button for layers on the maps page now fetches all data including linked resources with a single call. Additionally, the linked resources are stored in state such that re-fetching is not necessary when re selecting one layer again.