¶ Data Product Lifecycle
The data product lifecycle consists of six distinct states:
Draft → Submitted for Review → Approved for Publishing → Published
↓
Deprecated
↓
Retired
¶ Draft Data Product
Status: Work in progress, not visible to end users
Characteristics:
- Initial creation phase
- Schema being defined
- Documentation incomplete
- No access requests allowed
- Visible only to creators and stewards
Activities:
- Define metadata
- Create schema
- Set up sync strategy
- Add documentation
- Link semantics
- Add contributors
Who Can Access:
- Creator
- Data owners
- Data stewards
- Administrators
Transitions To:
- Submitted for Review: When ready for governance review
- Deleted: If abandoned
¶ Submitted for Review Data Product
Status: Pending governance approval
Characteristics:
- Complete and ready for review
- Under evaluation by governance team
- Not yet accessible to consumers
- May require changes
Review Criteria:
- Schema completeness
- Documentation quality
- Semantic mappings
- Access policies defined
- Compliance with standards
- Data quality metrics
Who Reviews:
- Data governance office
- Domain architects
- Compliance team
Possible Outcomes:
- Approved: Moves to approved state
- Rejected: Returns to draft with feedback
- Requires Changes: Specific modifications needed
¶ Approved for Publishing Data Product
Status: Approved but not yet live
Characteristics:
- Passed governance review
- Ready for publishing
- Final checks being performed
- Access policies configured
Activities:
- Final testing
- API endpoint configuration
- Access control setup
- Marketing page finalization
- Announcement preparation
Who Can Access:
- Same as draft state
- Plus governance reviewers
Transitions To:
- Published: When formally released
- Draft: If issues discovered
¶ Published Data Product
Status: Live and available for consumption
Characteristics:
- Discoverable in marketplace
- API endpoint active
- Access requests accepted
- SLA enforced
- Monitored for quality
Activities:
- Accept access requests
- Monitor usage
- Maintain data quality
- Update documentation
- Address issues
Who Can Access:
- All users (discovery)
- Authorized applications (data access)
- Can request access
Metrics Tracked:
- Access requests
- Data consumption
- API calls
- Data quality scores
- User feedback
¶ Deprecated Data Product
Status: Marked for retirement, still accessible
Characteristics:
- Warning displayed to users
- Replacement product identified
- Migration timeline provided
- Access still granted
- No new access requests
Deprecation Notice Example:
⚠️ DEPRECATED
This data product is deprecated and will be retired on 2025-12-31.
Replacement: Customer Analytics v2.0
Migration Guide: docs/migration-guide.md
Please migrate to the new product before the retirement date.
Activities:
- Notify existing consumers
- Provide migration support
- Update documentation
- Monitor migration progress
Who Can Access:
- Existing authorized applications
- Owners and stewards (for maintenance)
¶ Retired Data Product
Status: No longer available, archived
Characteristics:
- API endpoint disabled
- No data access allowed
- Metadata preserved
- Audit logs retained
- Can be restored if needed
Activities:
- Data archived
- Access revoked
- Historical records maintained
- Replacement links updated
Who Can View:
- Administrators (metadata only)
- Audit and compliance teams
¶ Next Steps
- Create a Data Product - Start creating your first product
- Governance & Approval Process - Learn about the review workflow
- Publishing Data Products - Make your product available