Skip to main content

Marketplace FAQ

How do I enable Marketplace in my instance?

  • Request the data.world support team to turn it on for the catalog and organization you would like to add Marketplace functionality to.

How do I access the Marketplace?

  • Access it via the New Navigation experience once enabled. Use https://[your-subdomain].data.world/switch-layout to opt into the new experience.

How is the Marketplace organized?

  • Marketplace is organized around Domains, which appear as a hierarchical structure. It showcases Data Products curated within these Domains. Search-based sections can be added to the homepage as visual filmstrips for discoverability.

What is a Domain and what are the requirements for Marketplace?

  • A Domain is a logical grouping of related data aligned with a business area or function. Technically, Domains are collections of tyye dwec:Domain or a subclass of it. All Domains appear in the Marketplace by default if their type matches the requirement.

How do I create a Domain?

  • Create a Collection of type dwec:Domain (or a subclass). Ensure the collection is properly authored and curated in the Catalog. Once created, it appears automatically in the Marketplace hierarchy.

What is a Data Product and what are the requirements for Marketplace?

  • A Data Product is a catalog resource of type kos-data-product:DataProduct. It can be customized in CTK. For it show in the marketplace, it must meet the following requirements:

    • Must be instantiable.

    • Must include: Cover Image field.

    • Marketplace Status field (set to Published to Marketplace to appear).

How do I create a Data Product?

  1. Create a new resource of type kos-data-product:DataProduct.

  2. Set it as instantiable in CTK.

  3. Author and enrich the Data Product in Catalog.

Can I put other things in my Marketplace that are not Data Products?

  • Yes, but they must:

    • Have the Marketplace Status and Cover Image fields.

    • Be of a type explicitly annotated with these fields in the metadata.

What should I do if I already have a custom collection type I am using as Domains?

  • Using CTK, make your custom type is a subclass of dwec:Domain.

What should I do if I already have a custom type I am using as a Data Product?

  • Yes, but they must:

    • Have the Marketplace Status and Cover Image fields.

    • Be of a type explicitly annotated with these fields in the metadata.

How do I publish a Data Product to the Marketplace?

  • Set the Marketplace Status field to Published to Marketplace. Ensure the resource is accessible in the Catalog (Marketplace mirrors Catalog permissions).

How do I add a cover image for my Data Product?

  • Use the Cover Image field, available by default in the Data Product profile. Add a visual image to improve visibility in discovery experiences.

Can I customize the fields on a Data Product?

  • Yes, via CTK. You can extend the profile to add custom selection fields and Make fields mandatory (which enables inline editing).

Can I control which users see Catalog vs Marketplace?

  • There is no separate control. Marketplace inherits Catalog permissions. If a user cannot see a resource in Catalog, they won’t see it in Marketplace either.

How do I customize the Marketplace home page?

  1. Perform a search in the Marketplace.

  2. Click Save as section.

  3. Provide a title and click Add section.

  4. This adds a custom film strip to the Marketplace homepage for all users.

When will Marketplace be available for end users?

  • Estimated Release date is September 2025. (Subject to change based on development timelines and release planning.)

In this section: