ge-aerospace/shopdb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove emojis from all markdown docs, add consolidation plan

Browse Source 
- 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
Download Patch File Download Diff File Expand all files Collapse all files

86
docs/DATABASE_MIGRATION_FINAL_DESIGN.md
View File

@@ -17,10 +17,10 @@ This document outlines the finalized database migration plan that:
6. Implements machine relationships tracking (dualpath, controller associations)
**Key Design Principles:**
- ✅ Simplicity over complexity
- ✅ Generic/flexible structures (address field in communications)
- ✅ Leverage existing tables (vendors for third-party management)
- ✅ Minimal columns (remove unnecessary audit fields)
- Simplicity over complexity
- Generic/flexible structures (address field in communications)
- Leverage existing tables (vendors for third-party management)
- Minimal columns (remove unnecessary audit fields)
---
@@ -374,11 +374,11 @@ ADD CONSTRAINT fk_machines_machinestatusid FOREIGN KEY (machinestatusid) REFEREN
| 21 | dateadded | DATETIME | **NEW** - Date added |
**REMOVED FIELDS (after migration):**
- ❌ `pctypeid` - No longer needed (use machinetypeid)
- ❌ `isvnc` - Tracked in communications table
- ❌ `requires_manual_machine_config` - Not needed
- ❌ `ipaddress1` - Migrated to communications
- ❌ `ipaddress2` - Migrated to communications
- `pctypeid` - No longer needed (use machinetypeid)
- `isvnc` - Tracked in communications table
- `requires_manual_machine_config` - Not needed
- `ipaddress1` - Migrated to communications
- `ipaddress2` - Migrated to communications
---
@@ -586,35 +586,35 @@ WHERE configtype = 'IP';
## KEY DESIGN DECISIONS
### ✅ Generic `address` Field
### Generic `address` Field
**Decision:** Use single `address` field in communications instead of separate ipaddress/portname/etc fields.
**Benefit:** Flexible, extensible, no unused columns per row.
### ✅ Simplified Warranties
### Simplified Warranties
**Decision:** Just warrantyname and enddate. No complex vendor/type/cost tracking.
**Benefit:** Easy to use, easy to maintain, covers 90% of use cases.
### ✅ Liaison in BusinessUnits
### Liaison in BusinessUnits
**Decision:** Add liaison fields directly to businessunits instead of separate table.
**Benefit:** Simpler structure, one less JOIN, appropriate granularity.
### ✅ Unified Machine Types
### Unified Machine Types
**Decision:** Add PC types as entries in machinetypes instead of separate pctype system.
**Benefit:** Single source of truth, eliminates pctypeid column.
### ✅ Vendor FK for Third-Party Management
### Vendor FK for Third-Party Management
**Decision:** Use vendorid FK in compliance.managedbyvendorid instead of text field.
**Benefit:** Normalized, prevents typos, enables vendor-based queries.
### ✅ JSON Settings Field
### JSON Settings Field
**Decision:** Use JSON for type-specific config in communications.
**Benefit:** Flexible, no table bloat, easy to extend.
### ✅ Minimal Audit Fields
### Minimal Audit Fields
**Decision:** Removed dateadded/lastupdated from warranties and communications.
**Benefit:** Simpler, only track audit fields where truly needed.
### ✅ Machine Relationships Table
### Machine Relationships Table
**Decision:** Generic relationship table instead of specific PC-to-machine or dualpath-only tables.
**Benefit:** Flexible, extensible, supports bidirectional and directional relationships, future-proof for clusters/backup systems.
@@ -625,14 +625,14 @@ WHERE configtype = 'IP';
### Phase 1: Infrastructure Setup (Scripts 01-08)
**Status:** Ready to create SQL scripts
1. ✅ Script 01: Create communications infrastructure (comstypes, communications)
2. ✅ Script 02: Extend machines table (+9 columns)
3. ✅ Script 03: Create PC machine types in machinetypes
4. ✅ Script 04: Create warranty infrastructure (warranties)
5. ✅ Script 05: Create compliance infrastructure (compliance, compliancescans)
6. ✅ Script 06: Extend businessunits table (+2 liaison fields)
7. ✅ Script 07: Rename pcstatus to machinestatus
8. ✅ Script 08: Create machine relationships infrastructure (relationshiptypes, machinerelationships)
1. Script 01: Create communications infrastructure (comstypes, communications)
2. Script 02: Extend machines table (+9 columns)
3. Script 03: Create PC machine types in machinetypes
4. Script 04: Create warranty infrastructure (warranties)
5. Script 05: Create compliance infrastructure (compliance, compliancescans)
6. Script 06: Extend businessunits table (+2 liaison fields)
7. Script 07: Rename pcstatus to machinestatus
8. Script 08: Create machine relationships infrastructure (relationshiptypes, machinerelationships)
**Estimated Time:** 25 minutes
**Reversible:** Yes (rollback scripts provided)
@@ -640,10 +640,10 @@ WHERE configtype = 'IP';
### Phase 2: Data Migration (Scripts 09-12)
**Status:** Design complete, scripts pending
1. ⏳ Script 09: Migrate PC data to machines
2. ⏳ Script 10: Migrate communication data (ipaddress1/2, pc_network_interfaces, pc_comm_config)
3. ⏳ Script 11: Migrate warranty data
4. ⏳ Script 12: Populate machine relationships (dualpath, controller associations)
1. Script 09: Migrate PC data to machines
2. Script 10: Migrate communication data (ipaddress1/2, pc_network_interfaces, pc_comm_config)
3. Script 11: Migrate warranty data
4. Script 12: Populate machine relationships (dualpath, controller associations)
**Estimated Time:** 30-45 minutes
**Reversible:** Yes (with backups)
@@ -651,32 +651,32 @@ WHERE configtype = 'IP';
### Phase 3: Application Updates
**Status:** Pending
1. ⏳ Update 19 database views
2. ⏳ Create compatibility views
3. ⏳ Update ASP files
4. ⏳ Test all functionality
1. Update 19 database views
2. Create compatibility views
3. Update ASP files
4. Test all functionality
**Estimated Time:** 2-3 weeks
### Phase 4: Cleanup (After 30 days)
**Status:** Pending
1. ⏳ Drop pc table
2. ⏳ Drop pc_comm_config, pc_network_interfaces
3. ⏳ Drop pctype table
4. ⏳ Drop compatibility views
5. ⏳ Drop machines.ipaddress1, machines.ipaddress2
1. Drop pc table
2. Drop pc_comm_config, pc_network_interfaces
3. Drop pctype table
4. Drop compatibility views
5. Drop machines.ipaddress1, machines.ipaddress2
---
## RISK MITIGATION
**Critical Success Factors:**
- ✅ Full database backup before any changes
- ✅ Test all scripts on dev environment first
- ✅ Rollback scripts for Phase 1
- ✅ 30-day verification period before dropping old tables
- ✅ Compatibility views to support gradual application migration
- Full database backup before any changes
- Test all scripts on dev environment first
- Rollback scripts for Phase 1
- 30-day verification period before dropping old tables
- Compatibility views to support gradual application migration
**Rollback Strategy:**
- Phase 1: Run rollback scripts (drop new tables, revert ALTER TABLEs)