beetbox / beetbox/beets

parentwork: Heuristic or manual selection when there are multiple parents

Open
#4,001 5 comments 0 reactions 0 assignees View on GitHub
feature parentwork
Dominant language
Python
Stars
15.7k
Forks
2.1k
Avg merge
4d 21h
Merged PRs (30d)
31

Description

I have [this album](https://beta.musicbrainz.org/release/dd440e84-add3-4f5b-b762-602d8df1c643) in my collection. On CD 4 the tracks 4.3 to 4.8 get their parentwork as [Fantasia](https://beta.musicbrainz.org/work/74e65a9e-608d-4097-b238-c1bb6536ce7c), instead of the proper [ballet suite](https://beta.musicbrainz.org/work/fd337fdc-a511-4830-8ee7-09d4ada32a54). I'm not sure if there's a good way to fix this either in the code or in the data in musicbrainz. One thought I had was to choose the work with the earliest composition date, but that might not always work (especially if the dates are not specified), and might be difficult to implement, including needing to get more data than we already do.

If anyone has any other ideas about how to work around or solve this problem, that would be great.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.