Notes List
Feature Detail
Description
The Notes List feature provides peer mentors and coordinators with a personal notes interface where they can view, search, and manage all notes they have recorded. Notes are linked to contacts or activities, giving users a contextual overview of follow-up items, observations, and reminders tied to their work. The list supports offline access via the Drift local database, ensuring notes are available without a network connection and synced automatically when connectivity is restored. The interface is WCAG 2.2 AA compliant with sufficient contrast, touch targets, and screen reader labels throughout.
Sources & reasoning
Line 163 places Notater as NICE priority in Phase 2 (maps to v1.0), confirmed by all five organizations. Line 162 ties notes to basic search (Phase 1 MUST), making the list a natural Phase 2 complement. The area taxonomy at line 465 canonically names this feature Notes List. Target v1.0 derived from Phase 2 matrix position.
-
docs/source/likeperson.md · line 163| Notater | ✓ | ✓ | ✓ | ✓ | ✓ | NICE | 2 |
-
docs/source/likeperson.md · line 162| Basic search (contact og notater) | ✓ | ✓ | ✓ | ✓ | ✓ | MUST | 1 |
-
docs/source/likeperson.md · line 465| notes | Notes | Notes List, Note Editor |
Analysis
Notes are a universal tool used by peer mentors across all five organizations (NHF, Blindeforbundet, HLF, Barnekreftforeningen, Norse Test) - confirmed NICE priority in the Phase 2 needs matrix. A structured notes list reduces reliance on informal channels (paper, phone memos) and gives coordinators and peer mentors a single, searchable place to track follow-up items tied to contacts and activities. The integration with basic search (MUST HAVE, Phase 1) means notes become part of the searchable corpus, directly supporting audit trails and Bufdir data quality. Capturing contextual observations digitally also improves handover quality when peer mentors change assignment.
Built as a Flutter screen backed by Drift for offline-first storage. NoteRepository handles CRUD against the local DB and the REST API sync queue. The list view renders notes sorted by updated_at descending, with optional filtering by linked contact or activity. Search is delegated to the shared contact/notes search infrastructure introduced in Phase 1. Pagination uses cursor-based loading to keep memory footprint low on older devices. All list items include semantic labels for VoiceOver/TalkBack compliance. The notes table (notes, contact_notes) is already defined in the data model, so no schema migration is required at feature introduction.
Components (8)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.