Remove emojis from all markdown docs, add consolidation plan

- Strip emojis from 47 markdown files across docs/, sql/, and root
- Add docs/DOCS_CONSOLIDATION_PLAN.md with plan to reduce 45 docs to 8
- Establish no-emoji rule for documentation going forward

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
cproudlock
2025-12-11 07:42:52 -05:00
parent 9fc3420716
commit e598f72616
42 changed files with 1105 additions and 937 deletions

View File

@@ -106,10 +106,10 @@ All views currently using the `pc` table will be updated to use `machines` with
### Phase 1: Infrastructure Setup (Scripts 01-04)
**Reversible**: Yes
1. Script 01: Create communications infrastructure
2. Script 02: Extend machines table
3. Script 03: Create PC machine types
4. Script 04: Create warranty infrastructure
1. Script 01: Create communications infrastructure
2. Script 02: Extend machines table
3. Script 03: Create PC machine types
4. Script 04: Create warranty infrastructure
**Production Deployment**: Run during maintenance window
**Estimated Time**: 15 minutes
@@ -118,10 +118,10 @@ All views currently using the `pc` table will be updated to use `machines` with
### Phase 2: Data Migration (Scripts 05-08)
**Reversible**: Yes (with backups)
5. Script 05: Migrate PC data to machines
6. Script 06: Migrate communication data
7. Script 07: Migrate warranty data
8. Script 08: Update relationship tables
5. Script 05: Migrate PC data to machines
6. Script 06: Migrate communication data
7. Script 07: Migrate warranty data
8. Script 08: Update relationship tables
**Production Deployment**: Run during maintenance window
**Estimated Time**: 30-45 minutes
@@ -130,11 +130,11 @@ All views currently using the `pc` table will be updated to use `machines` with
### Phase 3: Application Updates (Manual)
**Reversible**: Yes (via version control)
9. Update 19 database views
10. Create compatibility views
11. Update 10 ASP files (direct queries)
12. Update 30 ASP files (pc fields/views)
13. Test all functionality
9. Update 19 database views
10. Create compatibility views
11. Update 10 ASP files (direct queries)
12. Update 30 ASP files (pc fields/views)
13. Test all functionality
**Production Deployment**: Deploy with application
**Estimated Time**: 2-3 weeks development + testing
@@ -143,11 +143,11 @@ All views currently using the `pc` table will be updated to use `machines` with
### Phase 4: Cleanup (After 30 days)
**Reversible**: No - PERMANENT
14. Drop pc table
15. Drop pc_comm_config table
16. Drop pc_network_interfaces table
17. Drop compatibility views
18. Remove deprecated columns
14. Drop pc table
15. Drop pc_comm_config table
16. Drop pc_network_interfaces table
17. Drop compatibility views
18. Remove deprecated columns
**Production Deployment**: Final cleanup
**Estimated Time**: 15 minutes
@@ -186,37 +186,37 @@ All views currently using the `pc` table will be updated to use `machines` with
### Before Refactoring
**Data Model**:
- Machines and PCs tracked separately
- Warranty data scattered across PC records
- Communication data in PC-specific tables
- Multiple machines types systems (machines.machinetypeid, pc.pctypeid)
- Rigid communication tracking
- No warranty history
- Limited to one warranty per PC
- Machines and PCs tracked separately
- Warranty data scattered across PC records
- Communication data in PC-specific tables
- Multiple machines types systems (machines.machinetypeid, pc.pctypeid)
- Rigid communication tracking
- No warranty history
- Limited to one warranty per PC
**Code**:
- Duplicate logic for machines vs PCs
- Complex joins across pc/machines
- PC-specific ASP files
- Warranty tracking only for PCs
- Duplicate logic for machines vs PCs
- Complex joins across pc/machines
- PC-specific ASP files
- Warranty tracking only for PCs
### After Refactoring
**Data Model**:
- Unified machine tracking (all assets)
- Professional warranty management
- Generic communication infrastructure
- Single machine type system
- Extensible for new communication types
- Complete warranty audit trail
- Multiple warranties per machine
- Unified machine tracking (all assets)
- Professional warranty management
- Generic communication infrastructure
- Single machine type system
- Extensible for new communication types
- Complete warranty audit trail
- Multiple warranties per machine
**Code**:
- Single codebase for all machines
- Simpler queries
- Unified ASP files
- Warranty tracking for ALL machines
- Better reporting capabilities
- Single codebase for all machines
- Simpler queries
- Unified ASP files
- Warranty tracking for ALL machines
- Better reporting capabilities
---
@@ -237,15 +237,15 @@ All views currently using the `pc` table will be updated to use `machines` with
| Phase | Duration | Resources |
|-------|----------|-----------|
| Design & Review | 1-2 days | COMPLETE |
| SQL Script Development | 3-5 days | In Progress |
| Dev Environment Testing | 3-5 days | Pending |
| ASP File Updates | 5-7 days | Pending |
| Integration Testing | 3-5 days | Pending |
| User Acceptance Testing | 2-3 days | Pending |
| Production Deployment | 1 day | Pending |
| Monitoring Period | 30 days | Pending |
| Final Cleanup | 1 day | Pending |
| Design & Review | 1-2 days | COMPLETE |
| SQL Script Development | 3-5 days | In Progress |
| Dev Environment Testing | 3-5 days | Pending |
| ASP File Updates | 5-7 days | Pending |
| Integration Testing | 3-5 days | Pending |
| User Acceptance Testing | 2-3 days | Pending |
| Production Deployment | 1 day | Pending |
| Monitoring Period | 30 days | Pending |
| Final Cleanup | 1 day | Pending |
| **TOTAL** | **20-35 days** | |
---
@@ -348,7 +348,7 @@ All views currently using the `pc` table will be updated to use `machines` with
---
**Status**: DESIGN PHASE COMPLETE
**Status**: DESIGN PHASE COMPLETE
**Next Step**: Create migration scripts (scripts 05-08)
**Target Deployment**: TBD