Mar 18

To Resolve NotebookLM / Kortex Sorting Crash & Implement "Sort By Date Created"

1. Problem Statement Since integrating Kortex with NotebookLM, the notebook directory is experiencing severe sorting failures and system crashes. The native "Most Recent" filter in NotebookLM is completely non-functional. Notebooks are visually mixed up, and relying on alphabetical sorting is the only current workaround. The interference between Kortex's synced data and NotebookLM's native data is causing fatal errors.2. Current BehaviorSelecting the "Most Recent" filter fails to organize notebooks and triggers an app crash.NotebookLM and Kortex metadata are colliding; the systems are not properly isolated.Users are forced to use alphabetical sorting, which is inefficient for timeline-based knowledge management.3. Expected BehaviorSystem Isolation: Kortex integration should act as a parallel data source. It must not interfere with or break NotebookLM’s native sorting mechanisms.Graceful Degradation: If Kortex passes malformed or missing date metadata, the app should not crash. It should default the affected notebook to the bottom of the list or use a fallback date.Expanded Sorting UI: Users must be able to explicitly toggle sorting by:Alphabetical (A-Z, Z-A)Date Created (Newest First, Oldest First)Date Modified / Most Recent (Newest First, Oldest First)4. Proposed Technical FixesMetadata Normalization: Implement a data-parsing middleware between Kortex and NotebookLM. Ensure all incoming Kortex timestamps are strictly converted to NotebookLM’s expected format (e.g., ISO 8601 standard) before hitting the UI layer.Null-Safe Sorting: Update the sorting arrays to include standard error handling (e.g., optional chaining or Try/Catch blocks). If notebook.createdAt is null or undefined due to the Kortex sync, handle it gracefully without throwing a fatal error.Database Schema Update: Ensure DateCreated is a locked, immutable field at the moment of notebook generation, completely separate from LastModified (which Kortex might be constantly pinging/updating during syncs).
CompletedCompleted

Completed
changed status toCompleted·Mar 30, 2026
Planned
changed status toPlanned·Mar 19, 2026
Progress
changed status toIn Progress·Mar 19, 2026