Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agent that syncs pods and Google Sheets #120

Closed
pheyvaer opened this issue Jul 11, 2023 · 2 comments
Closed

Agent that syncs pods and Google Sheets #120

pheyvaer opened this issue Jul 11, 2023 · 2 comments
Labels
challenge technical problem applied to a use case completion: approved ✅ ongoing The challenge is actively being tackled. proposal: approved ✅ report: done ✅ The report of the complated challenge/scenario is done.

Comments

@pheyvaer
Copy link
Contributor

pheyvaer commented Jul 11, 2023

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

  1. There exists a public resource on the user's pod that they want to sync.
  2. The user opens a new Google Sheet.
  3. 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.
  4. The user starts the server application.
  5. The Google Sheets is initially filled with the data from the resource.
  6. The user updates a field in the Google Sheets.
  7. The application writes the changes to the resource.
  8. The user manually checks the resource and sees the changes.

We tackle the following in challenge #123:

  1. Steps 1 - 8 of above.
  2. The user updates the resource via another app or manually.
  3. The application updates the Google Sheet.

Pointers

Scenarios

@pheyvaer pheyvaer added challenge technical problem applied to a use case proposal: pending ❓ labels Jul 11, 2023
@pheyvaer pheyvaer added proposal: approved ✅ ongoing The challenge is actively being tackled. and removed proposal: pending ❓ labels Aug 2, 2023
@pheyvaer pheyvaer assigned pheyvaer and unassigned bjdmeest Aug 2, 2023
pheyvaer added a commit that referenced this issue Aug 7, 2023
@pheyvaer pheyvaer assigned bjdmeest and unassigned pheyvaer Aug 7, 2023
@pheyvaer
Copy link
Contributor Author

pheyvaer commented Aug 7, 2023

@bjdmeest Everything for this challenge is done. I included all requirements for completion directly in the corresponding PR #121 for the report. Can you have a look at that? Thanks!

pheyvaer added a commit that referenced this issue Aug 21, 2023
* Add report for challenge #120

* Add screencast

* Use v1.0.0 link for agent

* Clone v1.0.0

* Fix formatting

* Update README

* Fixing comments Ben

* Fix remarks Ben
@pheyvaer
Copy link
Contributor Author

You find the report for this challenge here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
challenge technical problem applied to a use case completion: approved ✅ ongoing The challenge is actively being tackled. proposal: approved ✅ report: done ✅ The report of the complated challenge/scenario is done.
Projects
None yet
Development

No branches or pull requests

2 participants