ES Mapping - Feature Page Predicate

Context :

Very basic mapping options will be possible, however, we cannot propose all combinations and hence need to leave space for manual mapping.

Designs :

https://www.figma.com/file/TKic9bHB2tuCkW4aveonak/NOS---Design?node-id=236%3A25090

> use standard studio formatting and icons, but get as close as possible to the designs 

To Do: 

Create a new feature page with a unique URL

The page should have a SAVE button in the top right as per other pages, which will save progress and remove the 'Not Configured' label, but should not have the disable option as per other features 

The feature page should include :

The name of the predicate as a title, will not change 

In the first Section 'Automapping"
It will have :

• Type -> Which should be auto-filled with the base type of the variable from the content model 
  • A drop down that will propose other types relevant to ES mapping (TBC, see exploration ticket) and can be selected, to date :
    • Text
    • Keyword 
    • Date
    • Boolean 
    • Integer 
    • geo_point

• Three mapping options 
  • Fulltext
  • ILIKE
    • These should are not cumulative, one deselects the others 
  • Boost as a separate item, which can be applied as a selector with .5 increments 

In a second Section "Manual Mapping"

• This will have a JSON screen as per other sections (like registries) which will be automatically initialized with the name of the variable and empty JSON brackets 

• If the editor is in error, it will still be able to save, a 'JSON Error' label will appear in the Elasticsearch Mapping list (TBC visual of editor error) and a warning dot in the left side menu 

• If manual mapping is used, a 'Manual' Label appears in the list next to the item 

(For info, list of possible labels 

• 'Not configured'
• 'Manual'
• 'JSON Error'

 __