Month: February 2025

Release 57

by

Alterations 15 Files Modified Key Fixes & Enhancements Notes 1. ⚠️ DIFFERENT: employee_absencelimit.sql2. ⚠️ DIFFERENT: infrastructure_changerequest.sql3. ⚠️ DIFFERENT: infrastructure_oshrecords.sql4. ⚠️ DIFFERENT: marketing_Advertising.sql5. ⚠️ DIFFERENT: marketing_campaignTraffic.sql6. ⚠️ DIFFERENT: marketing_campaignTrafficFormSubmissions.sql7. ⚠️ DIFFERENT: marketing_EmailCampaigns.sql8. ⚠️ DIFFERENT: marketing_Events.sql9. ⚠️ DIFFERENT: marketing_Forms.sql10. ⚠️ DIFFERENT: marketing_HubSpotLandingPages.sql11. ⚠️ DIFFERENT: marketing_Meltwater.sql12. ⚠️ DIFFERENT: marketing_pagePerformance.sql13. ⚠️ DIFFERENT: marketing_pagePerformanceFormSubmissions.sql14. ⚠️ DIFFERENT: marketing_SocialMedia.sql15. ⚠️ DIFFERENT: marketing_ThoughtLeadership.sql … Read more

Common Data Standard Reference Guide

by

Ensuring Structured, Reusable, and Scalable Data Architecture 1️⃣ Purpose of the Common Data Standard The Common Data Standard (CDS) establishes a structured framework for defining DataMart views in a consistent and scalable manner. This standard: ✅ Promotes reusability across different datasets.✅ Ensures alignment between business logic and reporting needs.✅ Enables efficient data joins and minimises … Read more

Utility (Commodity) Views

by

Bridging Structured Data with Usability 1️⃣ Understanding the Layers: CDS vs. Utility Views The Common Data Standard (CDS) defines a structured, specialist-oriented view of data, ensuring consistency and modularity in reporting. However, for non-specialists, the Utility (Commodity) View simplifies data consumption by cross-combining relevant details into a single, user-friendly dataset. View Type Purpose Audience Example … Read more

Data Dictionary Entries

by

1️⃣Overview The Data Dictionary serves as the backbone for structured data definitions across financials, operations, projects, compliance, and workforce domains. It ensures standardised terminology, clear metadata definitions, and structured governance for all key data entities. Key Functions: ✅ Standardised Definitions – Ensures clarity and uniformity across datasets.✅ Metadata-Driven Organisation – Supports schema validation and query … Read more

Release 56

by

Summary This minor release of some 36 changes to ensure that all view definitions now include an Alias for the table in the FROM clause. These updates are cosmetic in nature and do not impact the performance of the DataViews. Key Updates Impact Next Steps For any queries or issues, please reach out to the … Read more

get.myarchive

by

Purpose The get.myarchive stored procedure is designed to retrieve archived data from a specified DataMart view, allowing for historical analysis and structured retrieval. The procedure integrates data retrieval logic, version control, and debugging capabilities to ensure flexible and efficient access to archived data. Key Features Workflow Use Case This procedure is ideal for historical data … Read more

Infrastructure.OSHrecords

by

Purpose The Infrastructure.OSHrecords DataMart is designed to provide a structured and centralised repository for occupational health and safety (OHS) records sourced from the myOSH system via API exports. This DataMart enables efficient reporting, compliance tracking, and analysis of safety-related incidents, risk assessments, and other regulatory documentation. By transforming the raw API data into a well-structured … Read more

White Paper: Common Data Model (Datamarts)

by

Proposal for a white paper on Common Data Model (Datamarts) Proposed Structure for the White Paper 1. Executive Summary 2. Introduction 3. Objectives 4. Proposed Standardised Format 5. Naming Conventions 6. Standardised Structure for Views 7. Metadata Format 8. Implementation Roadmap 9. Benefits 10. Conclusion Naming Suggestions for Views Here are some options for naming … Read more