Option to name imported custom playlists after the source playlist

[Piero-93]

Current behaviour

When importing a custom playlist (Spotify / Apple Music / ListenBrainz), the playlist created in the music system is named Custom-<hash> — in my case Custom-Ce6504a0. PLAYLISTNAME_FORMAT only affects generated playlists (Weekly-Exploration-…, Daily-Jams-…), so there is currently no way to influence the name of an imported one.

Why it matters

The hash is meaningful to Explo but not to the listener. In Navidrome the playlist ends up sitting next to hand-made ones, and there is no way to tell what it is without opening it.

Renaming it manually works, but presumably breaks the link Explo uses to recognise an already-imported source — so it is only safe for one-off imports, not for sources you plan to re-run.

Proposal

An option to use the source playlist's title for the created playlist, for example PLAYLISTNAME_SOURCE=true, defaulting to off so current behaviour is preserved. The result would be Rock Classics instead of Custom-Ce6504a0. Explo already has the source title in hand when it reads the playlist, so this should not require fetching anything extra.

If a stable identifier is needed for re-import detection, a combined form such as Custom-Rock Classics would also work — or the identity could be tracked in Explo's own config rather than in the display name.

Related

#218 — a source-derived name would also make the duplicate-name collision described there easier to reason about, since two playlists from different sources would no longer be forced to share a generated name.

Environment

Explo via Docker (ghcr.io/lumepart/explo:latest), music system: Navidrome through the Subsonic API.

[LumePart]

What source are you importing from? Explo falls back to ID, when the playlist name can not be retrieved from the cache, otherwise it uses the source name as the playlist name.

Do you have a custom-playlists.json in your config folder?

Does the Custom-.... name also display in Explo's UI?

[Piero-93]

Thanks for the quick reply — and apologies for the false alarm: this works as designed.

The playlist in Navidrome does take the source name. What I reported was the download subdirectory on disk (Custom-<id>, created because I have USE_SUBDIRECTORY=true): I checked while the run was still in progress, before the playlist itself had been created, and mistook the folder name for the playlist name.

custom-playlists.json is present and holds the source name as expected:

{
  "id": "custom-<id>",
  "name": "<source playlist name>",
  "source": "spotify",
  ...
}

Closing — no change needed.