At BYU, files pile up in more places than anyone expects: research data, lecture recordings, publications and photo libraries, copied across computers, external drives, cloud storage and old backups. For individual faculty and staff, the problem is personal - finding the right file without spending hours organizing everything by hand.
For Dr. Daryl Lee, Professor of French, eight years of academic lectures, archival recordings, and iTunes music tracks had accumulated into tons of duplicates. The problem was compounded by the fact that track names weren’t identical: some had track numbers prepended, others had been ripped as WAV while an AAC copy already existed, and bitrates varied. Standard macOS searches were helpless because filenames didn’t match - and manual inspection would have meant listening to thousands of clips one by one.
Meanwhile, Administrative Assistant Traci Wright was wrestling with a visual catastrophe. Over years of documenting university banquets, academic conferences, visiting scholar summits, and commencement ceremonies, her Apple Photos library had swollen past 30,000 photos. Folders had been imported and re-imported whenever staff swapped MacBooks, creating duplicate album hierarchies on top of the duplicate images themselves.
Two very different collections, and the same four problems underneath. Key pain points included:
No iTunes or Photos library support
Standard macOS duplicate finders compared exact filenames and leaned on MD5 hashes. They had no support for iTunes or Apple Photos, so they stayed blind to audio files whose track numbers or bitrate tags differed but whose sound was identical.
Weeks of manual auditing
Eye-balling 30,000 event photos or listening to thousands of lecture recordings by hand would have cost weeks of faculty and staff time - work that had nothing to do with teaching or research.
Fear of losing master recordings
Generic Mac cleaner utilities could break Apple Photos SQLite catalogs or permanently delete master research recordings, with no safe restore path if the wrong copy went.
Compounding campus storage bloat
Duplicate research branches were synced to departmental shared servers without anyone noticing, inflating backup and storage costs across the university.
Across both collections, the question turned out to be the same: how do you tell which copy is the one worth keeping - without opening every file to find out?