Iterate on "Automatic After Upload" processing mode

オープン
#863 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
machine-learning, php

調査の方向性

まず、#862 の関連する作業と、既存の processing-mode 設定およびアップロードフローを確認します。Media Library と Edit Image の画面で処理状態がどのように表示されるかを整理し、実装前に提案されている UX と失敗処理の方針を決定します。合意済みのデザイン、バックグラウンド処理の動作、UI フィードバック、単一アップロードと一括アップロードの両方に対するカバレッジが揃えば完了です。

索引モデルが issue の本文から書いたものです。

説明

Is your enhancement related to a problem? Please describe.

Description

Building on the work in #862, we might consider introducing a new Processing Mode option:

  • "Automatic After Upload" (new) – Image uploads complete first, then processing occurs asynchronously.
  • "Automatic During Upload" (default, existing behavior) – Image processing happens in parallel with the upload process.

This new "Automatic After Upload" mode would allow for faster uploads by deferring AI processing until after the image is fully uploaded. However, this introduces potential UX challenges when users attempt to edit an image before processing is complete.

Considerations for UX/UI adjustments

1. Visibility of Ongoing Processing
  • If an image is still being processed, we should clearly indicate this in the Media Library and Edit Image screen.
  • Potential UI indicators:
    • Processing message (e.g., "AI processing in progress...")
    • Loading spinner or progress bar
    • Optionally disabling fields like Alt Text until processing is complete
2. Preventing Conflicts in Image Editing
  • If a user clicks into an image edit screen before processing completes, we should:
    • Display a notice about ongoing processing.
    • Prevent premature edits by temporarily disabling AI-generated fields (e.g., Alt Text, Description, Tags).
    • Possibly provide a refresh button once processing finishes.
3. Handling Edge Cases
  • Ensure that if a user uploads multiple images quickly, processing occurs in the correct order.
  • Determine how failures in async processing should be logged and surfaced to users.
  • Consider adding an optional admin notice or notification when processing completes for a batch of images.

Potential approach

  1. Update Processing Modes

    • Add "Automatic After Upload" as a new option in the settings.
    • Retain "Automatic During Upload" as the default behavior.
  2. Modify Image Processing Flow

    • Allow images to complete upload first, then queue for processing asynchronously.
    • Ensure processing runs in the background without blocking uploads.
  3. Improve User Feedback & UI Handling

    • Add a processing indicator in the Media Library & Edit Image screen.
    • Prevent editing AI-populated fields until processing is complete.
  4. Testing & QA

    • Validate behavior across single uploads, bulk uploads, and different media workflows.
    • Ensure compatibility with existing ClassifAI AI processing settings.

Action items

  • Confirm UI/UX direction for processing indicators and edit restrictions.
  • Implement background processing logic to handle "After Upload" mode efficiently.
  • Provide an admin setting for selecting between "Automatic After Upload" and "Automatic During Upload."
  • Test across various upload workflows and user interactions.
Designs

No response

Describe alternatives you've considered

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct
主要言語
PHP
スター
714
フォーク
68
平均マージ
4時間 32分
マージ済み PR(30日)
23

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

10up/classifai のほかの issue

10up/classifai の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。