Gallery Overview, Filters, and Categories

Summary

Gallery becomes unmanageable without filter and category discipline. This guide sets up scalable retrieval practices. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Find assets quickly in large libraries.
• Keep script media mapping clean.
• Reduce upload duplication.

Before you start

• Decide a simple category taxonomy.
• Align naming conventions across team.
• Check current uncategorized backlog.

Step-by-step workflow

1. Open /dashboard/gallery.
2. Use type filter (photo/video/audio/all).
3. Search by title or key terms.
4. Create or assign categories.
5. Review uncategorized assets and clean up.
6. Confirm assets are easy to locate for script builders.

Key states and error handling

• Selected categories alter API query scope.
• Uncategorized filter can be combined with category filtering logic.
• Search is text-based on title/key fields.

Best practices

• Use short descriptive titles.
• Avoid category explosion.
• Run weekly cleanup for uncategorized assets.

Troubleshooting

• If assets seem missing, reset filters and search terms.
• If category updates fail, retry with smaller selection.
• If list is stale, invalidate/refresh media query by reload.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Search and type filters control retrieval speed in large media libraries.
• Category selection changes query scope and can hide valid assets if misconfigured.
• Direct upload size limits differ by media type and must be respected.
• Audio pipeline only supports .ogg/.mp3 with strict size constraints.
• Telegram upload sessions are used for controlled constrained ingest paths.
• Batch limits exist for Telegram session uploads and require chunking.
• Bulk actions are powerful and must be validated before applying.
• Upload toasts classify most operational upload failures quickly.

Operator checklist (before shipping changes)

• Verify file formats and size before upload.
• Select correct bot for Telegram upload sessions.
• Upload in small controlled batches to reduce retries.
• Apply categories immediately after successful upload.
• Run periodic uncategorized cleanup to keep retrieval fast.
• Revalidate script media mappings after bulk maintenance.

Real-world scenario

A campaign upload fails minutes before launch. The operator splits files into compliant batches, converts invalid audio formats, runs a Telegram upload session for constrained files, and confirms all assets are visible before script activation.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.