Property:HasEntityBlurb
Jump to navigation
Jump to search
Has type
is Text
Predicate class is Property
Keywords
All facets for which this property "HasEntityBlurb" plays a constitutional role
Facet... | ...is constituted by... | ...having values |
---|
All statements for this property "HasEntityBlurb"
Subject | Predicate | Object |
---|---|---|
Argument "Flexibility of structure" | HasEntityBlurb |
|
Argument "Search result views have a unique reference URL" | HasEntityBlurb |
|
Argument "Structured and unstructured content go hand in hand" | HasEntityBlurb |
|
BusinessService "Run your organizational Find-And-Learn network!" | HasEntityBlurb |
|
Concept "Asymmetric Anaylsis" | HasEntityBlurb |
|
Concept "CoKe" | HasEntityBlurb |
|
Concept "Inheriting annotations if not customized by Indexer" | HasEntityBlurb |
|
Concept "IsRootPredicate" | HasEntityBlurb |
|
Concept "Keyword datatype" | HasEntityBlurb |
|
Concept "Parent-Child Relationship" | HasEntityBlurb |
|
Concept "Simple Analyzer" | HasEntityBlurb |
|
Concept "Standard Analyzer" | HasEntityBlurb |
|
Concept "Text datatype" | HasEntityBlurb |
|
Concept "full_text/query_string" | HasEntityBlurb |
|
Configuration "Wikitext Search" | HasEntityBlurb |
|
Dashboard "Enterprise Knowledge Management Aspects (Concerns, Responsibilities, Roles, Use Cases and Tools/Methodologies)" | HasEntityBlurb |
|
Feature "Code Graph" | HasEntityBlurb |
|
Feature "EnrichKGByExternalSources" | HasEntityBlurb |
|
Feature "Explain a domain (facet)" | HasEntityBlurb |
|
Feature "Link to dataspects facets" | HasEntityBlurb |
|
Feature "Mail to Knowledge Base" | HasEntityBlurb |
|
Feature "Nested Facet Maps" | HasEntityBlurb |
|
Feature "SIGINT explanations" | HasEntityBlurb |
|
Feature "Search engine mode (SEM)-specific search results design, behavior and interaction" | HasEntityBlurb |
|
Issue "Alert a slow network connection" | HasEntityBlurb |
|
Issue "Autocomplete multiple values" | HasEntityBlurb | |
Issue "Dynamically create XMind mind maps from search results" | HasEntityBlurb | |
Issue "Dynamically create vis.js graphs" | HasEntityBlurb | |
Issue "Faulty pagination" | HasEntityBlurb |
|
Issue "Make V1 responsive" | HasEntityBlurb |
|
Issue "Reindexing methods" | HasEntityBlurb |
|
Onepager "Easy diagram management in the wiki" | HasEntityBlurb |
|
Onepager "Onepager per role" | HasEntityBlurb |
|
Ontology "EnterpriseKnowledgeManagementOntology" | HasEntityBlurb |
|
Ontology "dataspectsSupportOntology" | HasEntityBlurb |
|
Ontology "dataspectsSystemCoreOntology" | HasEntityBlurb |
|
Ontology "issueManagementOntology" | HasEntityBlurb |
|
Principle "Efficient (Re-)Naming Support (ENS)" | HasEntityBlurb |
|
Recipe "Create a saved search in Kibana" | HasEntityBlurb |
|
Role "Ontology Designer" | HasEntityBlurb |
|
Role "User" | HasEntityBlurb |
|
Setup "dataspectsSystem on DigitalOcean" | HasEntityBlurb |
|
Solution "Delete Docker authentication token" | HasEntityBlurb |
|
Solution "Download again and check $HASH" | HasEntityBlurb |
|
Start "AAAA" | HasEntityBlurb |
|
Start "Introduction to FindAndLearn" | HasEntityBlurb |
|
Start "Introduction to FindAndLearn's (FAL) usage of Semantic MediaWiki (SMW)" | HasEntityBlurb |
|
Story "dataspects Usability Metrics" | HasEntityBlurb |
|
SystemComponent "Resource Facets" | HasEntityBlurb |
|
SystemComponent "Semantic MediaWiki" | HasEntityBlurb |
|
A
The structure (ontology, "network of relations") is powerful and flexible: While it's a good idea to start with a first structure to import and create initial content, the structure is growing with the wiki. New ideas and necessary changes can be integrated easily and updated with a few clicks. Even more, the growing structure is not just a technical, alimental skeleton, but an integral part of the content in the wiki and an additional source of newly created knowledge. +
Search results offer a wide range of details (show values, entities, facets) to specify, filter and drilldown results. Each result display/view gets a unique URL in the wiki, so that it can be referenced (i.e. the link forwarded, included in other wiki pages.) +
Content within the structured ontology in the wiki is closely held together by relations (via annotations, properties, categories). This structure is working in the background. The user has additional possibilities to relate content (via links and manually created annotations). Also content that is not prestructured whatsoever can be dropped in the wiki, linked to and integrated into the structure later on. +
B
Knowledge management consists of '''optimizing''' the '''access to''' and the '''management of knowledge''' for the sake of '''decision and performance support'''. +
C
Analysis applied at index time is different from the analysis applied at query time. +
Efficient retrieval is facilitated by prepending items in structured lists (nesting, bulleting, numbering, letter casing, coloring, linking) using cognitive keywords. This approach is understood as stating knowledge using the programming language CoKe meant to be executed on human brains. +
Understand how to customize ES doc compilation +
dataspects canonical ES index mapping contains domain-agnostic root fields (predicates) and nested annotations that accommodate domain-specific predicates. +
Index content without analyzing it such as status or zip codes typically used for filtering, sorting and aggregations. Keyword fields are only searchable by their exact value. +
The join data type is a special field that creates parent/child relation within documents of the same index. +
* breaks text into terms at non-letter characters
* all terms lower cased
+
'''Grammar based tokenization''' based on the Unicode Text Segmentation algorithm +
Index content analyzing it. +
The query_string query parses the input and splits text around operators. Each textual part is analyzed independently of each other. +
Wikitext search allows for finding raw wikitext snippets. +
D
Dashboard "Enterprise Knowledge Management Aspects (Concerns, Responsibilities, Roles, Use Cases and Tools/Methodologies)" +
This article explains all aspects (roles, responsibilities, use cases and tools/methodologies) that keep your enterprise knowledge management healthy, effective and efficient. +
F
Get a graph from a facet of your code base showing function calls. +
EnrichKGByExternalSourcesTest() +
Explain a (sub)domain as a facet of connected entities. Display the explanation as a graph and a bulleted story. +
Use GET-parametrized URLs to link to facets returned as search results, or create a parser function that would look up the facet JSON on [https://mwstakeorg.dataspects.com/wiki/SearchFacet SearchFacet] pages and then either GET or POST. +