Use a toast or email notification when the file is ready. 📋 Data Export Structure (Example) Venue Name Change Date Original Type Updated Type Modified By Central Park 2024-05-12 Recreational Protected Zone Admin_User_01 2024-05-14 Industrial Residential Planning_Dept
To develop a (Изменение типов участка) download feature, you need a robust pipeline that handles data extraction, file generation, and user notification. 🛠️ Core Functional Requirements Use a toast or email notification when the file is ready
POST /api/v1/venues/changes/export : Trigger the file generation. Allow users to filter changes by date, venue
Allow users to filter changes by date, venue category, or specific location. Format Options: Support CSV, XLSX, and PDF exports. old_type_id : The category before the change
Ensure your logs table captures the essential transformation data: venue_id : Reference to the location. old_type_id : The category before the change. new_type_id : The category after the change. changed_by : User ID of the editor. timestamp : When the change occurred. 2. Backend Logic (Pseudo-code)
GET /api/v1/venues/changes/export/{job_id} : Check status of large exports. 🎨 User Interface Elements
To help me refine this feature for your specific system, could you tell me: