Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iterate on "Automatic After Upload" processing mode #863

Open
1 of 5 tasks
jeffpaul opened this issue Mar 7, 2025 · 0 comments
Open
1 of 5 tasks

Iterate on "Automatic After Upload" processing mode #863

jeffpaul opened this issue Mar 7, 2025 · 0 comments

Comments

@jeffpaul
Copy link
Member

jeffpaul commented Mar 7, 2025

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant