-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
challengetechnical problem applied to a use casetechnical problem applied to a use casecompletion: approved ✅ongoingThe challenge is actively being tackled.The challenge is actively being tackled.proposal: approved ✅report: done ✅The report of the complated challenge/scenario is done.The report of the complated challenge/scenario is done.
Description
Pitch
A lot of users use Google Sheets to view and edit data. This data can be stored in Google Sheets itself or it can be coming from an external data source such as a MySQL database or MongoDB. So far, there is no solution that exists that allows doing this with data in Solid pods. This challenge focuses on the agent/backend part of a solution for this problem.
Desired solution
The solution is a server application that
- Reads data from a Solid pod and updates a Google Sheet.
- Reads data from a Google Sheets and updates the data in a Solid pod.
- Allows users to configure it via a YAML file.
For this challenge, we only consider public resources on a pod and public Google Sheets.
Acceptance criteria
- There exists a public resource on the user's pod that they want to sync.
- The user opens a new Google Sheet.
- The user updates the config file with
- Info about the Google Sheet.
- Info about the pod resource.
- SPARQL query that determines what data is selected from the resource and shown in a table.
- The user starts the server application.
- The Google Sheets is initially filled with the data from the resource.
- The user updates a field in the Google Sheets.
- The application writes the changes to the resource.
- The user manually checks the resource and sees the changes.
We tackle the following in challenge #123:
- Steps 1 - 8 of above.
- The user updates the resource via another app or manually.
- The application updates the Google Sheet.
Pointers
- Google Sheets API
- Google API Node.js Client
- Solid Agent
- Comunica to query pods.
Scenarios
Metadata
Metadata
Assignees
Labels
challengetechnical problem applied to a use casetechnical problem applied to a use casecompletion: approved ✅ongoingThe challenge is actively being tackled.The challenge is actively being tackled.proposal: approved ✅report: done ✅The report of the complated challenge/scenario is done.The report of the complated challenge/scenario is done.