Versions Compared

Key

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

...

  • A synonym is a word or phrase that means exactly or nearly the same as the topic (most likely be a noun, noun phrase, proper noun, or compound noun).

  • A synonym should be the singular form of the noun (e.g. Chemical Burn vs Chemical Burns). Orbita handles lexemes (burns, burning, burned, etc.)

  • A synonym should reflect the way people express topics conversationally and will not necessarily be a synonym that exists in a dictionary for your topic (e.g. severe allergic reaction or covered in hives may be synonyms for the topic anaphylaxis). Research ways people refer to concepts conversationally by looking at web search logs, call center logs, talking with customer support, etc.

  • A synonym should consider the question someone might ask about the topic. E.g. Assume a knowledge base of First Aid content, where a topic/relationship is Anaphylaxis/Causes. Consider the question What causes severe hives? ”severe hives” would be a synonym for Anaphylaxis

  • A synonym name doesn’t necessarily need to be a word in a dictionary. It could be a business name, brand name, product name, etc.

  • A synonym name can be an acronym. When specifying an acronym, use single letters with no spaces (e.g. COPD)

  • A good synonym reflects the ways people refer to the concept conversationally.

...

  1. Click on the Questions tab

  2. Enter in questions capturing the various ways someone might ask for information covered in the article. For example, if the article includes location information for a hospital, questions might include “Where is the hospital located?” “Where’s the hospital?”, etc.

  3. Click Save button

...

Best Practices for creating Facts

It is a best practice to add less than 8 Relationships on a Fact to avoid performance issues or timeout issues.

If you have 8 or more than 8 Relationships to be added to the Fact, as a workaround, instead of adding all the Relationships to a single Fact, you could create a separate Fact, spreading out the number of Relationships across them.

E.g. instead of having one single Fact with 1 Topic + 8 Relationships, you could have two Facts, with 1 Topic + 4 Relationships each. The drawback here would be that you’d have to duplicate answer content across the facts.
This would just be a temporary workaround until the new Answers is in place.

Managing a Knowledge Base in Orbita

...

In most cases, a knowledge base will be created to capture information on a specific topic. For example, imagine a knowledge base created to contain information about sleep & wellness. Topics in this knowledge base might include general information about sleep, or specific information about insomnia treatment.

...

By defining a fallback relationship, the fallback relationship will be used in cases where an end-user asks about a topic, without expressing a relationship in the question (e.g. “insomnia”, “COVID-19”, etc)

A general best practice is to create a relationship covering general information and to use it as a fallback relationship.

See also How do I set up and use Answers?

Related Articles

Filter by label (Content by label)
showLabelsfalse
max5
showSpacefalse
cqllabel = "answers"