OptionalassetsOptionalcollectionThe ending date timestamp for when the data spans
OptionalcollectionThe starting date timestamp for when the data spans
OptionalcollectionSmallest unit of time in the dataset
OptionalcostWhether the dataset is free or paid
OptionaldataWhere/how the data is sourced
OptionaldescriptionOptionaldocumentationOptionalembeddedOptionalfileOptionalgeographicalWhich geo region the listing data is collected from
OptionallicenseID 20, 21 removed don't use License of the data asset - Required for listings with model based assets
OptionalpricingWhat the pricing model is (e.g. paid, subscription, paid upfront); should only be present if cost is paid
OptionalprivacyOptionalsizesize of the dataset in GB
OptionalsupportOptionaltagsListing tags - Simple key value pair to annotate listings. When should I use tags vs dedicated fields? Using tags avoids the need to add new columns in the database for new annotations. However, this should be used sparingly since tags are stored as key value pair. Use tags only:
OptionaltermsOptionalupdateHow often data is updated
Type of assets included in the listing. eg. GIT_REPO, DATA_TABLE, MODEL, NOTEBOOK