Bulk Registration Defaults Provider
Component Detail
Description
Riverpod provider that computes and caches default values for bulk registration (current date, most recently used activity type) and persists coordinator preferences between sessions.
bulk-registration-defaults-provider
Summaries
The Bulk Registration Defaults Provider significantly improves coordinator efficiency by remembering their most recently used activity type and automatically pre-filling the current date when opening bulk registration sessions. This eliminates repetitive manual data entry across high-volume registration workflows, reducing human error and saving coordinators measurable time per session. Over weeks of operation, this translates into fewer incorrect submissions, reduced correction overhead, and a smoother coordinator experience — directly supporting operational throughput and data quality without requiring additional system infrastructure.
This is a low-complexity, self-contained Riverpod provider with no declared external dependencies, making it straightforward to develop and test in isolation. The primary delivery risk is ensuring that local preference persistence behaves correctly across app restarts and that override values do not bleed between registration sessions. Testing should cover the default computation at session start, preference recall after app close and reopen, and reset behavior. Since it is scoped to the bulk registration feature only (not shared), its blast radius on other features is zero — which simplifies regression testing and makes it a low-risk, high-value delivery item.
Implemented as a Riverpod provider exposing `getBulkDefaults()`, `overrideDate(DateTime)`, `overrideActivityType(String)`, `persistDefaults(BulkRegistrationDefaults)`, and `resetToSystemDefaults()`. Default date is computed at session initialization as `DateTime.now()`. The last-used activity type is read from local preferences storage (e.g., SharedPreferences) and surfaced via `getBulkDefaults()`. Override methods update in-memory state and are committed to persistent storage on successful form submission via `persistDefaults()`.
The `resetToSystemDefaults()` clears overrides and re-derives values from system state. No data model dependencies — pure preference and state management. Lifecycle should be tied to the bulk registration screen's widget scope to avoid stale state.
Responsibilities
- Compute default date as today's date at session start
- Recall the last-used activity type from local preferences
- Expose overridable defaults to the bulk registration screen
- Persist updated defaults after successful submission
Interfaces
getBulkDefaults()
overrideDate(DateTime date)
overrideActivityType(String activityTypeId)
persistDefaults(BulkRegistrationDefaults defaults)
resetToSystemDefaults()