Feat: Bulk AI Tagging & Progress Tracking for Folder Management

[VasuS609]

Describe the feature

Issue Summary
The folder management interface requires manual interaction with each folder's AI tagging toggle, making it tedious to manage multiple folders. Additionally, there's no visual indication of tagging progress or smart sorting to prioritize folders needing attention.

Currently users must:

• Manually tap the AI tagging toggle for each individual folder
• Scroll through an unsorted list to find folders that need tagging
• Have no overview of how many folders are tagged vs. pending

This creates friction when managing 10+ folders and makes it difficult to track AI tagging progress across the document collection.

Proposed Solution
1. Bulk Control Buttons
Add action buttons at the top of the folder list:

"AI Tag All" - Enable AI tagging for all folders at once
"Select All" - Checkbox to select multiple folders for bulk actions
"Tag Selected" - Apply AI tagging to selected folders only

2. Smart Sorting by Status
Auto-organize folders into three priority sections:

• Completed (AI tagged) [Collapse/Expand]
• In Progress (tagging...) [Collapse/Expand]
• Pending (not yet tagged) [Collapse/Expand]

3. Progress Summary
Display summary stats at the top:
AI Tagging Progress: 7/15 folders tagged (47%)
Completed: 7 | In Progress: 2 | Pending: 6

Benefits

Efficiency: Tag all folders with one click instead of 10+ clicks
Visibility: Immediately see which folders need attention
Progress Tracking: Clear overview of completion status
Flexibility: Option for selective bulk tagging or individual control

Technical Considerations

• Maintain existing individual toggle functionality alongside bulk actions
• Preserve user preferences (folders manually excluded from AI tagging)
• Handle API rate limits gracefully if tagging many folders simultaneously
• Persist sorting preference across sessions
• Show real-time progress updates for in-progress tagging

Priority
High - Significantly improves UX for users managing multiple folders

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

Checklist before Submitting.

• Have you updated docs for it?.
• Have you added unit tests?.
• Have you made sure unit tests pass?
• Have you made sure code formatting is correct?
• Does it contain any style related issues?

[Jitmisra]

hi i want to work on this issue team name bigbull

[VasuS609]

Hi @rahulharpal1603

I wanted to clarify the contribution workflow for this issue.

I opened the issue about 20 hours ago and mentioned my intent to work on it.
Since then, I noticed that multiple PRs (#728, #755, and one by @parthraninga)
have been opened before any assignment was made.

Could you please confirm how this project usually handles such cases?

• Should contributors wait for explicit assignment before starting work?
• Or is it generally first-PR-wins?

I’m happy to follow whichever process the project prefers.
I’ve already started working on this and can deliver a complete solution
within 1–2 days if assigned.

[rahulharpal1603]

Hi @rahulharpal1603

I wanted to clarify the contribution workflow for this issue.

I opened the issue about 20 hours ago and mentioned my intent to work on it. Since then, I noticed that multiple PRs (#728, #755, and one by @parthraninga) have been opened before any assignment was made.

Could you please confirm how this project usually handles such cases?

• Should contributors wait for explicit assignment before starting work?
• Or is it generally first-PR-wins?

I’m happy to follow whichever process the project prefers. I’ve already started working on this and can deliver a complete solution within 1–2 days if assigned.

You are correct. If the contributor opening the issue intends to work on it, we give them first priority. I am closing rest of the PRs.

[VasuS609]

Hey @rahulharpal1603, I have already raised pr on this issue on pr #787
#787