[dylanjeffers]

Summary

Community feature request from Discord #feature-requests (soulcracker, Sep 26, 2026, with a follow-up from Hunter_Sound on Oct 6): when uploading a soundtrack album, let each track have its own genre and mood instead of one genre for the whole collection.

The plumbing already existed: CollectionTrackField carried an override flag ("currently unavailable thru the UI ... we will revisit this with a new expandable edit UI"), and combineMetadata in usePublishCollection only falls back to trackDetails.genre/mood when a track has none of its own. This adds the UI:

• Each track row in the album/playlist upload form gets a Custom genre & mood switch.
• Turning it on reveals Genre and Mood fields for that track, prefilled with the collection defaults. Turning it off clears them so the track falls back to the collection values at publish.
• Only genre and mood are copied when overriding. Tags stay null so the collection's tags still apply.
• Not shown when editing an existing collection (unchanged behavior there).
• SelectGenreField takes an optional datalistId so multiple genre fields on one page don't share a datalist id.

Note: genres are already freeform since #14424, so "Film / Movie" (also asked for in that thread) can be typed today.

Test plan

• vitest for CollectionTrackField: hidden by default, prefill on override, clear on un-override, not offered in edit mode
• tsc and eslint clean for packages/web
• Manually upload a 3-track album with one track overridden to a different genre and mood; confirm the published tracks' genres

Open questions

• Mobile upload isn't covered here. Want a matching mobile change?
• The original note mentions a "new expandable edit UI". This is a simple switch plus fields per track. Design may want something richer.

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: bcc094d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR