Files
claudetools/.claude/memory/feedback_drive_letter_mapping.md
Howard Enos abbc185e02 sync: auto-sync from HOWARD-HOME at 2026-06-10 13:25:54
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-10 13:25:54
2026-06-10 13:26:10 -07:00

1.6 KiB

name, description, type
name description type
Drive-letter mapping convention — pick the main letter first When setting up mapped network drives, decide the main/primary drive letter first (the principal share everyone uses gets a consistent main letter), then assign secondary/smaller shares their own letters. Don't retroactively normalize existing maps unless asked. feedback

When provisioning mapped network drives for users, the order is: pick the MAIN drive letter first — the primary share everyone works out of gets one consistent letter across all users — then assign the smaller/secondary mapped drives their own letters underneath that.

Why: Howard's standing preference (2026-06-10). A consistent main letter means every user's primary share is at the same place, so support and instructions ("it's on your Y: drive") are uniform; secondary shares are clearly subordinate.

How to apply:

  • New drive-mapping work: confirm the main letter with Howard, map the primary share there for all users, then map any secondary ("smaller") shares.
  • Do NOT retroactively renumber existing maps to fit the convention unless explicitly asked. (2026-06-10: Howard chose to leave the existing Cascades AcctDept maps as-is — Lauren X:, Chris Y:, Zachary Y: — and apply this only going forward.)
  • Watch for letter collisions on a given machine (e.g. the main letter already in use); surface the conflict rather than silently picking a different letter.

Related: Cascades scan-to-folder shares use feedback_cascades_scan_account; current Cascades state project_cascades.