What happens to the reviews belonging to merged duplicated entities (artists, events, release groups, etc)

CritiqueBrainz
1

hi there,

I’ve been exploring MetaBrainz projects for a while now, mostly listenbrainz and critiquebrainz, and I was wondering what happens to the reviews from entities that got merged because of being duplicated. Is there any logic to handle this cases?

Thanks in advance

1 Like
2

Hello!

I can’t tell for certain as I haven’t tried to review an entity before merging it, but I would assume the same process as for entity merging: given a review for a merged entity, it should redirect to the entity it was merged into.

But there’s nothing like testing :slight_smile:
I’ve written Review of ".38 Special" by mr_monkey - CritiqueBrainz
for an artist (.38 Special - MusicBrainz) being merged into another (38 Special - MusicBrainz). The edit will be closed in 45 minutes (at the time of writing), let’s see how it is handled.

6 Likes
3

And here are my findings:

I’ll call the merged artist “B” and the artist it was merged into (the only one accessible on MusicBrainz now) “A”

  1. Artist B does not appear in CritiqueBrainz search anymore, only artist A: Search results - CritiqueBrainz
  2. The review for artist B is still accessible on CB, and shows artist B’s name: Review of ".38 Special" by mr_monkey - CritiqueBrainz
  3. The page for artist B is still accessible on CB: .38 Special - CritiqueBrainz
  4. The review does not appear on CB on the page of artist A (no reviews found): 38 Special - CritiqueBrainz
  5. The review does not appear on MusicBrainz for the artist (under the ratings tab, “reviews” section reads “No one has reviewed […]”): 38 Special - Reviews - MusicBrainz

Of these, point 1 is expected and does what I would expect it to do.
All the other points do the wrong thing and looks like a bug.

I’ve created a ticket for it: https://tickets.metabrainz.org/browse/CB-463
Thanks for asking a pointed question :slight_smile:

Full disclosure: we don’t have anyone working full-time on CB in our small team so fixing this might take a while (I don’t imagine it would be a very simple fix…).

11 Likes
4

hi!! super, thank you for the detailed and quick response.