OpenFn / OpenFn/apollo

vocab-mapper: feedback, ideas, next steps

Open
#164 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
5
Forks
10
Avg merge
2d 20h
Merged PRs (30d)
17

Description

Randomish thoughts:

  • we need to save the sheets extension to a repo here on github, and work out how to publish it outside of Sheets
  • work out how to add more logging so we can see more stuff from the workflow view. I think this means a) log more frequently in apollo itself, and b) work out how to get log line into the job
  • work how to feedback errors into the sheet
  • Instantly update the sheet columns with "loading..."
  • Add a streaming mode, which processes terms one a time and emits them through a websocket to the caller. This lets us update the sheet in realtime Kind hard but very achievable.
  • Run faster: it currently take 3 minute to process results. Does this matter? Can we easily speed it up? What about streaming mode? https://github.com/OpenFn/apollo/issues/165
  • When we're done, show a toaster saying "we've finished!" in the sheet
  • Is there any way we can poll apollo to get a progress update for the job?
  • how can we limit calls, so that if the workflow is running for that sheet, we return an error? oh, collections!
  • Can users paste their own target values? We'd have to process and embed them. When do we remove them? Should we cache?
  • How do users control target data sets?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by splitting these ideas into separately scoped issues with an identified code area and acceptance criteria; each item is done only when its specific behavior and validation are defined.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.