Breadcrumbs

Metadata

Custom Metadata is added in the packaging area when users create a data product, for view as additional information on the Exchange. For information on how to set this as a producer, see here.

Product and Asset custom metadata is now searchable within Global Search. It works by looking at values that user enters and displays what product/asset and key they were found in. 

https://lh7-rt.googleusercontent.com/slidesz/AGV_vUd7goHZeaKS-WnpIrsK9Qs2DQ4LJR0hRQuTK2rZOaiCkCk0KHmID5gh1nYzhj-nSdhTQ-IIKosorF6E6M50m2hi_7kKvjAIlJSfg-WHFJ8cY6jGg9smDxRjk7sPawt7bgL01-1J2g=nw?key=0k4066bN43dHSqCf16k4rw

Results are shown only for assets and products that user has visibility or permissions for.

Ecosystem Administrators can optionally enforce product custom metadata through providing default metadata field and values. By defining the product attributes that need to be provided by a Product Manager, Ecosystem Admins can ensure the standardization of certain product metadata across the ecosystem.

This can be achieved by adding a metadata key/value pair in the ‘Metadata’ section of the Ecosystem Administrator section.

https://lh7-rt.googleusercontent.com/slidesz/AGV_vUfza7Rh9PEyuyVy03ZnUhuqeDpLdZNafjneH3uDSHjWo1hQM2TOVMteY5urZeW1AsEOr0dSJbKXWAVUpMyUVuFBJn3FYI45bLElPnFzG5yV-rIvJtZa4ExY5a1M6GHmh8OBqZPKhQ=nw?key=hm-RFWmwbPLPt9JPkp1FwQ

For example, a configuration may look like this:

Key:

productPackagingMetadataSchema

Value:

{

    "fields": [

        {

            "key": "KeyName",

            "options": [

                "Value1",

                "Value2",

                "Value3",

                "Value4"

            ],

            "fieldType": "select",

            "required": true,

            "defaultValue": "",

            "placeholder": "Placeholder text"

        }

    ]

}