ref PR #10524
Description
According to the new Fields UI, it could be usefull to manage edition by fields.
This could be an answer to this use case :
As data manager (e.g natural area)
I need to use a configuration from fields UI
to allow some reporters to complete the land use value but prevent them to change assigned operator
Many way exists to do that.
I propose first to manage this by customEditorOptions in order to use regeEx control on field name. Then, editors can catch the props and affect editable value (true/false).
Next, I imagine in a second time to manage this type of configuration by the new fields UI. This requires to create a new columns in Fields table but it could be less good than expected. So, another way to do that in fields is to create a "settings" button by fields to open a modal and display many options as allowEdit and future improvements (i will create new ones).
I know that geoserver will always allow edition if someone use Qgis with the correct credentials, but we have many cases where basic user profile just use mapstore and needs to be regulated.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Please, share your point of view and technical advices according to mapstore2 good practices and possibility.
Description
According to the new Fields UI, it could be usefull to manage edition by fields.
This could be an answer to this use case :
Many way exists to do that.
I propose first to manage this by customEditorOptions in order to use regeEx control on field name. Then, editors can catch the props and affect editable value (true/false).
Next, I imagine in a second time to manage this type of configuration by the new
fieldsUI. This requires to create a new columns in Fields table but it could be less good than expected. So, another way to do that infieldsis to create a "settings" button by fields to open a modal and display many options asallowEditand future improvements (i will create new ones).I know that geoserver will always allow edition if someone use Qgis with the correct credentials, but we have many cases where basic user profile just use mapstore and needs to be regulated.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Please, share your point of view and technical advices according to mapstore2 good practices and possibility.