Closed OzBruno closed 9 years ago
This filed has to be used by the geographical search engine in the catalog.
I disagree about the “must”, for a couple reasons:
See detailed behaviour in caveat in https://github.com/pole-numerique/oasis-portal/issues/138#issuecomment-134219916
Forgotten February UI mock:
@tbroyer OK not to render the filed mandatory, especially as it is for the v1. @mdutoo OK to start first with a single value
As an alternative solution, I tried to use another framework for the select2 called react-select (https://github.com/JedWatson/react-select), but it still has some issues and the solution requires possible further tests and configurations to make it show the field - and at this point for this solution I couldn't make it work with multi-select as well.
When publishing an app or a service in the catalog, the provider must fill in a "geographical area of interest" for which the app or service is relevant. This filed can be multivalued and composed of areas of the datacore's geo model. In case of a public body publishing a service, the "geographical area of interest" should be prepopulated by its jurisdiction but remaining editable.