forked from istSOS/istSOS4
-
Notifications
You must be signed in to change notification settings - Fork 0
Week 06 Report
Vishmayraj Zala edited this page Aug 19, 2026
·
1 revision
I performed the following tasks during week 6:
Network-as-subcatalog architecture (completed)
- Completed the network-based architecture across the harvesting and caching layers.
harvester.pynow exposes two separate harvest queries, one for the with-network path and one for the without-network path, so deployments that don't use theNetworkentity aren't forced through unnecessary grouping logic. - Implemented
build_stac_catalog_with_networksalong with its supporting helper functions, producing a STAC catalog structure where each network is exposed as its own subcatalog rather than everything being flattened into a single top-level catalog. - Added a dedicated per-network caching path in
cache.pyso network-scoped catalogs are written and invalidated independently of the base catalog. - Updated
scheduler.pyto call the new network-aware functions instead of the old flat harvest path. - Fixed a crash in
_item_nav_linkscaused by hardcoded orphan-collection paths left over from before the network architecture existed, the function hadn't been updated to account for the new subcatalog structure and was producing broken navigation links for items outside any network. - With this, the network architecture itself is functionally complete. What remained was validating it end-to-end through the testing infrastructure.
Testing
- Moved into setting up the testing planned for this week, which requires a reproducible local test database. This surfaced a persistent environment/schema issue in the dummy-data generation path (
generator.py) that blocked verification of the completed architecture above. - Attempts so far touched the TimescaleDB/PostGIS extension setup,
.envdefaults, and the delete-user flow, without a confirmed fix by end of week. This is a blocker on testing, not on the architecture work itself, which stands complete.
Time away from the project
- Took a personal trip from July 3-5, which further narrowed the window to resolve the testing blocker this week.
Details can be found in:
- Network architecture:
api/app/v1/connector/harvester.py,stac_transformer.py,cache.py,scheduler.py - In-progress fix attempts:
api/app/v1/connector/generator.py,.env
What do I plan to do next week?
- Continue investigating the dummy-data/testing infrastructure issue. If it remains unresolved after another push, I'll flag it to my mentors directly rather than continuing to lose time on it solo.
- GSoC midterm evaluations run July 6-10 this period.
Am I blocked on anything?
- The network-as-subcatalog architecture is complete and not blocked.
- Testing/verification of that architecture is blocked on an unresolved dummy-data generation bug. Root cause not yet confirmed as of end of week 6.