Saving initial changes to the Leads v3 project files and directories.

src/routes/events/[event_id]/(leads)/README.md

@@ -2,6 +2,8 @@
 
 ## Overview
 
+This is a major work in progress. It still needs the overall directory and file structure planned, documented, and created.
+
 This module provides a comprehensive solution for event exhibitors to capture and manage leads. It supports exhibitor login, badge scanning for lead capture, manual lead entry, lead qualification (ranking/priority), and data export functionalities. It integrates with the Aether API for data synchronization and utilizes local caching for performance and offline capabilities.
 
 ## Key Features
@@ -22,7 +24,7 @@ The core data structures managed by this module are `Exhibit` and `Exhibit_track
 
 Represents an exhibitor's presence at an event. It contains configuration for lead retrieval, such as:
 
-- `event_exhibit_id_random`: Unique identifier for the exhibit (primary key).
+- `event_exhibit_id`: Unique identifier for the exhibit (primary key).
 - `code`, `name`, `description`: Basic information about the exhibit.
 - `staff_passcode`: For staff login.
 - `leads_api_access`: Boolean indicating if lead retrieval API access is enabled.
@@ -33,9 +35,9 @@ Represents an exhibitor's presence at an event. It contains configuration for le
 
 Represents a single lead captured by an exhibitor. It links an exhibitor to an attendee (badge) and stores details about the interaction:
 
-- `event_exhibit_tracking_id_random`: Unique identifier for the captured lead (primary key).
-- `event_exhibit_id_random`: Links to the `Exhibit` that captured the lead.
-- `event_badge_id_random`: Links to the attendee's `Badge` information.
+- `event_exhibit_tracking_id`: Unique identifier for the captured lead (primary key).
+- `event_exhibit_id`: Links to the `Exhibit` that captured the lead.
+- `event_badge_id`: Links to the attendee's `Badge` information.
 - `exhibitor_notes`: Notes added by the exhibitor about the lead.
 - `responses_json`: Responses to custom questions.
 - Contains duplicated badge information for convenience (e.g., `event_badge_full_name`, `event_badge_email`, `event_badge_professional_title`, `event_badge_affiliations`) to denormalize data for faster display.
@@ -48,7 +50,7 @@ Represents a single lead captured by an exhibitor. It links an exhibitor to an a
     - `+page.svelte`: Renders the list of exhibits.
     - `+page.ts`: Loads the data for available exhibits using `events_func.handle_load_ae_obj_li__exhibit`.
     - `+layout.svelte`/`+layout.ts`: Provides a common layout and data for the module, including a submenu.
-- `/events/[event_id]/(leads)/exhibit/[slug]`: Dynamic route for managing leads for a specific exhibitor within an event. The `[slug]` corresponds to `event_exhibit_id_random`.
+- `/events/[event_id]/(leads)/exhibit/[slug]`: Dynamic route for managing leads for a specific exhibitor within an event. The `[slug]` corresponds to `event_exhibit_id`.
     - `+page.svelte`: The primary interface for an exhibitor, orchestrating lead capture and management components.
     - `+page.ts`: Loads specific `Exhibit` data and associated `Exhibit_tracking` (leads) using `events_func.handle_load_ae_obj_id__exhibit` and `events_func.handle_load_ae_obj_li__exhibit_tracking`.
 
@@ -63,7 +65,7 @@ Represents a single lead captured by an exhibitor. It links an exhibitor to an a
 ## Technical Implementation
 
 - **Svelte v5 with Runes:** The module adheres to Svelte v5's reactivity model, utilizing `$state` and `$derived` for reactive state management.
-- **ID Convention (`id_random`):** All frontend operations, including routing and data fetching, consistently use the string-based `event_exhibit_id_random` and `event_exhibit_tracking_id_random` as primary identifiers, rather than numeric `id` values.
+- **ID Convention (`id`):** All frontend operations, including routing and data fetching, consistently use the string-based `event_exhibit_id` and `event_exhibit_tracking_id` as primary identifiers, rather than numeric `id` values.
 - **API Interaction:** Data is fetched and synchronized with the backend FastAPI application through functions exposed in `src/lib/ae_events_functions.ts`.
 - **Local Database (Dexie.js):** Data for `Exhibit` and `Exhibit_tracking` is cached in the browser's IndexedDB using Dexie.js, defined in `src/lib/ae_events/db_events.ts`. This ensures data persistence and fast retrieval, especially for offline scenarios.
 - **Styling:** The UI is primarily styled using Tailwind CSS, having migrated from Skeleton UI to resolve previous rendering issues.