You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: switch registry storage to DynamoDB via Dyntastic, add local fallback
- Add dyntastic
- Update `Meeting` model to inherit from Dyntastic
- Introduce `create_tables.py` for Dyntastic table creation
- Refactor meeting registry read/write logic to use Dyntastic with DynamoDB
- Add `src/local_store.py` for local JSON fallback when AWS is not configured
- Clarify and expand README with Prefect workflows and registry diagram
We use prefect to organize code into workflows of data tasks.
38
+
37
39
See https://docs.prefect.io/get-started
38
40
39
41
```bash
@@ -42,6 +44,42 @@ prefect server start # to start the persistent server
42
44
python -m flows.translate_meetings # to run a specific flow
43
45
```
44
46
47
+
#### Data "registry" for workflows
48
+
The prefect workflows use a "registry" to track meetings and urls to their data artifacts.
49
+
E.g., `get_new_meetings` task adds each meeting to the registry with a `video_url`, `transcribe_videos` transcribes the video and adds `transcription_url`, etc.
0 commit comments