Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Classical works detection broken for arrangements of other composers

Open
#1,673 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
perl
Domain
backend

Research direction

No files, tests, or entry points are named. Start by locating the classical Works detection algorithm and its tests, then trace how composer and arranger relationships are compared. Done means arrangements such as Mozart’s early piano concertos and the F. A. E. Sonata are detected as works without breaking existing cases.

Written by the indexing model from the issue text.

Description

The current algorithm for detection of classical "Works" insists that the composer field be identical for all movements in a work. This is not always the case, and it fails in quite a few cases, the most prominent being Mozart's first four piano concertos, which are arrangements of movements by other composers:

https://en.wikipedia.org/wiki/Piano_Concertos_Nos.1%E2%80%934(Mozart)

in which case any attempt to tag any of the complete a complete cycles of these always fails. For example the MusicBrainz release Murray Perahia playz Mozart, which has been mis-entered in MusicBrainz with multiple composer relationships including "Wolfgang Amadeus Mozart".

Ideally the audio files of these recordings ought to be tagged with COMPOSER="Hermann Raupach", for example and ARRANGER="Wolfgang Amadeus Mozart".

Another example is the F. A. E. sonata

I suggest that the "same composer" criterion be relaxed in two respects:

  1. If there are multiple composers listed, consecutive movements with the same composer at any position in the list should be considered part of the same work. This will allow tagging the work with a COMPOSER list containing the arranger.
  2. I suggest that tag ARRANGER be considered as equivalent to COMPOSER for the purposes of works detection only. This would further allow the tagging to better reflect reality.
Dominant language
Perl
Stars
1.8k
Forks
386
Avg merge
2d 7h
Merged PRs (30d)
14

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LMS-Community/slimserver

All issues in LMS-Community/slimserver

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.