Add support for `works` and `movements` fields from OpenSubsonic API `Child` response

Feature requests
,
1

Feature description

Hi Tolriq,
following up on our discussion on the OpenSubsonic repository (Adds work/movement fields to Child response by j-hugo · Pull Request #212 · opensubsonic/open-subsonic-api · GitHub), I’d love to see support for the new works and movements fields on the Child response object in the OpenSubsonic API similar to your implementation in the tag parser in version 13.3.0 (Version 13.3.0 — Symfonium). Thank you, keep up the great work!

Problem solved

Classical music tags describing the work/composition and movement of a piece can currently only be displayed if fetched from a file via the tags parser and not if passed as fields from the OpenSubsonic API.

Brought benefits

Classical music sorting benefits via the OpenSubsonic API

Device type

All

Additional description and context

As discussed on the OpenSubsonic PR, this most probably means just using the first items of the new works and movements list.

I searched existing feature requests

on

2

No server actually support that yet :wink:

3

Haha, yeah I know, thats why I also put in a Feature Request at LMS [Feature Request] Add movements and works as extra fields to OpenSubsonic API Child response · Issue #834 · epoupon/lms · GitHub

I’m dreaming of my music setup supporting these tags :star_struck: . I can ping you as soon as LMS supports it (hopefully it will be implemented).