If there is no drilldown/faceting specified, then a search button click/enter with an empty query string will provide a rough domain explanation.
When explaining a knowledge domain it is helpful to extract an abstraction layer from assertions. E.g. if it is asserted that the software "dataspectsd" can be installed on server "Tesseract One", then we can derive the abstract layer that "software can be installed on servers". This provides an insight into the knowledge domain that facilitates understanding.
Bookmark* any composed knowledge facet including aspects design and discovered consecutive knowledge.
Indexing refers to managing knowledge entities in Neo4j and Elasticsearch.
Indexing comprises these steps:
A node N's nested ES doc is updated whenever:
SIGINT is specified per ResourceSilo:
and performs the following steps:
An Elasticsearch's index mapping specifies analyzers for text fields (and their multi-fields). Essentially an analyzer's constitution must satisfy a field value's content nature analysis needs with regard to relevant search, which might require analyzing content in multiple ways by the use of multi-fields.
This is easy to do for an ES doc's root-level fields. However, in order to avoid special index mappings, root-level fields shall remain domain/resourceSilo/customer-agnostic, which means that an entity's domain/resourceSilo/customer-specific annotations must go into nested fields, which is problematic as analyzers for an annotation's predicate and object values cannot be comfortably made predicate-specific.
This is why each analysis type required gets its own nested field named
/AAT[A-Z]+/ (specifying its predicate's and object's analyzers and multi-fields) and annotations are assigned in accordance with their analysis needs by specifying
ESAnalysisType when adding Entity Annotations.
Predicates connect things.
|dam||Domain-agnostic meta predicates||root-level ||e.g. OriginatedFromResourceSiloLabel, HasEntityType|
|dsm||Domain-specific meta predicates||annotations|
|rssm||ResourceSilo-specific meta predicates||annotations||Wikitext|
|rsm||Resource-specific meta predicates||annotations||Wikitext|
|csm||Customer-specific meta predicates||annotations|
Below flowchart explains a recommended way of emerging a business domain model on a Semantic MediaWiki.
MATCH (s)-[r]->(o) RETURN s.name, keys(s), type(r), keys(r), o.name LIMIT 5