Initial commit: enterprise digital platform with portal SSO, DigiServer, IT Assets, NetworkView, Server Monitor

2026-05-10 21:07:50 +03:00
commit 8d9df56b0b
364 changed files with 73655 additions and 0 deletions
@@ -0,0 +1,96 @@
+# Groups Feature - Archived
+
+**Status: ARCHIVED AND REMOVED ✅**
+
+**Archive Date:** January 17, 2026
+
+## What Was Done
+
+### 1. **Files Archived**
+- `/app/templates/groups/` → `/old_code_documentation/templates_groups/`
+- `/app/blueprints/groups.py` → `/old_code_documentation/blueprint_groups.py`
+
+### 2. **Code Removed**
+- Removed groups blueprint import from `app/app.py`
+- Removed groups blueprint registration from `register_blueprints()` function
+- Removed Group import from `app/blueprints/admin.py` (unused)
+- Removed Group import from `app/blueprints/api.py` (unused)
+- Commented out `/api/groups` endpoint in API
+
+### 3. **What Remained in Code**
+- **NOT removed:** Group model in `app/models/group.py`
+  - Kept for database backward compatibility
+  - No imports or references to it now
+  - Database table is orphaned but safe to keep
+  
+- **NOT removed:** `app/utils/group_player_management.py`
+  - Contains utility functions that may be referenced
+  - Can be archived later if confirmed unused
+
+## Summary
+
+✅ Groups feature is now completely **unavailable in the UI and app logic**
+✅ No routes, blueprints, or navigation links to groups
+✅ Application loads cleanly without groups
+✅ Database tables preserved for backward compatibility
+
+## Why Groups Was Removed
+
+1. **Functionality replaced by Playlists**
+   - Groups: "Organize content into categories"
+   - Playlists: "Organize content into collections assigned to players"
+
+2. **Never used in the current workflow**
+   - Dashboard: Players → Playlists → Content
+   - No mention of groups in any UI navigation
+   - Players have NO relationship to groups
+
+3. **Redundant architecture**
+   - Playlists provide superior functionality
+   - Players directly assign to playlists
+   - No need for intermediate grouping layer
+
+## Original Purpose (Deprecated)
+
+- Groups were designed to organize content
+- Could contain multiple content items
+- Players could be assigned to groups
+- **BUT:** Player model never implemented group relationship
+- **Result:** Feature was incomplete and unused
+
+## Current Workflow (Active) ✅
+
+```
+1. Create Playlist (organize content)
+2. Upload Media (add files)
+3. Add Content to Playlist (manage items)
+4. Add Player (register device)
+5. Assign Playlist to Player (connect directly)
+6. Players auto-download and display
+```
+
+## If Groups Data Exists
+
+The `group` and `group_content` database tables still exist but are orphaned:
+- No code references them
+- No migrations to drop them
+- Safe to keep or drop as needed
+
+## Future Cleanup
+
+When ready, can be removed completely:
+- `app/models/group.py` - Drop Group model
+- Database migrations to drop `group` and `group_content` tables
+- Remove utility functions from `app/utils/group_player_management.py`
+- Clean up any remaining imports
+
+## References
+
+- **Archive date:** January 17, 2026
+- **Related:** See `LEGACY_PLAYLIST_ROUTES.md` for similar cleanup
+- **Similar action:** Playlist templates also archived as legacy
+
+---
+
+**Status:** ✅ Complete - Groups feature successfully archived and removed from active codebase
+