Merge pull request #8 from open-metadata/fix_build

Add Followers explanation and AI Governance model

Author: harshach

docs/core-concepts/followers.md

@@ -1363,6 +1363,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about API endpoint changes**
+
+Followers allow users to "follow" API endpoints and receive notifications when they change. This is critical for:
+
+- **API Consumers**: Monitor endpoints your applications depend on
+- **Backend Engineers**: Track endpoints you own or maintain
+- **Integration Teams**: Stay informed about contract changes
+- **API Product Managers**: Monitor endpoint usage and evolution
+
+**Key Benefits**:
+- Receive notifications about breaking changes to request/response schemas
+- Track deprecation notices and versioning changes
+- Monitor authentication or rate limiting updates
+- Get alerts for SLA or performance threshold changes
+
+**Common Use Cases**:
+- Frontend developers follow endpoints their apps consume
+- Backend engineers follow production endpoints they maintain
+- DevOps teams follow critical API endpoints for monitoring
+- Product teams follow public API endpoints for customer impact
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 ### List API Endpoints

docs/data-assets/apis/api-endpoint.md

@@ -1012,6 +1012,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about chart changes**
+
+Followers allow users to "follow" individual charts and receive notifications when they change. This is useful for:
+
+- **Chart Creators**: Monitor charts they've built
+- **Metric Owners**: Track visualizations of key business metrics
+- **Stakeholders**: Stay informed about specific KPI visualizations
+- **Collaboration**: Work with team members on chart refinements
+
+**Key Benefits**:
+- Receive notifications about chart configuration changes
+- Track changes to underlying queries or data sources
+- Monitor visualization type or display property updates
+- Get alerts for ownership or deprecation changes
+
+**Common Use Cases**:
+- Analysts follow charts they created or maintain
+- Business users follow charts showing their KPIs
+- Data teams follow charts using complex calculations
+- Executives follow critical metric visualizations
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 All Chart operations are available under the `/v1/charts` endpoint.

docs/data-assets/dashboards/chart.md

@@ -1034,6 +1034,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about dashboard changes**
+
+Followers allow users to "follow" a dashboard and receive notifications when it changes. This is particularly valuable for:
+
+- **Business Stakeholders**: Track dashboards with key business metrics and KPIs
+- **Report Consumers**: Get notified when dashboards are updated or metrics change
+- **Collaboration**: Stay in sync with team members working on shared dashboards
+- **Governance**: Monitor dashboards for compliance and data quality
+
+**Key Benefits**:
+- Receive notifications about dashboard updates and refreshes
+- Track changes to underlying data sources or calculations
+- Monitor chart additions, removals, or modifications
+- Get alerts for ownership, tier, or governance changes
+
+**Common Use Cases**:
+- Executives follow executive dashboards for KPI tracking
+- Product managers follow dashboards tracking product metrics
+- Analysts follow dashboards they've created or contributed to
+- Data engineers follow dashboards to monitor data pipeline health
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 All Dashboard operations are available under the `/v1/dashboards` endpoint.

docs/data-assets/dashboards/dashboard.md

@@ -14,13 +14,15 @@ The **DatabaseSchema** entity represents a logical namespace within a database t
 graph LR
     A[DatabaseService] --> B[Database]
     B --> C[Schema]
-    C --> D[Table]
-    D --> E[Column]
+    C --> D1[Table]
+    C --> D2[StoredProcedure]
+    D1 --> E[Column]
 
     style A fill:#667eea,color:#fff
     style B fill:#4facfe,color:#fff
     style C fill:#00f2fe,color:#333
-    style D fill:#00f2fe,color:#333
+    style D1 fill:#00f2fe,color:#333
+    style D2 fill:#00f2fe,color:#333
     style E fill:#e0f2fe,color:#333
 ```
 

docs/data-assets/databases/database-schema.md

@@ -14,13 +14,15 @@ The **Database** entity represents a logical database within a database service.
 graph LR
     A[DatabaseService] --> B[Database]
     B --> C[Schema]
-    C --> D[Table]
-    D --> E[Column]
+    C --> D1[Table]
+    C --> D2[StoredProcedure]
+    D1 --> E[Column]
 
     style A fill:#667eea,color:#fff
     style B fill:#4facfe,color:#fff
     style C fill:#00f2fe,color:#333
-    style D fill:#00f2fe,color:#333
+    style D1 fill:#00f2fe,color:#333
+    style D2 fill:#00f2fe,color:#333
     style E fill:#e0f2fe,color:#333
 ```
 
@@ -34,6 +36,7 @@ graph LR
 ### Child Entities
 - **DatabaseSchema**: Schemas within this database
 - **Table**: All tables across all schemas in this database
+- **StoredProcedure**: All stored procedures across all schemas in this database
 
 ### Associated Entities
 - **Owner**: User or team owning this database
