Property:HasEntityBlurb

From dataspects::Wiki
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
  • 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 "Search result views have a unique reference URL" HasEntityBlurb
  • 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" HasEntityBlurb
  • 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.
BusinessService "Run your organizational Find-And-Learn network!" HasEntityBlurb
  • Knowledge management consists of optimizing the access to and the management of knowledge for the sake of decision and performance support.
Concept "Asymmetric Anaylsis" HasEntityBlurb
  • Analysis applied at index time is different from the analysis applied at query time.
Concept "CoKe" HasEntityBlurb
  • 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 "Inheriting annotations if not customized by Indexer" HasEntityBlurb
  • Understand how to customize ES doc compilation
Concept "IsRootPredicate" HasEntityBlurb
  • dataspects canonical ES index mapping contains domain-agnostic root fields (predicates) and nested annotations that accommodate domain-specific predicates.
Concept "Keyword datatype" HasEntityBlurb
  • 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 "Parent-Child Relationship" HasEntityBlurb
  • The join data type is a special field that creates parent/child relation within documents of the same index.
Concept "Simple Analyzer" HasEntityBlurb
  • breaks text into terms at non-letter characters
  • all terms lower cased
Concept "Standard Analyzer" HasEntityBlurb
  • Grammar based tokenization based on the Unicode Text Segmentation algorithm
Concept "Text datatype" HasEntityBlurb
  • Index content analyzing it.
Concept "full_text/query_string" HasEntityBlurb
  • The query_string query parses the input and splits text around operators. Each textual part is analyzed independently of each other.
Configuration "Wikitext Search" HasEntityBlurb
  • Wikitext search allows for finding raw wikitext snippets.
Dashboard "Enterprise Knowledge Management Aspects (Concerns, Responsibilities, Roles, Use Cases and Tools/Methodologies)" HasEntityBlurb
  • This article explains all aspects (roles, responsibilities, use cases and tools/methodologies) that keep your enterprise knowledge management healthy, effective and efficient.
Feature "Code Graph" HasEntityBlurb
  • Get a graph from a facet of your code base showing function calls.
Feature "EnrichKGByExternalSources" HasEntityBlurb
  • EnrichKGByExternalSourcesTest()
Feature "Explain a domain (facet)" HasEntityBlurb
  • Explain a (sub)domain as a facet of connected entities. Display the explanation as a graph and a bulleted story.
Feature "Link to dataspects facets" HasEntityBlurb
  • 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 SearchFacet pages and then either GET or POST.
Feature "Mail to Knowledge Base" HasEntityBlurb
  • The MailToKnowledgeBase functionality enables sending content to the API via email for automatic semantic integration.
Feature "Nested Facet Maps" HasEntityBlurb
  • Contextualize entities along multiple dimensions simultaneously
Feature "SIGINT explanations" HasEntityBlurb
  • Covered by ds100 predicates
Feature "Search engine mode (SEM)-specific search results design, behavior and interaction" HasEntityBlurb
  • Search must optimize itself depending on the search context (represented by a SEM) that the user has in mind.
Issue "Alert a slow network connection" HasEntityBlurb
  • Mitigate user concerns over system quality if they are on a slow internet connection.
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
  • Sometimes when paginating the result list doesn't change based on the new "from".
Issue "Make V1 responsive" HasEntityBlurb
  • Make V1 simple search useable on any device
Issue "Reindexing methods" HasEntityBlurb
  • Reindex from ES (new index template), from Neo4j (cheap Re-SIGINT), from ResourceSilo (expensive Re-SIGINT)
Onepager "Easy diagram management in the wiki" HasEntityBlurb
  • Diagrams can easily (and visually appealing) be created via draw.io. The diagrams are stored on a server and are seamlessly integrated onto wiki pages and into search results. From search results, the diagrams can be viewed and edited (link to editing page). Like this, the external diagram service is best integrated into the wiki.
Onepager "Onepager per role" HasEntityBlurb
  • Onepager per user role in the company and/or ontology – benefits for this user role, responsibilites, working fields in the wiki, chances etc.
Ontology "EnterpriseKnowledgeManagementOntology" HasEntityBlurb
  • The pervasion of knowledge in an organization
Ontology "dataspectsSupportOntology" HasEntityBlurb
  • Manages problem hierarchies and their solutions.
Ontology "dataspectsSystemCoreOntology" HasEntityBlurb
  • How to store and structure knowledge on a SMW — here's the framework
Ontology "issueManagementOntology" HasEntityBlurb
  • Manage issues akin to GitHub
Principle "Efficient (Re-)Naming Support (ENS)" HasEntityBlurb
  • Optimal naming of knowledge assets evolves and a system must enable adapting names without breaking things.
Recipe "Create a saved search in Kibana" HasEntityBlurb
  • Saved searches are a type of saved objects in Kibana.
Role "Ontology Designer" HasEntityBlurb
  1. Facet management
  2. Type management
  3. Property management
Role "User" HasEntityBlurb
  1. Reader
  2. Contributor/Editor
  3. Poweruser
  4. Gardener
Setup "dataspectsSystem on DigitalOcean" HasEntityBlurb
  • This setup explains how dataspectsSystem is set up on dataspects' own DigitalOcean infrastructure.
Solution "Delete Docker authentication token" HasEntityBlurb
  • 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" HasEntityBlurb
  • 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 "AAAA" HasEntityBlurb
  • Anybody can say Anything about Anything Anywhere
Start "Introduction to FindAndLearn" HasEntityBlurb
  • When people convey/consume knowledge they express/grasp it by things/actions which are described/related by properties.
Start "Introduction to FindAndLearn's (FAL) usage of Semantic MediaWiki (SMW)" HasEntityBlurb
  • For FAL SMW fulfills the following requirements:
  • manage information for which there is no (need for a) specialized system
  • manage domain-wide meta information
  • allow for rapidly prototyping preliminary or short-lived subdomain management applications
Story "dataspects Usability Metrics" HasEntityBlurb
SystemComponent "Resource Facets" HasEntityBlurb
  • Resource facets are written in dataspectsScript and specify the set of resources that should be extracted as JSON from a specific ResourceSilo.
SystemComponent "Semantic MediaWiki" HasEntityBlurb
  • wiki.dataspectsSystem is the platform that glues together knowledge scattered across systems into useful recipes and explanations organized by the principles of https://everypageispageone.com/the-book.
Showing 20 pages using this property.
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
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.  +