Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As described above, manual aliasing configuration applies at the level of the community and is applied configured using JSON shares.  In this way, it is possible to build entire alias sets of master entities and associated aliases, which will apply to all queries against the source data within in the impacted communities.  

Aliasing can be manually disabled by setting the top-level query field "expandAlias" to false 

It is important to differentiate this type of "manual aliasing" with "automatic aliasing" which can be used setup simply be sending the entity query term with the "entityOpt.expandAlias" parameter.  This will allow matching not just on the entity but also on common, automatically extracted, "aliases". 

...

Code Block
 {
	"brooklyn, ny/location": {
		disambiguated_name: "Brooklyn, NY",
		type: "Location",
		dimension: "Where",
		index: "brooklyn, ny/location",
		alias: ["brooklyn/keyword"]
	},
	"DISCARD": {
		disambiguated_name: "DISCARD",
		index: "DISCARD",
		type: "SPECIAL",
		alias: [
			"sandy/keyword",
			"rt/keyword",
			"amp/keyword"
		]
	},
	"new york city, ny/location": {
		disambiguated_name: "New York City, NY",
		type: "Location",
		dimension: "Where",
		index: "new york city, ny/location",
		alias: [
			"nyc/keyword",
			"downtown nyc/keyword",
			"new york city/keyword",
			"new york city/location"
		]
	}
}

Alias

...

Management

When a query is performed, all JSON share objects belonging to the queried communities, and with type "infinite-entity-alias", are read from the database (or from cache if unchanged).

...

Files uploaded via the API can then be shared with other communities using the Share - Add - Community or Share - Remove - Community calls or again from the file uploader.Aliasing can be manually disabled by setting the top-level query field "expandAlias" to false (not to be mistaken for the false-by-default "expandAlias" fields that are present in the query terms, and which apply to the "automatic aliases" generated from entity extraction, ie the "actual names" corresponding to the entity's disambiguated names - this nomenclature will be tidied up in a forthcoming version of the platform).

Aliasing is a complicated topic, and the following additional functional items are planned on the roadmap:

...