Page MenuHome

Benchmarks should be Samples
Open, NormalPublic

Description

The Open Data platform aims at hosting more than benchmark results. For this reason we should look into introducing a more generic data structure, called 'sample'.

Sample schema on My Data

fieldtypedescription
idintthe PK
aidstrAlphanumeric representation of the PK
manage_tokenstrToken issued to the data owner to update/remove the data from Open Data
raw_datajsonThe sample as submitted by the client
date_createddatetimeSubmission date
is_redactedbool(to discuss - optionally specify which fields to redact?)
weightint(to discuss)
userintFK to the User
serieintFK to the Serie - e.g. benchmark, blender_org downloads, telemetry, etc

A similar schema could be adopted by Open Data

fieldtypedescription
idintthe PK
aidstrAlphanumeric representation of the PK
manage_tokenstrToken issued to the data owner to update/remove the data from Open Data
datajsonThe (redacted data) which should be indexed
date_createddatetimeSubmission date
weightint(to discuss)
seriestrThe Serie - e.g. benchmark, blender_org downloads, telemetry, etc

AlphaID vs UUID

While it would be fantastic to be able to reference a sample with a 6-chars alphanumeric string, which would be build starting from the My Data sample id, we understand that the Open Data portal will get data input from various sources. This issue can be solved by providing a 'serie' name with the sample.

Details

Type
Design