-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
So I'm not sure if this is just me, or if there are other early adopters who also experienced this issue but I'd really appreciate a way to resolve.
In the early days I imported my last.fm listens, which worked fine however every single listen is looking for a track entity, this means when you click on my early listens it takes you to a 404 page (as the links are design to point, correctly, to recording ID's).
Example:
https://listenbrainz.org/user/sound.and.vision/?min_ts=1205773648
If we look at the earliest imported listen under inspect we see the following data:
{
"inserted_at": 1591528410,
"listened_at": 1205773649,
"recording_msid": "d672c7e2-f0a1-41bc-98da-aa962c9217a1",
"track_metadata": {
"additional_info":Unknown macro: { "artist_msid"},
"artist_name": "Simple Plan",
"mbid_mapping":Unknown macro: { "recording_mbid"},
"release_name": "Still Not Getting Any",
"track_name": "Welcome to My Life"
},
"user_name": "sound.and.vision"
}
As mentioned recording_mbid is actually a track ID, not a recording ID.
Is there anyway to either:
- Update these "broken" listen items with the correct recording ID (at the moment I can choose "Link with MBz" but it makes no difference, as I think it requires 3 individual votes to work?)
- Remove all my listen data before 27th June 2018 (which is the last time I submitted any data to last.fm - https://www.last.fm/user/deadevil13)
If we choose the second method, do we know if I was to re-import that data if the issue would return or would we get the correct data submitted?