What does it mean to publish a Data Product

Publishing a Data Product involves registering its metadata and associated details into the Data Product Registry. This process ensures that the Data Product is discoverable, well-documented, and accessible for consumption or further governance actions. The registry acts as a centralized repository that manages the lifecycle of Data Products and their versions, providing a seamless integration point for various services and stakeholders.

How to publish a new data product from a descriptor

It’s possible to publish a new data product from a descriptor. In order to do that, from the Data Product Version List page, use the “Publish Data Product Version” button.

Inside the dialog, choose the radio button “Via File”.

Using the “Via File” option, you can upload a JSON or YAML file to create a new version of a data product and publish it on the Open Data Mesh platform. Ensure that the descriptor is complete and adheres to the required format.

How to publish a new data product from a repository

To publish a new data product version directly from a repository, follow these steps:

1. Navigate to the Data Product Version List page and click the “Publish Data Product Version” button.
2. In the dialog, select the “Via Repository” option.

3. Fill in the required fields:

   • Repository URL: Specify the URL of the repository where the data product descriptor is stored.
   • Descriptor File Path: Provide the path to the descriptor file inside the repository (e.g., src/descriptor.json).
   • Repository Branch: Enter the branch name (e.g., main or master) where the descriptor resides. This is optional if a tag is specified.
   • Repository Tag: Specify the exact tag of the repository that contains the descriptor. This ensures precise versioning.

4. Click Publish to initiate the publishing process. The system will fetch the descriptor from the specified repository and create a new version of the data product in the registry.

Using the repository option ensures that the descriptor remains consistent with the source control system, offering version traceability and seamless updates for collaborative workflows.