Introduction
The Business Schema manager is vital in ensuring that business views are optimized for Nexus consumption. Let's discuss best practices for designing Nexus-friendly business views.
What you need to know before reading this article
Let's Go
Step 1: Define the scope
Begin by understanding users' typical questions to create business views that directly address their requirements. Focus on one domain, refine it, and expand to other areas.
Step 2: Design effective business views
With the scope in mind, start designing business views or adjusting existing ones to fit the required domain.
- Column Names
- Example: Use "Shipment_Date" instead of "Date" to specify the context.
- Example: Create a column for "Total_Cost" that multiplies "Unit_Cost" by "Quantity" for quick insights.
- Limit the number of Columns: Keep the number of columns under 50 to enhance data clarity.
- Example: Instead of including every product detail, focus on critical metrics like inventory levels and reorder points.
- Use Descriptive Column Names: Ensure column names are meaningful and unique to avoid confusion.
- Include Pre-Calculated Values: Add complex calculations as separate columns for easier access.
- Column Descriptions
Add context and explain unfamiliar terms to improve data understanding.
- Provide Context: Provide descriptions for columns when additional context is needed.
- Example: To clarify its meaning, describe "Lead_Time" as the average days between order and delivery.
- Explain Jargon: Provide explanations for industry-specific jargon.
- Example: Define "Safety_Stock" as the buffer inventory to prevent stockouts.
- Column Data
For data security, Incorta Nexus does not have access to your actual data. Thus, it might misinterpret data, such as filtering for "Warehouse A" when "WH_A" is used.
If the set is small, list valid strings in the column description to prevent misinterpretation. For example, a gender column should specify that it uses the "M/F" format. Thus, when the user's question is about "female," it will search for the letter "F."
- Column Datatype
- The Business Views column data type can't be null, which could be the case when it can't resolve the data type from the source due to an undefined physical schema or unresolved formula.
- SQLx Views designed for Nexus can't use presentation variables. Business views with presentation variables are mainly intended for Incorta dashboards.
Step 3: Test with users
Test with small business users and refine the business view based on feedback. Update the business views to reflect new terminology or any other required columns. Once you are confident the scope is good enough to address the most common questions accurately, start expanding to a broader audience.
Step 5: Educate Users
Guide users for an effective use of Nexus:
- Set Expectations: Communicate the scope and types of questions it can handle.
- Simplify Queries: Encourage users to ask clear, straightforward questions.
- Rephrase: Suggest rephrasing or simplifying questions if Nexu struggles to answer.
- Feedback Loop: Foster continuous improvement by collecting and acting on user feedback.
.png "Employee"){kind=icon}
