The January 2025 monthly launch delivers long-awaited scale improvements, enhanced collaboration features, and important platform updates — including batched exports for enterprise catalogs, bidirectional ServiceNow integration, and expanded notification capabilities.
Note on Feature Timing: Some features in this January update were also included in our December communication. Due to the busy holiday season, the release of these features was rescheduled to January. Thank you for your patience as we ensured a smooth rollout.
🔥 What's New?
📤 Export More Than 2000 Resources Through Batching
Enterprise-scale exports without limits.
As previously announced in December, this feature is now live! Enhanced export capabilities remove the 2,000 resource limit by automatically splitting large exports into manageable batches. Exports exceeding 2,000 resources are delivered in multiple batch files of 2,000-resource increments — enabling bulk operations on enterprise-scale datasets without hitting hard limits.
Who benefits: Data stewards and administrators managing large catalogs who need to export and edit metadata for thousands of resources at once, particularly when using bulk import/export workflows.
Learn more in our documentation.
🔄 Access Request Updates from ServiceNow for Premium Request Access Automation
Bidirectional ServiceNow integration for complete visibility.
As previously announced in December, this feature is now live! Status updates now flow automatically from ServiceNow back to data.world, keeping users informed about access provisioning progress directly in the platform where they initiated their requests. No more checking multiple systems — users see exactly when their requested access has been granted.
Who benefits: Data consumers who request access to restricted resources and administrators who manage access workflows, particularly in organizations with ServiceNow-based provisioning processes. This functionality is part of premium governance automations.
🏥 Data Quality Badge Displayed in Graph Explorer
Data health at a glance in lineage views.
A data quality health badge is now included in the lineage/graph explorer view, showing the health status for each resource element. Health is determined by data from your integrated third-party data quality provider, giving you instant visibility into data quality as you explore dependencies and lineage.
Who benefits: Lineage and Graph Explorer users who need to understand data quality context while analyzing dependencies and impact.
💫 Coming Soon
✅ Automated Resource Status Update in Suggest Changes Premium Automation
Keep resource status current automatically.
An enhancement to Suggest Changes Premium Automation will enable automatic updates to the resource status field (an out-of-the-box metadata field on all catalog resources) when a change request is approved at the final workflow step. This configurable feature can be toggled on or off for each automation, reducing manual effort and ensuring resource status accurately reflects the latest approved changes.
Who benefits: Governance teams, data stewards, and administrators, especially those in organizations with high governance requirements who need to ensure resource status is always up to date without manual intervention. This functionality is part of premium governance automations.
💬 @Mentioning User Groups & SCIM Teams: Email Notifications for Group Mentions
Scale collaboration with group notifications.
An enhancement to the notifications system will enable email alerts to be sent to all members of a User Group — including SCIM-provisioned teams — when the group is @mentioned in a discussion thread. This brings parity with individual @mentions, eliminating the need to manually @mention dozens of individuals and streamlining collaboration and review processes.
Who benefits: Organizations with robust data governance programs, especially those leveraging SCIM for user provisioning, data stewards, subject matter experts (SMEs), and Data Councils who collaborate on business glossary definitions and metadata enrichment. Supports all user groups, not just SCIM teams, for broad applicability.
📋 Support a Single Form Across Multiple Automations in Premium Request Access Automation
Simplified form management for access workflows.
Enhanced configuration options will allow administrators to use a single access request form across multiple Premium Request Access automations, simplifying form management and creating a more consistent experience for data consumers across different access workflows.
Who benefits: Administrators managing multiple access request automations who want to streamline configuration and provide consistent request experiences. This functionality is part of premium governance automations.
🔧 Other Updates
Removal of "Getting Started" Checklist from App Home Page
A cleaner home page experience.
We're removing the "Getting Started" checklist widget from the home page in response to customer feedback. Many users found the checklist unhelpful after onboarding and felt it took up valuable space on the landing page. This change provides a cleaner, less cluttered experience for all catalog users.
Who benefits: All catalog users — especially those who have already completed onboarding or who use the catalog regularly.
🔌 Retirement of Legacy Hoots Admin Portal (Effective 1/16/2026)
Streamlined Hoots administration.
The legacy Hoots Admin Portal will be permanently removed from data.world on January 16th, following the rollout of Hoots 1.5 and the new Hoot Browser Extension module announced in October. All Hoots management is now handled through the new Hoot Browser Extension and Catalog Toolkit module.
Who benefits: All customers and admins who previously managed Hoots via the old admin portal. Teams who have not yet migrated to the new Hoot Browser Extension module should take immediate action to avoid disruption.
🆔 SCIM Team Agent IDs Are Now Generated IDs
More flexibility for SCIM team naming.
We're changing how agent IDs are formed on SCIM-created Teams to use generated hashes instead of matching the display name. This change allows for more flexibility in naming Teams and relaxes other restrictions. It does not negatively impact searchability or discoverability, and these changes affect newly created Teams only.
Who benefits: All SCIM-enabled customers who may notice newly created SCIM Teams having a generated agent ID that does not match the display name.