Song mapping to incorrect release

ListenBrainz
1

New to the community, so apologies if this is a repeat issue.

I am importing my listening data via last.fm. Sometimes tracks are not mapping to correct release. I have noticed that if a recording appears on multiple releases, it may choose a release that is different to the intended one. This could be an album over a compilation. For example:

{
  "inserted_at": 1777913341,
  "listened_at": 1777913038,
  "recording_msid": "0d271df3-b250-4b9a-9fd4-026ae9102d40",
  "track_metadata": {
    "additional_info": {
      "lastfm_artist_mbid": "b904d624-9e05-4398-8f4f-88fbcf022f79",
      "lastfm_release_mbid": "0aad7380-0b5c-4bc7-bac4-7317508b3cb6",
      "lastfm_track_mbid": "ce69b3c8-a0cf-4e2e-8309-4bfb7f9af87f",
      "recording_msid": "0d271df3-b250-4b9a-9fd4-026ae9102d40",
      "submission_client": "ListenBrainz lastfm importer v2"
    },
    "artist_name": "Barry White",
    "mbid_mapping": {
      "artist_mbids": [
        "b904d624-9e05-4398-8f4f-88fbcf022f79"
      ],
      "artists": [
        {
          "artist_credit_name": "Barry White",
          "artist_mbid": "b904d624-9e05-4398-8f4f-88fbcf022f79",
          "join_phrase": ""
        }
      ],
      "caa_id": 7948790095,
      "caa_release_mbid": "a52d88a4-103d-4a94-b1f9-8a54931545f7",
      "recording_mbid": "4bc6b7ae-5164-4484-a44e-22069435973f",
      "recording_name": "You’re the First, the Last, My Everything",
      "release_mbid": "84a41e38-2502-4bf6-97b6-c92899ed2bda"
    },
    "release_name": "The Ultimate Collection",
    "track_name": "You're the First, the Last, My Everything"
  },
  "user_name": "tharman"
}

Last.fm has the release name as “The Ultimate Collection”. When it comes to the API to map the recording, the release is Can’t Get Enough.

Can the API be configured to update release_mbid?

2

Hi!
Indeed currently we select the first album appearance of the recording in question.

We’re working on improvements to the automatic mapping that includes better album matching, but unfortunately the person behind the project has passed away unexpectedly.
So while this improvement will be deployed this year we are not yet sure exactly when.