The November 2024 release of Data Marketplace includes the following new features and enhancements.
Metadata access control
This release of Metadata Command Center introduces metadata access control, which provides options for enhanced control over how users interact with the assets in Data Governance and Catalog and Data Marketplace.
Metadata access control is the practice of managing the level of user access to assets in your organization through a set of rules called access policies. As an Administrator, you can use metadata access control to define and implement access policies in Metadata Command Center that restrict a user's access to metadata if necessary. This ensures that users can only view the data and perform the actions you deem appropriate. You can hide segments of data in Data Marketplace by configuring asset groups for categories. The asset group of a category is inherited down the hierarchy, so data collections within the category will also be hidden from those not associated to the asset group. For these users, the system will obfuscate or hide any mentions of the asset in the Data Marketplace interface.
For example, if you have data collections that contain sensitive information such as a possible but incomplete acquisition your company is planning to make, you may want to allow only your Mergers and Acquisitions team to view them. To accomplish this, you can create a separate category called ‘Mergers and Acquisitions’ and add the relevant data collections to this category. After this, you can apply the relevant metadata access controls to the category to hide it from the view of unauthorized users.
Note: After your Informatica Intelligent Cloud Services POD is upgraded, Data Marketplace will continue to work the same as the previous version.
For more information about metadata access control, see the Administration help in Metadata Command Center.
Stakeholder and user roles
Stakeholder roles are a set of permissions and privileges that you can assign to users and groups on a specific Data Marketplace asset, such as a category or a data collection. Unlike with Informatica Intelligent Cloud Services user roles that allow users to perform actions across Data Marketplace, a user with a stakeholder role can only perform actions on the assets on which they are assigned as a stakeholder.
For example, a user that is assigned with the Data Marketplace Administrator user role can perform various actions such as create, modify or delete data assets across Data Marketplace. On the other hand, a user that is assigned as a stakeholder of a category with the Category Owner stakeholder role can only manage their respective category and the subcategories and data collections within it.
To simplify your experience, the following changes have been made:
•A new tab called Stakeholders has been added to the category and data collection details pages. You can manage the stakeholders of an asset on this tab. The Summary tab will continue to show an overview of stakeholders but you can no longer modify an asset's stakeholders from the Summary tab.
•On the Search page, the Owners filter has been renamed to Stakeholders. Additionally, the Data Owners and Technical Owners columns have been replaced by a single column called Stakeholders.
For more information about stakeholder roles, see the Permissions and privileges for Data Marketplace topic in the Introduction and Getting Started help.
Support for custom user roles
You can now assign custom roles that you create in Administrator to Data Marketplace users in your organization. Custom roles allow you to refine user permissions and privileges based on the needs of your organization.
For example, if you want to verify that the orders for data collections comply with the policies defined for your organization, you can create a custom role called Auditor that has only read permission on data collections, orders, consumer accesses and data assets but doesn't have permissions to modify or delete any data.
For more information about custom roles, see the Custom roles topic in the Introduction and Getting Started help.
Improved user experience
Viewing a category
To improve your category browsing experience, the contents of a category page are now reorganized into the following tabs on a category page:
- Summary
- Data Collections
- Stakeholders
For more information about categories, see the Categories topic in the Introduction and Getting Started help.
Creating new categories and data collections
When you try to create a category or a data collection, Data Marketplace now opens a wizard. The new wizard simplifies the stakeholder assignment experience for the category or the data collection.
Ordering data collections
On the Request Details page of the order wizard, the Usage Context menu now displays certified uses in a separate section. This allows you to easily identify the certified uses of the data collection.
Furthermore, while ordering a data collection for which no certified uses are configured, the system no longer displays a warning message when you specify a usage context on the Request Details page of the order wizard.
For more information about how you can order a data collection, see the Ordering data collections topic in the Working With Data Collection help.
Recent data collections on the Home page and Category page
On the Home page and on a category page, the Recent Data Collections carousel now displays the most recently created data collections.
Earlier, the Recent Data Collections carousel displayed the most recently modified data collections.
For more information, see the Introduction and Getting Started help.
Support for additional Data Governance and Catalog asset types
On the Setup > Integration page, you can now import several new assets from Data Governance and Catalog. The following list shows the assets that you can now import:
•Azure Data Factory Data Set
•Database Objects External Table
•Database Objects Table
•Database Objects Unresolved View
•Database Objects View
•Informatica Intelligent Cloud ServicesData Integration Business Entity
•Looker Dashboard
•Looker Look
•Looker Query
•Looker Table
•Looker View
•Oracle Business Intelligence Suite Enterprise Alias Table
•Oracle Business Intelligence Suite Enterprise External Table
•Oracle Business Intelligence Suite Enterprise Logical Table
•Oracle Business Intelligence Suite Enterprise Logical Fact Table
•Oracle Business Intelligence Suite Enterprise Physical Table
•Oracle Business Intelligence Suite Enterprise Presentation Table
•Oracle Business Intelligence Suite Enterprise Presentation Face Table
•Oracle Business Intelligence Suite Enterprise Report
•Microsoft Power BI Dashboard
•Microsoft Power BI Dataflow Table
•Microsoft Power BI Paginated Report Data Set
•Salesforce Object
•SAP Classic Business Warehouse Info Provider
•SAP Classic Business Warehouse Query
•SAP Classic Business Warehouse Workbook
•SAP HANA Business Warehouse Info Provider
•SAP HANA Business Warehouse Query
•SAP S/4 HANA Function Module Table
•SAP S/4 HANA SAP Table
•SAP S/4 HANA SAP View
•SQL Server Reporting Services Data Set
•SQL Server Reporting Services Report
•Tibco Spotfire Custom Query
•Tibco Spotfire Data Table
•Tibco Spotfire ESRI Shape File
•Tibco Spotfire Excel Worksheet
•Tibco Spotfire Excel Workbook
•Tibco Spotfire File
•Tibco Spotfire Report
•Tibco Spotfire SBDF File
•Tibco Spotfire Table
•Tibco Spotfire Text File
•Tibco Spotfire View
For more information, see the Enrich data collections with Data Governance and Catalog assets topic in the Set Up Data Marketplace help.
REST API enhancements
Delete orders, data collection requests and consumer accesses
You can now use an API call to delete the following objects:
- A consumer access that is withdrawn.
- An order that isn't associated with a consumer access.
Earlier, you couldn't delete a fulfilled order.
- A data collection request in any state.
Earlier, you couldn't delete a completed data collection request.
Invoke an API without using Application Integration
You can now authenticate yourself with JSON Web token authentication to invoke an API that utilizes the GET method.
Use GET APIs to retrieve more results per page
When you invoke an API that utilizes the GET method, you can now configure the limit parameter to display a maximum of 100 results per page.