How vickyapril02/girder-redcap-mimic-sync works
This POC accepts patient metadata and files through a REDCap-style interface, organizes them by center, patient, visit, and document type, and uploads them to Girder. Its mimic workflow can save files locally for later synchronization; a separate schema-creation utility provisions the matching Girder folders. SQLite holds the hierarchy, file records, sync state, and folder IDs. The excerpts show the principal calls, but not every route implementation or the full HTML behavior, so those links are limited to documented or visible relationships.
Main entry points: app.py FastAPI Routes · girder_client.py Girder Client · database.py Study Catalog · create_girder_schema.py Folder Provisioning
Components 11
Data Capture
- FastAPI Routes
app.py - Mimic Interface
redcap_mimic.html - Patient Model
models.py - Local Uploads
app.py
Study Catalog
- Study Catalog
database.py - Folder Provisioning
scripts/create_girder_schema.py
Girder Sync
- Batch Sync
sync/extract_sync.py - Girder Client
girder_client.py
Other components
- REDCap
- Web User
- Girder Storage
Connections 13
- Web User → Mimic Interface: uses
README.md - Web User → FastAPI Routes: uploads
README.md - REDCap → FastAPI Routes: webhook posts
app.py - FastAPI Routes → Mimic Interface: serves
app.py - FastAPI Routes → Patient Model: validates
app.py - FastAPI Routes → Study Catalog: reads and writes
app.py - FastAPI Routes → Local Uploads: saves uploads
README.md - FastAPI Routes → Girder Client: uploads directly
app.py - Folder Provisioning → Study Catalog: reads structure; stores IDs
scripts/create_girder_schema.py - Folder Provisioning → Girder Client: creates folders
scripts/create_girder_schema.py - Batch Sync → Study Catalog: reads files; marks synced
sync/extract_sync.py - Batch Sync → Girder Client: validates and uploads
sync/extract_sync.py - Girder Client → Girder Storage: calls API
girder_client.py