So, as part of our efforts to be a bit more FAIR and given that we are currently forwarding data to other Standard platforms (see https://citiobs.demo.secure-dimensions.de/staplus/v1.1), I suggest an enhancement to our Measurements and Sensors model to contain additional information, that would make our platform more traceable and more "interoperable".
Add three fields: datasheet, encoding and unit_definition:
datasheet (str): will contain a link to a datasheet, either on docs.smartcitizen.me or storage.smartcitizen.me containing the sensor datasheet
~- encoding (str) - (this one I am not totally sold on) will contain the encoding type, such as: application/pdf~
timcowlishaw
commented
2 weeks ago
So, as part of our efforts to be a bit more FAIR and given that we are currently forwarding data to other Standard platforms (see https://citiobs.demo.secure-dimensions.de/staplus/v1.1), I suggest an enhancement to our
MeasurementsandSensorsmodel to contain additional information, that would make our platform more traceable and more "interoperable".Measurements
Add
definitionfield, with typestr, to contain a link to a standard vocabulary definition for the measured property, such as: https://vocabs.lter-europe.net/envthes/en/page/?uri=http://vocabs.lter-europe.net/EnvThes/21579Sensors
Add three fields:
datasheet,encodingandunit_definition:datasheet(str): will contain a link to a datasheet, either on docs.smartcitizen.me or storage.smartcitizen.me containing the sensor datasheet ~-encoding(str) - (this one I am not totally sold on) will contain the encoding type, such as:application/pdf~unit_definition(str) - would include a link to another vocabulary with units definition such as: https://qudt.org/vocab/unit/PERCENT~These properties should be subject to CRUD operations by
adminrole only once we work on: https://github.com/fablabbcn/smartcitizen-api/issues/229~