Song versioning / arrangements #1

Open
opened 2026-07-11 21:02:32 +00:00 by GKaszewski · 0 comments
Owner

Support multiple versions of the same song — different chord arrangements, keys, or interpretations.

Why: UG often has multiple versions of the same song (different users' transcriptions, simplified vs. full chords, different keys). Right now each import is a standalone song with no relation to other versions.

Open questions to grill on:

  • Data model: separate songs linked by a parent ID? A versions array inside a song? A separate arrangements table?
  • UI: how to switch between versions on the song detail page?
  • Should importing a second version of an existing song auto-detect and link them (by title+artist match)?
  • Version labels: "Original", "Simplified", "Capo 3 version", user-defined?
Support multiple versions of the same song — different chord arrangements, keys, or interpretations. **Why:** UG often has multiple versions of the same song (different users' transcriptions, simplified vs. full chords, different keys). Right now each import is a standalone song with no relation to other versions. **Open questions to grill on:** - Data model: separate songs linked by a parent ID? A `versions` array inside a song? A separate `arrangements` table? - UI: how to switch between versions on the song detail page? - Should importing a second version of an existing song auto-detect and link them (by title+artist match)? - Version labels: "Original", "Simplified", "Capo 3 version", user-defined?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GKaszewski/pocket-chords#1