Feat: Add "Configure Tagging" Button to AI Tagging Page

[Cubix33]

Describe the feature

🌟 Feature Description

I propose adding a "Configure Tagging" (or "Manage Folders") button to the header of the AI Tagging page.

Currently, the AI Tagging page displays recognized faces and tagged images, but it lacks any controls to actually enable or configure the tagging process. Users must currently navigate away to the Settings page and find the Folder Management section to toggle AI tagging for their folders.

This feature would add a direct link from the AI Tagging page to the Settings configuration, bridging the gap between viewing results and managing the source.

🔍 Problem Statement

The current workflow disconnects the "output" (tagged images) from the "input" (tagging configuration):

1. User Context: The user is on the AI Tagging page.
2. The Friction: If a user notices a folder is missing or wants to enable tagging for a new directory, there is no button to do so.
3. The Workaround: The user must manually navigate to Settings -> Folder Management.

This lack of navigation makes the AI tagging feature feel static and harder to configure for new users.

🎯 Expected Outcome

1. UI Update: A new button is added to the top header of AITagging.tsx, aligned with the page title.
2. Label: "Configure" or "Manage Folders".
3. Action: Clicking the button redirects the user to the /settings route.
4. Design: The button should use the existing design system (Button component) and a relevant icon (e.g., Settings or FolderCog from lucide-react).

📷 Screenshots and Design Ideas

Current State (No Configuration Option to navigate to Settings where AI Tagging can be enabled)

Target Destination (Settings Page)

Proposed Implementation

We can modify the header section of src/pages/AITagging.tsx to include the navigation button.
Mockup:

// src/pages/AITagging.tsx

import { useNavigate } from 'react-router'; //
import { Settings } from 'lucide-react';
import { Button } from '@/components/ui/button';

export const AITagging = () => {
  const navigate = useNavigate(); 

  return (
    <div className="relative flex h-full flex-col pr-6">
      <div className="mt-6 mb-6 flex items-center justify-between"> {/* Flex container for alignment */}
        <h1 className="text-2xl font-bold">AI Tagging</h1>
        
        {/* New Configuration Button */}
        <Button 
          variant="outline" 
          size="sm" 
          onClick={() => navigate('/settings')}
          className="gap-2"
        >
          <Settings className="h-4 w-4" />
          Configure Tagging
        </Button>
      </div>

      {/* ... rest of the component ... */}

Record

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

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[AnubhavKiroula]

Hi! I'd like to work on this issue as part of my GSoC preparation. The feature makes sense and I’d be happy to implement the “Configure Tagging” button on the AI Tagging page using the existing design system and routing logic.

Please assign this to me. Thanks!

[MohitHaibatpure]

I have implemented the “Configure Tagging” button.
The button appears in the page header and redirects users to /settings, allowing quick access to Folder Management for managing AI Tagging folders.
Uses existing Button component + lucide-react Settings icon.
Thank you.

[rahulharpal1603]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

@MohitHaibatpure Read this :)

[Kalpana-chavhan]

Hello @rahulharpal1603 , If opening or raising pr is not allowed untill you review the issue then does that mean we can only raise a certain issue, fix it locally, wait for u to review the issue and response?? can u elaborate a little bit more on this topic? (note: dont mind, i am new to contributing and wants to contribute to aossie )

[rahulharpal1603]

Hello @rahulharpal1603 , If opening or raising pr is not allowed untill you review the issue then does that mean we can only raise a certain issue, fix it locally, wait for u to review the issue and response?? can u elaborate a little bit more on this topic? (note: dont mind, i am new to contributing and wants to contribute to aossie )

No, do not start the work locally also. If the issue you have opened is not valid, you would be wasting your time.

[Cubix33]

@rahulharpal1603 sir please go through this feature and let me know if i should start working on it