feat: Remove legacy files and fix first svelte/no-at-html-tags error\n\n- Moved legacy files from src/routes/legacy to backups/legacy/src/routes/legacy.\n- Removed the empty src/routes/legacy directory.\n- Fixed a svelte/no-at-html-tags error in src/routes/idaa/(idaa)/archives/[archive_id]/+page.svelte by replacing '{@html ?.name ?? 'Archive'}' with '{?.name ?? 'Archive'}'.\n- Addressed a misidentified '{@html}' tag in src/lib/ae_core/ae_comp__hosted_files_clip_video.svelte by removing commented-out code that might have caused false positives.
This commit is contained in:
@@ -1,9 +1,11 @@
|
||||
# Aether (AE) Event Lead Retrieval Module (v3)
|
||||
|
||||
## Overview
|
||||
|
||||
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
|
||||
|
||||
- **Exhibitor Login:** Secure access for exhibitors using a shared passcode or individual license keys (email-based).
|
||||
- **Lead Capture:** Efficiently add new leads by scanning attendee badge QR codes or through manual data entry.
|
||||
- **Lead Management:** A dedicated interface for exhibitors to view, sort, and manage their collected leads.
|
||||
@@ -17,7 +19,9 @@ This module provides a comprehensive solution for event exhibitors to capture an
|
||||
The core data structures managed by this module are `Exhibit` and `Exhibit_tracking`.
|
||||
|
||||
### Exhibit
|
||||
|
||||
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).
|
||||
- `code`, `name`, `description`: Basic information about the exhibit.
|
||||
- `staff_passcode`: For staff login.
|
||||
@@ -26,7 +30,9 @@ Represents an exhibitor's presence at an event. It contains configuration for le
|
||||
- `license_max`, `license_li_json`: Details regarding lead retrieval licenses.
|
||||
|
||||
### Exhibit_tracking
|
||||
|
||||
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.
|
||||
@@ -37,6 +43,7 @@ Represents a single lead captured by an exhibitor. It links an exhibitor to an a
|
||||
## Routing and Components
|
||||
|
||||
### Routes
|
||||
|
||||
- `/events/[event_id]/(leads)`: The main entry point for the Leads module within a specific event, typically displays a list of available exhibits.
|
||||
- `+page.svelte`: Renders the list of exhibits.
|
||||
- `+page.ts`: Loads the data for available exhibits using `events_func.handle_load_ae_obj_li__exhibit`.
|
||||
@@ -46,6 +53,7 @@ Represents a single lead captured by an exhibitor. It links an exhibitor to an a
|
||||
- `+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`.
|
||||
|
||||
### Core Components (within `src/routes/events/[event_id]/(leads)/exhibit/[slug]/`)
|
||||
|
||||
- `leads_add_scan.svelte`: Handles the process of adding new leads, either by scanning QR codes (badge) or manual entry.
|
||||
- `leads_list.svelte`: Displays a sortable and filterable list of captured leads for the current exhibitor.
|
||||
- `leads_manage.svelte`: Provides functionalities for managing individual leads, potentially including editing notes or qualification status.
|
||||
|
||||
Reference in New Issue
Block a user