Open aeonSolutions opened 1 year ago
Sounds fine, as long it's generic enough. Lemme know if you'd like to join a community call and talk about it! https://dataverse.org/community-calls
The smart data acquisition devices (S.D.A.D.) I've been prototyping have onboard, built into it, a security IC with a unique 72bit serial number. This means any S.D.A.D. can be programmed to identify itself on a #dataverse repository when doing experimental data exchange .
Overview of the Feature Request I'm prototyping a smart data acquisition device with the main functionality to update collected experimental data directly to a data repository, a dataverse. LIVE. This enables remote teams of researchers to access the most recent and up-to-date experimental data directly into any Excel workbook or Python script for machine learning modeling. The current status of the programming of the firmware already includes a Geo Location Unique Fingerprint ID and also an experimental data record fingerprint ID. And to me, it makes sense, the ability of a dataverse to be able to receive and store a record of authorized DAQ devices running on a particular experimental campaign. The current hardware specifications already have a unique device serial number that can be sent to a dataverse. Currently, the only possibility to do it is to store that information in a file, meaning anyone looking to audit and verify running DAQ devices needs to have some programming skills ....
What kind of user is the feature intended for? (Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin) All
What inspired the request? Current prototype development of my own smart DAQ . More info here
What existing behavior do you want changed? no change. only add new.
Any brand new behavior do you want to add to Dataverse? Yes. A simple green/red/yellow status of DAQ devices connected to a particular dataverse / dataset.
Any open or closed issues related to this feature request? not that I'm aware of .