Search Elastic - Revision history

80.229.4.125: /* Search Brand Service */

2024-04-09T16:27:24Z

Search Brand Service

← Older revision		Revision as of 16:27, 9 April 2024
Line 489:		Line 489:
	This can be used when you wish to keep a single search index for the instance but want to be able to filter based on the domain/taxonomy		This can be used when you wish to keep a single search index for the instance but want to be able to filter based on the domain/taxonomy

	The basic implementation looks for tags with a category of 'brand' alongside the page domain to add additional meta data of metaData.brand.xxx or metadata.brand.yyy		The basic implementation looks for tags with a category as defined in config, in this example 'brand' alongside the page domain to add additional meta data of metaData.brand.xxx or metadata.brand.yyy

			You can also define mappings which check the individual fields within the primaryObject and if they match expose a defined value

			In the example below we check for a boolean for Bigcorp and/or the city being London.

	Sample config		Sample config

2024-04-09T16:12:37Z

Search Brand Service

2024-04-09T15:47:40Z

← Older revision		Revision as of 15:47, 9 April 2024
Line 468:		Line 468:
	],		],
	"i": 3		"i": 3
			}

			</syntaxhighlight>


			== Multi domain sites ==

			There are a couple of services which can be used to extend/manage how content is indexed for multi domain sites

			=== Search Domain Service ===

			This service interacts with events during the indexing cycle to determine which indexes are used for queries and storage based on the SiteDomains service

			The basic implementation stores each sub-site into a separate index based on the domain code

			=== Search Brand Service ===

			This service interacts with events during the indexing cycle to expose additional meta data to the indexed documents based on domains and taxonomy

			This can be used when you wish to keep a single search index for the instance but want to be able to filter based on the domain/taxonomy

			The basic implementation looks for tags with a category of 'brand' alongside the page domain to add additional meta data of metaData.brand.xxx or metadata.brand.yyy

			Sample config

			<syntaxhighlight lang="json">
			{
			"IsEnabled": true,
			"MetaDataKey":"brand",
			"Mappings": [
			{
			"Field":"IsBigCorp",
			"Value":"true",
			"Brand":"bigcorp"
			},
			{
			"Field":"City",
			"Value":"london",
			"Brand":"UK"
			}
			]
	}		}

	</syntaxhighlight>		</syntaxhighlight>

2024-01-09T16:22:40Z

Admin

← Older revision		Revision as of 16:22, 9 January 2024
Line 134:		Line 134:

	<code>		<code>
	bin/elasticsearch-reset-password -u elastic -i		/usr/share/elasticsearch/bin/elasticsearch-reset-password -u elastic
	</code>		</code>

2024-01-09T16:22:11Z

Admin

← Older revision		Revision as of 16:22, 9 January 2024
Line 129:		Line 129:

	openssl x509 -fingerprint -sha256 -in http_ca.crt		openssl x509 -fingerprint -sha256 -in http_ca.crt
	</code>~~which~~		</code>

	To reset the user password		To reset the user password

2024-01-09T16:06:37Z

Installation

← Older revision		Revision as of 16:06, 9 January 2024
Line 10:		Line 10:

	== Installation ==		== Installation ==

			Social stack cloud can now deploy a standalone elastic node to Digital Ocean, but the manual steps for local deployment are detailed below

	The basic setup steps are		The basic setup steps are

2023-12-12T15:34:38Z

Forcing a boolean value to pass both checked and unchecked values

← Older revision		Revision as of 15:34, 12 December 2023
Line 285:		Line 285:
	</syntaxhighlight>		</syntaxhighlight>

	=== Forcing a boolean value to ~~pass~~ both checked and unchecked values ===		=== Forcing a boolean value to return both checked and unchecked values ===

	<syntaxhighlight lang="json">		<syntaxhighlight lang="json">

2023-12-12T15:34:19Z

UI Components

← Older revision		Revision as of 15:34, 12 December 2023
Line 284:		Line 284:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

			=== Forcing a boolean value to pass both checked and unchecked values ===

			<syntaxhighlight lang="json">
			{
			"name": "primaryObject.isCompleted",
			"label": "Show completed events",
			"prompt": "",
			"inputType": "checkbox",
			"isBoolean": true,
			"returnAllValues": true,
			"buckets": []
			}
			</syntaxhighlight>

			=== Forcing a simple select dropdown ===

			<syntaxhighlight lang="json">
			{
			"name": "primaryObject.country",
			"label": "Location",
			"all": "Any location",
			"prompt": "",
			"inputType": "select",
			"allowAllOptions": true,
			"buckets": []
			}
			</syntaxhighlight>


	=== Allow multiple unrelated values to be chosen ===		=== Allow multiple unrelated values to be chosen ===

2023-12-12T15:30:44Z

UI Components

2023-12-12T15:27:45Z

UI Components

← Older revision		Revision as of 15:27, 12 December 2023
Line 224:		Line 224:
	;UI/ContentSearch		;UI/ContentSearch

	This provides a good example with filtering and paging		This provides a good example with filtering and paging see the amba repo

	The component will also allow you to override the default values/titles for any aggregation using the aggregationOverrides property, this can be useful to add grouping to values such as regions/countries etc		The component will also allow you to override the default values/titles for any aggregation using the aggregationOverrides property, this can be useful to add grouping to values such as regions/countries etc