DAQ smart devices: API to automate publishing of live data collected on my research experiments
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
integrate it into my own DAQ smart devices, to automate publishing of live data collected from my research experiments
My open project related to this request can be found here
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
API, Depositor
What inspired the request?
I'm part of open source community since ...forever. And currently, i have here on Github more than 20 PCB designs for smart devices.
What existing behavior do you want changed?
Any brand new behavior do you want to add to Dataverse?
What i liked more above all others was the fact of providing a unique number fingerprint UNF plus a DOI web address link. However is not enough for me as i work a lot with LIVE data acquisition. Is there any API for me to use, so I can integrate it into my own DAQ smart devices, to automate publishing of live data collected from my research experiments ?
Currently only file uploads are allowed.
It would be great to upload:
- one line of CSV data records to append on a existing CSV file (no database, standard file).
- Alternatively upload a data record to a SQLite database file hosted on the repository.
This request was initially published here:
https://www.linkedin.com/posts/migueltomas_harvard-dataverse-platform-activity-6971002717045407745--Dn6?utm_source=share&utm_medium=member_desktop
Any related open or closed issues to this feature request?
no
final note:
i'm available to provide my smart DAQ devices programmed with dataverse API for live data uploading to a dataverse repository
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing Dataverse API and upload behavior, then clarify whether appending CSV records or writing to hosted SQLite files is supported and define the publishing, versioning, and completion requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sqlite
- Domain
- api, data, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100