Did you know a resource on data.world, like a table, business term, or dashboard, can belong to multiple collections?

We've now made it easy to pick which collections a resource belongs to: simply click "Edit" on the resource page, then pick & choose which collections the resource should appear in and save those changes.

For example, if you had a business term in a "Sales" collection, you can now easily add that same business term to your "Finance" and "Customer Service" collections with only a few clicks. 

Likewise, if you wanted to move a resource from one collection to another, you can click "Edit" on the resource page, select the new collection, de-select the existing collection, and save that change. 

Customers who use Open collections can create a resource in a private collection, and only when it's ready for global consumption, add it to the Open collection.

We've also recently added the ability to create collections in the UI - read more about that here.

Stay tuned for editing collections in the API, and allow collections to be edited in bulk!

For customers leveraging data artifact lineage, it was a little counterintuitive that the high-level business lineage diagram would show up below your dataset relationships but above all your other relationships. So, we've moved it to just above the Technical details section.

First of all, this update includes a couple fixes:

• Visits - New Users By Month was based off of pageviews, which can be affected by ad blockers or restrictive browser settings. It has been switched to use a more robust source of events. This may slightly increase this metric going forward.
• Visits - Unique Visitors to Date was based off of pageviews, which can be affected by ad blockers or restrictive browser settings. It has been switched to use a more robust source of events. This may slightly increase this metric going forward.

Next, we've added an additional table/report:

• Users love leveraging our built-in query workbench and federated query capabilities, however often it could be challenging for administrators to easily troubleshoot when queries go wrong or audit what queries are being executed.
• The new Events - Queries report in your ddw-metrics dataset now provides quick access to audit level details on what queries are being run, by whom, including what the query text is, for fast troubleshooting and effective auditing.
• This report is currently only available for multi-tenant enterprise customers -- it will be rolled out to single-tenant customers in the next few business days.

Previously, data.world used the words people, contributors, invite, share, and a few other names in various places in the application, which caused confusion.

We now use Members to show the users that are part of an organization, Access as the tab where you can manage access at a more granular level on datasets or other resource pages, and Grant access as a consistent call to action to add additional members.

Also, the Member organization role has been updated to be Basic member to be clear and unique from members more generally.

Our automated lineage capabilities, powered by MANTA, now are incorporated into our metadata collector module, also known as the data.world catalog collector (DWCC). This enables you to integrate technical lineage into your data catalog in a more consistent way to our other metadata integrations.

Thank you for checking out the data.world Product - What's New changelog to learn about all the new and updated features hot off the presses. We wanted to have an interactive, rapidly and frequently updated newsfeed that reflects on data.world's continuous integration and continuous deployment approach -- where multiple product releases happen every week, and the product is constantly evolving.

As always, if you have questions or feedback feel free to reach out to us at support@data.world or your Customer Success Manager, and if you are looking for older release notes, you can click here.