Draft a Listing

Title and Description

Great listing titles:

  • Start with company names for higher visibility.

    Example: "Company X – Consumer behavior data for the US"

  • Use commonly used terms, no abbreviations, no internal jargon​.

    Example: Spell out FCD as "floating car data" or "traffic" or "GPS probe" instead of simply labeling it as FCD in the title.

  • Are proofread and typo-free​.

  • Are self-explanatory and specific, free from vague and generic terms like "Location data".

Listing Description

Best listing descriptions:

  • Describe the offering from a customer standpoint and answer the question "Why would a customer purchase this data?"
  • Feature a clear and specific data type.

    Examples:

    • "Location data for your retail site planning" is a vague description.
    • "Real-time pedestrian traffic/footfall" is more precise.
  • Pertain to one data type only or related data types. Unrelated datasets should not be bundled into one listing.

    Examples:

    • For weather data and elevation, consider creating separate listings.
    • For closely related data types like weather data and wind speed or road attributes and road curvature, consider a catalog with multiple layers attached to one listing.
  • Specify data format and list key attributes.

  • Provide numbers or metrics that match those in the supporting material. If such numbers change, they may need to be reviewed on a regular basis.

    Examples:

    • Data points collected per minute.
    • Number of monthly active users per day/week/month.
  • Indicate geographical coverage, especially if the catalog only contains a small sample and the map in the listing displays only a fraction of the real coverage.

    Examples:

    • For a geo coverage with less than 10-15 countries, write a paragraph listing those: "Geographical coverage: Italy, Spain, Australia".
    • For an extensive geo coverage (15+ countries), make sure to check all necessary countries when creating a catalog (see Create Data Catalogs). The map in the listing will reflect your selection. Furthermore, you can create a separate Excel sheet/PDF file to upload in the Resources section or include a list into a data spec.
  • Indicate data freshness and update frequency.

  • Describe data collection mechanisms.

    Example: Data is collected from proprietary IoT sensors as well as state authorities.

  • Briefly introduce the company.

    Example: 2-3 sentences "About Us" following the data description.

  • Contain terminology commonly used in the industry and keywords, no abbreviations, no internal jargon.

    Example: "Probe", "traffic", "mobility" for GPS data points.

  • Are proofread and typo-free.

Suggested Use

The Suggested Use section typically:

  • Describes possible use cases based on the previous provider experience or expected/desired interaction with customers.

  • Is specific and emotionally neutral.

    Example: "Retail location planning" is a better choice than "Choose the best location for your next store with our data!"

References

The References section typically:

  • Offers a valid URL to the company homepage.
  • Offers a product-specific URL.

results matching ""

    No results matching ""