Feedbacks about mapstore2 homepage

[jusabatier]

Here I want to discuss about some functions of the new MS2 homepage that appears strange to me :

• The maps tab :

When a user is on a functionnal context with specifics enabled plugins like cadastrapp, urbanisme, ... and want to save his map it create a new entry in the tab. But when he want to use this saved map for working, as it's loaded from default context, he will lost all specific plugins.

Shouldn't the map be opened with the context from which they were created ?

• Ability to hide some public contexts from homepage

Don't know for others but here we have some functional contexts that have to be accessible publicly, but that we don't want to be visible by users in contexts list. They should only be listed in admin panel. For example : IFrame, Test, Demo, Example, and more generally all temp contexts that need to be shared.

Some opinions related with this ?

[tdipisa]

@jusabatier

• The maps tab : When a user is on a functionnal context with specifics enabled plugins like cadastrapp, urbanisme, ... and want to save his map it create a new entry in the tab. But when he want to use this saved map for working, as it's loaded from default context, he will lost all specific plugins.

Shouldn't the map be opened with the context from which they were created ?

I'm sorry but I'm not sure if I understood it properly. Anyway, as usual, when you save a map from a context you create a context map. This is considered like all the other maps so it is present in the Maps tab along with the others. You can then search for maps belonging to a context with the advanced search tool in home

As usual, nothing is changed when you open a context map: you will open the saved map with all plugins defined for the context.

From Home page you have two possibilities then:

1. Create a map from the default context (localConfig)

2. Create a map from a selected context. In this case the context is opened, you can work on this and save your context map as usual

• Ability to hide some public contexts from homepage

Don't know for others but here we have some functional contexts that have to be accessible publicly, but that we don't want to be visible by users in contexts list. They should only be listed in admin panel. For example : IFrame, Test, Demo, Example, and more generally all temp contexts that need to be shared.

Some opinions related with this ?

This is not currently possible without development. App Contexts, like all other resources in MS, follow the same authorizations rules so you can make them private, public or visible only to certain groups of users.

[jusabatier]

Ok for the first point, it appear I test it a bad way, but effectively it work well with your process.

For the second point, I think it can be a good improvement to have the hability to make a public accessible context not displayed on home page. Dont't know if other patforms have the same problem ?