Ah ok, I think now I understood So if someone marked some releasegroup in my app as “owned”, and this releasegroup gets merged, it doesn’t appear in the releasegroups anymore retrieved by the release-group endpoint using the GET parameter “artist”. So hence, all I would have to do is to remove the “orphans” in my database linking to a release group with an id not being output by the releasegroup endpoint used as described above.
The only thing that is unsolved is that (at least to my knowledge) there’s no flag or something in the data that I get from the api when I lookup some merged release group by id. There’s no way to see in this info that I’m currently looking at a merged record, right? If this info was there, I could migrate my data to the new record.
What I would need is:
- record 1 and record 2 are duplicates
- record 1 is merged into record 2 -> record 2 is the primary one that survives, record 1 is the “old” merged one
- when looking up record 2 by id there’s a field called “isMergeOf” that contains the id of record 1
If this is not possible, would it be possible to add that functionality in the future?