Add project roadmap and architecture docs
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# Case Study: OneDrive Mac Migration
|
||||
|
||||
## Scenario
|
||||
|
||||
A large Serato DJ library was migrated from an older Mac to a newer Mac using OneDrive.
|
||||
|
||||
## Symptoms
|
||||
|
||||
- OneDrive client stuck syncing
|
||||
- Duplicate OneDrive folders
|
||||
- Thousands of files renamed with trailing ` 2`
|
||||
- Serato reported many tracks as missing
|
||||
- Some files existed on disk but still appeared orange in Serato
|
||||
|
||||
## Findings
|
||||
|
||||
- OneDrive sync state was rebuilt successfully
|
||||
- Thousands of orphaned filename conflicts were repaired
|
||||
- Some Serato references were stale database objects, not missing files
|
||||
- Smart/dynamic crates should be classified separately from static user crates
|
||||
|
||||
## Lessons
|
||||
|
||||
- Filesystem health and Serato database health are separate problems
|
||||
- Smart crates should not be treated the same as static crates
|
||||
- Repair tools must be read-only by default and generate a plan before changing anything
|
||||
Reference in New Issue
Block a user