Best Practices and Common Pitfalls

Naming conventions

[Note: This section needs to be completed with specific naming conventions]

When to Edit your Model

You can fine-tune the taxonomy's internal structure to optimize the system's accuracy and align it with specific business needs.

• If the model is incomplete, such that core entities are missing - Adding
• If the fundamental base sql is not wide enough, and core properties from the underlying tables are missing, you can expand the scope of the entity - Add-Edit
• If the SQL are not accurate enough - and does not capture your internal business logic - Editing
• One can also sharpen the textual definitions when needed - Editing

Best Practices

1. Base Query Manipulation
2. Keep base queries as simple as possible
3. Attribute Design
4. Define commonly used attributes
5. Give clear, business-friendly descriptions
6. Use consistent naming conventions
7. Dimension Planning
8. Create dimensions that align with common analysis patterns
9. Consider performance implications of different grouping levels
10. Document any special handling requirements
11. Relation Management
12. Define commonly used relations
13. Make sure to perform the join operation between 2 base queries (of the source and the target entities of the relation)
14. Document cardinality (one-to-one, one-to-many, etc.)
15. Consider join performance
16. Handle null values appropriately