Organization admins can now edit multiple resources directly from the Organization Profile Page.

Community organizations support editing multiple datasets or projects that match the filters in the Resources tab.

Enterprise organizations also support editing multiple analyses, business terms, or tables.

The Organization Profile Page now features quick links to collections for enterprise organizations.

Members of an organization can filter and browse collections by name on the Overview tab. Admins can also create new collections directly from the organization profile.

Use the "None of the following" option in the Advanced Search Builder to exclude search results that match a specific value. This feature works with the logical NOT operator in our Advanced Search Syntax.

Expand and collapse controls are now available for the search filters sidebar to help you quickly locate available filtering options.

The Organization Profile Page is getting a facelift this week to offer more intuitive navigation, stronger support for custom catalog types, and richer discovery features. 

Browse the Overview tab for quick links to different resource categories in your catalog. The quick link tiles will take you to a filtered presentation of the new Resources tab. This view operates much like the main search page with support for facets and advanced search syntax, all scoped to your organization's resources. 

Searching for open data? Community organizations will now also have these search and filter options available on the new Resources tab.

Another neat feature for our customers leveraging data artifact lineage! In addition to being interactive, the resource items now display a summary card when hovering. You can preview metadata at a glance and click through to the collection, individual tags, or to the resource itself.

Updated metrics tables/reports have arrived on October 18, 2021! Some reports may take 24-48 hours to reflect the new data after deploy due to sync timing.

Data dictionary has been updated to reflect the latest updates as well.

Updated Tables - For multi-tenant

1. Events - Dataset or Project Views By Org - Name changed (from “Events - Views by Org”) and column name “dataset_views” changed to “views”
2. Events - Searches - Last 90 Days - Fixed a bug that sometimes caused duplicate rows
3. Membership - Daily Counts - By Org - Name changed (from “Membership - Daily - By Org")
4. Resources - Org Owned Database connections - Name changed (from “Resources - Database connections”) and added column “owner”
5. Tops - Bookmarks - Extended range to all users (it previously was limited to the top 10 users) and added column “displayname”
6. Tops - Dataset Creation - Extended range to all users (it previously was limited to the top 10 users) and added column “displayname”
7. Tops - Most Bookmarked Resources - Extended date range to all resources (it previously was limited to the top 10 resources)
8. Tops - Most Comments - All Time - Extended date range to all resources (it previously was limited to the top 10 resources)
9. Tops - Most Searched Terms - Fixed a bug that sometimes caused duplicate rows
10. Tops - Most Viewed Resources - Added “catalog” type category to the resource_type variable
11. Tops - Pageviews By Resource and Agentid - Added “catalog” type category to the resource_type variable

Updated Tables - For single-tenant

1. Events - Dataset or Project Views By Org - Name changed (from “Events - Views by Org”) and column name “dataset_views” changed to “views”
2. Resources - Org Owned Database connections - Added column “owner”
3. Tops - Bookmarks - Extended range to all users (it previously was limited to the top 10 users) and added column “displayname”
4. Tops - Dataset Creation - Extended range to all users (it previously was limited to the top 10 users) and added column “displayname”
5. Tops - Most Viewed Resources - Added “catalog” type category to the resource_type variable
6. Tops - Pageviews By Resource and Agentid - Added “catalog” type category to the resource_type variable

For customers leveraging data artifact lineage, the resource items are now interactive. You can click through the icons to view the respective resource pages.

Updated metrics tables/reports have arrived on September 16, 2021! Some reports may take 24-48 hours to reflect the new data after deploy due to sync timing.

New Tables (multi tenant & single tenant)

• Resources - Dataset Files - A detailed listing of all (currently existing) files residing in datasets.
• Tops - Engagement - A list of users ranked by key engagement metrics.
• Resources - Live Metadata Assets Created - By Day - A long form series of counts of metadata assets created by date.
• Events - Dataset Activity - By Day - A fact table containing dataset activity measurements, aggregated by UTC-based calendar day.
• Events - Metadata Assets Activity - By Day - A fact table containing metadata assets activity measurements aggregated by UTC-based calendar day.

Updated Tables (multi tenant & single tenant)

• Membership - Current - By Org - Added new columns for email address, user display name, org-level authorization settings, org-level visibility settings and date of most recent update to authorization settings.
• Events - Searches - Last 90 Days - Fixed a bug that caused the counts of search results to be capped at 10.
• Events - Downloads (previously Events - Downloads - Last 90 Days) - Extended the timeframe to all-time; added new columns for file labels and user displayname. 

Base platform data updates (single tenant only):

• DOWNLOADS - new columns: (type, filename, filelabels) providing information about file downloads.
• DAILY_DWEC_ASSET_FACTS - new fact table providing measurements of metadata asset activity by date.
• FILES_DATASET_DIM - new dimension table providing information about files residing in Datasets.

The data.world public API supports several options for programmatically making updates to resources on the platform. PATCH is a method for making partial updates to individual records, such as adding tags, changing a description, or modifying a title.

In the next two weeks, we will be making a change to the way PATCH endpoints modify list values. We outline these changes below.

Existing Merge Behavior

Lists are merged with existing values on PATCH requests

1. A dataset has tags: [tag A , tag B] 
2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
3. The dataset is updated to reflect tags: [ tag A, tag B, tag C ,tag D]
4. A PATCH request is sent to /datasets/democorp/my-example-dataset with payload: { "tags": []  }
5. No change is applied and the tags remain: [ tag A, tag B, tag C ,tag D]

New Replace Behavior

Lists replace existing values on PATCH requests

1. A dataset has tags: [tag A , tag B] 
2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
3. The dataset is now updated to have tags: [ tag C ,tag D].  tag A and tag B have been removed.
4. I send a PATCH request to /datasets/democorp/my-example-dataset with body: { "tags": []  }
5. The dataset has been updated to remove all tags.

Why we are making this change

Today, PATCH can be used to add, modify, or remove fields for all non-list values. With the current merge logic, items can only be appended to list values using PATCH. As a consequence, if you want to remove or reorder the items in a list, you must use the PUT method, which does not support partial updates and requires a full overwrite of the existing record. The new logic to overwrite list values will allow users to make partial updates to records that remove or modify the order of items in the list without needing to modify the entire record.

This new logic primarily impacts tags, file labels, collections, and multi-select custom metadata fields.