EntityType
|
Entities
|
AAAA-Ingestion
Add new
|
|
Argument
Add new
|
Argument "Flexibility of structure" 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.
|
|
Argument "No vendor lock-in"
|
|
Argument "Search result views have a unique reference URL" 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.)
|
|
Argument "Structured and unstructured
content go hand in hand" 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.
|
|
|
Audience
Add new
|
|
BusinessService
Add new
|
|
Concept
Add new
|
Concept "_analyze"
|
|
Concept "_source"
|
|
Concept "Asymmetric Anaylsis" Analysis applied at index time is different from the analysis applied at query time.
|
|
Concept "Capture meaning with synonyms"
|
|
Concept "CoKe" 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.
|
|
Concept "Controlled, faceted, multilateral, asynchronous, bidirectional synchronisation of multiple SMWs (CFMABS)"
|
|
Concept "Document Text Analysis"
|
|
Concept "Full text queries > match_phrase (aka proximity)"
|
|
Concept "Inheriting annotations if not customized by Indexer" Understand how to customize ES doc compilation
|
|
Concept "Integration Testing dataspect Search Gatsby"
|
|
Concept "IsRootPredicate" dataspects canonical ES index mapping contains domain-agnostic root fields (predicates) and nested annotations that accommodate domain-specific predicates.
|
|
Concept "Join: has_child and has_parent queries"
|
|
Concept "Keyword datatype" 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.
|
|
Concept "Knowledge Topics/Subjects/Bites"
|
|
Concept "Manage Domain Terms"
|
|
Concept "Modeling specificity"
|
|
Concept "Parent-Child Relationship" The join data type is a special field that creates parent/child relation within documents of the same index.
|
|
Concept "Reification"
|
|
Concept "SIGINT DSL Actions"
|
|
Concept "SIGINT"
|
|
Concept "Simple Analyzer" * breaks text into terms at non-letter characters
|
|
Concept "Standard Analyzer" Grammar based tokenization based on the Unicode Text Segmentation algorithm
|
|
Concept "Text datatype" Index content analyzing it.
|
|
Concept "Unit Testing dataspect Search Gatsby"
|
|
Concept "dataspects Knowledge Graph"
|
|
Concept "full_text/match_phrase_prefix"
|
|
Concept "full_text/query_string" The query_string query parses the input and splits text around operators. Each textual part is analyzed independently of each other.
|
|
|
Concern
Add new
|
|
Configuration
Add new
|
|
Dashboard
Add new
|
|
DataspectsSystemModule
Add new
|
|
DesignPrinciple
Add new
|
|
Diagram
Add new
|
|
Feature
Add new
|
|
IndexingSetup
Add new
|
|
Dataspects:Issue
Add new
|
|
Onepager
Add new
|
|
Ontology
Add new
|
|
Presentation
Add new
|
|
Principle
Add new
|
|
Problem
Add new
|
|
Recipe
Add new
|
|
RelevanceEngineeringCase
Add new
|
|
ResourceIndexerClass
Add new
|
|
ResourceIndexerModule
Add new
|
|
ResourceSiloType
Add new
|
|
ResourceType
Add new
|
|
Responsibility
Add new
|
|
Role
Add new
|
|
RubyGem
Add new
|
|
SearchContext
Add new
|
|
Setup
Add new
|
|
Solution
Add new
|
Solution "Delete Docker authentication token" There might be an (apparently expired) authentication token in ~/.docker/config.json file, which the daemon then tried to use to pull the image from Dockerhub. Deleting the file resolved the problem.
|
|
Solution "Download again and check $HASH" Download the Composer installation script again and double check the value of the $HASH variable with echo $HASH. Once the installer is verified, you can continue with the next step.
|
|
|
Start
Add new
|
|
Story
Add new
|
|
SystemComponent
Add new
|
|
Team
Add new
|
|
Tool
Add new
|
|
Untyped
Add new
|
|
UsabilityCondition
Add new
|
|
UseCase
Add new
|
|
UseCaseGoal
Add new
|
|