Restructure datastore #257
Description
Context
Currently, fertiscan-backend depends on a shared ailab-datastore repository that holds common and project-specific data access logic. Over time, the separation of responsibilities has become unclear, causing confusion and complicating development.
Desired Outcomes
- Move fertiscan's datastore logic into the fertiscan-backend.
- Remove fertiscan's datastore logic from ailab-datastore.
- Keep only truly common utilities in ailab-datastore.