-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Store third-party identifiers #249
Comments
Since commit 1eaba88, maloja saves various MBID tags |
say whaaat. It looks like this is just for the listenbrainz endpoint, however. The native endpoint does not store extra fields and the scrobbles endpoint does not display them. |
We could add something like |
Would be cool to store spotify data too for cases like mine where I scrobble from spotify but have not used it to gather album art data yet and would like to later on |
#361 would fix this issue |
Implement storage of 3rd party IDs for tracks, artists, and albums. Common IDs:
Benefits of storage:
The IDs could be stored on a new table that is a simple KV store with a FK/discriminator for the entity it is associated with. The ID should be able to be submitted alongside a new scrobble (free lookup!) since some scrobble clients can do this. Additionally, it should be able to be edited/updated through an API endpoint.
The text was updated successfully, but these errors were encountered: