`SortBy` parameter is not retained in the configuration definition for catalog pluing in context about mapstore2 HOT 4 CLOSED

@ale-cristofori
MetadataExplorer plugin doesn't allow configuring services directly via the plugin config. Instead default services are added to initialState of localConfig. The same service is visualized in both the catalog of Map viewer and Step2 of context creator (i.e Catalog of Map), if I'm not wrong

Evidently from the video above, you have different services in json but you were able to visualize only the default list of catalog service configured in localconfig.

If you like the context to have different "default" services configured, you may need to do so from the Catalog panel of Step2 in context-creator. When saved the services are saved along with other map configurations. And eventually the same services are copied over to map created from the context

SortByContext in this context I have modified the sort order on csw service and saved the context. So the same is visualized when you load the context and #/context/SortByContext/50078 in this map created from context, the modified sort order on csw service which is reflected correctly.

from mapstore2.

As confirmed the issue can be closed

from mapstore2.

Thank you @dsuren1. @ale-cristofori let me know if we can close the issue then.

from mapstore2.

@tdipisa @dsuren1, I can see the rationale of it and for the purpose of setting the value it makes sense.

Though I test the following

If you like the context to have different "default" services configured, you may need to do so from the Catalog panel of Step2 in context-creator. When saved the services are saved along with other map configurations. And eventually the same services are copied over to map created from the context

And I get errors

@tdipisa @dsuren1 is it something that needs to be looked into? If so let me know, it seems a bad response from gs-stable.

from mapstore2.