@@ -746,6 +749,39 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about database changes**
+
+Followers allow users to "follow" a database and receive notifications when it changes. This is useful for:
+
+- **Monitoring Dependencies**: Get notified when databases your applications depend on change
+- **Staying Informed**: Track databases you're interested in without being the owner
+- **Collaboration**: Stay in sync with team members working on the same databases
+- **Governance**: Monitor databases with compliance requirements
+
+**Key Benefits**:
+- Receive notifications about schema changes, new schemas, or deletions
+- Track governance changes (tags, ownership, domain assignments)
+- Monitor data quality issues at the database level
+- Get alerts for deprecation notices
+
+**Following vs Ownership**:
+- **Ownership** = Responsibility and accountability for the database
+- **Following** = Interest and awareness about the database
+
+Any user can follow any database they have access to. A database can have multiple followers.
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about:
+
+    - How to follow databases via UI and API
+    - Notification preferences and configuration
+    - Best practices for using followers effectively
+    - Integration with webhooks and activity feeds
+
+---
+
 ## API Operations
 
 All Database operations are available under the `/v1/databases` endpoint.

docs/data-assets/databases/database.md

@@ -1322,6 +1322,47 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about table changes**
+
+Followers allow users to "follow" a table and receive notifications when it changes. This is one of the most useful features for data practitioners:
+
+- **Monitor Dependencies**: Get notified when tables your applications or dashboards depend on change
+- **Schema Changes**: Receive alerts when columns are added, removed, or modified
+- **Data Quality**: Be notified of test failures, anomalies, or freshness issues
+- **Collaboration**: Track tables you're working on with others
+
+**Key Benefits**:
+- Receive notifications about schema changes (new columns, type changes)
+- Track data quality test results and failures
+- Monitor data profiling anomalies (unusual null rates, distribution changes)
+- Get alerts for deprecation, tier changes, or ownership updates
+- Stay informed about query usage patterns and popularity
+
+**Following vs Ownership**:
+- **Ownership** = Responsibility and accountability for the table's quality and accuracy
+- **Following** = Interest in being notified about changes to the table
+
+Any user can follow any table they have access to. Tables typically have multiple followers (analysts, engineers, data scientists who use the data).
+
+**Common Use Cases**:
+- Data scientists follow source tables for their ML models
+- Analysts follow tables used in their reports and dashboards
+- Data engineers follow tables in production pipelines
+- Compliance officers follow tables containing PII or sensitive data
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about:
+
+    - How to follow tables via UI and API
+    - Configuring notification preferences (immediate vs digest)
+    - Best practices for avoiding notification overload
+    - Bulk following patterns (e.g., follow all tables in a domain)
+    - Integration with webhooks and Slack/Teams
+
+---
+
 ## API Operations
 
 All Table operations are available under the `/v1/tables` endpoint.

docs/data-assets/databases/table.md

@@ -1233,6 +1233,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about topic changes**
+
+Followers allow users to "follow" a topic and receive notifications when it changes. This is critical for:
+
+- **Event Producers**: Monitor topics they publish to
+- **Event Consumers**: Track schema changes in topics they consume
+- **Platform Teams**: Get notified of topic configuration changes
+- **Compliance**: Monitor topics with sensitive data
+
+**Key Benefits**:
+- Receive notifications about schema changes (critical for compatibility)
+- Track partition count or replication factor changes
+- Monitor retention policy or configuration updates
+- Get alerts for deprecation, ownership, or governance changes
+
+**Common Use Cases**:
+- Developers follow topics their services consume
+- Platform engineers follow all production topics
+- Data scientists follow topics with ML training events
+- Compliance officers follow topics with PII or sensitive data
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 All Topic operations are available under the `/v1/topics` endpoint.

docs/data-assets/messaging/topic.md

@@ -1419,6 +1419,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about ML model changes**
+
+Followers allow users to "follow" an ML model and receive notifications when it changes. This is valuable for:
+
+- **Data Scientists**: Monitor models they've developed or deployed
+- **ML Engineers**: Track model version changes and deployments
+- **Stakeholders**: Stay informed about production model updates
+- **Compliance**: Monitor models for governance and regulatory requirements
+
+**Key Benefits**:
+- Receive notifications about model version updates
+- Track feature or algorithm changes
+- Monitor performance metrics and drift
+- Get alerts for ownership, deprecation, or governance updates
+
+**Common Use Cases**:
+- Data scientists follow models in production
+- ML engineers follow models they deploy and maintain
+- Product managers follow models powering product features
+- Compliance teams follow models with regulatory implications
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 All ML Model operations are available under the `/v1/mlmodels` endpoint.

docs/data-assets/ml/mlmodel.md

@@ -1207,6 +1207,34 @@ for details on defining and using custom properties.
 
 ---
 
+## Followers
+
+**Stay informed about pipeline changes**
+
+Followers allow users to "follow" a pipeline and receive notifications when it changes. This is essential for:
+
+- **Data Engineers**: Monitor pipelines they own or maintain
+- **Pipeline Dependencies**: Track upstream/downstream pipeline changes
+- **Operations**: Get notified of pipeline failures or configuration changes
+- **Stakeholders**: Stay informed about ETL processes affecting their data
+
+**Key Benefits**:
+- Receive notifications about pipeline configuration changes
+- Track task additions, removals, or modifications
+- Monitor pipeline schedule or trigger changes
+- Get alerts for ownership, deprecation, or governance updates
+
+**Common Use Cases**:
+- Data engineers follow production pipelines they maintain
+- Analysts follow pipelines that refresh their reports
+- Data scientists follow pipelines feeding their ML models
+- Operations teams follow critical data pipelines
+
+!!! tip "Learn More"
+    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+
+---
+
 ## API Operations
 
 All Pipeline operations are available under the `/v1/pipelines` endpoint.